BSOD when PC left idle; Error Code 0x124

Zedasiobud · 21 May 2015

This is my first custom PC build and I thought everything was going smoothly until I started getting BSoDs whenever I left the PC idle with not inputs for a period of time. Now, mind you I can go days without a BSoD if I don't leave it alone and idle. I mean even just leaving the space bar held down will prevent it from BSoDing, but if I don't touch my mouse or keyboard it will happen. Even running a simple keyboard macro off my Razer Blackwidow that spams F5 prevents this, but again if I just want to sit back and watch a movie or step away for grab lunch, it BSoDs on me.

Things I have done:
-Flash the BIOS
-MEMTests
-chkDSK on both my Hard Drives
-Updated all drivers
-Disabled any sleep/charger functions that kick in after a set period of time
-I have forced the PC into Sleep & Hibernate. This does not trigger it.

I'm hoping for any help on this matter.

Boozad · 22 May 2015

Hello Zedasiobud, welcome to 7F. I've taken a look at your dumps and you're receiving 0x124s which are generic bugchecks that indicate a hardware fault. 0x124s very rarely give an indication as to what the problem is and that's the case here, the only thing we can recommend here is a series of stress and diagnostic tests to try and pinpoint the hardware that is causing the issue. Please follow the steps below to the letter and post the results for each, some of them may duplicate what you've already tried but please perform them again.

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: fffffa801272a038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

7: kd> !errrec fffffa801272a038
===============================================================================
Common Platform Error Record @ fffffa801272a038
-------------------------------------------------------------------------------
Record Id     : 01d08f0ff6819fe4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/15/2015 13:06:33 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000002

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

Local APIC Id : 0x0000000000000002
CPU Id        : c3 06 03 00 00 08 10 02 - bf fb fa 7f ff fb eb bf
                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  @ fffffa801272a250

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

Error         : Internal unclassified (Proc 2 Bank 1)
  Status      : 0xbf80000000200401
  Address     : 0x00000000fee00040
  Misc.       : 0x0000000000000086

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. Hardware - Stress Test With Prime95

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. RAM - Test with Memtest86+

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. SeaTools for DOS and Windows - How to Use

Note

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

Run chkdsk Disk Check

FOUR

GPU TEST

Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

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.