Windows 10: Whea uncorrectable error, possible thermal issue?

Just built my new x99 platform pc, from the first install of windows I had issues with random hangs, but only when using specific programs, like core temp. When I game or stress test it seems fine, which is really odd, since the bsod seems to be a thermal issue. I have never been good at deciphering the dumps files, and I suspect this is a ram issue, any help would be appreciated since most of the parts are still in the 30 period where amazon will help me out with advanced RMA.

:)

 

Getting WHEA_UNCORRECTABLE_ERROR while installing VMware or Virtual Box.

Hi Siva,

How to fix whea uncorrectable error

https://support.microsoft.com/en-us...845cfc1d6/how-to-fix-whea-uncorrectable-error

Thank you.

 

Uncorrectable Error when installing Windows 10

See the following:

0x0000124 (WHEA UNCORRECTABLE ERROR): Fix for Windows

 

Hi Darcw0lf,

Welcome to the 10forums.

What stress test(s) have you done, for how long and what was/were the result(s)?

It looks like the CPU is causing trouble, but it could be a driver issue or overclocking problem.

I guess you know the CPU temperature under load and when idle?

 

It's been a few years since I really have used any software for troubleshooting purposes, so I could be using the wrong thing. I am currently using prime 95, which always was good in the past. I'm using HWinfo to monitor the temps, idle I'm in the low 30's, under load I'm in the low 50's while gaming. I'm running prime 95 again for a longer period, because it does tend to rise after a while, but after about 5 minutes so far it's only hitting mid 50's.

Currently I'm stock, just updated the bios a few days ago. I did run an extended memtest and it hard locked the system at 21% on first pass.

*****
Update, ok a bit weird, so prime 95 got core 2 up to 67, others were low 60's, now a few minutes later they have all dropped to low 50's, core 2 is still high at the mid 50's.

 

What about the drivers?
Have you checked for updates?

Looking at the stack, the intel CPU drivers are the cause of the crash.

 

All drivers are up to date, pulled right from websites, when you say intel cpu drivers, do you mean the inf drivers?

 

Here is what I mean.

The stack (marked in red where it starts)
Code: ffffd001`b5e757f8 fffff802`26a9894f : 00000000`00000124 00000000`00000000 ffffe001`78ea0028 00000000`be000000 : nt!KeBugCheckEx ffffd001`b5e75800 fffff802`264640e0 : ffffe001`78ea0028 ffffe001`77ed26d0 ffffe001`77ed26d0 ffffe001`77ed26d0 : hal!HalBugCheckSystem+0xcf ffffd001`b5e75840 fffff802`26a98e3c : 00000000`00000728 00000000`0000000b ffffd001`b5e75c30 00000000`00000000 : nt!WheaReportHwError+0x258 ffffd001`b5e758a0 fffff802`26a9919c : ffffe001`00000010 ffffe001`77ed26d0 ffffd001`b5e75a48 ffffe001`77ed26d0 : hal!HalpMcaReportError+0x50 ffffd001`b5e759f0 fffff802`26a99088 : ffffe001`77ed1760 00000000`00000001 00000000`0000000b 00000000`00000000 : hal!HalpMceHandlerCore+0xe8 ffffd001`b5e75a40 fffff802`26a992c6 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4 ffffd001`b5e75a80 fffff802`26a99450 : ffffe001`77ed1760 ffffd001`b5e75cb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce ffffd001`b5e75ab0 fffff802`26368b7b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 ffffd001`b5e75ae0 fffff802`26368931 : 00000000`00000000 fffff802`263688b0 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b ffffd001`b5e75c20 fffff800`79873548 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171 ffffd001`b5e9b828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!ReadIoMemRaw+0xe8[/quote] More information about the driver
Code: 11: kd> lmvm intelppm start end module name fffff800`79870000 fffff800`79899000 intelppm (pdb symbols) c:\windows\symbol_cache\intelppm.pdb\89FABBD09556447FB6B157B5A3A81CD91\intelppm.pdb Loaded symbol image file: intelppm.sys Mapped memory image file: c:\windows\symbol_cache\intelppm.sys\559F383B29000\intelppm.sys Image path: \SystemRoot\System32\drivers\intelppm.sys Image name: intelppm.sys Timestamp: Fri Jul 10 05:12:59 2015 (559F383B) CheckSum: 0001FAC6 ImageSize: 00029000 File version: 10.0.10240.16384 Product version: 10.0.10240.16384 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: intelppm.sys OriginalFilename: intelppm.sys ProductVersion: 10.0.10240.16384 FileVersion: 10.0.10240.16384 (th1.150709-1700) FileDescription: Processor Device Driver LegalCopyright: © Microsoft Corporation. All rights reserved.[/quote]

 

So what would you recommend? This is a clean install, all drivers are up to date, I'm kinda at a loss, unless you think the cpu is bad, which how often does that happen with an intel cpu

 

Well I have already done prime 95, works fine. Memtest does lock the computer when doing an extended test. I know it's not the ssd, have used a samsung evo and my current samsung XP941. Video card was in the system right before I built this one and had no issuses.

I'm going with it being a ram issue, after reading some reviews about my ram I found it has some xmp profile issues, sending it back and getting a new set, hopefully that does it.

 

That is why I said you can skip it *Wink

You mean you have to force shutdown to get the pc working again?

Please run Furmark, that the GPU was already in the system before you built it does not mean the GPU is not the cause.

 

Yes, the memory test hard locks the pc, I have to hold down the power button and completly reboot it. I also am using the windows 10 memtest, the one that makes you reboot your computer to test it, basically in dos. I will go ahead and run furmark, I don't think it's the problem, but hey, I'm willing to listen to suggestions from people trying to help me *Smile

Also, the blue screens only happen when the pc seems to go into stand by, or sleep or whatever. I will walk away and come back an hour later and there is a blue screen. It NEVER happens while I'm actually doing anything.

uggg..... G.Skill just replied back, basically blaming the chipset and the board basically saying that it's not capable of supporting the ram. I personally think this is crap, board actually supports up to 3333mhz according to the manufacturer.

**********
Update
Ran furmark about 35 minutes, temp never went above 71c, stayed 70 pretty much the whole time.

 

That sounds more like a problem with the sleep/hybernate functions in windows 10.
There are a lot of people having this problem, the best solution for this is to not use the functions until Microsoft fixes it.

 

ok, I will disable it, which I usually do anyway, this was a fresh install and just never got around to it before this started happening, that and hopefully once I get the ram it will solve my other little weird issues. What do you think about gskill trying to blame the x99 chipset, trying to say it can't handle it?

 

Would you mind posting the conversation?
I would like to read it before I go into it.