BSOD randomly while surfing--BCCode: 9f Drive_Power_State_Failure

MightyWind · 05 Dec 2013

BSOD randomly while surfing listed as Driver_Power_State_Failure. I'm a newb who just registered but have attached the zipped SF file for your perusal if you so choose. Not even sure how to open the .dmp file to further explore the issue.

Thanks for whatever help you can provide.

Aaron

MightyWind · 05 Dec 2013

Update: I upgraded the BIOS versions to A11 then A12 to see if that might help solve the problem and also installed driver updates. While restarting the system to apply BIOS updates, just prior to shut down I received 2 consecutive BSOD notifications that were identical to the others experienced in the past. The system is back up and running smoothly for now...pretty sure the BSODs will start soon. Dell PC diagnostics haven't located any hardware issues but did see the BSOD notices. No solutions offered from Dell...

koolkat77 · 06 Dec 2013

Please remove Norton for testing purpose. Use Microsoft Security Essentials, it is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET

Run Disk Check on your Hard Drive(s): Disk Check

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Please remove the software below with Revo Uninstaller Free:

Code:

Start Menu\Programs\RegClean Pro	Public:Start Menu\Programs\RegClean Pro	Public

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling. This allows you to remove leftover registry entries of the software: Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence. If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything. 10 Tips on How to Properly Maintain Your Computer

Let us know the results.

Code:


Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_05-12-2013\SF_05-12-2013\120513-53305-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00764962?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00ba2730?
Symbol search path is: SRV*c:\symbols*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 Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03665000 PsLoadedModuleList = 0xfffff800`038a86d0
Debug session time: Thu Dec  5 22:24:17.378 2013 (UTC + 6:00)
System Uptime: 0 days 0:56:54.205
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800b6ca060, fffff80000ba2748, fffffa800a415bd0}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************
Probably caused by : usbhub.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800b6ca060, Physical Device Object of the stack
Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800a415bd0, The blocked IRP

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: USBHUB!_DEVICE_EXTENSION_PDO                  ***
***                                                                   ***
*************************************************************************

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5227239a

MODULE_NAME: usbhub

FAULTING_MODULE: fffff880050b1000 usbhub

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  N360.exe

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00ba26f8 fffff800`0374a8d2 : 00000000`0000009f 00000000`00000003 fffffa80`0b6ca060 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`036e585c : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00ba27a0 fffff800`036e56f6 : fffff800`0388af80 00000000`000356e9 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`036e55de : 00000007`f3066fa1 fffff800`00ba2e88 00000000`000356e9 fffff800`03859fa8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`036e53c7 : fffffa80`0af25cc1 fffffa80`000356e9 00000000`00000000 00000000`000000e9 : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`036ddd15 : 00000000`00000000 fffffa80`07a32b50 00000000`00000000 fffff880`018c2800 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`036ddb2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0e090750 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_BTHUSB_IMAGE_usbhub.sys

BUCKET_ID:  X64_0x9F_3_BTHUSB_IMAGE_usbhub.sys

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

0: kd> !irp fffffa800a415bd0
Irp is active with 12 stacks 11 is current (= 0xfffffa800a415f70)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800c539040 00000000 00000000-00000000    pending
	       \Driver\BTHUSB
			Args: 00000000 00000001 00000003 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8007700010    

			Args: 00000000 00000000 00000000 00000000

MightyWind · 07 Dec 2013

Koolkat77:

Thanks very much for the assistance. I followed your direction for the past 2.5 days and the BSOD problem seems to have been resolved.

I removed Norton for BSOD testing purposes, ran MS Security Essentials (full scan found nothing), reduced startup files, ran Malware Bytes (found 404 cookies and 1 potentially dangerous file called PUP.cnet Installer which apparently is simply an adware bundle so perhaps not terribly malicious), ran a clean boot, ran TDSSKiller from Kaspersky (found nothing), ran ESET's scanner (cleared a few items but nothing that appeared terribly malicious), ran disk check on both C:\ and D:\ drives which essentially found nothing, defragged both drives, ran memtest overnight to well over 200% on all checks (no bad memory), got rid of a lot of old crap and updated as many drivers as applied to my system.

I believe I've narrowed the issue down to a few possibilities: I had an old thumb drive that no longer had updates available which may have caused issues with usbhub.sys, my Dell touchpad driver needed an update, my Intel Wireless-N adapter driver was way out of date, the BIOS had 2 more versions available which I installed.

After all that, no BSOD issues have resurfaced and my system is running like a jackrabbit on coke with faster boot times, videos loading faster, heavier websites loading quickly and all around better responsiveness. I'd love to be able to say which of these solutions was the one that did the trick but alas I fixed so many outstanding issues, I may never know. If it does resurface, I'll certainly be back for follow-on advice, but in the meantime I'll just say "Thank you!"

Best,

Aaron

p.s. Should I reinstall Norton at this point?

koolkat77 · 08 Dec 2013

Install norton if you didn't get BSOD's after disabling Norton.

You may have to unisntall norton if the BSOD's come back though.