0x124 bugchecks are caused by detection of faulty hardware.
Lets take a look.
Code:
BugCheck [COLOR="Red"]124[/COLOR], {[COLOR="Blue"]0[/COLOR], [COLOR="Green"]fffffa8004cc18f8[/COLOR], 0, 0}
What does this all mean?
Well the number in
red is the bugcheck code which I've just mentioned.
The
blue number is null which means a
Machine Check Exception occurred, this indicates the CPU found a fault with a hardware piece then sends out the
KeBugCheckEx routine which is your BSOD.
The
green text is the address where the
WHEA Error Record is contained.
WHEA stands for
Windows Hardware Error Architecture.
Lets take a look and see if we can find the hardware piece causing the issue.
Code:
0: kd> [COLOR="green"]!errrec fffffa8004cc18f8[/COLOR]
===============================================================================
Common Platform Error Record @ fffffa8004cc18f8
-------------------------------------------------------------------------------
Record Id : 01cf78c235dcb909
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : [COLOR="Blue"]Machine Check Exception[/COLOR]
Timestamp : 5/26/2014 9:09:42 (UTC)
Flags : 0x00000002 PreviousError
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa8004cc1978
Section @ fffffa8004cc1a50
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : BUS error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000600f20
Processor ID : 0x0000000000000005
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa8004cc19c0
Section @ fffffa8004cc1b10
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000005
CPU Id : 20 0f 60 00 00 08 06 05 - 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 @ fffffa8004cc1b10
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8004cc1a08
Section @ fffffa8004cc1b90
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : [COLOR="Red"]BUSLG_GENERIC_ERR_*_NOTIMEOUT_ERR[/COLOR] (Proc 5 Bank 5)
Status : 0xb480000000040e0f
Address : 0x0000000000000002
Misc. : 0x0000000000000000
As you can see, there's the machine check exception, now it looks like your graphics card is failing.
We can test this by running Furmark.
Stress test your graphics card with Furmark
I recommend running it for around 30 minutes
Warning
Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures
I also noticed a 0x101 bugcheck, meaning a processor was hung and not able to perform interrupt requests so the system bugcheck.
Code:
BugCheck [COLOR="Red"]101[/COLOR], {21, 0, fffff880009b3180, 4}
Probably caused by : Unknown_Image ( [COLOR="red"]ANALYSIS_INCONCLUSIVE[/COLOR] )
The reason it says analysis inconclusive is because we cannot analyse 0x101 errors at all on minidumps, we need Kernel Memory Dumps.
This is because the processor hung did not call the KeBugCheckEx function, rather another processor did and because minidumps contain only the processor that called the KeBugCheckEx function we cannot find the cause.
I think for the time being we should leave this and see how Furmark does.
This is a little bit of an analysis though.
Code:
BugCheck [COLOR="red"]101[/COLOR], {[COLOR="Red"]21[/COLOR], 0, [COLOR="blue"]fffff880009b3180[/COLOR], [COLOR="green"]4[/COLOR]}
Alright, basically windows use a technique that calls all the processors and asks them to answer, it's a way of synchronizing all the processors, when one doesn't respond the system bugchecks.
The first parameter is how many ticks it took until the timeout which caused the system to bugcheck.
The third parameter is the Processor Control Block address for the hung processor which contains information such as pointers to the current thread be executed.
The fourth parameter generally indicates the processor that was hung which in this case it is the fourth one.
