Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032111-32406-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`043f6500?
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`0328ce50
Debug session time: Mon Mar 21 20:51:34.826 2011 (UTC - 4:00)
System Uptime: 0 days 22:00:51.253
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80071ed050, fffff800043f6518, fffffa8008b9ec50}
Probably caused by : sbp2port.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80071ed050, Physical Device Object of the stack
Arg3: fffff800043f6518, Functional Device Object of the stack
Arg4: fffffa8008b9ec50, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: sbp2port.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc119
MODULE_NAME: sbp2port
FAULTING_MODULE: fffff8800121b000 sbp2port
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`043f64c8 fffff800`0312e273 : 00000000`0000009f 00000000`00000003 fffffa80`071ed050 fffff800`043f6518 : nt!KeBugCheckEx
fffff800`043f64d0 fffff800`030cb29e : fffff800`043f6618 fffff800`043f6618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`043f6570 fffff800`030cadd6 : fffff800`0326f700 00000000`004d64d0 00000000`00000000 fffff880`041b97da : nt!KiProcessTimerDpcTable+0x66
fffff800`043f65e0 fffff800`030cb4be : 000000b8`856da9b5 fffff800`043f6c58 00000000`004d64d0 fffff800`0323dc88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`043f6c30 fffff800`030cacb7 : 00000030`2a492ec2 00000030`004d64d0 00000030`2a492e11 00000000`000000d0 : nt!KiTimerExpiration+0x1be
fffff800`043f6cd0 fffff800`030c7eea : fffff800`03239e80 fffff800`03247c40 00000000`00000000 fffff880`04199db0 : nt!KiRetireDpcList+0x277
fffff800`043f6d80 00000000`00000000 : fffff800`043f7000 fffff800`043f1000 fffff800`043f6d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_sbp2port.sys
BUCKET_ID: X64_0x9F_3_disk_IMAGE_sbp2port.sys
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032511-34375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`04401500?
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03243e50
Debug session time: Fri Mar 25 20:41:38.761 2011 (UTC - 4:00)
System Uptime: 3 days 23:49:51.703
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800716d050, fffff80004401518, fffffa8005d60770}
Probably caused by : sbp2port.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800716d050, Physical Device Object of the stack
Arg3: fffff80004401518, Functional Device Object of the stack
Arg4: fffffa8005d60770, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: sbp2port.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc119
MODULE_NAME: sbp2port
FAULTING_MODULE: fffff880013da000 sbp2port
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`044014c8 fffff800`030e5273 : 00000000`0000009f 00000000`00000003 fffffa80`0716d050 fffff800`04401518 : nt!KeBugCheckEx
fffff800`044014d0 fffff800`0308229e : fffff800`04401618 fffff800`04401618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`04401570 fffff800`03081dd6 : fffff800`03226700 00000000`0150e7ed 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`044015e0 fffff800`030824be : 00000323`3f144352 fffff800`04401c58 00000000`0150e7ed fffff800`031f5028 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04401c30 fffff800`03081cb7 : 000000d1`ac4e66c2 000000d1`0150e7ed 000000d1`ac4e669a 00000000`000000ed : nt!KiTimerExpiration+0x1be
fffff800`04401cd0 fffff800`0307eeea : fffff800`031f0e80 fffff800`031fec40 00000000`00000000 fffff880`01453c50 : nt!KiRetireDpcList+0x277
fffff800`04401d80 00000000`00000000 : fffff800`04402000 fffff800`043fc000 fffff800`04401d40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_disk_IMAGE_sbp2port.sys
BUCKET_ID: X64_0x9F_3_disk_IMAGE_sbp2port.sys
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032511-29593-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0304d000 PsLoadedModuleList = 0xfffff800`0328ae50
Debug session time: Fri Mar 25 21:54:34.084 2011 (UTC - 4:00)
System Uptime: 0 days 0:06:44.350
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\drivers\Lycosa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+1c23 )
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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, 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: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+6634346165623566
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff800030b546e to fffff800030bd710
STACK_TEXT:
fffff800`043f0ba8 fffff800`030b546e : 00000000`0000003c fffff880`00e01c74 fffff800`043f13b0 fffff800`030ea668 : nt!KeBugCheck
fffff800`043f0bb0 fffff800`030e340d : fffff800`032cbb7c fffff800`03205ea4 fffff800`0304d000 fffff800`043f1310 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`043f0be0 fffff800`030eaa90 : fffff800`0320cb34 fffff800`043f0c58 fffff800`043f1310 fffff800`0304d000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`043f0c10 fffff800`030ec06a : fffff800`043f1310 fffff800`043f13b0 fffff800`00000001 fffff800`043f1300 : nt!RtlDispatchException+0x410
fffff800`043f12f0 fffff800`03118112 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`07558d00 : nt!RtlRaiseStatus+0x4e
fffff800`043f1890 fffff880`061a4c23 : fffffa80`075909c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0xf5fc
fffff800`043f1910 fffffa80`075909c0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`00000000 : Lycosa+0x1c23
fffff800`043f1918 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`00000000 fffff880`00000000 : 0xfffffa80`075909c0
STACK_COMMAND: kb
FOLLOWUP_IP:
Lycosa+1c23
fffff880`061a4c23 ?? ???
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: Lycosa+1c23
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Lycosa
IMAGE_NAME: Lycosa.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c86fc86
FAILURE_BUCKET_ID: X64_0x1E_0_Lycosa+1c23
BUCKET_ID: X64_0x1E_0_Lycosa+1c23
Followup: MachineOwner
---------