WHEA Uncorrectable Error Windows 10

[EbonKnight]

Hello,

So recently I've started getting a lot of problems with the WHEA error. Thing is, this could in theory be to do with my CPU (I7 4790k) because under normal circumstances, the bloody BIOS defaults to stupidly huge voltage for the chip (Gigabyte z97-udh3, known error, cannot fix it in BIOS it seems) so I have to use the Intel Utility to set the voltages manually. Problem is that I have set these to the Intel recommendations, and even a bit above and my processor runs cool under even big stress (I have a custom cooler, did Prime95 for a bit) YET this error will randomly occur even in, say Word 10 or while browsing light content on the Internet. Meanwhile, sometimes it will happen while playing a video or an mp3 track YET it will very rarely happen in games, where the CPU should be under most stress.

I also thought it might be the fact I have 2x2 different sticks of RAM but those were thoroughly checked for errors AND they worked fine together for years now (set them to the same frequencies in BIOS and everything) but this problem is only recent.

So, I got a hold of the last five of my BlueScreenView crash logs.. hopefully someone can figure this out. Bonus points if anyone could point me towards solving the CPU voltage issue in BIOS without having to do it manually with the Intel XTU utility, since I will bet that this causes some problems, even if not necessarily the main one. Yet, if I don't touch it at all the CPU just gets fed a butt ton of voltage (the default states around 4k, which is silly ofc) and thus overheats too much even when idling.

file:///D:/Downloads/drivers/BlueScreenView/report.html

Since I'm not sure you can see that link, here are the latest five:

052417-3250-01.dmp 5/24/2017 11:31:57 PM 0x00000124 00000000`00000000 ffff8a0f`9ce00028 00000000`bf800000 00000000`00000124 hal.dll hal.dll+395cf Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.0 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c310 C:\Windows\Minidump\052417-3250-01.dmp 8 15 15063 618,212 5/24/2017 11:32:22 PM


052317-3375-01.dmp 5/23/2017 11:32:25 PM 0x00000124 00000000`00000000 ffffe784`97975028 00000000`bf800000 00000000`00000124 hal.dll hal.dll+395cf Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.0 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c310 C:\Windows\Minidump\052317-3375-01.dmp 8 15 15063 663,044 5/23/2017 11:33:00 PM

052217-3812-01.dmp 5/22/2017 10:04:35 PM 0x00000124 00000000`00000000 ffff9c88`7ef54028 00000000`bf800000 00000000`00000124 hal.dll hal.dll+395cf Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.0 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c310 C:\Windows\Minidump\052217-3812-01.dmp 8 15 15063 676,716 5/22/2017 10:05:23 PM

051917-3515-01.dmp 5/19/2017 8:18:36 PM 0x00000124 00000000`00000000 ffffe488`12759028 00000000`bf800000 00000000`00000124 hal.dll hal.dll+395cf Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.0 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c310 C:\Windows\Minidump\051917-3515-01.dmp 8 15 15063 477,188 5/19/2017 8:19:05 PM

051817-3453-01.dmp 5/18/2017 1:43:06 AM 0x00000124 00000000`00000000 ffffb30b`e1975028 00000000`bf800000 00000000`00000124 hal.dll hal.dll+395cf Hardware Abstraction Layer DLL Microsoft® Windows® Operating System Microsoft Corporation 10.0.15063.0 (WinBuild.160101.0800) x64 ntoskrnl.exe+16c310 C:\Windows\Minidump\051817-3453-01.dmp 8 15 15063 512,924 5/18/2017 1:43:38 AM


Thanks in advance guys!

 

[EbonKnight]

Anyone?!

 

[Colif]

Can you follow option one here: http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

Windows Hardware Error Architecture errors are generally CPU errors, and given your story I would lean that direction

Can you run Intel Processor Diagnostic Tool on PC and see if that Bios fault has damaged CPU

 

[EbonKnight]

Okay, I thought they were minidumps cause that's what the folder I found them in was called in Windows, but it turns out it was automatic dumps. I also did a MemTest and the Intel test and it seems that all four sticks of RAM -and- the CPU are a pass.. that's good news, right?

Here's the latest minidump.. computer worked fine all day, including a memtest, cpu test -and- about 3 hours non stop gaming + watching a youtube video.. then just crashed randomly while watching another video. http://s000.tinyupload.com/?file_id=01700125637372048375

Here is an earlier dump, also in that folder, but done as an automatic dump:

http://s000.tinyupload.com/?file_id=04619926978567240003

 

[gardenman]

Hi, I downloaded the dumps and WhoCrashed reported the following:

Spoiler

On Fri 5/26/2017 11:29:45 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052617-3437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
Bugcheck code: 0x124 (0x0, 0xFFFFBE86C9B75028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 5/25/2017 3:17:39 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\052517-3500-01.dmp
This was probably caused by the following module: hal.dll (hal+0x395CF)
Bugcheck code: 0x124 (0x0, 0xFFFFAA08A6B54028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

In addition, the Win 10 Kit Debugger reported the following:

052617-3437-01.dmp https://pastebin.com/nynzUMwm
052517-3500-01.dmp https://pastebin.com/R42056HG

I forgot to look up more info on the errors and add it to the text so I'll do that here.

052617-3437-01.dmp
BUGCHECK_P1: 0 <-- A machine check exception occurred. These parameter descriptions apply if the processor is based on the x64 architecture, or the x86 architecture that has the MCA feature available (for example, Intel Pentium Pro, Pentium IV, or Xeon).
BUGCHECK_P2: ffffbe86c9b75028
BUGCHECK_P3: bf800000
BUGCHECK_P4: 124

052517-3500-01.dmp
Same as other one, parameter 1 was 0

I can't help you with these. Wait for Colif or someone else to reply. Good luck.

 

[Colif]

Yes, its good IPDT didn't find anything. WHEA errors can be any hardware on PC, I just go to CPU as they are called by the CPU

@ gardenman, did you run a command like !errrec ffffaa08a6b54028 or !errrec ffffbe86c9b75028 to get those reports? John asked last whea poster to do same so I was wondering as that might be what I am seeing (I don't know)

one mentioned firefox but that is likely just the program it was last running when it crashed. unlikely to mean anything (I learned that last time)

 

[gardenman]

@ gardenman, did you run a command like !errrec ffffaa08a6b54028 or !errrec ffffbe86c9b75028 to get those reports? John asked last whea poster to do same so I was wondering as that might be what I am seeing (I don't know)

Colif, I just tried it. It's not useful info (to me anyway). The first memory address was invalid. Here's the one that is mentioned as parameter 2 in the dump.

Spoiler

6: kd> !errrec ffffbe86c9b75028
===============================================================================
Common Platform Error Record @ ffffbe86c9b75028
-------------------------------------------------------------------------------
Record Id : 01d2d6100a2e2079
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 5/26/2017 15:29:45 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ ffffbe86c9b750a8
Section @ ffffbe86c9b75180
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 : 0x0000000000000006

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ ffffbe86c9b750f0
Section @ ffffbe86c9b75240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000006
CPU Id : c3 06 03 00 00 08 10 06 - 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 @ ffffbe86c9b75240

I also tried the address listed as parameter 3 and it was also invalid and not helpful.

 

[Colif]

cache error, seem to go along with overclocked systems so maybe that voltage problem is responsible, think I ask for some assistance on this...

found one post that suggests ipdt isn't perfect and can miss problems.

 

[EbonKnight]

Thanks for trying guys, but I'm really still at a loss here.. is it CPU, then? I mean, I know there's an issue with Gigabyte Z97 boards and I7 Devil's Canyon CPU's but frankly at this point I'm at a loss as to what I should do.. funnily enough, some game tests etc recently, without changing any voltage (eg with Intel XTU reporting ridiculous over-voltage by the mobo) still didn't have the CPU going past 57ish degrees celsius under gaming load, so I can't really imagine overheating or anything like that is the issue. Yet, after thoroughly checking the memory and even changing the gfx card (had a 390x, currently running a 1070) it seems that, hardware-wise, there isn't much else but the CPU that could be causing problems..

 

[Colif]

I am fairly sure its the CPU but I am not sure if it can be fixed by resolving that bios problem you have with voltages. How old is motherboard?

Which version number Bios do you have? this talks about your board and suggests a bios update may fix: https://forum.giga-byte.co.uk/index.php?topic=14757.0

Download page for motherboard: http://www.gigabyte.com/Motherboard/GA-Z97X-UD3H-rev-10#support-dl

this talks about your board and the voltage problem and leads me to think it may be cause - see last post: http://www.tomshardware.com/answers/id-2203379/4790k-vcore-49v-gigabyte-uefi.html

 

[EbonKnight]

Yeah, my money is on the board/CPU problem, for sure. I think I got the CPU about 3-4 months after it came out so that makes it what, about 2 1/2 years old now, along with the board? Not sure.. the board is a Gigabyte Z97, UDH3, though. It's actually F8, but it still didn't fix things. When I look in the BIOS it claims to give 88W and 105 Ampers but then when I go into Intel XTU, it gives outrageous numbers like 3408 to 4500+ watts when on Turbo, which is obviously insane. So, what to do? It's really weird, used to be that I would get much higher temps unless I fix it in Intel XTU but then also I'm pretty sure those lower (and sane) wattage numbers I put in (from this thread https://communities.intel.com/thread/54032?start=210&tstart=0) would get more WHEA's. Now, even though my BIOS didn't change or anything, I still get the insane numbers in XTU but if I leave them unchanged the temps aren't too bad. That being said, if the wattage really is being overloaded to the CPU, it's going to eventually screw it up, even if the temps are good.

I'm afraid that the only thing I'll be able to do is use Intel XTU on a regular basis, but that it might not be enough :/ Stupid problem, really.. quite frustrating.

 

[Colif]

if CPU is cause, at least the warranty is 3 years so you could rma it if need be. I am not sure I would put a new CPU on that board if its the cause, that sounds like a painful bios bug and one they should have fixed.

I am hoping someone looks in here and gives a 2nd opinion. I am not ignoring the thread, I am just not 100% sure at this moment. Have you posted on the gigabyte forums?

 

[Turb0Yoda]

I'm inclined to agree with colif. WHEA generally points to a bad OC/BIOS setting or windows corruption
I'm assuming you've reinstalled windows.

 

[EbonKnight]

Thanks so much guys.. actually, yeah, I figured it couldn't be just Windows.. but maybe it'll help.. I'll have to try! Yesterday I did only gaming and light browsing, and there were no crashes, funnily enough. I'll also post on the Gigabyte forums, see if they have any ideas. Thanks again, hopefully this can get fixed!