When the first one happened i was using the Driver "TBS 5922 USB DVBS/S2 BDA, 09.09.2011, 2.0.1.6"
I was looking for a solution, and hoped that the recently released Driver "TBS 5922 USB DVBS/S2 BDA, 25.11.2011, 2.0.1.9" would fix it. Today i got another blue screen running the new driver though.
Also, while rebooting directly after the blue screen the system would hang in BIOS POST, even after a cold restart, until i unplug the TBS5922 from USB. It seems like the TBS5922 switches into a state blocking the USB during the crashes. After windows reboot the TBS5922 doesn't work if i just replug USB. It is shown as unknown USB device. I have to unplug the TBS5922 power cable once to make it work again, so the hardware seems to run into a strange locked up state.
The TBS5922 is directly connected to my Mainboards IO-Panel (Model GA-MA78GM-S2H rev 1.1).
I am running Windows 7 64-Bit.
I hope my information helps in debugging the issue. I added the WinDbg output of both bluescreens below.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Andy\Desktop\TBS Debug\112611-12916-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325e670
Debug session time: Sat Nov 26 16:04:26.786 2011 (UTC + 1:00)
System Uptime: 4 days 5:36:51.224
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa800b0ce440, fffff80000ba2748, fffffa8009026790}
Probably caused by : usbhub.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: fffffa800b0ce440, Physical Device Object of the stack
Arg3: fffff80000ba2748, Functional Device Object of the stack
Arg4: fffffa8009026790, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15
MODULE_NAME: usbhub
FAULTING_MODULE: fffff880064aa000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: plugin-contain
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00ba26f8 fffff800`03103cd2 : 00000000`0000009f 00000000`00000003 fffffa80`0b0ce440 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`030a15fc : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00ba27a0 fffff800`030a1496 : fffff800`03240f00 00000000`0165cec7 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`030a137e : 00000353`b87b2375 fffff800`00ba2e88 00000000`0165cec7 fffff800`0320fb68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`030a1167 : fffffa80`079431c1 fffffa80`0165cec7 00000000`00000000 00000000`000000c7 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`03098765 : 00000000`00000000 fffffa80`0b0db2d0 00000000`00000000 fffff880`014cfa00 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`0309857c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`029f5be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_tbs5922_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_3_tbs5922_IMAGE_usbhub.sys
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Andy\Desktop\TBS Debug\112911-12994-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03013000 PsLoadedModuleList = 0xfffff800`03258670
Debug session time: Tue Nov 29 09:35:26.705 2011 (UTC + 1:00)
System Uptime: 0 days 20:50:51.365
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
.........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80080e9060, fffff80000b9c518, fffffa8015e67890}
Probably caused by : usbhub.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: fffffa80080e9060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa8015e67890, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88006227000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00b9c4c8 fffff800`030fdcd2 : 00000000`0000009f 00000000`00000003 fffffa80`080e9060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`0309b5fc : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`0309b496 : fffff800`0323af00 00000000`004968ca 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`0309b37e : 000000ae`be197956 fffff800`00b9cc58 00000000`004968ca fffff800`03209bc8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`0309b167 : 00000033`6c42d3c1 00000033`004968ca 00000033`6c42d3b5 00000000`000000ca : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`0308796a : fffff800`03205e80 fffff800`03213cc0 00000000`00000000 fffff880`016f0a00 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_tbs5922_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_3_tbs5922_IMAGE_usbhub.sys
Followup: MachineOwner
---------
