locked
Odd Bug Check Event ID 18 - BCCode 124; Can anyone help? RRS feed

  • Question

  • Hello,

    I understand that each bug check is different even if the codes are the same due to different real world problems but I'm stumped, granted I don't know too much. Hence I am here. I'm getting a BSOD every time I let my computer idle for 10 and half minutes. Like clockwork it will blue screen. However, whenever I am using it, it won't blue screen at all. I have even used my computer nonstop for 13 hours and no BSOD, leave it for 10 minutes and you guessed it, blue screen. 

    So here's the info...

    Problem signature:

      Problem Event Name:                        BlueScreen

      OS Version:                                          6.1.7601.2.1.0.768.3

      Locale ID:                                             1033

    Additional information about the problem:

      BCCode:                                               124

      BCP1:                                                    0000000000000000

      BCP2:                                                    FFFFFA800CDCC028

      BCP3:                                                    00000000BF800000

      BCP4:                                                    0000000000200401

      OS Version:                                          6_1_7601

      Service Pack:                                       1_0

      Product:                                               768_1

    Not too helpful right? Alright, so I have updated the BIOS to latest version, all drivers are up to date, everything is as up to date as I can get it as (as far as I can perceive). I am still getting bug checks when it idles for 10 minutes. So I do a bug check analysis...

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa800ccf7028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000200401, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

    PROCESS_NAME:  ubssrv_oc_only

    CURRENT_IRQL:  f

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    STACK_TEXT:  
    fffff880`033dfa58 fffff800`0302da3b : 00000000`00000124 00000000`00000000 fffffa80`0ccf7028 00000000`bf800000 : nt!KeBugCheckEx
    fffff880`033dfa60 fffff800`031f0463 : 00000000`00000001 fffffa80`0c484ea0 00000000`00000000 fffffa80`0c484ef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`033dfaa0 fffff800`0302d700 : 00000000`00000728 fffffa80`0c484ea0 fffff880`033dfe30 fffff880`033dfe00 : nt!WheaReportHwError+0x263
    fffff880`033dfb00 fffff800`0302d052 : fffffa80`0c484ea0 fffff880`033dfe30 fffffa80`0c484ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`033dfc50 fffff800`0302cf0d : 00000000`00000004 00000000`00000001 fffff880`033dfeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`033dfc90 fffff800`03020e88 : 00000000`00000000 00000000`00000010 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`033dfcc0 fffff800`030d84ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`033dfcf0 fffff800`030d8313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`033dfe30 fffff800`030d07b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`09e9f638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0x208


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: GenuineIntel

    IMAGE_NAME:  GenuineIntel

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    IMAGE_VERSION:  

    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae

    FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}

    Followup: MachineOwner

    I should also mention that I checked hard drive for bad sectors and ram for any errors using 10 passes with Memcheck86 and nothing bad to report. If anyone can help me out with this that would be great! I can provide as many minidump files as you need, if need be. 

    Note: I have previously tried resolving this issue and rather than GenuineIntel being the probable cause, it used to show netio.sys as the culprit. However, I tried using a registry cleaner and of course it wiped all previous minidumps that showed netio.sys as probable source of error and now it just shows GenuineIntel. Interesting? Sorry I can't provide those "previous" minidump files accusing netio.sys, because the registry cleaner wiped them, but I can provide current minidump files. 

    Thanks for any help!!

    Saturday, September 20, 2014 2:42 AM

Answers

  • Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    -- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.

    2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows' default method of zipping folders.

    Compress and uncompress files (zip files).

    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need to allow the system to crash once again to generate a crash dump.

    3. Upload the .ZIP containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply.

    Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is the best choice. Do note that Kernel Memory Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link - Share files and folders and change permissions and view 'Get a link'.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Michael_LS Friday, October 10, 2014 4:38 AM
    Saturday, September 20, 2014 3:45 AM
  • Thanks.

    WHEA_UNCORRECTABLE_ERROR (124)

    A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

    If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800ccf7138
    Section       @ fffffa800ccf72c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal unclassified (Proc 3 Bank 1)
      Status      : 0xbf80000000200401
      Address     : 0x00000000fee00040
      Misc.       : 0x0000000000000086
    

    It's an internal unclassified error, which implies it's not publicly documented whatsoever. You'd need to get in contact with an engineer internally at Intel.

    In any case, we can still get to the bottom of it ourselves.

    ---------------------------------

    1. AppleCharger.sys is listed and loaded which is the GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

    Very troublesome software, so please uninstall ASAP! Please also uninstall all Gigabyte software as it's crapware and will cause problems (Easy Tune for example).

    2. Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes as it's likely causing conflicts:

    Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    ---------------------------------

    If the above fails, there is only so much you can do with a bug check like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

    1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

    2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

    3. Ensure your BIOS is up to date.

    4. If all of the above fail, the only left to do is replace your processor as it is faulty.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Icemonkey01 Saturday, September 20, 2014 4:27 PM
    Saturday, September 20, 2014 5:28 AM

All replies

  • Hi,

    In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where .DMP files are located, here's how to get to them:

    1. Navigate to the %systemroot%\Minidump folder.

    -- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.

    2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows' default method of zipping folders.

    Compress and uncompress files (zip files).

    Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need to allow the system to crash once again to generate a crash dump.

    3. Upload the .ZIP containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply.

    Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.

    4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is the best choice. Do note that Kernel Memory Dumps are much larger in size due to containing much more info, which is why I mentioned upload speed, etc.

    If you are going to use Onedrive but don't know how to upload to it, please visit the following:

    Upload photos and files to Onedrive.

    After doing that, to learn how to share the link to the file if you are unaware, please visit the following link - Share files and folders and change permissions and view 'Get a link'.

    If your computer is not generating .DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.

    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.

    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log'.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    4. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Michael_LS Friday, October 10, 2014 4:38 AM
    Saturday, September 20, 2014 3:45 AM
  • I appreciate your help! I created a OneDrive file containing the minidumps;

    https://onedrive.live.com/redir?resid=C8E6474C0B77A377%21106

    I will go ahead and set my computer to generate a Kernal Memory Dump and provide a link to the zipped-up file for that as well, as soon as I am able to get one (shouldn't be too long). 

    Edit: I uploaded the zipped MEMORY.DMP file that I got. I'm fairly certain the link above will provide the same location for this file, but I'll just add the new link here:

    https://onedrive.live.com/redir?resid=C8E6474C0B77A377%21107

    • Edited by Icemonkey01 Saturday, September 20, 2014 5:27 AM Update
    Saturday, September 20, 2014 5:00 AM
  • Thanks.

    WHEA_UNCORRECTABLE_ERROR (124)

    A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

    If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800ccf7138
    Section       @ fffffa800ccf72c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : Internal unclassified (Proc 3 Bank 1)
      Status      : 0xbf80000000200401
      Address     : 0x00000000fee00040
      Misc.       : 0x0000000000000086
    

    It's an internal unclassified error, which implies it's not publicly documented whatsoever. You'd need to get in contact with an engineer internally at Intel.

    In any case, we can still get to the bottom of it ourselves.

    ---------------------------------

    1. AppleCharger.sys is listed and loaded which is the GIGABYTE On/Off Charge driver. See here for details - http://www.gigabyte.us/MicroSite/185/on-off-charge.htm

    Very troublesome software, so please uninstall ASAP! Please also uninstall all Gigabyte software as it's crapware and will cause problems (Easy Tune for example).

    2. Remove and replace Norton with Microsoft Security Essentials for temporary troubleshooting purposes as it's likely causing conflicts:

    Norton removal - https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us;jsessionid=841A6D40BA6872C47697C6C6B19C8E11.4?entsrc=redirect_pubweb&pvid=f-home

    MSE -  http://windows.microsoft.com/en-us/windows/security-essentials-download

    ---------------------------------

    If the above fails, there is only so much you can do with a bug check like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

    1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - http://www.piriform.com/speccy

    2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

    3. Ensure your BIOS is up to date.

    4. If all of the above fail, the only left to do is replace your processor as it is faulty.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    • Marked as answer by Icemonkey01 Saturday, September 20, 2014 4:27 PM
    Saturday, September 20, 2014 5:28 AM
  • Alright, so here is a list of what I have done for clarification:

    • Removed the AppleCharger.sys file 
    • Removed Easy Tune, then removed ALL Gigabyte software
    • Removed Norton and replaced it with Microsoft Security Essentials

    I will now let my computer idle for a while and see if it blue screens again. If it does I'll pack the new minidump and Memory dump files onto Onedrive for checking. If it doesn't blue screen I'll be sure to let you know and thank you!

    Edit: I have let my computer sit idle for 30 minutes now with no bug checks, no problems. Truly amazing considering I couldn't leave it alone for more than 10 minutes before. It seems that the problem has been fixed. I'll let it run idle for much longer later today to see if anything goes wrong.

    I appreciate your help Patrick! Thank you!

    • Edited by Icemonkey01 Saturday, September 20, 2014 4:27 PM Update
    Saturday, September 20, 2014 3:47 PM
  • My pleasure, glad to hear.

    Regards,

    Patrick

    “Be kind whenever possible. It is always possible.” - Dalai Lama

    Saturday, September 20, 2014 9:37 PM