Hi,
Well i have an ati 9800 pro vid card on my p4 3.0ghz comp running 2 monitors. I was launching warcraft on the main monitor and as usual leaving the second monitor just on msn. Suddenly as i launched warcraft it went into a bsod. I opened up the minidump and these are the results below. Can anyone see if its hardware/drivers?
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Jason Yap\Desktop\WER50c3.dir00\Mini030807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Mar 8 17:07:23.074 2007 (GMT-8)
System Uptime: 7 days 17:37:43.958
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {84375ac8, 86abcec0, f7966cbc, 1}
*** WARNING: Unable to verify timestamp for hal.dll
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
Unable to load image ati2mtag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
Unable to load image ati2cqag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: watchdog!_DEFERRED_WATCHDOG ***
*** ***
*************************************************************************
Probably caused by : ati2mtag.sys ( ati2mtag!_SEH_prolog+2c )
Followup: MachineOwner
---------
1: kd> .reload
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
1: kd> !analyze -v
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 84375ac8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 86abcec0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7966cbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for hal.dll
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
Unable to load image ati2mtag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
Unable to load image ati2cqag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: watchdog!_DEFERRED_WATCHDOG ***
*** ***
*************************************************************************
OVERLAPPED_MODULE: Address regions for 'yk51x86' and 'yk51x86.sys' overlap
FAULTING_THREAD: 84375ac8
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: war3.exe
LAST_CONTROL_TRANSFER: from f7817a67 to 804dc7e8
STACK_TEXT:
884bf378 f7817a67 f7966b9c 00000000 00000000 nt!KeWaitForSingleObject+0x24b
884bf66c 804ecd6a f7966b48 884bf6b8 884bf6ac watchdog!WatchdogKernelApc+0x13b
884bf6bc 806ffef2 00000000 00000000 884bf6d4 nt!KeRestoreFloatingPointState+0xb
884bf6d4 806ff99a badb0d00 00000000 8053dac7 hal!HalBuildMdlFromScatterGatherList+0xda
884bf7a0 f6e66cc6 00000001 00300000 30303352 hal!HalCalculateScatterGatherListSize+0x4
884bf7b4 f6e7e340 86d69350 00000001 00300000 VIDEOPRT!VideoPortAllocatePool+0x14
884bf7dc f6e7c7ab 86d69350 00000001 00300000 ati2mtag!_SEH_prolog+0x2c
884bf7f4 bfa2cd92 86d69350 00300000 00300000 ati2mtag!IoctlVideoAtiCommitAgpMemory+0x69
884bf824 00000000 00000000 bfa2aef9 e231dbb0 ati2cqag!MSF::save_recoverable_surfaces+0xa2
STACK_COMMAND: .thread 0xffffffff84375ac8 ; kb
FOLLOWUP_IP:
ati2mtag!_SEH_prolog+2c
f6e7e340 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: ati2mtag!_SEH_prolog+2c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45c3990c
FAILURE_BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_02_02
BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_02_02
Followup: MachineOwner
---------
Well i have an ati 9800 pro vid card on my p4 3.0ghz comp running 2 monitors. I was launching warcraft on the main monitor and as usual leaving the second monitor just on msn. Suddenly as i launched warcraft it went into a bsod. I opened up the minidump and these are the results below. Can anyone see if its hardware/drivers?
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Jason Yap\Desktop\WER50c3.dir00\Mini030807-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Mar 8 17:07:23.074 2007 (GMT-8)
System Uptime: 7 days 17:37:43.958
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {84375ac8, 86abcec0, f7966cbc, 1}
*** WARNING: Unable to verify timestamp for hal.dll
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
Unable to load image ati2mtag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
Unable to load image ati2cqag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: watchdog!_DEFERRED_WATCHDOG ***
*** ***
*************************************************************************
Probably caused by : ati2mtag.sys ( ati2mtag!_SEH_prolog+2c )
Followup: MachineOwner
---------
1: kd> .reload
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.....................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
1: kd> !analyze -v
Unable to load image watchdog.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for watchdog.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 84375ac8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 86abcec0, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7966cbc, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for hal.dll
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
Unable to load image ati2mtag.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
Unable to load image ati2cqag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: watchdog!_DEFERRED_WATCHDOG ***
*** ***
*************************************************************************
OVERLAPPED_MODULE: Address regions for 'yk51x86' and 'yk51x86.sys' overlap
FAULTING_THREAD: 84375ac8
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: war3.exe
LAST_CONTROL_TRANSFER: from f7817a67 to 804dc7e8
STACK_TEXT:
884bf378 f7817a67 f7966b9c 00000000 00000000 nt!KeWaitForSingleObject+0x24b
884bf66c 804ecd6a f7966b48 884bf6b8 884bf6ac watchdog!WatchdogKernelApc+0x13b
884bf6bc 806ffef2 00000000 00000000 884bf6d4 nt!KeRestoreFloatingPointState+0xb
884bf6d4 806ff99a badb0d00 00000000 8053dac7 hal!HalBuildMdlFromScatterGatherList+0xda
884bf7a0 f6e66cc6 00000001 00300000 30303352 hal!HalCalculateScatterGatherListSize+0x4
884bf7b4 f6e7e340 86d69350 00000001 00300000 VIDEOPRT!VideoPortAllocatePool+0x14
884bf7dc f6e7c7ab 86d69350 00000001 00300000 ati2mtag!_SEH_prolog+0x2c
884bf7f4 bfa2cd92 86d69350 00300000 00300000 ati2mtag!IoctlVideoAtiCommitAgpMemory+0x69
884bf824 00000000 00000000 bfa2aef9 e231dbb0 ati2cqag!MSF::save_recoverable_surfaces+0xa2
STACK_COMMAND: .thread 0xffffffff84375ac8 ; kb
FOLLOWUP_IP:
ati2mtag!_SEH_prolog+2c
f6e7e340 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: ati2mtag!_SEH_prolog+2c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ati2mtag
IMAGE_NAME: ati2mtag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45c3990c
FAILURE_BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_02_02
BUCKET_ID: 0xEA_IMAGE_ati2mtag.sys_DATE_2007_02_02
Followup: MachineOwner
---------
