Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\043011-23593-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Sat Apr 30 14:52:34.803 2011 (UTC - 4:00)
System Uptime: 0 days 14:58:03.377
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff88006e6b650, 0, 0}
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : tdx.sys ( tdx+e3a2 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006e6b650, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+3131373832353134
fffff880`06e6b650 68c5e60680 push 0FFFFFFFF8006E6C5h
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f040e0
0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88006e6c568 -- (.exr 0xfffff88006e6c568)
ExceptionAddress: fffff88000dec3a2 (tdx+0x000000000000e3a2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88006e6c610 -- (.trap 0xfffff88006e6c610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880017485b0 rbx=0000000000000000 rcx=fffffa80046e8200
rdx=fffff88006e6c7e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000dec3a2 rsp=fffff88006e6c7a0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000007
r11=fffff88000de77b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
tdx+0xe3a2:
fffff880`00dec3a2 ff5020 call qword ptr [rax+20h] ds:aa02:fffff880`017485d0=000a000900060008
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d5ebdb to fffff80002ccc740
STACK_TEXT:
fffff880`06e6b598 fffff800`02d5ebdb : 00000000`0000001e ffffffff`c0000005 fffff880`06e6b650 00000000`00000000 : nt!KeBugCheckEx
fffff880`06e6b5a0 fffff800`02d1dd30 : fffff880`06e6b730 fffff880`0158bc5a fffff880`06e6b790 fffff880`0158bc5a : nt!KipFatalFilter+0x1b
fffff880`06e6b5e0 fffff800`02cfad1c : fffff880`06e6b640 fffff880`0158d901 fffff880`06e6b668 fffff880`06e6b660 : nt! ?? ::FNODOBFM::`string'+0x95d
fffff880`06e6b620 fffff800`02cf240d : fffff800`02e18be4 fffff880`06e6d420 00000000`00000000 fffff800`02c5c000 : nt!_C_specific_handler+0x8c
fffff880`06e6b690 fffff800`02cf9a90 : fffff800`02e18be4 fffff880`06e6b708 fffff880`06e6c568 fffff800`02c5c000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`06e6b6c0 fffff800`02d069ef : fffff880`06e6c568 fffff880`06e6bdd0 fffff880`00000000 fffffa80`0468f9e0 : nt!RtlDispatchException+0x410
fffff880`06e6bda0 fffff800`02ccbd82 : fffff880`06e6c568 fffffa80`044aaa30 fffff880`06e6c610 fffffa80`0468fa58 : nt!KiDispatchException+0x16f
fffff880`06e6c430 fffff800`02cca68a : 00000000`00000000 fffffa80`05c06050 00000000`00000036 fffffa80`05004160 : nt!KiExceptionDispatch+0xc2
fffff880`06e6c610 fffff880`00dec3a2 : fffffa80`044aaa30 00000000`00000000 fffff880`06e6c880 fffff880`03cb070b : nt!KiGeneralProtectionFault+0x10a
fffff880`06e6c7a0 fffff880`00ded0cc : 00000000`c0000016 00000000`00000820 fffff880`06e6cb38 00000000`c000021b : tdx+0xe3a2
fffff880`06e6c840 fffff880`0167b44e : fffffa80`07e8b001 fffff880`0164b2e0 00000000`00000000 fffffa80`07e8b0e0 : tdx+0xf0cc
fffff880`06e6c980 fffff880`0167f13b : 0000000c`8c018f4b fffffa80`046e8360 fffffa80`046e8200 00000000`00000000 : tcpip!TcpIndicateData+0xfe
fffff880`06e6ca80 fffff880`0167fa99 : fffffa80`046e8200 fffffa80`046e8200 00000000`00000586 fffffa80`06146a30 : tcpip!TcpDeliverDataToClient+0x2bb
fffff880`06e6cc00 fffff880`01679298 : fffffa80`049c3260 fffffa80`046e8200 fffffa80`049c3260 fffffa80`042bfaf0 : tcpip!TcpDeliverReceive+0xa9
fffff880`06e6cd00 fffff880`01679e95 : 00000000`00000000 fffffa80`04a30e50 fffffa80`060fbe14 00000000`00000010 : tcpip!TcpTcbFastDatagram+0x208
fffff880`06e6cec0 fffff880`0167e86a : fffffa80`04a69e80 fffff800`02c14900 fffffa80`04a2c701 00000000`00000000 : tcpip!TcpTcbReceive+0x1f5
fffff880`06e6d070 fffff880`0167e3b7 : fffffa80`0622202c fffffa80`04a6f008 00000000`00000000 fffffa80`04a0ed00 : tcpip!TcpMatchReceive+0x1fa
fffff880`06e6d1c0 fffff880`01680191 : fffffa80`07e51180 00000000`00000010 fffffa80`06145000 00000000`00000009 : tcpip!TcpPreValidatedReceive+0x177
fffff880`06e6d270 fffff880`01677e22 : fffffa80`05bc3150 fffffa80`06716010 fffffa80`06540006 00000000`00000000 : tcpip!IpFlcReceivePreValidatedPackets+0x4a1
fffff880`06e6d3d0 fffff800`02cdbe5a : 00000000`00000000 fffff880`06e68000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2
fffff880`06e6d420 fffff880`01677882 : fffff880`01677d80 fffff880`06e6d530 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`06e6d500 fffff880`014be0eb : fffffa80`067168d0 00000000`00000000 fffffa80`05c061a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`06e6d570 fffff880`01487fc6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`06e6d5e0 fffff880`01401ef1 : fffffa80`05c061a0 00000000`00000002 00000000`00000001 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`06e6da60 fffff880`042d5f08 : fffffa80`05d01000 fffffa80`0621f370 fffff880`06e6dc18 fffff880`06e6db60 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`06e6dab0 fffffa80`05d01000 : fffffa80`0621f370 fffff880`06e6dc18 fffff880`06e6db60 00000000`00000001 : nvmf6264+0xbf08
fffff880`06e6dab8 fffffa80`0621f370 : fffff880`06e6dc18 fffff880`06e6db60 00000000`00000001 00000000`00000000 : 0xfffffa80`05d01000
fffff880`06e6dac0 fffff880`06e6dc18 : fffff880`06e6db60 00000000`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`0621f370
fffff880`06e6dac8 fffff880`06e6db60 : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`062a0428 : 0xfffff880`06e6dc18
fffff880`06e6dad0 00000000`00000001 : 00000000`00000000 00000000`00000000 fffffa80`062a0428 fffff880`042d1bc0 : 0xfffff880`06e6db60
fffff880`06e6dad8 00000000`00000000 : 00000000`00000000 fffffa80`062a0428 fffff880`042d1bc0 00000000`00000000 : 0x1
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx+e3a2
fffff880`00dec3a2 ff5020 call qword ptr [rax+20h]
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: tdx+e3a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc16b
FAILURE_BUCKET_ID: X64_0x1E_c0000005_tdx+e3a2
BUCKET_ID: X64_0x1E_c0000005_tdx+e3a2
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\041611-38500-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e57e50
Debug session time: Sat Apr 16 23:17:57.104 2011 (UTC - 4:00)
System Uptime: 1 days 8:38:59.166
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff88000cdcc29, 2, 0, fffff88000cccaa8}
*** ERROR: Module load completed but symbols could not be loaded for tdx.sys
Probably caused by : tdx.sys ( tdx+caa8 )
Followup: MachineOwner
---------
0: 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: fffff88000cdcc29, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000cccaa8, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec20e0
fffff88000cdcc29
CURRENT_IRQL: 2
FAULTING_IP:
tdx+caa8
fffff880`00cccaa8 80792904 cmp byte ptr [rcx+29h],4
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88008488940 -- (.trap 0xfffff88008488940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88000cd8110 rbx=0000000000000000 rcx=fffff88000cdcc00
rdx=fffff88008488b02 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000cccaa8 rsp=fffff88008488ad0 rbp=0000000000000000
r8=00000000c0000201 r9=0000000000000000 r10=fffffa8004a0ea50
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
tdx+0xcaa8:
fffff880`00cccaa8 80792904 cmp byte ptr [rcx+29h],4 ds:0001:fffff880`00cdcc29=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c89ca9 to fffff80002c8a740
STACK_TEXT:
fffff880`084887f8 fffff800`02c89ca9 : 00000000`0000000a fffff880`00cdcc29 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`08488800 fffff800`02c88920 : fffff880`08488bc0 fffffa80`05b186d0 fffff880`08488b50 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`08488940 fffff880`00cccaa8 : fffff880`0848d2d2 fffff880`03d165c5 fffffa80`062cbe20 00000000`00000000 : nt!KiPageFault+0x260
fffff880`08488ad0 fffff880`00ccce8f : fffffa80`05b186d0 fffff880`00cd8400 00000000`c000020d fffffa80`0503f810 : tdx+0xcaa8
fffff880`08488b20 fffff880`00ccf393 : 00000000`00000004 fffff880`08488bc0 fffffa80`05b186d0 fffff880`08488bf0 : tdx+0xce8f
fffff880`08488b50 fffff880`01843be5 : fffffa80`0503f810 00000000`00000004 fffffa80`04a0ec10 fffffa80`0503f810 : tdx+0xf393
fffff880`08488bc0 fffff880`01868ff3 : 00000000`00000003 00000000`00000004 fffffa80`04a0ec10 00000000`00000000 : tcpip!TcpNotifyAbortDelivery+0x45
fffff880`08488bf0 fffff880`01843b02 : fffffa80`062c2674 fffffa80`08722e30 fffffa80`0503f810 fffff880`01877474 : tcpip!TcpShutdownTcb+0x603
fffff880`08488ce0 fffff880`0186b953 : 00000000`00000000 fffff880`08488e68 fffffa80`062c2674 00000000`00000037 : tcpip!TcpAbortTcbDelivery+0x32
fffff880`08488d10 fffff880`01878334 : fffffa80`054962f0 00000000`00000000 fffffa80`04a53008 00000000`00000000 : tcpip!TcpTcbCarefulDatagram+0xbe3
fffff880`08488ec0 fffff880`0187c86a : fffffa80`04a35900 00000000`00000000 fffffa80`04a0ec01 00000000`00000000 : tcpip!TcpTcbReceive+0x694
fffff880`08489070 fffff880`0187c3b7 : fffffa80`062bf02c fffffa80`04a53008 00000000`00000000 fffffa80`062c0300 : tcpip!TcpMatchReceive+0x1fa
fffff880`084891c0 fffff880`0187e191 : fffffa80`062c0370 00000000`00000001 fffff880`084885fd 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x177
fffff880`08489270 fffff880`01875e22 : fffffa80`06109220 fffffa80`065f88a0 fffffa80`065f0006 00000000`00000000 : tcpip!IpFlcReceivePreValidatedPackets+0x4a1
fffff880`084893d0 fffff800`02c99e5a : 00000000`00000000 fffff880`08484000 00000000`00004800 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2
fffff880`08489420 fffff880`01875882 : fffff880`01875d80 fffff880`08489530 00000000`00000002 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`08489500 fffff880`015970eb : fffffa80`065f9010 00000000`00000000 fffffa80`05abc1a0 fffff800`02c92de7 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`08489570 fffff880`01560fc6 : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`084895e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
STACK_COMMAND: kb
FOLLOWUP_IP:
tdx+caa8
fffff880`00cccaa8 80792904 cmp byte ptr [rcx+29h],4
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: tdx+caa8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: tdx
IMAGE_NAME: tdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc16b
FAILURE_BUCKET_ID: X64_0xD1_tdx+caa8
BUCKET_ID: X64_0xD1_tdx+caa8
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050211-23921-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Mon May 2 19:38:31.391 2011 (UTC - 4:00)
System Uptime: 0 days 21:27:10.469
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 0, fffff8800feb0fff}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+6dfff )
Followup: MachineOwner
---------
1: 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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800feb0fff, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f080e0
0000000000000010
CURRENT_IRQL: 2
FAULTING_IP:
nvlddmkm+6dfff
fffff880`0feb0fff 48 ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: dwm.exe
TRAP_FRAME: fffff88008977fd0 -- (.trap 0xfffff88008977fd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8008373120 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800feb0fff rsp=fffff88008978160 rbp=00000000807d0000
r8=fffff88008978180 r9=0000000000000000 r10=0000000000000000
r11=fffff880009e7180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvlddmkm+0x6dfff:
fffff880`0feb0fff 48 ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ccfca9 to fffff80002cd0740
STACK_TEXT:
fffff880`08977e88 fffff800`02ccfca9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`08977e90 fffff800`02cce920 : fffffa80`00000000 00000000`00000000 00000000`00000400 fffff800`02dd69b1 : nt!KiBugCheckDispatch+0x69
fffff880`08977fd0 fffff880`0feb0fff : 00000000`00000000 00000000`00000000 fffffa80`0834b600 fffff880`08978410 : nt!KiPageFault+0x260
fffff880`08978160 00000000`00000000 : 00000000`00000000 fffffa80`0834b600 fffff880`08978410 00000000`00000000 : nvlddmkm+0x6dfff
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+6dfff
fffff880`0feb0fff 48 ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+6dfff
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da
FAILURE_BUCKET_ID: X64_0xD1_nvlddmkm+6dfff
BUCKET_ID: X64_0xD1_nvlddmkm+6dfff
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\050811-26171-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e53e50
Debug session time: Sun May 8 09:06:53.766 2011 (UTC - 4:00)
System Uptime: 0 days 15:22:20.844
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {8c, 2, 0, fffff80002c91e13}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+103 )
Followup: MachineOwner
---------
1: 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: 000000000000008c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002c91e13, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebe0e0
000000000000008c
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiProcessExpiredTimerList+103
fffff800`02c91e13 0fb6432b movzx eax,byte ptr [rbx+2Bh]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002f1b450 -- (.trap 0xfffff88002f1b450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=fffffa80045ffc58
rdx=fffffa80045b2488 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c91e13 rsp=fffff88002f1b5e0 rbp=fffffa80045b2428
r8=0000000000000002 r9=0000000000000000 r10=0000000000000036
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!KiProcessExpiredTimerList+0x103:
fffff800`02c91e13 0fb6432b movzx eax,byte ptr [rbx+2Bh] ds:00000000`0000002b=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c85ca9 to fffff80002c86740
STACK_TEXT:
fffff880`02f1b308 fffff800`02c85ca9 : 00000000`0000000a 00000000`0000008c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b310 fffff800`02c84920 : 00000000`00000000 00000000`00000061 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b450 fffff800`02c91e13 : fffffa80`045b2ce0 fffffa80`048b7168 fffffa80`048b7168 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f1b5e0 fffff800`02c924be : 00000080`d9b6c321 fffff880`02f1bc58 00000000`00360b36 fffff880`009e9c48 : nt!KiProcessExpiredTimerList+0x103
fffff880`02f1bc30 fffff800`02c91cb7 : 0000002e`2071f8c1 0000002e`00360b36 0000002e`2071f8e2 00000000`00000036 : nt!KiTimerExpiration+0x1be
fffff880`02f1bcd0 fffff800`02c8eeea : fffff880`009e7180 fffff880`009f1f40 00000000`00000000 fffff880`03e4adb0 : nt!KiRetireDpcList+0x277
fffff880`02f1bd80 00000000`00000000 : fffff880`02f1c000 fffff880`02f16000 fffff880`02f1bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiProcessExpiredTimerList+103
fffff800`02c91e13 0fb6432b movzx eax,byte ptr [rbx+2Bh]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiProcessExpiredTimerList+103
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
FAILURE_BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+103
BUCKET_ID: X64_0xA_nt!KiProcessExpiredTimerList+103
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\051211-25781-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Thu May 12 21:19:53.000 2011 (UTC - 4:00)
System Uptime: 1 days 3:18:27.078
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002cc53d5}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2a5 )
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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002cc53d5, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiTimerWaitTest+2a5
fffff800`02cc53d5 488b6d00 mov rbp,qword ptr [rbp]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff8000407e3d0 -- (.trap 0xfffff8000407e3d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cc53d5 rsp=fffff8000407e560 rbp=0000000000000000
r8=fffffa8004b28810 r9=0000000000000005 r10=fffff80002c4b000
r11=fffffa8005d6d500 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac pe cy
nt!KiTimerWaitTest+0x2a5:
fffff800`02cc53d5 488b6d00 mov rbp,qword ptr [rbp] ss:0018:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cbac69 to fffff80002cbb700
STACK_TEXT:
fffff800`0407e288 fffff800`02cbac69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`0407e290 fffff800`02cb98e0 : 00000000`00000000 fffffa80`04b287f8 00000000`00000000 fffffa80`05d6d520 : nt!KiBugCheckDispatch+0x69
fffff800`0407e3d0 fffff800`02cc53d5 : ffffffff`ff676980 fffff800`02cc72ae fffff800`0407e600 fffffa80`00000000 : nt!KiPageFault+0x260
fffff800`0407e560 fffff800`02cc6d8d : fffffa80`04b287f0 fffffa80`05b58168 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x2a5
fffff800`0407e5e0 fffff800`02cc74ce : 000000e4`e395af42 fffff800`0407ec58 00000000`006000c5 fffff800`02e39b28 : nt!KiProcessExpiredTimerList+0x6d
fffff800`0407ec30 fffff800`02cc6cc7 : 00000051`f05862c3 00000051`006000c5 00000051`f058626f 00000000`000000c5 : nt!KiTimerExpiration+0x1be
fffff800`0407ecd0 fffff800`02cc3eea : fffff800`02e35e80 fffff800`02e43c40 00000000`00000000 fffff880`0fe4a684 : nt!KiRetireDpcList+0x277
fffff800`0407ed80 00000000`00000000 : fffff800`0407f000 fffff800`04079000 fffff800`0407ed40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTimerWaitTest+2a5
fffff800`02cc53d5 488b6d00 mov rbp,qword ptr [rbp]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiTimerWaitTest+2a5
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
FAILURE_BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2a5
BUCKET_ID: X64_0xA_nt!KiTimerWaitTest+2a5
Followup: MachineOwner
---------