Hi everyone. I've been scratching my head on this for a while now but my computer keeps blue screening with a "WHEA UNCORRECTABLE ERROR".
I've done the following things in order to try to fix this:
Heatsink: I've took out the heatsink, cleaned it, and put it back with no luck. I just switched out the heatsink to a liquid cooling one, but no luck there either.
RAM: I've done a memtest on the ram. (also removed and added it back in with no luck) It didn't give me an errors after 10 passes.
Harddrives: I've removed all the harddrives and am currently using a new one. (Boxing day in Canada. Hooray!). I then thought maybe it was the SATA cables, but it freezes after a while when I live boot into Linux using a USB flash drive as well, and sometimes gives me a CPU kernel error. I thought maybe it was a driver issue but it also blue screens in safe mode and a clean install it's still doing this.
PSU: Thought maybe my PSU was giving up, so I switched to a new PSU.
Graphics Card: It used to not even let me go into the OS before I've removed the GPU, but it's at least letting me browse the internet for 5 minutes before Bluesceening now.
I've made sure to update the BIOS as well. I looked at all the motherboard capacitors and there doesn't seem to be any bulging. It's interesting that I can idle indefinitely in the BIOS and/or memtest without it turning off.
Google points to cpu / bios / driver issues. It seems you addressed these. Can you boot win10 into safe mode? I don't like how win10 handles all of this safe mode stuff, it is trying to be android or something. If not, do you have linux on a usb, or some other OS you can boot into and see if you have any dramas? Exercise the hardware? It is good to have a copy of the ultimate boot disk on a thumbdrive for testing.
I'm not sure, but this WHEA may be Windows Hardware Evaluation something-something. So I guess it's one of those "it won't work because we told you so" cases. Like Cisco VPN client which won't install just because.
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck 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: ffffe00030cd4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000fb800040, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000174, Low order 32-bits of the MCi_STATUS value.
Then the error itself:
kd> !errrec ffffe00030cd4028
===============================================================================
Common Platform Error Record @ ffffe00030cd4028
-------------------------------------------------------------------------------
Record Id : 01d2625e6d35823c
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 12/30/2016 5:41:14 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffe00030cd40a8
Section @ ffffe00030cd4180
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 : 0
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000005
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffe00030cd40f0
Section @ ffffe00030cd4240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000005
CPU Id : c3 06 03 00 00 08 10 05 - bf fb da 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 @ ffffe00030cd4240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe00030cd4138
Section @ ffffe00030cd42c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : DCACHEL0_EVICT_ERR (Proc 5 Bank 1)
Status : 0xfb80004000000174
Thank you! I've used linux on a USB before and it ended up freezing everything for 30 seconds, then automatically restarting. I'll definitely give it another shot though!
Sysnative points to ASUS AI Suite which has been known to cause BSODs whether you have OC or not. Then there is the outdated NIC driver. That is all I could get from the dmp.
Sysnative seems to point to these two: AsIO.sys belongs to ASUS AI Suite.
Thank you! It's a pretty new install. I'm not sure if that has something to do with it. I'll definitely try this out and let you know. I'll upload another dmp as well.
What an adventure. I think I figured it out. I'm going to be doing some stress testing and such to see, but I think I figured it out. It was Intel speedstep in my BIOS that was crashing my OS. Ubuntu still keeps freezing which is odd, but that must be unrelated.
Thanks to everyone who has posted to help out. (Novasty, dmj, ArgGrr)
If it is intel speedstep, you seriously need to return that processor if it is new. Otherwise you are SOL with a defective part. Did uninstalling AI Suite not do anything?
Oh I bought it three years ago. The CPU I own is an unlocked quad core. Could that have anything to do with it? Maybe I've disabled something else in the BIOS that fixed it, but I thought I was certain that that was it.
I didn't have it installed or I was either too stupid to find it. haha
