Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032011-26520-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c59e90
Debug session time: Sun Mar 20 01:22:14.511 2011 (UTC - 4:00)
System Uptime: 0 days 16:52:32.212
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff8800f46c4d1}
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+1c34d1 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8800f46c4d1
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 5
LAST_CONTROL_TRANSFER: from fffff80002a93be9 to fffff80002a94640
STACK_TEXT:
fffff800`00ba4d28 fffff800`02a93be9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02a920b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`0f46c4d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`05f53fd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x1c34d1
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+1c34d1
fffff880`0f46c4d1 ff5378 call qword ptr [rbx+78h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+1c34d1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d64bb6c
FAILURE_BUCKET_ID: X64_0x7f_8_nvlddmkm+1c34d1
BUCKET_ID: X64_0x7f_8_nvlddmkm+1c34d1
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032011-28282-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c54e90
Debug session time: Sun Mar 20 06:57:09.140 2011 (UTC - 4:00)
System Uptime: 0 days 5:33:47.841
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {b, 2, 8, b}
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 : ataport.SYS ( ataport!IdeProcessPortNotification+30d )
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: 000000000000000b, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 000000000000000b, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc00e8
000000000000000b
CURRENT_IRQL: 2
FAULTING_IP:
+3238656131643539
00000000`0000000b ?? ???
PROCESS_NAME: System
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
TRAP_FRAME: fffff80000b9cbf0 -- (.trap 0xfffff80000b9cbf0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000187000 rsi=0000000000000000 rdi=0000000000000000
rip=000000000000000b rsp=fffff80000b9cd80 rbp=fffff80000b97000
r8=fffffa80048f20c8 r9=0000000000000000 r10=fffffffffffffffe
r11=fffff80002c01e00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
00000000`0000000b ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a8ebe9 to fffff80002a8f640
FAILED_INSTRUCTION_ADDRESS:
+3238656131643539
00000000`0000000b ?? ???
STACK_TEXT:
fffff800`00b9caa8 fffff800`02a8ebe9 : 00000000`0000000a 00000000`0000000b 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`00b9cab0 fffff800`02a8d860 : fffffa80`063833e8 fffffa80`061a11a0 fffffa80`061a11a0 fffff800`02c01e80 : nt!KiBugCheckDispatch+0x69
fffff800`00b9cbf0 00000000`0000000b : fffff800`02c01e80 00000000`00000001 00000000`00000002 00000000`00000201 : nt!KiPageFault+0x260
fffff800`00b9cd80 fffff800`02c01e80 : 00000000`00000001 00000000`00000002 00000000`00000201 fffff800`00b9ce30 : 0xb
fffff800`00b9cd88 00000000`00000001 : 00000000`00000002 00000000`00000201 fffff800`00b9ce30 00000000`00000001 : nt!KiInitialPCR+0x180
fffff800`00b9cd90 00000000`00000002 : 00000000`00000201 fffff800`00b9ce30 00000000`00000001 fffffa80`048601a0 : 0x1
fffff800`00b9cd98 00000000`00000201 : fffff800`00b9ce30 00000000`00000001 fffffa80`048601a0 fffff800`00b97000 : 0x2
fffff800`00b9cda0 fffff800`00b9ce30 : 00000000`00000001 fffffa80`048601a0 fffff800`00b97000 fffff800`00b9cd40 : 0x201
fffff800`00b9cda8 00000000`00000001 : fffffa80`048601a0 fffff800`00b97000 fffff800`00b9cd40 fffff880`00e32731 : 0xfffff800`00b9ce30
fffff800`00b9cdb0 fffffa80`048601a0 : fffff800`00b97000 fffff800`00b9cd40 fffff880`00e32731 fffff800`00b97000 : 0x1
fffff800`00b9cdb8 fffff800`00b97000 : fffff800`00b9cd40 fffff880`00e32731 fffff800`00b97000 00000000`00000000 : 0xfffffa80`048601a0
fffff800`00b9cdc0 fffff800`00b9cd40 : fffff880`00e32731 fffff800`00b97000 00000000`00000000 00000000`00000000 : 0xfffff800`00b97000
fffff800`00b9cdc8 fffff880`00e32731 : fffff800`00b97000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00b9cd40
fffff800`00b9cdd0 fffff880`00e290c5 : 00000000`00000000 fffffa80`04861601 fffffa80`048616a8 00000000`00000000 : ataport!IdeProcessPortNotification+0x30d
fffff800`00b9ce10 fffff880`00e1cb7b : 00000000`0000e400 fffff880`01072742 00000000`00000002 fffff880`00e1b604 : ataport!AtaPortCompleteRequest+0x21
fffff800`00b9ce80 fffff880`00e1ca10 : fffffa80`048b1801 fffffa80`048616a8 fffffa80`0554c758 fffffa80`04861650 : atapi!AtapiCompleteRequest+0x147
fffff800`00b9cec0 fffff880`00e1b83a : fffffa80`048b1850 fffffa80`048b1804 fffffa80`048a5000 fffffa80`0554c758 : atapi!AtapiProcessInterrupt+0x2ac
fffff800`00b9cf20 fffff880`0108c7c8 : 00000000`00000050 fffffa80`048b1810 fffffa80`048a5000 fffffa80`048616a8 : atapi!AtapiHwInterrupt+0x156
fffff800`00b9cf80 00000000`00000050 : fffffa80`048b1810 fffffa80`048a5000 fffffa80`048616a8 00000000`00000000 : sptd+0x457c8
fffff800`00b9cf88 fffffa80`048b1810 : fffffa80`048a5000 fffffa80`048616a8 00000000`00000000 00000000`00000000 : 0x50
fffff800`00b9cf90 fffffa80`048a5000 : fffffa80`048616a8 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`048b1810
fffff800`00b9cf98 fffffa80`048616a8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`048a5000
fffff800`00b9cfa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`082f2080 : 0xfffffa80`048616a8
STACK_COMMAND: kb
FOLLOWUP_IP:
ataport!IdeProcessPortNotification+30d
fffff880`00e32731 488b5c2440 mov rbx,qword ptr [rsp+40h]
SYMBOL_STACK_INDEX: d
SYMBOL_NAME: ataport!IdeProcessPortNotification+30d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ataport
IMAGE_NAME: ataport.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79293
FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_ataport!IdeProcessPortNotification+30d
BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_ataport!IdeProcessPortNotification+30d
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032011-28111-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c52e90
Debug session time: Sun Mar 20 07:06:07.973 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:50.674
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80002a97c5d}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002a97c5d
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
LAST_CONTROL_TRANSFER: from fffff80002a8cbe9 to fffff80002a8d640
STACK_TEXT:
fffff800`00ba4d28 fffff800`02a8cbe9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02a8b0b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`02a97c5d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`053e4fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeUpdateSystemTime+0x11d
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02a8b0b2 90 nop
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiDoubleFaultAbort+b2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a
FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032111-26910-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a07000 PsLoadedModuleList = 0xfffff800`02c4ce90
Debug session time: Sun Mar 20 09:01:43.063 2011 (UTC - 4:00)
System Uptime: 0 days 0:07:42.764
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff8800f4d28f4}
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+23d8f4 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8800f4d28f4
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 5
LAST_CONTROL_TRANSFER: from fffff80002a86be9 to fffff80002a87640
STACK_TEXT:
fffff800`00ba4d28 fffff800`02a86be9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02a850b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff880`0f4d28f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0a990000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x23d8f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+23d8f4
fffff880`0f4d28f4 ff5378 call qword ptr [rbx+78h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nvlddmkm+23d8f4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d64bb6c
FAILURE_BUCKET_ID: X64_0x7f_8_nvlddmkm+23d8f4
BUCKET_ID: X64_0x7f_8_nvlddmkm+23d8f4
Followup: MachineOwner
---------