BSOD playing ARK: Survival Evolved

0x124s are virtually always down to a faulty piece of hardware, but they rarely tell us what piece of hardware is causing the issues, as is the case here.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800e3c4038, 0, 0}

Probably caused by : GenuineIntel

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffa800e3c4038, 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.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

STACK_TEXT:  
fffff880`0357e6f0 fffff800`036dccb9 : fffffa80`0e3c4010 fffffa80`0cda1040 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0357ec10 fffff800`035bd157 : fffffa80`0e3c4010 fffff800`036372d8 fffffa80`0cda1040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0357ec40 fffff800`03524505 : fffff800`03698d00 00000000`00000001 00000000`00000000 fffffa80`0cda1040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0357ec80 fffff800`03499a95 : fffff880`01442400 fffff800`035244e0 fffffa80`0cda1000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0357ecb0 fffff800`0372eb8a : 00000000`00000000 fffffa80`0cda1040 00000000`00000080 fffffa80`0cd1ab30 : nt!ExpWorkerThread+0x111
fffff880`0357ed40 fffff800`034818e6 : fffff880`0336a180 fffffa80`0cda1040 fffff880`033750c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0357ed80 00000000`00000000 : fffff880`0357f000 fffff880`03579000 fffff880`0357e6a0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae_prv

FAILURE_ID_HASH:  {435e2195-e498-1e77-0526-f8d7450275e5}

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

2: kd> !errrec fffffa800e3c4038
===============================================================================
Common Platform Error Record @ fffffa800e3c4038
-------------------------------------------------------------------------------
Record Id     : 01d0c68008076403
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 7/25/2015 2:17:30 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800e3c40b8
Section       @ fffffa800e3c4190
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   : 0x00000000000106a5
Processor ID  : 0x0000000000000000

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

Local APIC Id : 0x0000000000000000
CPU Id        : a5 06 01 00 00 08 10 00 - bd e3 98 00 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  @ fffffa800e3c4250

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

Error         : Internal unclassified (Proc 0 Bank 5)
  Status      : 0xfa00000000400405

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.