BSOD分析

[swimmer2000]

Windows XP下的USB设备，使用我自己写的驱动后设备不停的Reset，该设备是透过一个USB Hub与电脑相连，
重启后得到如下的信息，请各位帮忙分析下原因：

*******************************************************************************
* *
* 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: 00000107, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f75489f0, address which referenced memory

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for bhound5.sys
*** ERROR: Module load completed but symbols could not be loaded for bhound5.sys
*** WARNING: Unable to verify timestamp for hcmon.sys
*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys

READ_ADDRESS: 00000107

CURRENT_IRQL: 2

FAULTING_IP:
usbhub!USBH_FdoQueryBusRelations+472
f75489f0 8b10 mov edx,dword ptr [eax]

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: System

LOCK_ADDRESS: 805523e0 -- (!locks 805523e0)

Resource @ nt!PiEngineLock (0x805523e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805523e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from f7548f9f to f75489f0

STACK_TEXT:
f78d2994 f7548f9f 84b26d50 846d8008 846d8008 usbhub!USBH_FdoQueryBusRelations+0x472
f78d29b4 f7549039 84b26d50 846d8008 00000007 usbhub!USBH_FdoPnP+0x143
f78d29dc f75491ee 84b26d50 846d8008 f78d2a08 usbhub!USBH_FdoDispatch+0x63
f78d29ec f7710435 84b26c98 846d8008 846d8008 usbhub!USBH_HubDispatch+0x5e
WARNING: Stack unwind information not available. Following frames may be wrong.
f78d2a08 b56f67dd 84b26c98 00000000 846d8008 bhound5+0x1435
f78d2a24 804ef003 84b26c98 846d8008 f78d2aa4 hcmon+0x27dd
f78d2a34 805880a9 00000000 84713ee8 84713fc8 nt!IopfCallDriver+0x31
f78d2a60 804f6ba9 84b26c98 f78d2a80 84713fc8 nt!IopSynchronousCall+0xb7
f78d2aa8 805843b5 00000000 84784530 00000001 nt!IopQueryDeviceRelations+0x45
f78d2ac0 80587817 84713ee8 00000001 84a8d208 nt!PipEnumerateDevice+0x23
f78d2d18 80587c56 84713ee8 00000001 00000000 nt!PipProcessDevNodeTree+0x21b
f78d2d4c 804f675d 00000003 805524c0 8055b47c nt!PiProcessReenumeration+0x60
f78d2d74 8053500e 00000000 00000000 86fba8b8 nt!PipDeviceActionWorker+0x141
f78d2dac 805c5d5e 00000000 00000000 00000000 nt!ExpWorkerThread+0x100
f78d2ddc 805421f2 80534f0e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
bhound5+1435
f7710435 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: bhound5+1435

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bhound5

IMAGE_NAME: bhound5.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f8bbffd

FAILURE_BUCKET_ID: 0xD1_bhound5+1435

BUCKET_ID: 0xD1_bhound5+1435

Followup: MachineOwner
---------

[曹大夯]

可能你的设备有问题，某些实现不符合USB规范。然后系统里又安装的Bushoud，Bushound在某些情况下非常容易蓝屏。

[cnzdgs]

从错误信息来看，是访问了无效地址。根据调用堆栈的信息找到自己的代码，设置断点调试。常见的原因是传递的参数不正确或者没有正确执行相关的初始化操作。

[swimmer2000]

Call Stack里并没有调用我写的驱动程序，所以应该和我的驱动无关。
google到默认的usbhub驱动在连续移除设备时会崩溃。

[swimmer2000]

问题还是没解决

[swimmer2000]

真实是我的驱动导致设备Reset，继而引起USBHUB蓝屏。
出现问题的语句是StartDevice里的：
// Start out with the device powered down.
GenericIdleDevice(pdx->pgx, PowerDeviceD3);
改成
GenericIdleDevice(pdx->pgx, PowerDeviceD0);
问题解决。

这个问题与硬件也有关系，因为硬件没有处理好供电状态变换。