Whea uncorrectable error, possible thermal issue?

Darcw0lf · 15 Sep 2015

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.

axe0 · 16 Sep 2015

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?

Darcw0lf · 16 Sep 2015

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.

axe0 · 16 Sep 2015

What about the drivers?
Have you checked for updates?

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

Darcw0lf · 16 Sep 2015

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

axe0 · 16 Sep 2015

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

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.

Darcw0lf · 16 Sep 2015

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 O.o

axe0 · 17 Sep 2015

We need to rule out hardware

The errors are 0x124 WHEA_UNCORRECTABLE_ERROR (Windows Hardware Error Architecture)
This means that there are problems with your hardware, unfortunately this error rarely gives enough information for a specific cause. Fortunately, this error is mostly caused by overclocking or faulty drivers
Prime95 may be ignored this time.

STOP 0x124 Troubleshooting

Read carefully before proceeding.

Warning

If you're overclocking your system, revert back to stock clocks now.

Note

Test the system once the overclock is removed before continuing with the steps outlined below.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

ONE

CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

TWO

RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

Note

MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

THREE

HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html

Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html

FOUR

GPU TEST

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 10 Forums

Note

Run Furmark for around 30 minutes.

Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.

Darcw0lf · 17 Sep 2015

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.

axe0 · 17 Sep 2015

Well I have already done prime 95, works fine.

That is why I said you can skip it

Memtest does lock the computer when doing an extended test.

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

Video card was in the system right before I built this one and had no issuses.

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