COD4 BSOD, Minidump info inside

[SylEm]

Was playing COD4 and about 20 mins into the game I got a BSOD. (its been happening frequently) Here's the dump info that was requested:

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


Loading Dump File [C:\Windows\Minidump\Mini011209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\debug*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x82042000 PsLoadedModuleList = 0x82159c70
Debug session time: Mon Jan 12 11:01:31.701 2009 (GMT-8)
System Uptime: 1 days 14:05:34.402
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
................
Unable to load image ha10kx2k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000BE, {912d6040, 2f40121, 9cc09a3c, a}

*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
Probably caused by : ha10kx2k.sys ( ha10kx2k+51a5b )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 912d6040, Virtual address for the attempted write.
Arg2: 02f40121, PTE contents.
Arg3: 9cc09a3c, (reserved)
Arg4: 0000000a, (reserved)

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xBE

PROCESS_NAME: audiodg.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 9128b9ab to 9127ca5b

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
9cc09ab4 9128b9ab 864b3cd0 863d60c0 87af9008 ha10kx2k+0x51a5b
9cc09ac8 9128b42f 866b3cbc 863d60c0 866b3ce4 ha10kx2k+0x609ab
9cc09adc 9128c5e1 866b3cbc 86581864 86581790 ha10kx2k+0x6042f
9cc09af4 8b95fa9f 863d60c0 86581790 9cc09b38 ha10kx2k+0x615e1
9cc09b04 8b9607f2 88619548 8658184c 8bbd3000 ctaud2k+0x6a9f
9cc09b38 8b960929 87cf85b8 8579d538 8bbd3000 ctaud2k+0x77f2
9cc09b4c 8b95dd93 86581790 9cc09b68 8bbcbaec ctaud2k+0x7929
9cc09b58 8bbcbaec 8579d538 8bbcf348 9cc09b8c ctaud2k+0x4d93
9cc09b68 8bbd958a 87cf85b8 852b04a0 00000701 portcls!CPortPinWavePci::IrpSubmitted+0x66
9cc09b8c 8bbe26f9 00000000 852b04a0 00000701 portcls!CIrpStream::TransferKsIrp+0x2d4
9cc09bc0 8bbd4060 00000000 86ad1878 852b04a0 portcls!CPortPinWavePci:eviceIoControl+0xd6
9cc09be0 82725246 86ad1930 852b04a0 9cc09c08 portcls!DispatchDeviceIoControl+0x5b
9cc09bf0 8bbd9d73 86ad1878 852b04a0 887d4948 ks!KsDispatchIrp+0xa5
9cc09c08 8bbda908 86ad1878 852b04a0 9cc09c2c portcls!KsoDispatchIrp+0x43
9cc09c18 8b9acc8d 86ad1878 852b04a0 86ad1878 portcls!PcDispatchIrp+0x2d
9cc09c2c 820fdfd3 86ad1878 852b04a0 852b04a0 ctaud2k+0x53c8d
9cc09c44 8228e615 887d4948 852b04a0 852b0534 nt!IofCallDriver+0x63
9cc09c64 8228edba 86ad1878 887d4948 00000000 nt!IopSynchronousServiceTail+0x1d9
9cc09d00 82278a8d 86ad1878 852b04a0 00000000 nt!IopXxxControlFile+0x6b7
9cc09d34 82099a1a 0000027c 000001b0 00000000 nt!NtDeviceIoControlFile+0x2a
9cc09d34 778f9a94 0000027c 000001b0 00000000 nt!KiFastCallEntry+0x12a
00dffa34 00000000 00000000 00000000 00000000 0x778f9a94


STACK_COMMAND: kb

FOLLOWUP_IP:
ha10kx2k+51a5b
9127ca5b c78028010000feffffff mov dword ptr [eax+128h],0FFFFFFFEh

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ha10kx2k+51a5b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ha10kx2k

IMAGE_NAME: ha10kx2k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45d050cd

FAILURE_BUCKET_ID: 0xBE_ha10kx2k+51a5b

BUCKET_ID: 0xBE_ha10kx2k+51a5b

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

Anyone have any ideas?

 

[mpilchfamily]

Does this happen with any other game or program?

COD4 has been known to crash allot and have problems. So if its only occuring in that game then its the game not your system. Just make sure you have all the recent patches for the game. If it is happening elsewhere then you may have a problem with the video card. Be it hardware or driver issue. Best bet is to reinstall the drivers.

 

[SylEm]

Not just cod4 but also in bioshock and left4dead. It also, but rarely, happens in wow.

 

[SylEm]

Drivers are fully up to date on all my hardware

 

[SylEm]

any ideas?

 

[krnmastersgt]

Please don't make multiple threads about the same topic/idea/problem.

 

[dclive]

Originally posted by: SylEm
any ideas?

Read the debug guide on my web page; what is the ha...sys file that is crashing? Figure out what that is then post what it's the driver for; that is currently seen (in this dump) as the culprit.