Win 10 - 3570k - STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR

[opethdisciple]

Received this error last night whilst playing the Witcher 3 on Win 10.

I suspect it's my cpu oc. It has to be as it's the only part of the system tweaked.

However, I recalibrated my cpu voltages back in April. It passes 8hrs of prime 95 and has been gamed on ever since.

It COULD be a Win 10 thing.... but can software or driver cause this?

The memory dump doest show much other than: STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR.

However the error logs do mention: GenuineIntel_PROCESSOR_CACHE which to me looks like it's the oc thats unstable.

The CPU is a 3570k currently at 4.5Ghz @ 1.35v I think.

Should I go 4.4Ghz @ 1.35v or 4.5Ghz @ 1.36v?

I am already at the 85c thermal threshold.

 

[opethdisciple]

What do the experts on here say?

1. Up vcore to 1.36v and leave at 4.5ghz

or

2. Lower CPU clock speed to 4.4Ghz and leave at 1.35v

 

[opethdisciple]

I'm running a Noctua NH-D14.

I think it's pretty clear I should lower the clock speed.

It's just a coincidence I get my first sign of instability in about 4 months a few days after the move to Win 10.

 

[opethdisciple]

how much ram? and are you clocked with a fixed cpu v or through cpu offset/dvid

8gb ram. Using fixed cpu v.

 

[opethdisciple]

I just downloaded the Windows SDK which has a debugger and crash dump analyser.

I found something interesting:

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff80138276000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

STACK_TEXT:
fffff801`3a0f8a38 fffff801`3823a94f : 00000000`00000124 00000000`00000000 ffffe000`a794d028 00000000`be200000 : nt!KeBugCheckEx
fffff801`3a0f8a40 fffff801`384c926c : ffffe000`a794d028 ffffe000`a4c92b60 ffffe000`a4c92b60 ffffe000`a4c92b60 : hal!HalBugCheckSystem+0xcf
fffff801`3a0f8a80 fffff801`3823ae3c : 00000000`00000728 00000000`00000000 fffff801`3a0f8e70 00000000`00000000 : nt!WheaReportHwError+0x258
fffff801`3a0f8ae0 fffff801`3823b19c : ffffe000`00000010 ffffe000`a4c92b60 fffff801`3a0f8c88 ffffe000`a4c92b60 : hal!HalBugCheckSystem+0x5bc
fffff801`3a0f8c30 fffff801`3823b088 : ffffe000`a4c8f640 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalBugCheckSystem+0x91c
fffff801`3a0f8c80 fffff801`3823b2c6 : 00000000`00000004 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalBugCheckSystem+0x808
fffff801`3a0f8cc0 fffff801`3823b450 : ffffe000`a4c8f640 fffff801`3a0f8ef0 00000000`00000000 00000000`00000000 : hal!HalBugCheckSystem+0xa46
fffff801`3a0f8cf0 fffff801`383ccb7b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff801`3a0f8d20 fffff801`383cc931 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x2aeb
fffff801`3a0f8e60 fffff961`1c26f4aa : fffff961`1c26709a 00000000`00000000 ffffd000`2725db80 00000000`00000022 : nt!setjmpex+0x28a1
ffffd000`2725d8c8 fffff961`1c26709a : 00000000`00000000 ffffd000`2725db80 00000000`00000022 00000000`00003dff : win32kfull!xxxWindowEvent+0x159a
ffffd000`2725d8d0 fffff961`1c2661d4 : ffffd000`2725da48 ffffd000`2725c240 00000000`00000000 fffff801`ffffffff : win32kfull!NtUserGetMessage+0x72a
ffffd000`2725da00 fffff801`383cd863 : ffffe000`b043f080 00000051`15d0fd38 ffffd000`2725daa8 00000000`00000000 : win32kfull!NtUserPeekMessage+0x94
ffffd000`2725da90 00007fff`b82efc6a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x37d3
00000051`15d0fd18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`b82efc6a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

IMAGE_VERSION:

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner
---------


See the part in red. This machine is now running Win 10, having done the upgrade last week.

It says quite clearly DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT. Perhaps then this isn't a hardware instability thing and it's just that it's hit a fault due to no longer running win 8 anymore?

It also references the HAL. I'm no windows engineer but as I understand it the HAL gets built during install of the os. If I've done an upgrade from Win 8.1 to Win 10 then perhaps it's just come across an issue due to the HAL not matching exactly any more, due to the in place upgrade?

It's speculative but I think I will try a fresh install before I go changing my cpu oc. As it was rock solid under win 8.1

 

[opethdisciple]

not necessarily coincidence, different software can stress hardware differently, thus exposing a problem that never came up previously. The instability may have always theoretically existed but if with a different windows some particular sequence of commands didn't happen then you'd never know so it's like it wasn't unstable at all.

Meh, that was a terrible description, hope you understand what I mean been a long day...

I get you!

 

[opethdisciple]

Just had a look in my bios now that I'm at home.

Cpu vcore is set to 1.33v for 4.5Ghz. Under full (prime 95) load it does hit 84c.

Sort of in to minds what to do here.

I'm gonna try 1.34v and see how it goes. I am careful with this PC and I don't really game on it when the ambients temps are high.

 

[opethdisciple]

Well I bumped vcore to 1.34v and tested small fft and it passed for 1 hour. Within 5 mins of the Witcher 3 it blue screened with the same error.

As this PC was rock solid for the last 4 months prior to Win 10, I'm going to see what a clean install will do.

 

[opethdisciple]

Thanks for you help guys.

I think I've given up OC'ing my pc. I clearly have no idea what I'm doing and have settled for a stable system than a fast one.

I've reverted CPU to stock settings and the PC running Win 10 is stable again.

I was hoping to keep things simple with just vcore increases as LLC and all the rest is over my head.

Maybe one day I'll have another go at it. But we are in summer at the moment so the cpu is generally turned off, until it cools down at night so not in the mood for having another go at it.

Perhaps next time I should aim for around 4.4Ghz rather than 4.5Ghz as it seemed even at 1.34v the cpu wasn't stable (under win 10!!!!!) (Which is the bizarre part) and my temps where quite high already in the region of 87c ish.

---

Considering I'm now basically at stock settings, is there any sort of performance benefit upgrading to a 6700k or a 5820k paired with a 970?

 

[opethdisciple]

is it a gigabyte board?

Yes

 

[opethdisciple]

I could do it the other way round. I.e set in the bios the max safe 24/7 vcore then work down the frequency until I find what is stable at that vcore?

 

[opethdisciple]

for 4.4ghz try

manualy set pcie/clock to 100
set cpu multi to 44x
set cpu voltage to normal
set pwm phase control to extreme performance
set vcore voltage response to fast
set dvid to +0.050
set llc/loadline calibration to medium

download cpu-z and prime95 and load both up and stress cpu making a note of how much the load cpu voltage is in cpu-z and post back

I'll give this a shot, once the weather cools off a little in few weeks.

Ideally will shoot for 4.5Ghz.