BSOD ntoskrnl.exe DRIVER_POWER_STATE_FAILURE 0x0000009f

M

Microfishd

New member
Joined
Nov 22, 2016
Posts
3
Hi,
Please help me with my BSoD! It is getting a bit frustrating.
I have the following:
OS: 7 Home Premium 64bit OEM (Lenovo) (original OS, not reinstalled)
purchased 2009/2010
CPU: AMD Athlon IIx2 215
GPU: AMD 760G (Radeon3000?)
Motherboard: Lenovo Tilapia CRB (Sapphire Hybrid CrossFire 780G ?)
PSU: Ultra LSP550
Lenovo H215 Desktop



Over the last few days, I have had four BSODs with the same code (0x9f) and BlueScreenView lists the crash address as ntoskrnl.exe
Some years ago, we had similar problems, where it would crash if it timed-out into sleepmode (somewhere between p[ower states S1-S3), and solved it by either applying a hotfix or we updated/removed a driver, but I don't remember which.

I know that the Perfmon log wrongly shows no anti-virus, but I have McAfee suite and MalwareBytes.
Sfc /scannow shows no errors.:s4:

Bluscreenview shows:
==================================================
Dump File : 112216-16504-01.dmp
Crash Time : 11/22/2016 8:40:14 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`04602060
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`0688b680
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+73c40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.19045 (win7sp1_gdr.151019-1254)
Processor : x64
Crash Address : ntoskrnl.exe+73c40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\112216-16504-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7601
Dump File Size : 1,085,408
Dump File Time : 11/22/2016 9:31:26 AM
==================================================
==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+e3930
From Address : fffff800`03a63000
To Address : fffff800`0404f000
Size : 0x005ec000
Time Stamp : 0x5625815c
Time String : 10/19/2015 5:48:44 PM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7601.19045 (win7sp1_gdr.151019-1254)
Company : Microsoft Corporation
Full Path : C:\windows\system32\ntoskrnl.exe
==================================================

Full BlueScreenView Logs hereView attachment 11-22-2016 BSV full.zip

Any and all help is greatly appreciated. I think that it is probably a driver, but I have no way of knowing which one it is, and don't feel like updating all of them one at a time.
Thank you!

Sysnative BSOD and Perfmon Log files are here:
View attachment Perfmon 2016-11-22.zipView attachment SysnativeFileCollectionApp.zip
 
Hi Microfishd,

Looks to be the network driver, usbhub.sys fault with a blocked IRP.

From the most recent minidump:

Code: 
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005dab060, Physical Device Object of the stack
Arg3: fffff80005106518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: [COLOR=#008000]fffffa8008537360[/COLOR], The blocked IRP


0: kd> !irp fffffa8008537360
Irp is active with 7 stacks 5 is current (= 0xfffffa8008537550)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  0 fffffa8005de4050 00000000 00000000-00000000    
          *** WARNING: Unable to verify timestamp for netr7364.sys
*** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
 \Driver\[COLOR=#ff0000]netr7364[/COLOR]
            Args: 00015400 00000000 00000005 00000003
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 fffffa8003c6ee10 00000000 fffff80003d28210-fffffa8003e32ca0 Success Error Cancel pending
           \Driver\[COLOR=#ff0000]vwifibus[/COLOR]    nt!PopSystemIrpCompletion
            Args: 00015400 00000000 00000005 00000003

0: kd> lmvm netr7364
Browse full module list
start             end                 module name
fffff880`02407000 fffff880`024c0000   netr7364 T (no symbols)           
    Loaded symbol image file: netr7364.sys
    Image path: \SystemRoot\system32\DRIVERS\netr7364.sys
    Image name: netr7364.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Feb 24 02:02:51 2010 (4B84CF1B)
    CheckSum:         000B3720
    ImageSize:        000B9000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm vwifibus
Browse full module list
start             end                 module name
fffff880`024c0000 fffff880`024cd000   vwifibus   (pdb symbols)          c:\symbols\vwifibus.pdb\DA6BF743D34D43E986CA50E6ADF553061\vwifibus.pdb
    Loaded symbol image file: vwifibus.sys
    Mapped memory image file: c:\symbols\vwifibus.sys\4A5BCC39d000\vwifibus.sys
    Image path: \SystemRoot\system32\DRIVERS\vwifibus.sys
    Image name: vwifibus.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 13 20:07:21 2009 (4A5BCC39)
    CheckSum:         0000C5FA
    ImageSize:        0000D000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     VWiFiBus.sys
    OriginalFilename: VWiFiBus.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Virtual WiFi Bus Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Does this sound similar as to what you were experiencing before?
 
First off, thanks very much for your quick response!
I think that first (series of) times, we might have been on an Ethernet cable--at least we definitely were at the time of the May BSoD. When the Oct31 @10AM BSOD occurred we were on Ethernet, but that night we had to use the Ethernet cable (for a different PC) and switched (this one) back to the WIFI USB stick.

Sometimes it seemed it would only crash (on wake?) when it went (or was put) into sleep.

How would I go about fixing this problem? Device Manager>Network Adapters, and tell them both to look for updates, or the same on/for any of the USB devices, or a specific USB device from the Device Manager's list:
Device Manager.jpg ?

Thank you very much!
 
Thanks to MichaelB for filling in the blanks, that was my thinking as well. Hopefully things have been smooth for you since!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top