Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042311-29125-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`02e4a000 PsLoadedModuleList = 0xfffff800`03087e50
Debug session time: Sat Apr 23 03:19:00.115 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:26.988
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80048a0b30, fffffa80048a0e10, fffff800031c32d0}
c0000005 Exception in ext.Analyze debugger extension.
PC: 000007fe`ff9b17a6 VA: 00000000`00000001 R/W: 0 Parameter: 00000000`00000000
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80048a0b30, Terminating object
Arg3: fffffa80048a0e10, Process image file name
Arg4: fffff800031c32d0, Explanatory message (ascii)
Debugging Details:
------------------
c0000005 Exception in ext.analyze debugger extension.
PC: 000007fe`ff9b17a6 VA: 00000000`00000001 R/W: 0 Parameter: 00000000`00000000
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042411-33867-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`02e02000 PsLoadedModuleList = 0xfffff800`0303fe50
Debug session time: Sun Apr 24 08:08:30.017 2011 (UTC - 4:00)
System Uptime: 1 days 0:04:11.890
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {15d0, 9, 0, fffff88000dad66a}
Unable to load image \SystemRoot\system32\drivers\amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
Probably caused by : amd_sata.sys ( amd_sata+266a )
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: 00000000000015d0, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000dad66a, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030aa0e0
00000000000015d0
CURRENT_IRQL: 9
FAULTING_IP:
amd_sata+266a
fffff880`00dad66a 488b81d0150000 mov rax,qword ptr [rcx+15D0h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: plugin-contain
TRAP_FRAME: fffff88007b279a0 -- (.trap 0xfffff88007b279a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000dad66a rsp=fffff88007b27b30 rbp=fffff88007b27ca0
r8=0000000000000029 r9=0000000000000000 r10=fffffa8004273008
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
amd_sata+0x266a:
fffff880`00dad66a 488b81d0150000 mov rax,qword ptr [rcx+15D0h] ds:00000000`000015d0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e71ca9 to fffff80002e72740
STACK_TEXT:
fffff880`07b27858 fffff800`02e71ca9 : 00000000`0000000a 00000000`000015d0 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffff880`07b27860 fffff800`02e70920 : 00000000`0054c18c fffffa80`0427ef70 fffff880`009e8180 fffff800`02e7f618 : nt!KiBugCheckDispatch+0x69
fffff880`07b279a0 fffff880`00dad66a : 00000000`00000000 fffffa80`04273008 fffffa80`04274b68 fffff880`00dae8a0 : nt!KiPageFault+0x260
fffff880`07b27b30 00000000`00000000 : fffffa80`04273008 fffffa80`04274b68 fffff880`00dae8a0 fffffa80`04274b28 : amd_sata+0x266a
STACK_COMMAND: kb
FOLLOWUP_IP:
amd_sata+266a
fffff880`00dad66a 488b81d0150000 mov rax,qword ptr [rcx+15D0h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: amd_sata+266a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: amd_sata
IMAGE_NAME: amd_sata.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bedc8c7
FAILURE_BUCKET_ID: X64_0xD1_amd_sata+266a
BUCKET_ID: X64_0xD1_amd_sata+266a
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\042411-22994-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`02e64000 PsLoadedModuleList = 0xfffff800`030a1e50
Debug session time: Sun Apr 24 12:09:53.308 2011 (UTC - 4:00)
System Uptime: 0 days 0:32:18.180
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {15d0, 9, 0, fffff88000dd166a}
Unable to load image \SystemRoot\system32\drivers\amd_sata.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amd_sata.sys
*** ERROR: Module load completed but symbols could not be loaded for amd_sata.sys
Probably caused by : amd_sata.sys ( amd_sata+266a )
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: 00000000000015d0, memory referenced
Arg2: 0000000000000009, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000dd166a, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310c0e0
00000000000015d0
CURRENT_IRQL: 9
FAULTING_IP:
amd_sata+266a
fffff880`00dd166a 488b81d0150000 mov rax,qword ptr [rcx+15D0h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9c880 -- (.trap 0xfffff80000b9c880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88000dd166a rsp=fffff80000b9ca10 rbp=fffff80000b9cb80
r8=0000000000000029 r9=0000000000000000 r10=fffffa8004255008
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
amd_sata+0x266a:
fffff880`00dd166a 488b81d0150000 mov rax,qword ptr [rcx+15D0h] ds:00000000`000015d0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ed3ca9 to fffff80002ed4740
STACK_TEXT:
fffff800`00b9c738 fffff800`02ed3ca9 : 00000000`0000000a 00000000`000015d0 00000000`00000009 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c740 fffff800`02ed2920 : 00000002`00000001 fffffa80`04260f70 00000000`00000010 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c880 fffff880`00dd166a : 00000000`ffffffff fffffa80`04255008 fffffa80`04256b68 fffff880`00dd28a0 : nt!KiPageFault+0x260
fffff800`00b9ca10 00000000`ffffffff : fffffa80`04255008 fffffa80`04256b68 fffff880`00dd28a0 fffffa80`04256b28 : amd_sata+0x266a
fffff800`00b9ca18 fffffa80`04255008 : fffffa80`04256b68 fffff880`00dd28a0 fffffa80`04256b28 fffff800`00b9ca60 : 0xffffffff
fffff800`00b9ca20 fffffa80`04256b68 : fffff880`00dd28a0 fffffa80`04256b28 fffff800`00b9ca60 00000000`ffffffff : 0xfffffa80`04255008
fffff800`00b9ca28 fffff880`00dd28a0 : fffffa80`04256b28 fffff800`00b9ca60 00000000`ffffffff fffff880`00dd1a62 : 0xfffffa80`04256b68
fffff800`00b9ca30 fffffa80`04256b28 : fffff800`00b9ca60 00000000`ffffffff fffff880`00dd1a62 fffffa80`04aa8030 : amd_sata+0x38a0
fffff800`00b9ca38 fffff800`00b9ca60 : 00000000`ffffffff fffff880`00dd1a62 fffffa80`04aa8030 fffff800`00b9ca98 : 0xfffffa80`04256b28
fffff800`00b9ca40 00000000`ffffffff : fffff880`00dd1a62 fffffa80`04aa8030 fffff800`00b9ca98 fffff800`00000001 : 0xfffff800`00b9ca60
fffff800`00b9ca48 fffff880`00dd1a62 : fffffa80`04aa8030 fffff800`00b9ca98 fffff800`00000001 fffffa80`04260f70 : 0xffffffff
fffff800`00b9ca50 fffffa80`04aa8030 : fffff800`00b9ca98 fffff800`00000001 fffffa80`04260f70 00000000`00000000 : amd_sata+0x2a62
fffff800`00b9ca58 fffff800`00b9ca98 : fffff800`00000001 fffffa80`04260f70 00000000`00000000 fffff880`010cc0a3 : 0xfffffa80`04aa8030
fffff800`00b9ca60 fffff800`00000001 : fffffa80`04260f70 00000000`00000000 fffff880`010cc0a3 fffff800`fffffff8 : 0xfffff800`00b9ca98
fffff800`00b9ca68 fffffa80`04260f70 : 00000000`00000000 fffff880`010cc0a3 fffff800`fffffff8 fffff800`02ed0347 : 0xfffff800`00000001
fffff800`00b9ca70 00000000`00000000 : fffff880`010cc0a3 fffff800`fffffff8 fffff800`02ed0347 fffffa80`00000000 : 0xfffffa80`04260f70
STACK_COMMAND: kb
FOLLOWUP_IP:
amd_sata+266a
fffff880`00dd166a 488b81d0150000 mov rax,qword ptr [rcx+15D0h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: amd_sata+266a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: amd_sata
IMAGE_NAME: amd_sata.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4bedc8c7
FAILURE_BUCKET_ID: X64_0xD1_amd_sata+266a
BUCKET_ID: X64_0xD1_amd_sata+266a
Followup: MachineOwner
---------