Windows 10: Bsod "whea_uncorrectable_error (124)"

  1.    27 Dec 2017 #1

    Bsod "whea_uncorrectable_error (124)"


    Hi, I'm having a hard time figuring out the source of my blue screen on my Gigabyte Aero 14. The bluescreens happen mostly on battery mode, for exemple when I startup the computer, when I unplug the power cord, or when I wake up the computer from sleepmode. In some rare cases it had happened randomly when using the computer plugged in (but most cases when unplugged).
    I'm very happy with this computer otherwise so the situation start to bum me out. I think the problem is probably driver related because I feel like I never had these blue screens before I decided one night to update all of my drivers at once (even the bios) but I cannot find the culprit.
    By the way I don't get any blue screen in windows safe mode, even on battery. I also ran the Intel Processor Diagnostic Tool and everything passed.
    LAPTOP-GREG-27-Dec-17_165555_77.zip
    I've attached the diagnostic to my post and added to the zip some crash dumps I analyzed with WinDbg before running the forum diagnostic tool.

    Thanks to anyone who would take time to look into my problem.
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,218
    Windows 10 Pro X64 17134.191
       27 Dec 2017 #2

    Only two dumps in the zip file, should be more. There are 22 WHEA 124 entries in Event log. Are you running a program like CCleaner to cleanup your hard drive? If so, please stop until this is resolved.

    Both dumps indicate a hardware CPU failure:
    Code:
    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: ffffa08986814028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f60017c0, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040150, Low order 32-bits of the MCi_STATUS value.
    Code:
    !errrec  ffffa08986814028
    ===============================================================================
    Common Platform Error Record @ ffffa08986814028
    -------------------------------------------------------------------------------
    Record Id     : 01d37f2a7a4ed1ff
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/27/2017 15:54:16 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffa089868140a8
    Section       @ ffffa08986814180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Instruction Execute
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x00000000000906e9
    Processor ID  : 0x0000000000000005
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffa089868140f0
    Section       @ ffffa08986814240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000005
    CPU Id        : e9 06 09 00 00 08 10 05 - bf fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ ffffa08986814240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffa08986814138
    Section       @ ffffa089868142c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : ICACHEL0_IRD_ERR (Proc 5 Bank 0)
      Status      : 0xf60017c000040150
      Address     : 0x00007ffd6ef7db20
      Misc.       : 0x0000000000000000
    Event log also shows hardware failure:
    Code:
    Event[16431]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2017-12-27T16:55:46.832
      Event ID: 19
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: AUTORITE NT\SERVICE LOCAL
      Computer: LAPTOP-GREG
      Description: 
    A corrected hardware error has occurred.
    
    Reported by component: Processor Core
    Error Source: Corrected Machine Check
    Error Type: Cache Hierarchy Error
    Processor APIC ID: 4
    
    The details view of this entry contains further information.
    
    Event[16432]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2017-12-27T16:56:46.825
      Event ID: 19
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: AUTORITE NT\SERVICE LOCAL
      Computer: LAPTOP-GREG
      Description: 
    A corrected hardware error has occurred.
    
    Reported by component: Processor Core
    Error Source: Corrected Machine Check
    Error Type: Cache Hierarchy Error
    Processor APIC ID: 4
    
    The details view of this entry contains further information.
    It's possible this is caused by a device driver but unlikely. You can try setting up Driver Verifier as follows to see what it shows:

    ===================================================
    Driver Verifier
    is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
    Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

    Driver Verifier - Enable and Disable in Windows 10

    Pay close attention to PART TWO and make sure the correct boxes are checked.

    Warning:
    It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

    Always create a Restore Point prior to enabling Driver Verifier.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun dm_log_collector and upload the resulting zip file.
    ===================================================

    If this doesn't show anything then you need to start thinking about replacing the motherboard since it's impossible to replace the CPU on a laptop board.
      My ComputersSystem Spec

  3.    27 Dec 2017 #3

    Thanks for the reply. Yeah some dumps got removed by CCleaner, I only have an SSD so all these dump files can take end up taking a lot of space. I'm going to look into the driver verifier, and guess I'll have to contact Gigabyte if I don't find anything wrong.
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,218
    Windows 10 Pro X64 17134.191
       27 Dec 2017 #4

    You have a 500GB SSD though, the dumps don't take up that much room, a little over 1MB per. Change your CCleaner setup to not delete minidumps then delete them manually later.

    Click image for larger version. 

Name:	CCleaner.jpg 
Views:	1 
Size:	49.9 KB 
ID:	169756

    If the laptop is still under warranty then definitely start the RMA process.
      My ComputersSystem Spec


 

Related Threads
The following was displayed in 'Automatic Repair' on startup: "The operating system couldn't be loaded because a critical system driver is missing or contains errors" "amdkmafd.sys" "0xc000007b" I had installed the new windows 10 anniversary...
Hi I have recently updated to the creator version My files end up in unintended destinations. When I click in the documents tab in the sidebar of the documents screen, it takes me to a “Documents” folder that appears in “One Drive” group. Any...
One of our Win10 laptops has a context menu with "Properties" that uses shortcut key "r". The other uses key "o" which conflicts with "open". I have no idea how it got corrupted. Suggested locations in the registry for context menu doesn't list it....
Hi, guys I got a problem with constantly repeating BSOD mostly because these two reasons in topic. I have checked online and did everything for preventing this from happening. And it doesnt worked :/ The other things I have done are checking...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:11.
Find Us