BSOD playing CS:GO, error 0x00000124

Hello Everyone,

I have frequent 0x00000124 errors. I know these are not easy to overcome and I would greatly appreciate the help of a tech guru to help me understand my crash dump and where I should put my effort.

So far I have tried these steps:

Fresh copy of win7 on my sata drive instead of SSD
I did a memtest stress test and no error came up.

I don't see this error when I use my computer to browse the web or watch movies. It is most of the time when I am playing games. I have a huge heat sink with a dual 120mm fans over my cpu and a lot of 120mm for the rest of the case... I don't really suspect overheating. I did not try to overclock any of my components, everything is on factory settings.

Thanks for your much needed help.

The problem is the hardware, run SeaTools for DOS and Windows and Furmark.
SeaTools for DOS and Windows - How to Use
Video Card - Stress Test with Furmark

I have established that it is a problem with the hardware and before I just in all the stress tests. I'm looking for someone knowledgeable enough to read my crash dump and tell me who is the culprit. I have this issue for over 6 months and I did extensive research on google, some blame the PSU some the CPU other the GPU.

I did some more digging and I was able to extract the error for the bug check report:

0: 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: fffffa800f9f9028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200119, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: csgo.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff800`00ba8a98 fffff800`03418a3b : 00000000`00000124 00000000`00000000 fffffa80`0f9f9028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02fab713 : 00000000`00000001 fffffa80`0fa76a60 00000000`00000000 fffffa80`0fa76ab0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`03418700 : 00000000`00000728 fffffa80`0fa76a60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`03418052 : fffffa80`0fa76a60 fffff800`00ba8e70 fffffa80`0fa76a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`03417f0d : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`0340be88 : 00000000`21f42f34 00000000`21f42f28 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02e927ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02e92613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`1d7f5c69 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`00346760 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1d7f5c69


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner



Should I suspect my CPU based on this information ? Could the thermal paste gone bad and my CPU is overheating or I should change it ? I guess I have to suspect the CPU Socket as well... so the motherboard... any advices ?

Update: I said that I was not overclocking, but doing a !sysinfo cpuspeed I found out my 3400mhz to be running at 3500mhz looks like my Asus P8P67 motherboard is using a turbo mode feature by default and this feature will try to max out the capacity of the CPU. I will now run the game for a few hours to see if the issue is coming back.

Thx...

Okay, but the dump clearly blames the hardware. Thats why we will run the stress tests because it will find out who is failing.

Laith thanks for your help, but saying that the error is blaming the hardware for me is the same as saying something is wrong with your car, probably a part in it ! Go do circle until it fails... I think I can get more for the dump that just pointing vaguely to hardware that's all I am saying.

I understand what you are saying, i wish that too.
If someday in the future that the dumps will write which one is failing so it will be much easier to troubleshoot rather than running a dozen of stress tests or fixes.

Since, the overclocking was removed. I have not witnessed another crash.

Oh so the overclocking was the issue. Good for you!