BSOD when starting COD MW2

[seadooin]

I have been getting a BSOD when i try to start MW2 as the title says. I have double checked to make sure all of my ram, gpu's are seated correctly. I have read else where that people had a problem with ATi's CCC running at the same time. The dump files (attached) point to a hardware issue, just can't figure it out. Any help would be great!


Specs
win 7 64bit
i7 960 cpu
6gigs ram 1600
1000watt psu
Two 5850 GPU's

 

[zigzag3143]

I have been getting a BSOD when i try to start MW2 as the title says. I have double checked to make sure all of my ram, gpu's are seated correctly. I have read else where that people had a problem with ATi's CCC running at the same time. The dump files (attached) point to a hardware issue, just can't figure it out. Any help would be great!


Specs
win 7 64bit
i7 960 cpu
6gigs ram 1600
1000watt psu
Two 5850 GPU's

This one was caused by hardware. use these to try and identify which. http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Let us know if you need help


Ken

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


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

Symbol search path is: SRV*d:\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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Wed Feb 10 18:13:18.190 2010 (GMT-5)
System Uptime: 0 days 0:00:09.252
Loading Kernel Symbols
...............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8006ad88f8, 0, 0}

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: fffffa8006ad88f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, 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:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`033776f0 fffff800`030d3a89 : fffffa80`06ad88d0 fffffa80`05b25680 fffff8a0`00000005 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03377c10 fffff800`02fb5547 : fffffa80`06ad88d0 fffff800`0302e5f8 fffffa80`05b25680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03377c40 fffff800`02f1db95 : fffff800`03090360 fffffa80`06aca898 fffffa80`06aca890 fffffa80`05b25680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03377c80 fffff800`02e98161 : fffff880`01113e00 fffff800`02f1db70 fffffa80`05b25680 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03377cb0 fffff800`0312e166 : 01ca0444`e48124c2 fffffa80`05b25680 00000000`00000080 fffffa80`05a919e0 : nt!ExpWorkerThread+0x111
fffff880`03377d40 fffff800`02e69486 : fffff880`03186180 fffffa80`05b25680 fffff880`031910c0 00000000`00580068 : nt!PspSystemThreadStartup+0x5a
fffff880`03377d80 00000000`00000000 : fffff880`03378000 fffff880`03372000 fffff880`03f49540 00000000`00000000 : nt!KxStartSystemThread+0x16


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_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

 

[seadooin]

Thanks for the quick reply Zig! I did see that other post before and have tried most of those fixes. I am wondering if I have a bad 5850 card. This computer is not even a month old! Am I crazy for thinking a brand new computer should not be having problems like? I am going to contact the company that built it and see what they say, maybe they will send some replacement parts.

 

[seadooin]

So, it turns out that the problem was a bad mb. the first pci express slot is bad. when not using said slot, all problems go away. in the process of sending computer back to supplier...