Microsoft (R) Windows Debugger Version 6.6.0007.5 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [c:\windows\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available Symbol search path is: srv*e:\winstuff\symbols\*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_qfe.070227-2300 Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700 Debug session time: Sat Sep 22 16:12:57.598 2007 (GMT-7) System Uptime: 0 days 19:32:32.593 Loading Kernel Symbols ....................................................................................................................................................................... Loading User Symbols Loading unloaded module list .................................................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck EA, {88292da8, 88425968, bacf3cbc, 1} ************************************************************************* *** *** *** *** *** 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 : nv4_mini.sys ( nv4_mini+69ceb ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* THREAD_STUCK_IN_DEVICE_DRIVER (ea) 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 (OS builds <= 3790) 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: 88292da8, Pointer to a stuck thread object. Do .thread then kb on it to find the hung location. Arg2: 88425968, Pointer to a DEFERRED_WATCHDOG object. Arg3: bacf3cbc, Pointer to offending driver name. Arg4: 00000001, Number of times this error occurred. If a debugger is attached, this error is not always fatal -- see DESCRIPTION below. On the blue screen, this will always equal 1. Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* FAULTING_THREAD: 88292da8 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT BUGCHECK_STR: 0xEA PROCESS_NAME: System LAST_CONTROL_TRANSFER: from b6e91ceb to 8052ac8e STACK_TEXT: ac03f400 b6e91ceb b3987400 b6eb468b 88f18688 nt!READ_REGISTER_ULONG+0x6 WARNING: Stack unwind information not available. Following frames may be wrong. ac03f408 b6eb468b 88f18688 88cfe9e8 00009400 nv4_mini+0x69ceb ac03f428 b7041b84 88cfe9e8 00009400 88cfe9e8 nv4_mini+0x8c68b ac03f444 b6ee6b7e dc1857c0 88cf5008 88e42750 nv4_mini+0x219b84 00000000 00000000 00000000 00000000 00000000 nv4_mini+0xbeb7e STACK_COMMAND: .thread 0xffffffff88292da8 ; kb FOLLOWUP_IP: nv4_mini+69ceb b6e91ceb c20c00 ret 0Ch SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nv4_mini+69ceb FOLLOWUP_NAME: MachineOwner MODULE_NAME: nv4_mini IMAGE_NAME: nv4_mini.sys DEBUG_FLR_IMAGE_TIMESTAMP: 46e78061 FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2007_09_11 BUCKET_ID: 0xEA_IMAGE_nv4_mini.sys_DATE_2007_09_11 Followup: MachineOwner --------- 0: kd> lmvm nv4_mini start end module name b6e28000 b74b1100 nv4_mini (no symbols) Loaded symbol image file: nv4_mini.sys Image path: \SystemRoot\system32\DRIVERS\nv4_mini.sys Image name: nv4_mini.sys Timestamp: Tue Sep 11 23:00:01 2007 (46E78061) CheckSum: 0068C100 ImageSize: 00689100 Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0