Solved BSOD running COD4:MW2 in Single Player

[chisser98]

Hey guys,

I keep getting the BSOD when running MW2 in Single Player (haven't tried MP yet). It goes to BSOD then reboots my machine. I've updated my video card drivers and ended my Anti-Virus scanner's process (AVG 9 Free Edition) but to no avail.

I've completed the steps in the BSOD Posting Instructions (http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html). I would love some help on this issue

System (Custom Built):
Windows 7 Home Premium 64bit OEM DVD
- Installed myself
- System is about 2 months old
- Installed OS about 2 months ago
- No other known problems (played StarCraft 2, Half-Life 2, Left 4 Dead 2, Minecraft, etc. without incident)
Intel i7 960 @ 3.20GHz
ASUS P6T Motherboard
Corsair 12GB DDR3 RAM 1333MHz (6 x 2048MB)
Radeon HD 5850 - 1GB GDDR5
LG Flatron 23" Monitor
WD Caviar Black 500GB, 7200RPM, 32MB
Corsair TX750W 750-Watt Power Supply - ATX
Cooler Master HAF 932 Full Tower
On-Board Case Cooling

Thanks all

Jarrett

 

[zigzag3143]

Hey guys,

I keep getting the BSOD when running MW2 in Single Player (haven't tried MP yet). It goes to BSOD then reboots my machine. I've updated my video card drivers and ended my Anti-Virus scanner's process (AVG 9 Free Edition) but to no avail.

I've completed the steps in the BSOD Posting Instructions (http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html). I would love some help on this issue

System (Custom Built):
Windows 7 Home Premium 64bit OEM DVD
- Installed myself
- System is about 2 months old
- Installed OS about 2 months ago
- No other known problems (played StarCraft 2, Half-Life 2, Left 4 Dead 2, Minecraft, etc. without incident)
Intel i7 960 @ 3.20GHz
ASUS P6T Motherboard
Corsair 12GB DDR3 RAM 1333MHz (6 x 2048MB)
Radeon HD 5850 - 1GB GDDR5
LG Flatron 23" Monitor
WD Caviar Black 500GB, 7200RPM, 32MB
Corsair TX750W 750-Watt Power Supply - ATX
Cooler Master HAF 932 Full Tower
On-Board Case Cooling

Thanks all

Jarrett

Jarrett

Three of 4 point to your video driver directly. the fourth indirectly.

Re-install the video driver

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

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\Windows_NT6_BSOD_jcgriff2\103110-18954-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c68000 PsLoadedModuleList = 0xfffff800`02ea5e50
Debug session time: Sun Oct 31 01:58:46.723 2010 (GMT-4)
System Uptime: 0 days 1:45:26.817
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8b60916a9d0, 0, fffff8800439205b, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b )

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

4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8b60916a9d0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800439205b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f100e0
 fffff8b60916a9d0 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`0439205b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88002807740 -- (.trap 0xfffff88002807740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8b60916a9d0 rbx=0000000000000000 rcx=fffff8a00916a9e8
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800439205b rsp=fffff880028078d0 rbp=000000000076786c
 r8=0000000000000003  r9=0000000000000003 r10=0000000000000018
r11=fffffa800bdd63c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b:
fffff880`0439205b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp ds:0002:fffff8b6`0916a9d0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d578c1 to fffff80002cd8740

STACK_TEXT:  
fffff880`028075d8 fffff800`02d578c1 : 00000000`00000050 fffff8b6`0916a9d0 00000000`00000000 fffff880`02807740 : nt!KeBugCheckEx
fffff880`028075e0 fffff800`02cd682e : 00000000`00000000 fffff8a0`0916c4b0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`02807740 fffff880`0439205b : fffff8a0`0916c4b0 fffffa80`0a71c940 fffffa80`0bdd5000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`028078d0 fffff880`0438f8af : 00000000`00000000 fffffa80`0a483220 00000000`000000a0 fffffa80`0a4b7668 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x10b
fffff880`02807910 fffff880`043a965d : 00000000`00000000 fffff8a0`0b153cc0 fffffa80`00000000 fffffa80`0a3cd910 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`02807ae0 fffff880`043a9398 : fffff800`0401a080 fffff880`043a8d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`02807cd0 fffff880`043a8e96 : 00000000`00000000 fffffa80`09f6fc00 00000000`00000080 fffffa80`09d80410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`02807d00 fffff800`02f7cc06 : 00000000`02f391dd fffffa80`0bae0b60 fffffa80`09d40040 fffffa80`0bae0b60 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`02807d40 fffff800`02cb6c26 : fffff800`02e52e80 fffffa80`0bae0b60 fffff800`02e60c40 fffff880`01251534 : nt!PspSystemThreadStartup+0x5a
fffff880`02807d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b
fffff880`0439205b 48392cf0        cmp     qword ptr [rax+rsi*8],rbp

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+10b

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

 

[AstaLaVista]

Patch the game if you haven't done so yet.

Make sure you uninstall the drivers from Control Panel or Device Manager, then make sure you also Uninstall the PhysX drivers. Restart to safe mode and run the sweeper.

Update your Audio drivers while you are at it.

Reboot and Install fresh drivers with Elevated Admin Rights (right click file Run as Admin).

Don't let Win 7 update your drivers.

 

[chisser98]

Hi KEn and AstaLaVista,

Thanks for the info - works like a charm now! Haven't had a BSOD yet after re-installing the ATI drivers. I appreciate the help!

Just out of curiosity, any idea what would cause the drivers to screw up? I mean, I just installed them after a fresh Win 7 installation..very wierd.

Anyway, thanks again guys!

Cheers

Jarrett

 

[AstaLaVista]

Well, two things I have noticed and I am not a PC Guru by any stretch of the imagination but I do play a lot of games.

Windows drivers From Windows Update seem to be sucky drivers so I upgrade by downloading a fresh copy from the source (ATI or Nvidia)

Drivers get corrupted very easily this days so from time to time, every time I install a Game, new or old (I tend to replay my games from time to time), I notice something wrong so I just make a habit of downloading and refreshing my drivers.

Now, since I only do SP Campaigns, I don't bother patching but since you mentioned MP, I thought patching could help.

 

[chisser98]

hmm, never thought of windows updating the drivers itself. Pain in the buttocks!

Thanks again!

Happy gaming