Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010311-36410-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a18000 PsLoadedModuleList = 0x82b60810
Debug session time: Sun Jan 2 14:23:36.338 2011 (UTC - 5:00)
System Uptime: 0 days 0:04:14.428
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 85d52508, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 00000000, Pointer to offending driver name.
Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
FAULTING_THREAD: 85d52508
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8f8c7bbc to 82af4d10
STACK_TEXT:
8c8cc388 8f8c7bbc 000000ea 85d52508 00000000 nt!KeBugCheckEx+0x1e
WARNING: Stack unwind information not available. Following frames may be wrong.
8c8cc3cc 8f8c034d 8c8cc418 00000000 8f8ba673 dxgkrnl+0x11bbc
8c8cc3f4 8f2398d2 8c8cc418 00000000 00000000 dxgkrnl+0xa34d
8c8cc444 8f233029 8f3e663e 8c8cc4e4 ffffffff atikmdag+0x298d2
8c8cc464 8f3e357f 85c28001 8c8cc480 1fff1fff atikmdag+0x23029
8c8cc4c0 8f3e67b7 869f1004 8f3e663e 8c8cc4e4 atikmdag+0x1d357f
8c8cc4fc 8f41901b 85d08000 00000000 00000001 atikmdag+0x1d67b7
8c8cc518 8f3881ef 85d08000 00000000 00000000 atikmdag+0x20901b
8c8cc538 8f39f086 869f1000 869f9f7e 00000000 atikmdag+0x1781ef
8c8cc55c 8f39f11c 869f1000 869f9658 00000000 atikmdag+0x18f086
8c8cc57c 8f370508 869f12c0 00000000 00000000 atikmdag+0x18f11c
8c8cc590 8f29b90a 00000000 00000000 8c8cc5b4 atikmdag+0x160508
8c8cc5a0 8f24a21e 84acc058 00000000 00000000 atikmdag+0x8b90a
8c8cc5b4 8f260b58 00000000 85c47008 85c47390 atikmdag+0x3a21e
8c8cc5cc 8f252685 00000001 8c8cc80c 85d988c0 atikmdag+0x50b58
8c8cc624 8f21f579 8c8cc80c 85d988c0 00000000 atikmdag+0x42685
8c8cc63c 8db09e48 00000001 8c8cc80c 82e2d6ee atikmdag+0xf579
8c8cc678 8f8ec968 85d988c0 8c8cc80c 8c8cc814 atikmpag+0x5e48
8c8cc6a4 8f917ff6 8c8cc80c b06373a4 88df41b0 dxgkrnl+0x36968
8c8cc828 8f8f10de b05be008 00000000 8c8ccc00 dxgkrnl+0x61ff6
8c8cc87c 8f91a5bb 865cd000 89a62ca0 b05be008 dxgkrnl+0x3b0de
8c8cca78 94712611 00000004 00000000 8c8ccd28 dxgkrnl+0x645bb
8c8ccac0 94715151 ffb89010 8c8cccd0 8c8ccd28 cdd!CreateAndEnableDevice+0x171
8c8ccd50 82c266d3 ffb89010 a27d775a 00000000 cdd!PresentWorkerThread+0x81d
8c8ccd90 82ad80f9 94714934 ffb89010 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .thread 0xffffffff85d52508 ; kb
FOLLOWUP_IP:
dxgkrnl+11bbc
8f8c7bbc ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl+11bbc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ac54de1
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\DMP\010311-35178-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a49000 PsLoadedModuleList = 0x82b91810
Debug session time: Sun Jan 2 22:47:10.418 2011 (UTC - 5:00)
System Uptime: 0 days 0:11:45.399
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, 82ab2daf}
Probably caused by : ntkrpamp.exe ( nt!KiTimerExpiration+15d )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82ab2daf, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82bb1718
Unable to read MiSystemVaType memory at 82b91160
00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerExpiration+15d
82ab2daf 8911 mov dword ptr [ecx],edx
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: atieclxx.exe
TRAP_FRAME: 8078aedc -- (.trap 0xffffffff8078aedc)
ErrCode = 00000002
eax=862460c8 ebx=82b755d8 ecx=00000000 edx=84ae1888 esi=82b755dc edi=82b74680
eip=82ab2daf esp=8078af50 ebp=8078afac iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!KiTimerExpiration+0x15d:
82ab2daf 8911 mov dword ptr [ecx],edx ds:0023:00000000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 82ab2daf to 82a8f82b
STACK_TEXT:
8078aedc 82ab2daf badb0d00 84ae1888 88a1357c nt!KiTrap0E+0x2cf
8078afac 82ab120e 0000b0a1 95e6b87c 00000000 nt!KiTimerExpiration+0x15d
8078aff4 82ab09dc 95e6b82c 00000000 00000000 nt!KiRetireDpcList+0xcb
8078aff8 95e6b82c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82ab09dc 00000000 0000001a 00d6850f bb830000 0x95e6b82c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTimerExpiration+15d
82ab2daf 8911 mov dword ptr [ecx],edx
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiTimerExpiration+15d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac
FAILURE_BUCKET_ID: 0xA_nt!KiTimerExpiration+15d
BUCKET_ID: 0xA_nt!KiTimerExpiration+15d
Followup: MachineOwner
---------