Vista BSOD in-game.

[dds14u]

I've been getting a lot of in-game BSODs lately while playing Warcraft III (happens as early as 5 minutes into a game).

I downloaded MSFT's debugger tool and below I have the details. It seems like the culprit is dxgkrnl.sys, but I'm not sure how to resolve this...

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00204720, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00004720, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 83b73868
Unable to read MiSystemVaType memory at 83b53420
00204720

CURRENT_IRQL: 0

FAULTING_IP:
+4720
00004720 ?? ???

PROCESS_NAME: war3.exe

ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.

BUGCHECK_STR: DISABLED_INTERRUPT_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

TRAP_FRAME: ade2c6fa -- (.trap 0xffffffffade2c6fa)
ErrCode = 00000010
eax=882215b8 ebx=00000000 ecx=a7a59b28 edx=00000002 esi=aa947008 edi=88014000
eip=00004720 esp=ade2c76e ebp=ade2c780 iopl=0 nv up di pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
00004720 ?? ???
Resetting default scope

UNALIGNED_STACK_POINTER: ade2c6e2

LAST_CONTROL_TRANSFER: from 00004720 to 83a96d24

STACK_TEXT:
ade2c6fa 00004720 badb0d00 00000002 d30087fa nt!KiTrap0E+0x2ac
WARNING: Frame IP not in any known module. Following frames may be wrong.
ade2c76a 0008002a d0440246 40008684 00008801 0x4720
ade2c780 8993ef86 882215b8 00000000 00000000 0x8002a
ade2c7e0 89940dd3 ac105058 00000000 86999f60 dxgkrnl!VIDMM_GLOBAL:repareDmaBuffer+0x1b9
ade2c8e8 8993e930 85fd5648 87f2d378 ade2c928 dxgkrnl!VidSchiSubmitRenderCommand+0x126
ade2c8f8 899209a1 85fd5648 85fd5648 86e07e18 dxgkrnl!VidSchiSubmitQueueCommand+0x61
ade2c928 8993e876 87fab000 ade2c94c 86e07e18 dxgkrnl!VidSchiSubmitQueueCommandDirect+0x1ae
ade2c950 89940a3d 01fd5648 8e9f3100 9cc559e8 dxgkrnl!VidSchiSubmitCommandPacketToQueue+0x171
ade2c974 8994464a 86e07e18 ade2ca94 00000000 dxgkrnl!VidSchSubmitCommand+0x2bf
ade2cb90 89943f30 ade2cbac 24717f3a 0012f684 dxgkrnl!DXGCONTEXT::Render+0x513
ade2cd58 83a93a1a 0012f684 0012f7c8 77479a94 dxgkrnl!DxgkRender+0x272
ade2cd58 77479a94 0012f684 0012f7c8 77479a94 nt!KiFastCallEntry+0x12a
0012f7c8 00000000 00000000 00000000 00000000 0x77479a94


STACK_COMMAND: kb

FOLLOWUP_IP:
dxgkrnl!VIDMM_GLOBAL:repareDmaBuffer+1b9
8993ef86 3bc3 cmp eax,ebx

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: dxgkrnl!VIDMM_GLOBAL:repareDmaBuffer+1b9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4893b1df

FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_dxgkrnl!VIDMM_GLOBAL:repareDmaBuffer+1b9

BUCKET_ID: DISABLED_INTERRUPT_FAULT_dxgkrnl!VIDMM_GLOBAL:repareDmaBuffer+1b9

Followup: MachineOwner

 

[mpilchfamily]

I'm pretty sure its a compatibility issue between the game and Vista. Just like when you try to play an old 8 bit BOS based game on XP. Compatibility modes can only do so much.

 

[dclive]

Originally posted by: mpilchfamily
I'm pretty sure its a compatibility issue between the game and Vista. Just like when you try to play an old 8 bit BOS based game on XP. Compatibility modes can only do so much.

Interesting. Where do you see that in the debugger output?

 

[dclive]

Originally posted by: dds14u

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4893b1df

Running all Windows updates?
Running the latest driver from ATI/nVidia?

 

[dds14u]

Originally posted by: dclive

Originally posted by: dds14u

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4893b1df

Running all Windows updates?
Running the latest driver from ATI/nVidia?

Check and check.

My ATI driver is from December.

Any other ideas?

Before this, Vista had been pretty darn reliable in terms of not crashing.

 

[dclive]

Give me output from more crashes. Post a few more here.

 

[dds14u]

Here is another:
PAGE_FAULT_BEYOND_END_OF_ALLOCATION (cd)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 8d335000, memory referenced
Arg2: 00000000, value 0 = read operation, 1 = write operation
Arg3: 83a13926, if non-zero, the address which referenced memory.
Arg4: 00000000, Mm internal code.

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

Unable to load image \SystemRoot\system32\DRIVERS\ATITool.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ATITool.sys
*** ERROR: Module load completed but symbols could not be loaded for ATITool.sys

OVERLAPPED_MODULE: Address regions for 'ssmdrv' and 'kbdhid.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from 83b3b868
Unable to read MiSystemVaType memory at 83b1b420
8d335000

FAULTING_IP:
nt!wcsrchr+a
83a13926 668b08 mov cx,word ptr [eax]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR: 0xCD

PROCESS_NAME: System

CURRENT_IRQL: 0

TRAP_FRAME: 80399960 -- (.trap 0xffffffff80399960)
ErrCode = 00000000
eax=8d335000 ebx=8e0d40a0 ecx=00005f5f edx=8d334fe0 esi=8dc04000 edi=8e0d40c0
eip=83a13926 esp=803999d4 ebp=803999d4 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!wcsrchr+0xa:
83a13926 668b08 mov cx,word ptr [eax] ds:0023:8d335000=????
Resetting default scope

LAST_CONTROL_TRANSFER: from 83a5eb54 to 83aa90f5

STACK_TEXT:
80399948 83a5eb54 00000000 8d335000 00000000 nt!MmAccessFault+0x10a
80399948 83a13926 00000000 8d335000 00000000 nt!KiTrap0E+0xdc
803999d4 8e0ce017 8d334fe0 0000005c 8dc00750 nt!wcsrchr+0xa
WARNING: Stack unwind information not available. Following frames may be wrong.
803999f0 83b73376 8dc00750 8dc04000 00000000 ATITool+0x2017
00000000 00000000 00000000 00000000 00000000 nt!IopLoadDriver+0x805


STACK_COMMAND: kb

FOLLOWUP_IP:
ATITool+2017
8e0ce017 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: ATITool+2017

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ATITool

IMAGE_NAME: ATITool.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 455479e3

FAILURE_BUCKET_ID: 0xCD_VRF_ATITool+2017

BUCKET_ID: 0xCD_VRF_ATITool+2017

Followup: MachineOwner

 

[dds14u]

This last one looks more like a video driver thing...but the problem is I already have the latest!

 

[dclive]

Temporarily swap the video card and see if you can repro the dumps.

 

[dds14u]

Originally posted by: dclive
Temporarily swap the video card and see if you can repro the dumps.

Hmm...no easy access to a video card right now.

Is your hunch a video card hardware problem?

I'll see what I can do.

 

[dclive]

The errors you are getting are video related, so it's logical to replace the card and see if the problems persist.

Another easy thing to do is uninstall the current drivers and roll back to a prior version.