Hi guys. Im looking for some help with my BSOD issue. I installed everything like requested and got no errors. Now if i leave my unattended for about 15mins, the computer will blue screen and then restart. not sure why it is doing this but it is getting very annoying as i built my rig as a gaming rig and need it to perform flawlessly.....of course....
attached is the zip of my file in the minidump folder(zipped with winrar). I hve no knowledge on how to fix this so maybe you can help me understand this.
I am running WIN 7 Ult x64 if that helps any.
any help is appreciated.
Thanks!!!
USBHUB.sys. Run system file check to verify and repair suystem files
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\032211-23836-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:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ace90
Debug session time: Tue Mar 22 17:57:29.197 2011 (GMT-4)
System Uptime: 0 days 2:09:21.086
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80077b4060, fffff80000b9c518, fffffa800a39e310}
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: fffffa80077b4060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800a39e310, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800a39e310
DEVICE_OBJECT: fffffa80077b4060
DRIVER_OBJECT: fffffa80075d2060
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a68e
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005b22000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003153b52 to fffff800030e7640
STACK_TEXT:
fffff800`00b9c4c8 fffff800`03153b52 : 00000000`0000009f 00000000`00000003 fffffa80`077b4060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030f3062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`030f2f06 : fffff800`0328f740 00000000`0007975e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`030f2dee : 00000012`11f7c1ce fffff800`00b9cc58 00000000`0007975e fffff800`0325ce48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030f2bd7 : 00000005`ac1961c1 00000005`0007975e 00000005`ac196177 00000000`0000005e : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030df36a : fffff800`03259e80 fffff800`03267cc0 00000000`00000001 fffff880`00000000 : 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_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_IMAGE_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: fffffa80077b4060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800a39e310, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa800a39e310
DEVICE_OBJECT: fffffa80077b4060
DRIVER_OBJECT: fffffa80075d2060
IMAGE_NAME: usbhub.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a68e
MODULE_NAME: usbhub
FAULTING_MODULE: fffff88005b22000 usbhub
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80003153b52 to fffff800030e7640
STACK_TEXT:
fffff800`00b9c4c8 fffff800`03153b52 : 00000000`0000009f 00000000`00000003 fffffa80`077b4060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`030f3062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90
fffff800`00b9c570 fffff800`030f2f06 : fffff800`0328f740 00000000`0007975e 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`030f2dee : 00000012`11f7c1ce fffff800`00b9cc58 00000000`0007975e fffff800`0325ce48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`030f2bd7 : 00000005`ac1961c1 00000005`0007975e 00000005`ac196177 00000000`0000005e : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`030df36a : fffff800`03259e80 fffff800`03267cc0 00000000`00000001 fffff880`00000000 : 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_IMAGE_usbhub.sys
BUCKET_ID: X64_0x9F_IMAGE_usbhub.sys
Followup: MachineOwner
---------
Old drivers needing update
Code:
SaiH0BAC.sys 7/2/2007 5:25:35 fffff880`07390000 fffff880`073b9b00 0x00029b00 0x4688c48f
SaiH0C2D.sys 7/2/2007 5:25:35 fffff880`0733b000 fffff880`07364b00 0x00029b00 0x4688c48f
SaiH0763.sys 2/15/2008 9:15:05 fffff880`07365000 fffff880`0738f380 0x0002a380 0x47b59059
gfvknt64.sys 11/24/2008 14:43:41 fffff880`04a29000 fffff880`04a33000 0x0000a000 0x492af5dd
tcusb.sys 12/8/2008 19:54:41 fffff880`073ba000 fffff880`073cd000 0x00013000 0x493db3c1
hamachi.sys 2/19/2009 6:36:41 fffff880`059f4000 fffff880`059ff000 0x0000b000 0x499d3639
gdrv.sys 3/12/2009 23:22:29 fffff880`088c6000 fffff880`088cf000 0x00009000 0x49b9d175
spldr.sys 5/11/2009 12:56:27 fffff880`01909000 fffff880`01911000 0x00008000 0x4a0858bb
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads
Quote