Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\073110-19047-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a4e000 PsLoadedModuleList = 0xfffff800`02c8be50
Debug session time: Sat Jul 31 11:18:44.475 2010 (GMT-4)
System Uptime: 1 days 13:33:16.254
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {61, 0, fffff880009e7180, 1}
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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e7180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0c1de478 fffff800`02a6c443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e7180 : nt!KeBugCheckEx
fffff880`0c1de480 fffff800`02ac6cf7 : 00000000`00000000 fffff800`00000001 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`0c1de510 fffff800`02a0f895 : fffff800`02a34460 fffff880`0c1de6c0 fffff800`02a34460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0c1de610 fffff800`02abaaf3 : fffff800`02c38e80 00000000`00000001 fffff880`0c1de730 fffff800`02aba207 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0c1de640 fffff800`02a7d999 : fffffa80`06e06000 fffffa80`06ac1000 fffff880`0c1de9b0 fffff880`1289a13f : nt!KiInterruptDispatchNoLock+0x163
fffff880`0c1de7d0 fffff800`02dbd158 : 00000000`00000000 fffff880`0c1deca0 fffff800`02a4e000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`0c1de840 fffff800`02dbe149 : 00000000`0918e950 fffff800`02db9cee 00000000`00000000 00000000`00000040 : nt!ExpQuerySystemInformation+0x1368
fffff880`0c1debe0 fffff800`02abd853 : fffffa80`04a00000 000007fe`f9d80b98 ffffffff`fffec780 000007fe`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`0c1dec20 00000000`775e00ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a8f148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775e00ba
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: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------