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\013111-17518-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a3b000 PsLoadedModuleList = 0x82b83810
Debug session time: Mon Jan 31 16:15:20.298 2011 (UTC - 5:00)
System Uptime: 0 days 0:10:03.968
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..................................................
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: 86c6ee10, Device object pointer.
Arg3: 850f7900, Power Irp.
Arg4: 8642dcf0, Reserved.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
BUGCHECK_STR: 0x10D_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8ac4ef9e to 82b17d10
STACK_TEXT:
9d88bbec 8ac4ef9e 0000010d 0000000d 86c6ee10 nt!KeBugCheckEx+0x1e
9d88bc08 8ac61f72 8642dcf0 0000000d 86c6ee10 Wdf01000!FxVerifierBugCheck+0x24
9d88bc24 8ac61fce 8642dcf0 9d88bc50 8ac55e02 Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x6e
9d88bc30 8ac55e02 86c6e010 9d88bc58 850f7900 Wdf01000!FxPkgFdo::_DispatchSetPower+0x23
9d88bc50 8ac32a3f 850f7900 9d88bc78 8ac32c63 Wdf01000!FxPkgPnp::Dispatch+0x207
9d88bc5c 8ac32c63 86c6ee10 850f7900 850f7900 Wdf01000!FxDevice::Dispatch+0x7f
9d88bc78 82a46d16 86c6ee10 850f7900 00000016 Wdf01000!FxDevice::DispatchWithLock+0x7b
9d88bc90 82a774ae 00000003 86c6ee10 9d88bca8 nt!IopPoHandleIrp+0x28
9d88bca0 82a49049 9d88bcd8 9691528c 86c6ee10 nt!IofCallDriver+0x55
9d88bca8 9691528c 86c6ee10 850f7900 00620073 nt!IoCallDriver+0x10
WARNING: Stack unwind information not available. Following frames may be wrong.
9d88bcd8 969123dc 86c670e0 850f7900 82b7c400 libusb0+0x428c
9d88bcf8 82a46823 86c67028 850f7900 00000000 libusb0+0x13dc
9d88bd50 82c496d3 8680c828 b586f017 00000000 nt!PopIrpWorker+0x351
9d88bd90 82afb0f9 82a464d2 8680c828 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
libusb0+428c
9691528c ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: libusb0+428c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: libusb0
IMAGE_NAME: libusb0.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45ffb877
FAILURE_BUCKET_ID: 0x10D_d_libusb0+428c
BUCKET_ID: 0x10D_d_libusb0+428c
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\013111-21933-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a44000 PsLoadedModuleList = 0x82b8c810
Debug session time: Mon Jan 31 14:36:23.033 2011 (UTC - 5:00)
System Uptime: 0 days 0:50:02.687
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
..................................................
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: 86d33ef0, Device object pointer.
Arg3: 87449738, Power Irp.
Arg4: 8645ff08, Reserved.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
BUGCHECK_STR: 0x10D_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8ac7df9e to 82b20d10
STACK_TEXT:
8c137bec 8ac7df9e 0000010d 0000000d 86d33ef0 nt!KeBugCheckEx+0x1e
8c137c08 8ac90f72 8645ff08 0000000d 86d33ef0 Wdf01000!FxVerifierBugCheck+0x24
8c137c24 8ac90fce 8645ff08 8c137c50 8ac84e02 Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x6e
8c137c30 8ac84e02 86d30d30 8c137c58 87449738 Wdf01000!FxPkgFdo::_DispatchSetPower+0x23
8c137c50 8ac61a3f 87449738 8c137c78 8ac61c63 Wdf01000!FxPkgPnp::Dispatch+0x207
8c137c5c 8ac61c63 86d33ef0 87449738 87449738 Wdf01000!FxDevice::Dispatch+0x7f
8c137c78 82a4fd16 86d33ef0 87449738 00000016 Wdf01000!FxDevice::DispatchWithLock+0x7b
8c137c90 82a804ae 00000003 86d33ef0 8c137ca8 nt!IopPoHandleIrp+0x28
8c137ca0 82a52049 8c137cd8 9522828c 86d33ef0 nt!IofCallDriver+0x55
8c137ca8 9522828c 86d33ef0 87449738 00620073 nt!IoCallDriver+0x10
WARNING: Stack unwind information not available. Following frames may be wrong.
8c137cd8 952253dc 86d340e0 87449738 82b85400 libusb0+0x428c
8c137cf8 82a4f823 86d34028 87449738 00000000 libusb0+0x13dc
8c137d50 82c526d3 87035ea8 a4109078 00000000 nt!PopIrpWorker+0x351
8c137d90 82b040f9 82a4f4d2 87035ea8 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
libusb0+428c
9522828c ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: libusb0+428c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: libusb0
IMAGE_NAME: libusb0.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45ffb877
FAILURE_BUCKET_ID: 0x10D_d_libusb0+428c
BUCKET_ID: 0x10D_d_libusb0+428c
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\013111-19266-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 (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a56000 PsLoadedModuleList = 0x82b9e810
Debug session time: Mon Jan 31 21:42:28.457 2011 (UTC - 5:00)
System Uptime: 0 days 0:09:54.517
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
..................................................
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000d, A power irp was received for the device but the irp was not
requested by the device (the power policy owner). Possibly there
are multiple power policy owners. Only one driver in the stack can
be the power policy owner. A KMDF driver can change power policy
ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
Arg2: 86203cf0, Device object pointer.
Arg3: 855a3278, Power Irp.
Arg4: 86be6388, Reserved.
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
BUGCHECK_STR: 0x10D_d
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 8ac7ef9e to 82b32d10
STACK_TEXT:
9b6bbbec 8ac7ef9e 0000010d 0000000d 86203cf0 nt!KeBugCheckEx+0x1e
9b6bbc08 8ac91f72 86be6388 0000000d 86203cf0 Wdf01000!FxVerifierBugCheck+0x24
9b6bbc24 8ac91fce 86be6388 9b6bbc50 8ac85e02 Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x6e
9b6bbc30 8ac85e02 86bea950 9b6bbc58 855a3278 Wdf01000!FxPkgFdo::_DispatchSetPower+0x23
9b6bbc50 8ac62a3f 855a3278 9b6bbc78 8ac62c63 Wdf01000!FxPkgPnp::Dispatch+0x207
9b6bbc5c 8ac62c63 86203cf0 855a3278 855a3278 Wdf01000!FxDevice::Dispatch+0x7f
9b6bbc78 82a61d16 86203cf0 855a3278 00000016 Wdf01000!FxDevice::DispatchWithLock+0x7b
9b6bbc90 82a924ae 00000004 86203cf0 9b6bbca8 nt!IopPoHandleIrp+0x28
9b6bbca0 82a64049 9b6bbcd8 93f3b28c 86203cf0 nt!IofCallDriver+0x55
9b6bbca8 93f3b28c 86203cf0 855a3278 858cc010 nt!IoCallDriver+0x10
WARNING: Stack unwind information not available. Following frames may be wrong.
9b6bbcd8 93f383dc 86c4a0e0 855a3278 82b97400 libusb0+0x428c
9b6bbcf8 82a61823 86c4a028 855a3278 00000000 libusb0+0x13dc
9b6bbd50 82c646d3 86c1e9f0 b364df67 00000000 nt!PopIrpWorker+0x351
9b6bbd90 82b160f9 82a614d2 86c1e9f0 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
libusb0+428c
93f3b28c ?? ???
SYMBOL_STACK_INDEX: a
SYMBOL_NAME: libusb0+428c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: libusb0
IMAGE_NAME: libusb0.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 45ffb877
FAILURE_BUCKET_ID: 0x10D_d_libusb0+428c
BUCKET_ID: 0x10D_d_libusb0+428c
Followup: MachineOwner
---------