WHEA_UNCORRECTABLE_ERROR

oaksmokedbacon · 28 Jun 2015 at 21:52

Hi all

not a regular occurrence but in the last couple of days I've had a couple of WHEA Blue Screen errors forcing a restart. Both have occurred during playing BF4.

I have the mini-dump files but was wondering how I can find out what might be causing the error? There wasn't a code given on the light BSOD.

Any help much appreciated to find out what might be the problem. Generally the PC is running very well and well within temp limits.

5960xNvidiaGamer · 28 Jun 2015 at 21:57

Maybe try updating the bios, or lowering the overclock. Someone else said it was down to C1E, Intel SpeedStep or Intel C-State, maybe disable the C states.

Pulseammo · 28 Jun 2015 at 22:11

My 3770k is pretty new to me, but after overclocking it I got these errors in my event log:

Code:

A corrected hardware error has occurred.

Reported by component: Processor Core
Error Source: Corrected Machine Check
Error Type: Internal parity error
Processor ID: 1

The details view of this entry contains further information.

They come off the WHEA Logger and the way I solved mine was by raising voltage. I was at 4.2ghz @ 1.12v and I think I'm now at 1.14v or 1.15v. Each time I raised my voltage by 0.01v and the logged errors got less and less until they didn't occur at all.

If you're overclocked check your event logger (eventvwr into run on the start menu) for system event warnings Event ID 19. If you have lots of those and you're overclocked then you need to bump voltage or reduce clock speed. It's not the same error but I think event 19 leads to your error eventually.

kaku · 29 Jun 2015 at 13:21

It's an unstable overclock for sure. I would bump VCore first. Is your VCCIO at stock? It's possible it could need a bump if VCore doesn't work because of the high memory speed.

varkanoid · 29 Jun 2015 at 15:46

post a link to a mem dump file

oaksmokedbacon · 29 Jun 2015 at 16:57

Cheers for the replies all.

My VCore is at 1.25v at the moment on an overclock to 4.6 which has caused no problems on any benchmarks.

From reading a previous thread posted about BSOD the error code was 124. He solved his issue by removing the Gigabyte App Suite with all the tools (never used it anyway) and it seems to have corrected the problem. MS website also mentions these BiOS Accessing tools can cause issues.

Bios is up to date with F8 and the RAM is on an XMP profile.

I'm going to keep an eye on things and work from there as it has been a rare occurrence.