WHEA_UNCORRECTABLE ERROR during games

oldage · 31 Jul 2015

Okay it was one game so far, Rust. I plan on trying others and doing some prime95/memtest later on but I'm gonna post this here already incase someone more knowledgeable wants to take a look, and to make sure if it's an actual faulty CPU or some driver being funny.

Attachment 27123

FX-6300
GA-970A-UD3
HD7850
Antec EA650
2 x 4 GB Ballistix (or sports, or both, I'm not sure)

Temps were fine, no overclocking is done, BIOS was reset to default. A while ago my BIOS did corrupt itself after waking from hibernation (I forgot to turn it off), that was on my windows 7 installation.

edit: just crashed with same message while running DISM.exe /Online /Cleanup-image /Restorehealth

edit2: crashed while browsing internet, ran chkdsk after restart but found no errors. Waiting on next crash...

edit3: spent some time in safe mode to fix the sfc issues, it didn't BSOD there whereas I was there for much longer than in a normal session.

Boozad · 31 Jul 2015

You've encountered a STOP 0x124 which indicates a hardware failure, but as with most 0x124s it's not giving away any signs of which piece of hardware is actually failing.

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00156a12028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000060151, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  RustClient.exe

CURRENT_IRQL:  f

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

0: kd> !errrec ffffe00156a12028
===============================================================================
Common Platform Error Record @ ffffe00156a12028
-------------------------------------------------------------------------------
Record Id     : 01d0cb6d5eb06197
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/31/2015 13:15:55 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffffe00156a120a8
Section       @ ffffe00156a12180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e ff fb 8b 17
                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  @ ffffe00156a12240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffffe00156a12138
Section       @ ffffe00156a122c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : ICACHEL1_IRD_ERR (Proc 0 Bank 1)
  Status      : 0xb080000000060151

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. http://www.sevenforums.com/tutorials...t-prime95.html

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. http://www.sevenforums.com/tutorials...memtest86.html

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. http://www.sevenforums.com/tutorials...t-furmark.html

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.

oldage · 01 Aug 2015

The system hangs and reboots during a prime95 in a normal session, in safe mode however it is able to finish the test (blend).

Will leave memtest on a bit later today.

Boozad · 01 Aug 2015

OK let us know how it goes. Did you notice your temperatures during Prime95?

oldage · 01 Aug 2015

Boozad said:

OK let us know how it goes. Did you notice your temperatures during Prime95?

CPU never went over 45°C. Used HWMonitor in both runs.

Right now I'm on xubuntu, going to play rust again and see how long I can play for before it crashes, if it will. After that I will let memtest do its thing.

oldage · 02 Aug 2015

Game doesn't even start but I guess that's just a linux thing.

10 Memtest passes without errors, figured that was enough. Chkdsk/SeaTools found nothing bad. Currently running furmark. I'm curious, while it may end up being a faulty processor, can this be a PSU issue aswell? Or would this error indicate that my processor is already too damaged?

edit: no crashing with furmark (35 minutes)

In any case, here's the zip with the other dump files from the 4 other crashes, no idea what program you guys use otherwise I could check for patterns myself.
Attachment 27797

edit2: Well today I've had an uptime of 8 hours without any issues. Did some light games, mostly watched twitch. Had to restart for cortana though. I don't understand what caused the previous bsods

oldage · 03 Aug 2015

Another update, Prime95 ran fine for 4 hours until I ended it, whereas last time it crashed after an hour.

Is there a way to figure out if it's a specific core causing the problem? I found out I can disable cores in my BIOS. Kind of want to do that before I try games.

Boozad · 03 Aug 2015

I wouldn't disable any cores. Does the system seem more stable now?

oldage · 03 Aug 2015

Boozad said:

I wouldn't disable any cores. Does the system seem more stable now?

Haven't had a BSOD yet, but I haven't played a game yet. The only thing I did was changing the power management from high performance to balanced. I don't overclock so I have no idea if that actually fixed it. It is a hardware error code after all.

Do you see anything in the other .dmp files that could pinpoint the bad core if it is that? Want to try atleast (if I still crash during games)

oldage · 04 Aug 2015

Just crashed again, was just watching a twitch stream. I am so confused.

The only other thing I can think of that changed was the power strip, which I've now changed again. After this I guess I'm gonna try wiping my hard drive and just fresh installing w7 again but I doubt it's w10's fault.