Windows 10: Bsod - whea_uncorrectable_error.

  1. Posts : 3
    Windows 10 Pro (Version 1607)
       02 Nov 2016 #1

    Bsod - whea_uncorrectable_error.

    My fairly new computer running windows 10 just keeps crashing. Usually at least once a day. The reported error is usually the WHEA error. I have looked at the minidump but it might as well be in chinese. XP was so reliable, this is not a step forward thankyou Microsoft.

    Can anyone have a look at the information and decipher what the problem is. I would be most grateful.



    Attachment 108643
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,259
    Windows 10 Pro X64 17134.191
       03 Nov 2016 #2

    I only looked at the last dump and it shows a hardware machine check, cache error:

    3: kd> !errrec ffffb80e6a0dc028
    Common Platform Error Record @ ffffb80e6a0dc028
    Record Id     : 01d234e96bc0cad8
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 11/2/2016 17:48:49 (UTC)
    Flags         : 0x00000000
    Section 0     : Processor Generic
    Descriptor    @ ffffb80e6a0dc0a8
    Section       @ ffffb80e6a0dc180
    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         : 2
    CPU Version   : 0x00000000000506e3
    Processor ID  : 0x0000000000000003
    Section 1     : x86/x64 Processor Specific
    Descriptor    @ ffffb80e6a0dc0f0
    Section       @ ffffb80e6a0dc240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000003
    CPU Id        : e3 06 05 00 00 08 10 03 - 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  @ ffffb80e6a0dc240
    Section 2     : x86/x64 MCA
    Descriptor    @ ffffb80e6a0dc138
    Section       @ ffffb80e6a0dc2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : GCACHEL2_ERR_ERR (Proc 3 Bank 6)
      Status      : 0xbe0000000100110a
      Address     : 0x000000026e4c9a80
      Misc.       : 0x0000009084000086
    Try running Prime95, a CPU stress test, see if that shows any problems:
    Follow this tutorial to stress test your CPU:
    Prime95 - Stress Test Your CPU - Windows 10 Forums

    If not, turn on Driver Verifier and run as directed:
    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
    and make sure the correct boxes are checked.

    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 BSOD with a mini dump that will tell us what driver caused it.
      My ComputersSystem Spec

  3. Posts : 3
    Windows 10 Pro (Version 1607)
    Thread Starter
       05 Nov 2016 #3

    Results of tests


    Thanks for looking at this problem. As you suggested, I ran the stress test on the cpu. It did not reveal any problem, although I stopped the test fairly quickly as the core temps rose rapidly to 70+ degs.

    I then enabled the driver verifier. The system crashed after about 18 hrs or so. I have attached the latest information. Unfortunately (to a dummy like myself) it does not appear to offer a definitive answer. Unless it is a fault in the cache on the cpu.

    Perhaps you could kindly have a look.


      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,259
    Windows 10 Pro X64 17134.191
       05 Nov 2016 #4

    No new dump in the zip. Oldest is still 11/2.

    The hardware error could very well be a CPU problem but unless you have one you can replace it with there is no way I know of to test it other than programs like Prime95.

    How are the temps and voltages normally? You could try monitoring them with Speedfan or CPUZ or equivalent.
      My ComputersSystem Spec

  5.    05 Nov 2016 #5

    I had a problem with WHEA Uncorrectable Errors. The problem turned out to be a defective i7 3770 CPU. However, diagnostics never turned up anything, including the Intel CPU diagnostic. I did what was asked on the Win 7 forum and the dumps never showed anything. I finally decided to "shotgun" it and started replacing parts (fortunately I had spare parts). I started with power supply, then video card, then memory and finally the motherboard. I still had the problem and the only thing left was the CPU. I had a spare i5 3550 and I installed that and the WHEA error went away. After several exchanges with Intel they finally replaced the i7 3770 under warranty.
      My ComputersSystem Spec

  6. Posts : 3
    Windows 10 Pro (Version 1607)
    Thread Starter
       06 Nov 2016 #6

    BSOD pain.


    The latest dump (Windows10pc-05_11_2016_114206_39) shows the last minidump as 110516-6483-01 dated 05/11/2016 0600.

    could you have a look at it please.

      My ComputerSystem Spec

  7. Ztruker's Avatar
    Posts : 6,259
    Windows 10 Pro X64 17134.191
       07 Nov 2016 #7

    It's another machine check WHEA_UNCORRECTABLE_ERROR (124). Windbg won't show me the error record this time, coimplains about
    Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for PSHED.dll
    *** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
    More dumps are not going to help resolve this. As Firebird mentioned, the only way I can think of to determine what is actually causing this is to swap out parts, especially the CPU. If it's still under warranty then see if you can get manufacture to replace it.
      My ComputersSystem Spec


Related Threads
Bsod whea_uncorrectable_error in BSOD Crashes and Debugging
Alright, Ive had a good run of bad luck with bsod recently this one though has been pretty bad.. im averaging 4 crashes in 2 days with 2 being within 20 min of each other. when the bsod shows up I get the WHEA_UNCORRECTABLE_ERROR. So I did do a...
BSOD 0x124 WHEA_UNCORRECTABLE_ERROR in BSOD Crashes and Debugging
i have had this error for like a month, tested all components on the Pc and none of them seems to be failing, so i started searching so i can figured out which component is failing according to minidump file according to minidump it say...
Bsod: Whea_uncorrectable_error in BSOD Crashes and Debugging
For the past month, I have been trying to diagonose the WHEA_UNCORRECTABLE_ERROR BSOD. The issue started occurring after I upgraded to Windows 10 build 1151. I had updates disabled for a while, and I believe that it is some kind of chipset driver...
Bsod - whea_uncorrectable_error in BSOD Crashes and Debugging
Hello everyone. As stated in the title I am experiencing BSOD with the message "WHEA_UNCORRECTABLE_ERROR". The computer usually loads up to 100% and then restarts, but not always. Sometimes I will have to manually restart the computer. System...
BSOD WHEA_Uncorrectable_Error in BSOD Crashes and Debugging
Hello everyone, I've recently purchased a new SSD and upon receiving it decided to do a complete wipe of my system including resetting BIOS back to default. I have two SSD's installed in my system, with the OS installed onto the old ssd. This...
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 19:49.
Find Us