Stop: 0x00000124

Erebus · 26 Jun 2011

Stop: 0x00000124 (0x0000000000000000, 0xfffffa800ac4a028, 0x00000000bf800000, 0x0000000000200001)

See attached dump files.

BSOD only occurs when running Battlefield: Bad company 2 (Steam) in multiplayer mode (fine in single-player). It seems to be independent of clocking (I set everything to stock when it first started, not that it was aggressively clocked).

I Have tried backing down the GFX levels but it still crashes. (With GFX on low CPU runs at about 40% and GPU's run about 30-50%). I worry abt temps as I am still running stock but with everything on low CPU and GPU's are < 60C.

All drivers are up to date.

System Specs:
OS: Windows 7 home premium 64bit oem
CPU: i7 2600k sandy bridge
Motherboard: Gigabyte: P67A-UD7-B3
Memory: 12GB (3X4GB) PC3, Patriot sector 7, Viper II
Graphics Card(s): 2X Radeon HD 6970 running in crossfire
Sound Card: On the motherboard
Monitor(s) Displays: Acer B243H and Acer V223W
Screen Resolution: 1920X1080 and 1680X1050
Hard Drives: SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal PSU: OCZ ZX Series 1250W Fully-Modular 80PLUS Gold High Performan
Case: COOLER MASTER HAF X RC-942-KKN1 Black Steel
Cooling: Stock
Keyboard: Dell usb
Mouse: Logitech thumb ball
Internet Speed: 12.5MB/sec

yowanvista · 27 Jun 2011

Its a hardware error caused by defective components/outdated BIOS
Stop overclocking
Stop 0x124 - what it means and what to try

Information

Run Prime 95 again to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa800b3be028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000200001, 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:  BFBC2Game.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f4b58 fffff800`03215a3b : 00000000`00000124 00000000`00000000 fffffa80`0b3be028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`009f4b60 fffff800`02da7563 : 00000000`00000001 fffffa80`0aa1b830 00000000`00000000 fffffa80`0aa1b880 : hal!HalBugCheckSystem+0x1e3
fffff880`009f4ba0 fffff800`03215700 : 00000000`00000728 fffffa80`0aa1b830 fffff880`009f4f30 fffff880`009f4f00 : nt!WheaReportHwError+0x263
fffff880`009f4c00 fffff800`03215052 : fffffa80`0aa1b830 fffff880`009f4f30 fffffa80`0aa1b830 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f4d50 fffff800`03214f0d : 00000000`00000008 00000000`00000001 fffff880`009f4fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f4d90 fffff800`03208e88 : 00000000`0005691a 00000000`34ee7880 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f4dc0 fffff800`02c985ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f4df0 fffff800`02c98453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f4f30 00000000`7105de61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`10bafd6c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7105de61


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

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

Erebus · 28 Jun 2011

I stopped OC when the BSOD first started. Max it was ever clocked to was multiplier of 40.

Last night before I read your post I was testing/playing BFBC2 multiplayer (it really only happens in multiplayer, I even maxed it out in single player with no errors, no other program has ever given me a BSOD) again and it crashed but this time windows did not recover properly. After using the restore point I still get an error of:
"Could not load file or assembly 'shortkey.nlp' or one of its dependencies. The system cannot find the file specified."
Whenever I start catalyst control center.
I will likely just reformat the drive later this week to start with a blank slate.

With that said I started prime95 last night running the Small FFT's test. I stopped after about 10 minutes because CPU temp crept above 70C (max I feel comphy with right now). I am looking into some cooling options.

Today is colder out so I opened the window with a fan in it. I have been running the Small FFT's test for about 2 hours without errors. Temp is staying steady at 65C. I don't think I want to run it without watching it so I guess after work tomorrow I will try a different test and run some long ones over the weekend.