Windows 10: blue screen issue

**Boozad** · 19 Aug 2015

All 0x124s denoting a hardware error, but as with most 0x124s they're showing no signs of which piece of hardware is problematic.

Code:

BugCheck 124, {0, ffffe00125b25028, be200000, b110a}

Probably caused by : GenuineIntel

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

6: 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: ffffe00125b25028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000000b110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

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

STACK_TEXT:  
ffffd000`8c60a7f8 fffff800`9949d94f : 00000000`00000124 00000000`00000000 ffffe001`25b25028 00000000`be200000 : nt!KeBugCheckEx
ffffd000`8c60a800 fffff800`98e69118 : ffffe001`25b25028 ffffe001`24ad1fa0 ffffe001`24ad1fa0 ffffe001`24ad1fa0 : hal!HalBugCheckSystem+0xcf
ffffd000`8c60a840 fffff800`9949de3c : 00000000`00000728 00000000`00000006 ffffd000`8c60ac30 00000000`00000000 : nt!WheaReportHwError+0x258
ffffd000`8c60a8a0 fffff800`9949e19c : ffffe001`00000010 ffffe001`24ad1fa0 ffffd000`8c60aa48 ffffe001`24ad1fa0 : hal!HalpMcaReportError+0x50
ffffd000`8c60a9f0 fffff800`9949e088 : ffffe001`24ad13f0 00000000`00000001 00000000`00000006 00000000`00000000 : hal!HalpMceHandlerCore+0xe8
ffffd000`8c60aa40 fffff800`9949e2c6 : 00000000`0000000c 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
ffffd000`8c60aa80 fffff800`9949e450 : ffffe001`24ad13f0 ffffd000`8c60acb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
ffffd000`8c60aab0 fffff800`98d6d67b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffffd000`8c60aae0 fffff800`98d6d431 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffffd000`8c60ac20 fffff800`9947cf5f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
ffffd000`8c62a858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalProcessorIdle+0xf


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  0x124_GenuineIntel_PROCESSOR_CACHE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_processor_cache

FAILURE_ID_HASH:  {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}

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

6: kd> !errrec ffffe00125b25028
===============================================================================
Common Platform Error Record @ ffffe00125b25028
-------------------------------------------------------------------------------
Record Id     : 01d0d780242cc365
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/15/2015 17:30:58 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306e4
Processor ID  : 0x0000000000000006

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

Local APIC Id : 0x0000000000000006
CPU Id        : e4 06 03 00 00 08 20 06 - bf e3 be 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  @ ffffe00125b25240

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

Error         : GCACHEL2_ERR_ERR (Proc 6 Bank 19)
  Status      : 0xbe200000000b110a
  Address     : 0x000000085fcdab00
  Misc.       : 0xbcfe2050881c4086

STOP 0x124 Troubleshooting blue screen issue

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. Prime95 - Stress Test Your CPU - Windows 10 Forums

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. MemTest86+ - Test RAM - Windows 10 Forums

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. FurMark - GPU Stress Test - Windows 10 Forums

Note

Run Furmark for around 30 minutes.

Warning