0x124 BSOD while playing MoH Airborne

Hello,

I recently built a new system with Win 7 x64 (clean install). When I play my favorite game, Medal of Honor Airborne, I get a BSOD with an 0x124 error within 5-15 minutes. COD WaW seems to play fine. Everything that I have read tells me that 0x124 is a hardware issue that is hard to diagnose, which is why I'm posting here... I need some expert help.

My system is:

Gigabyte GA-X58A-UD3R motherboard
Intel i7 930 CPU with stock cooler that came with CPU
6GB [3x 2GB Corsair triple channel kit of DDR3 1600 (PC3 12800)]
twin MSI N260GTX Twin Frozr OC Geforce GTX 260 as SLI
Antec TP-750 power supply
Seagate Barracuda 1TB SATA2 hard drive
Windows 7 x64 Professional

Nothing is overclocked. I have two of the video cards, and I had them both in, running SLI. CPU never goes above 46 oC. I have installed the latest motherboard, device, and video drivers from the web.

What I have done so far:
- Video Cards. I have swapped them around, remove one and then the other. Ran with only one in the x16_1 slot; then ran with only one in the x16_2 slot.
- Ran MemTest86+. No reported issues.
- Ran the MSI Kombustor graphics test program for 35 minutes. GPU temp stabilized at 75 oC with 35% GPU fan speed. CPU temp never moved above 44 oC.
- Power supply. The TP-750 has four +12V rails of 40A (according to Antec). Each video card needs two 6-pin PCI-E, and I have 4 of those; I have tried every combination of two for the graphics card.
- Ran SFC /scannow. No issues.

I'm at a total loss as it only seems to happen when playing that one game. Everything else that I do on it seems to be fine. When playing Airborne, I Win-D out of it and check the CPU temp and GPU temps and nothing is in the red.

I've attached the last mini-dump for the forum experts to review and hopefully shed some light for me.

takker said:

Hello,

I recently built a new system with Win 7 x64 (clean install). When I play my favorite game, Medal of Honor Airborne, I get a BSOD with an 0x124 error within 5-15 minutes. COD WaW seems to play fine. Everything that I have read tells me that 0x124 is a hardware issue that is hard to diagnose, which is why I'm posting here... I need some expert help.

My system is:

Gigabyte GA-X58A-UD3R motherboard
Intel i7 930 CPU with stock cooler that came with CPU
6GB [3x 2GB Corsair triple channel kit of DDR3 1600 (PC3 12800)]
twin MSI N260GTX Twin Frozr OC Geforce GTX 260 as SLI
Antec TP-750 power supply
Seagate Barracuda 1TB SATA2 hard drive
Windows 7 x64 Professional

Nothing is overclocked. I have two of the video cards, and I had them both in, running SLI. CPU never goes above 46 oC. I have installed the latest motherboard, device, and video drivers from the web.

What I have done so far:
- Video Cards. I have swapped them around, remove one and then the other. Ran with only one in the x16_1 slot; then ran with only one in the x16_2 slot.
- Ran MemTest86+. No reported issues.
- Ran the MSI Kombustor graphics test program for 35 minutes. GPU temp stabilized at 75 oC with 35% GPU fan speed. CPU temp never moved above 44 oC.
- Power supply. The TP-750 has four +12V rails of 40A (according to Antec). Each video card needs two 6-pin PCI-E, and I have 4 of those; I have tried every combination of two for the graphics card.
- Ran SFC /scannow. No issues.

I'm at a total loss as it only seems to happen when playing that one game. Everything else that I do on it seems to be fine. When playing Airborne, I Win-D out of it and check the CPU temp and GPU temps and nothing is in the red.

I've attached the last mini-dump for the forum experts to review and hopefully shed some light for me.

You seem to have covered most the bases, but have a hardware problem. I dont know if you have read this but give it shot and if it doesnt help feel free to PM Me. https://www.sevenforums.com/crash-loc...-what-try.html

Let me know if you help

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\031410-26192-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c13000 PsLoadedModuleList = 0xfffff800`02e50e50
Debug session time: Sun Mar 14 03:58:45.170 2010 (GMT-4)
System Uptime: 0 days 0:08:18.263
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80087f4028, b6000000, 200001}

Probably caused by : hardware

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

4: 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: fffffa80087f4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6000000, 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:  PnkBstrB.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009b9b58 fffff800`03202903 : 00000000`00000124 00000000`00000000 fffffa80`087f4028 00000000`b6000000 : nt!KeBugCheckEx
fffff880`009b9b60 fffff800`02d99513 : 00000000`00000001 fffffa80`087a1250 00000000`00000000 fffffa80`087a12a0 : hal!HalBugCheckSystem+0x1e3
fffff880`009b9ba0 fffff800`032025c8 : 00000000`00000728 fffffa80`087a1250 fffff880`009b9f30 fffff880`009b9f00 : nt!WheaReportHwError+0x263
fffff880`009b9c00 fffff800`03201f1a : fffffa80`087a1250 fffff880`009b9f30 fffffa80`087a1250 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009b9d50 fffff800`03201dd5 : 00000000`00000008 00000000`00000001 fffff880`009b9fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009b9d90 fffff800`031f5e88 : 00000000`00000002 00000000`00001000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009b9dc0 fffff800`02c837ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009b9df0 fffff800`02c83613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009b9f30 fffff800`02c7bcf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0895a778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcpy+0xb4


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

Takker


If none of these help we need to get more aggressive by using driver verifier. Before we do you need to make a backup and have a Win 7 dvd.

Let me know if and when you need to do that


Ken

zigzag3143,

Thanks for providing the "plain english" version of the mini-dump. I see a reference to Punkbuster B (PnkBstrB.exe) in the debugging details section. Would it be correct to say that this may have caused the BSOD or been the active process when the crash happened?


Debugging Details:
------------------
BUGCHECK_STR: 0x124_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: PnkBstrB.exe
CURRENT_IRQL: f

Trakker


Upon futher analysis I found that PnkBstrB,exe was involved. You might want to un-install it and re-install a new copy.

Ken

zigzag3143,

What program do you use to view the mini-dumps?

Update:

I suffered through several more days of 0x124 BSOD while playing MoH Airborne. I re-loaded the Win7 Pro x64 OS, but that made no difference.

Last night I updated the motherboard (Gigabyte GA-X58A-UD3R motherboard) BIOS to the latest F5 version, and that seems to have ended the BSOD issue.

I have been able to play MoH Airborne in two sessions now for more than an hour, whereas before I was getting kicked by 0x124 BSOD within 5-15 minutes each time.

takker said:

zigzag3143,

What program do you use to view the mini-dumps?

I use several. Blue screen view, win debugger, etc. If you are interested in learning feel free to PM me. Ken

I was able to get win debugger loaded after I did some more searching and reading on these forums - they are a great help!

Thank you very much for your help!