Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini040509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:Symbolsnew*
http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows
Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18145.x86fre.vistasp1_gdr.080917-1612
Machine Name:
Kernel base = 0x8204e000 PsLoadedModuleList = 0x8215b930
Debug session time: Sun Apr 5 15:01:16.454 2009 (GMT+2)
System Uptime: 1 days 1:51:49.884
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, 806d1120, 1}
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for DRVMCDB.SYS
*** ERROR: Module load completed but symbols could not be loaded for DRVMCDB.SYS
*** WARNING: Unable to verify timestamp for DLACDBHM.SYS
*** ERROR: Module load completed but symbols could not be loaded for DLACDBHM.SYS
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 806d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 1c
STACK_TEXT:
8069daac 820bafba 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8069dae0 820bc6ed 86c9b51b 000000d1 8069db7c nt!KeUpdateRunTime+0xd5
8069dae0 820559b1 86c9b51b 000000d1 8069db7c nt!KeUpdateSystemTime+0xed
8069db7c 8a241b3e 8a241982 8069db94 00040000 nt!KeIpiGenericCall+0x94
WARNING: Stack unwind information not available. Following frames may be wrong.
8069dbcc 8a24226a 0000001f 8a24184e 8069dbf0 sptd+0x14b3e
8069dbfc 8a23c5e3 01000001 87f7e45c 8800ff20 sptd+0x1526a
8069dc14 8a23df6d 00000103 87c1ef30 87f59190 sptd+0xf5e3
8069dc40 8a2408c4 87f7e380 8069dc98 8a23d8ec sptd+0x10f6d
8069dcb0 820941cd 87e65030 87f7e380 87f7e49c sptd+0x138c4
8069dcc8 8a58d779 87f7e380 87f5e018 87c1ef30 nt!IofCallDriver+0x63
8069dce8 8a590430 87f5e018 4a000000 820941cd PxHelp20+0x2779
8069dd0c 8a584a8b 87f7e480 8a5849d7 87e6e310 PxHelp20+0x5430
8069dd30 8a583b8f 87e6e310 87f7e380 87e6e310 DRVMCDB+0x10a8b
8069dd48 820941cd 87e6e310 87f7e380 87f7e4c8 DRVMCDB+0xfb8f
8069dd60 8ed45b31 8a4a11f4 87e64d80 8a4a3000 nt!IofCallDriver+0x63
8069dd84 820941cd 87e64d80 00f7e380 87f7e380 DLACDBHM+0xb31
8069dd9c 8a494264 87efdb70 87c1ef10 87efdab8 nt!IofCallDriver+0x63
8069ddb0 8a49445d 87efdb70 87c1ef28 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
8069ddc8 8a4942af 87efdb70 87179074 82178700 CLASSPNP!ClassCheckMediaState+0x54
8069dde8 820bd5a3 87efdab8 00000000 8069de4c CLASSPNP!ClasspTimerTick+0x41
8069de08 820b92a0 821786e0 02178684 9a87694a nt!IopTimerDispatch+0x49
8069df28 820b8e60 8069df70 00000002 8069df78 nt!KiTimerListExpire+0x367
8069df88 820b8a23 00000000 00000000 005b11ec nt!KiTimerExpiration+0x22a
8069dff4 820b6fb5 807a8c40 00000000 00000000 nt!KiRetireDpcList+0xba
8069dff8 807a8c40 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
820b6fb5 00000000 0000001b 00c7850f bb830000 0x807a8c40
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------