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\031711-31668-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c5de90
Debug session time: Thu Mar 17 12:42:28.271 2011 (UTC - 4:00)
System Uptime: 0 days 0:38:37.582
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff880009e8180, 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
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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e8180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 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: d
STACK_TEXT:
fffff800`0420be68 fffff800`02aefa89 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009e8180 : nt!KeBugCheckEx
fffff800`0420be70 fffff800`02aa2eb7 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff880`010499d2 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`0420bf00 fffff800`0300c895 : fffff800`030323c0 fffff800`0420c0b0 fffff800`030323c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`0420c000 fffff800`02a94b73 : fffffa80`05e79000 fffff880`0102da0d fffff880`0462b094 fffffa80`05e79000 : hal!HalpHpetClockInterrupt+0x8d
fffff800`0420c030 fffff800`02b3dcb8 : fffffa80`07fc5110 00000000`00000000 fffffa80`07fc5110 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`0420c1c0 fffff880`0104a6c4 : fffff880`0104a514 fffff800`0420c268 fffff880`00000002 00000000`00000002 : nt!KeIpiGenericCall+0x138
fffff800`0420c230 fffff880`0104a514 : fffff800`0420c268 fffff880`00000002 00000000`00000002 00000000`00000000 : sptd+0x496c4
fffff800`0420c238 fffff800`0420c268 : fffff880`00000002 00000000`00000002 00000000`00000000 fffff880`0104fed0 : sptd+0x49514
fffff800`0420c240 fffff880`00000002 : 00000000`00000002 00000000`00000000 fffff880`0104fed0 00000000`00000002 : 0xfffff800`0420c268
fffff800`0420c248 00000000`00000002 : 00000000`00000000 fffff880`0104fed0 00000000`00000002 fffff880`01049cd8 : 0xfffff880`00000002
fffff800`0420c250 00000000`00000000 : fffff880`0104fed0 00000000`00000002 fffff880`01049cd8 fffff800`0420c2e0 : 0x2
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_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
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\031711-36660-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a4b000 PsLoadedModuleList = 0xfffff800`02c90e90
Debug session time: Thu Mar 17 13:33:15.362 2011 (UTC - 4:00)
System Uptime: 0 days 0:30:59.064
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88003163180, 2}
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
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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003163180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: set8EE6.tmp
CURRENT_IRQL: d
STACK_TEXT:
fffff800`04220a98 fffff800`02b22a89 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03163180 : nt!KeBugCheckEx
fffff800`04220aa0 fffff800`02ad5eb7 : 00000000`00000000 fffff800`00000002 00000000`00002710 fffffa80`07725930 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff800`04220b30 fffff800`02a0c895 : fffff800`02a323c0 fffff800`04220ce0 fffff800`02a323c0 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`04220c30 fffff800`02ac7b73 : 00000566`f8d74a70 fffff800`04220ce0 00000000`00000031 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff800`04220c60 fffff800`02a122c3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff800`04220df0 fffff800`02a11a7b : 00000000`00000001 00000000`00000032 00000000`00000000 63006f00`52000000 : hal!HalpTscStallExecutionProcessor+0xbf
fffff800`04220e50 fffff880`010dfaf9 : 00000000`00000001 fffffa80`04a67640 fffffa80`04a676a8 fffff880`0f2065d3 : hal!KeStallExecutionProcessor+0x183
fffff800`04220e80 00000000`00000001 : fffffa80`04a67640 fffffa80`04a676a8 fffff880`0f2065d3 fffffa80`08302000 : sptd+0x48af9
fffff800`04220e88 fffffa80`04a67640 : fffffa80`04a676a8 fffff880`0f2065d3 fffffa80`08302000 fffff880`010d9150 : 0x1
fffff800`04220e90 fffffa80`04a676a8 : fffff880`0f2065d3 fffffa80`08302000 fffff880`010d9150 00000000`00000000 : 0xfffffa80`04a67640
fffff800`04220e98 fffff880`0f2065d3 : fffffa80`08302000 fffff880`010d9150 00000000`00000000 fffffa80`08303210 : 0xfffffa80`04a676a8
fffff800`04220ea0 fffff800`02ad6b1c : fffff800`02c3de80 fffffa80`00000000 fffffa80`08302000 00000000`000000f8 : portcls!CServiceGroup::ServiceDpc+0xa7
fffff800`04220f00 fffff800`02ace165 : 00000000`00000000 fffffa80`04d81b60 00000000`00000000 fffff880`010d9110 : nt!KiRetireDpcList+0x1bc
fffff800`04220fb0 fffff800`02acdf7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`09fc6bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
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_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
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\031711-39561-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a01000 PsLoadedModuleList = 0xfffff800`02c46e90
Debug session time: Thu Mar 17 13:43:45.555 2011 (UTC - 4:00)
System Uptime: 0 days 0:02:08.334
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {0, 2, 8, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e8
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
+3364613036316532
00000000`00000000 ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff8800318baf0 -- (.trap 0xfffff8800318baf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8800316dfc0 rbx=0000000000000000 rcx=fffff80000b9c2b8
rdx=fffff880010e7ed8 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8800318bc88 rbp=fffff880010e7ed8
r8=0000000000000000 r9=fffff880010da501 r10=0000000000019905
r11=fffff88000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
00000000`00000000 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a80be9 to fffff80002a81640
FAILED_INSTRUCTION_ADDRESS:
+3364613036316532
00000000`00000000 ?? ???
STACK_TEXT:
fffff880`0318b9a8 fffff800`02a80be9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`0318b9b0 fffff800`02a7f860 : 00000000`0001fca2 fffffa80`03c9f900 fffffa80`05931888 fffff880`03163180 : nt!KiBugCheckDispatch+0x69
fffff880`0318baf0 00000000`00000000 : fffff800`02a8cb1c 00000000`13fa6554 00000000`13fa862b 00000000`13fa6554 : nt!KiPageFault+0x260
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiPageFault+260
fffff800`02a7f860 440f20c0 mov rax,cr8
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiPageFault+260
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
BUCKET_ID: X64_0xD1_CODE_AV_NULL_IP_nt!KiPageFault+260
Followup: MachineOwner
---------