Random BSOD while playing MW2, error 0x00000124

[kingsface]

Hello everybody ! I've been browsing this forum in the past but decided to make an account today. I need help with a BSOD that I've started getting a few times.

This error arises only when playing MW2 ONLY and that too randomly ! At other times I play mw2 without any problem whatsoever.

Other more taxing games and benchmarks run perfectly fine !
eg. Crysis 2, Bad Company 2, Unigine Heaven Benchmark, Alien vs Predator Benchmark and nearly every other game I have.

CPU is overclocked at 4.5Ghz with max temps 65 to 67C, is p95 stable, checked atleast for an hour.
GSkill 8GB Rams are at stock 1600Mhz. GPU clocks are at stock. Using latest Nvidia drivers 280.36. Nearly every component is relatively new, only 2 months old.

Attached are the dump files and perfmon.html files as outlined in the sticky BSOD thread.

Really appreciate if anybody could help identifying the cause. I just hope it's not faulty hardware. I can play more taxing games without any problem. Heck I even played Battlefield 3 Alpha trial without any problem!

Thanks alot in advance !

 

[yowanvista]

Seems to be caused by your CPU being unstable
http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
This is a hardware error

*******************************************************************************
*                                                                             *
*                        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: fffffa8009bc8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iw4mp.dat

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`0336ca58 fffff800`033f1903 : 00000000`00000124 00000000`00000000 fffffa80`09bc8028 00000000`be200000 : nt!KeBugCheckEx
fffff880`0336ca60 fffff800`02f89293 : 00000000`00000001 fffffa80`09bc9d30 00000000`00000000 fffffa80`09bc9d80 : hal!HalBugCheckSystem+0x1e3
fffff880`0336caa0 fffff800`033f15c8 : 00000000`00000728 fffffa80`09bc9d30 fffff880`0336ce30 fffff880`0336ce00 : nt!WheaReportHwError+0x263
fffff880`0336cb00 fffff800`033f0f1a : fffffa80`09bc9d30 fffff880`0336ce30 fffffa80`09bc9d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`0336cc50 fffff800`033f0dd5 : 00000000`00000004 00000000`00000001 fffff880`0336ceb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`0336cc90 fffff800`033e4e88 : 00000000`00000000 00000000`000002bc 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`0336ccc0 fffff800`02e71e6c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0336ccf0 fffff800`02e71cd3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0336ce30 00000000`76cc0aa4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0e2ffed4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76cc0aa4


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
---------

 

[kingsface]

Thanks for the reply. So the dump files also confirm that CPU oc is unstable or is it the generic cause of 0x124 error ? I am going to lower the oc and raise the vcore hopefully in an attempt to get it stable. Would appreciate the answer to this question also as well.

 

[yowanvista]

Thanks for the reply. So the dump files also confirm that CPU oc is unstable or is it the generic cause of 0x124 error ? I am going to lower the oc and raise the vcore hopefully in an attempt to get it stable. Would appreciate the answer to this question also as well.

Don't push your CPU clocks too much. Dumps confirmed your CPU as the cause
Check if it still BSODs at stock settings

 

[kingsface]

Thanks for the reply. Am trying lower cpu clocks now. Will check for stability and report back.