Windows 8 and 8.1 Forums

WHEA_uncorrectable_error BSOD after update to W8.1

  1. #1

    Posts : 1
    Windows 8.1

    WHEA_uncorrectable_error BSOD after update to W8.1

    Since my update to windows 8.1 I receive BSOD when I stress my system (BOINC-calculations). After some seconds/minutes the BSOD appears. Some extra information: recently I moved, so the computer was transported. From then on I also got problems with windows 7. Updating to windows 8 didn't change anything. What could be wrong?

      My System SpecsSystem Spec

  2. #2

    Posts : 660
    windows 8.1

    All your 11 dumpfiles have the same BSOD BugCheck 124, {0, ffffe0000173d028, b265c000, 175}WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred.
    Probably caused by : AuthenticAMD.

    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, ffffe0000173d028, b265c000, 175}
    Probably caused by : AuthenticAMD
    Followup: MachineOwner
    2: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    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.
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0000173d028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b265c000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000175, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    BUGCHECK_STR:  0x124_AuthenticAMD
    PROCESS_NAME:  primegrid_cllr
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    ffffd000`20649c68 fffff800`9e838c9f : 00000000`00000124 00000000`00000000 ffffe000`0173d028 00000000`b265c000 : nt!KeBugCheckEx
    ffffd000`20649c70 fffff800`9ea29d41 : 00000000`00000001 ffffe000`0019fea0 ffffe000`0019fea0 ffffe000`0173d028 : hal!HalBugCheckSystem+0xcf
    ffffd000`20649cb0 fffff800`9e83912c : 00000000`00000728 00000000`00000002 ffffd000`2064a070 00000000`00000000 : nt!WheaReportHwError+0x22d
    ffffd000`20649d10 fffff800`9e839499 : ffffe000`00000010 ffffe000`0019fea0 ffffd000`20649eb8 ffffe000`0019fea0 : hal!HalpMcaReportError+0x50
    ffffd000`20649e60 fffff800`9e839384 : ffffe000`0019f990 00000000`00000001 00000000`00000002 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
    ffffd000`20649eb0 fffff800`9e839758 : ffffe000`0019f990 ffffd000`2064a0f0 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    ffffd000`20649ef0 fffff800`9e9ca7bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
    ffffd000`20649f20 fffff800`9e9ca571 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd000`2064a060 00007ff6`4e7cc11c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    00000000`00841fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`4e7cc11c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: AuthenticAMD
    IMAGE_NAME:  AuthenticAMD
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache
    FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}
    Followup: MachineOwner
    The errrrec command gave this result
    Section 0     : Processor Generic
    Descriptor    @ ffffe0000173d0a8
    Section       @ ffffe0000173d180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Generic
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f53
    Processor ID  : 0x0000000000000002
    Section 1     : x86/x64 Processor Specific
    Descriptor    @ ffffe0000173d0f0
    Section       @ ffffe0000173d240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000002
    CPU Id        : 53 0f 10 00 00 08 03 02 - 09 20 80 00 ff fb 8b 17
                    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  @ ffffe0000173d240
    Section 2     : x86/x64 MCA
    Descriptor    @ ffffe0000173d138
    Section       @ ffffe0000173d2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : DCACHEL1_EVICT_ERR (Proc 2 Bank 0)
      Status      : 0xb265c00000000175

    A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


    Please stop overclocking.
    Max Speed 3100MHz
    Current Speed 3623MHz
    Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

    You mentioned that you transported machine.
    Check your machine for loose devices, cpucooler, dried out coolerpasta, dust etc.

    Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. It is good practice to run the latest drivers anyway.
    Please update these older drivers. Linksare included to assist in looking up the source of the drivers. If unable tofind an update, please remove (un-install) the program responsible for thatdriver. DO NOT manually delete/rename the driver as it may make the systemunbootable! :

    nusb3hub fffff800`01bb8000 fffff800`01bd0000 Fri Apr 23 03:34:35 2010 (4bd0f92b) 0001b8ec nusb3hub.sys
    nusb3xhc fffff800`0371b000 fffff800`0374b000 Fri Apr 23 03:34:36 2010 (4bd0f92c) 000303db nusb3xhc.sys

    Driver Description: NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)
    Driver Update Site: Try OEM first - Drivers available at the following link require registration and a lot of research: Support/Design | Renesas Electronics

    AODDriver2_fffff80003843000 fffff800`03843000 fffff800`03874000 Wed May 05 06:03:12 2010 (4be0ee00) 0001b98b AODDriver2.sys
    Driver Description: AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
    Known BSOD issues in Win7 Part of AMD Fuel
    Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys
    Driver Update Site: Raid. Frag. Dominate your games. | GAME.AMD.COM

    amdkmafd fffff800`036f8000 fffff800`03702000 Sun Sep 23 03:04:42 2012 (505e602a) 0000f46b amdkmafd.sys
    Driver Description: AMD PCI Root Bus Lower Filter or AMD Audio Bus Lower Filter
    Driver Update Site: Download Drivers

    ASACPI fffff800`037f8000 fffff800`03800000 Fri Nov 02 02:54:34 2012 (509327da) 00008405 ASACPI.sys
    iver Description: Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)
    Driver Update Site:

    netr28ux fffff800`01e01000 fffff800`02054000 Fri Apr 26 04:33:43 2013 (5179e787) 002545c1 netr28ux.sys

    Driver Description: Ralink RT2870 series USB802.11n Wireless Adapter Driver (you may have a different manufacturer)
    Driver Update Site:

    Rt630x64 fffff800`01a00000 fffff800`01a94000 Fri May 10 11:59:08 2013 (518cc4ec0009d8fe) Rt630x64.sys
    Driver Description: Realtek PCI/PCIe Adapters
    Driver Update Site: Realtek

    Update the motherboard BIOS and Drivers
    Your version is 1005 from 08/24/2010. The latest version is 2001 from
    2011.04.01 see Motherboards - M4A87TD EVO
    There are no windows 8.1 compatible drivers for your motherboard and also your bios will probably not be windows 8.1 compatible.

    If all after all of the steps mentioned above you stiil have the bugcheck 124 bsod , unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware. In your case the processor or your uncompatible windows 8.1 mainboard.
      My System SpecsSystem Spec

WHEA_uncorrectable_error BSOD after update to W8.1

Similar Threads
Thread Forum
Bsod whea_uncorrectable_error
Hey guys, After updating every driver I can find and doing a fresh install of windows 8.1 Pro, I am still having problems with WHEA_UNCORRECTABLE ERROR. I have also updated my BIOS and ran sfc scan, memtest, stress tested my CPU and GPU and ran chkdsk. Can anyone take a look at my crash...
BSOD Crashes and Debugging
BSOD whea_uncorrectable_error
Hello When i play any HTML5 videos on Google Chrome, the BSOD whea_uncorrectable_error happen. I had updated my motherboard to the latest version and i had formatted my SSD and install Windows 8.1 Pro again but it is still happen when i play any HTML5 videos on Google Chrome. Dump file +...
BSOD Crashes and Debugging
Bsod whea_uncorrectable_error
Bought computer from a friend and been running into this issue and struggling to figure out what exactly is causing it. I've nailed it down to either drivers or hardware but I don't know where to go from here to fix the problem. The issue doesn't seem to occur during any certain action. Gaming,...
BSOD Crashes and Debugging
Hello I have a problem with my PC getting the WHEA_UNCORRECTABLE_ERROR bsod. It is a few months old pc. I am not overclocking or changing anything in bios, but sometimes (this is my third time) I get this bsod out of nowhere. This last time I was just watching some stream on twitch when the pc...
BSOD Crashes and Debugging
Edited for proper format! Hi, I recently moved my computer from one house to another and with now hardware/software changes I've been getting BSOD everyday since I set it up and running at the new house. I hadn't changed anything. I also checked to make sure everything was seated properly...
BSOD Crashes and Debugging
BSOD - whea_uncorrectable_error
Hello everyone :D Im new to Windows 8. My computer crash while surfing on news sites with video or in computer games after 10 sek in there. The computer is brand new! See my attachment please
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook