Windows 10: 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.

regards,



Attachment 108643

:)

 

BSOD WHEA_UNCORRECTABLE_ERROR

Getting a blue screen of randomly after it's been on for a while but I can start up just fine in safe mode with no crashes.

No overclocks as far as I know, and the PC is relatively new (only 2 months old)

Any idea what could be causing this?

Dump files here:

Dropbox - 032918-5812-01.dmp

 

BSOD - WHEA_UNCORRECTABLE_ERROR

These are called BCC124 and are related to hardware. Read how to diagnose and hopefully to fix them in this
wiki

 

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

Code: 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[/quote] 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


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

 

Ztruker,

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.

regards,

 

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.

 

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.

 

Ztruker,

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.

regards,

 

It's another machine check WHEA_UNCORRECTABLE_ERROR (124). Windbg won't show me the error record this time, coimplains about
Code: 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[/quote] 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.