DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe (again)


  1. Posts : 11
    Windows 7
       #1

    DRIVER_POWER_STATE_FAILURE caused by ntoskrnl.exe (again)


    In my previous thread about a week ago I solved this problem by updating my Ralink USB wireless driver. Things were fine for a few days. Then after Windows Update (it seems) the problem is back.

    The two dumps of concern are from Sep/12/2012 and Sep/11/2012.

    I'd appreciate it if someone can figure out the offending driver this time. Thanks.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    No dumps? - :)
      My Computer


  3. Posts : 11
    Windows 7
    Thread Starter
       #3

    Forgot the attachment
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Get an update for your atheros driver Driver Reference Table - athrxusb.sys

    Code:
     kd> lmvm athrxusb
    start             end                 module name
    fffff880`062b6000 fffff880`063c3000   athrxusb T (no symbols)           
        Loaded symbol image file: athrxusb.sys
        Image path: \SystemRoot\system32\DRIVERS\athrxusb.sys
        Image name: athrxusb.sys
        Timestamp:        Tue Jul 29 18:17:13 2008 (488F1151)
        CheckSum:         00107E18
        ImageSize:        0010D000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  5. Posts : 11
    Windows 7
    Thread Starter
       #5

    Thanks for the info koolkat77. I've updated my Atheros driver and hopefully this is resolved.
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    You're welcome.
    Let us know if you have more BSoDs
      My Computer


  7. Posts : 11
    Windows 7
    Thread Starter
       #7

    I updated the Atheros driver from this link: MSI Global ? Mainboard - 785GM-P45

    When I hibernated yesterday it went into the "driver power state" BSOD again. I've attached the dump. Is it still from the Atheros driver?
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Well done on the update. Now, have a look again:
    Code:
    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: fffffa800a781060, Physical Device Object of the stack
    Arg3: fffff80000ba2748, Functional Device Object of the stack
    Arg4: fffffa800bcfc010, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  usbhub.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15
    
    MODULE_NAME: usbhub
    
    FAULTING_MODULE: fffff880048e2000 usbhub
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`00ba26f8 fffff800`02f336c2 : 00000000`0000009f 00000000`00000003 fffffa80`0a781060 fffff800`00ba2748 : nt!KeBugCheckEx
    fffff800`00ba2700 fffff800`02ed3e3c : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34050
    fffff800`00ba27a0 fffff800`02ed3cd6 : fffff800`03070f20 00000000`00333725 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00ba2810 fffff800`02ed3bbe : 00000079`e998ad69 fffff800`00ba2e88 00000000`00333725 fffff800`0303e728 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00ba2e60 fffff800`02ed39a7 : fffff800`0303bec1 fffffa80`00333725 fffffa80`08969d40 00000000`00000025 : nt!KiTimerExpiration+0x1be
    fffff800`00ba2f00 fffff800`02ecc305 : 00000000`00000000 fffffa80`07f26060 00000000`00000000 fffff880`03e02db0 : nt!KiRetireDpcList+0x277
    fffff800`00ba2fb0 fffff800`02ecc11c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`0af05be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_netr28ux_IMAGE_usbhub.sys
    
    BUCKET_ID:  X64_0x9F_3_netr28ux_IMAGE_usbhub.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa800bcfc010
    Irp is active with 7 stacks 5 is current (= 0xfffffa800bcfc200)
     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
    >[ 16, 2]   0  0 fffffa800a7cc050 00000000 00000000-00000000    
              Unable to load image \SystemRoot\system32\DRIVERS\netr28ux.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for netr28ux.sys
    *** ERROR: Module load completed but symbols could not be loaded for netr28ux.sys
     \Driver\netr28ux
                Args: 00015500 00000000 00000005 00000003
     [ 16, 2]   0 e1 fffffa800a7f3520 00000000 fffff8000310d200-fffffa800b440db0 Success Error Cancel pending
               \Driver\vwifibus    nt!PopSystemIrpCompletion
                Args: 00015500 00000000 00000005 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800b440db0    
    
                Args: 00000000 00000000 00000000 00000000
    0: kd> !devobj fffffa800a7cc050
    Device object (fffffa800a7cc050) is for:
     InfoMask field not found for _OBJECT_HEADER at fffffa800a7cc020
     \Driver\netr28ux DriverObject fffffa800a7da060
    Current Irp 00000000 RefCount 0 Type 00000017 Flags 00002050
    DevExt fffffa800a7cc1a0 DevObjExt fffffa800a7cd8b8 
    ExtensionFlags (0x00000800)  
                                 Unknown flags 0x00000800
    AttachedDevice (Upper) fffffa800a7f3520 \Driver\vwifibus
    AttachedTo (Lower) fffffa800a781060 \Driver\usbhub
    Device queue is not busy.
    So, it is Ralink RT2870 series USB802.11n Wireless Adapter Driver now.
    I would suggest you to first uninstall the driver, and then get the updates from Ralink-A MEDIATEK COMPANY.

    BTW, how many network connections do you use? You should uninstall those drivers those you dont use.
      My Computer


  9. Posts : 11
    Windows 7
    Thread Starter
       #9

    Arc, I appreciate the reply.

    I had updated the Ralink RT2870 from that link due to a prior BSOD, which centaur78 found to be caused by the Ralink adapter. I will try to uninstall the driver first, and then reinstall it.

    I am not sure why this is happening now as I have been using the computer the same way a long time, and it only started acting this way since a recent Windows update it seems.

    I have never been able to properly hibernate/sleep my self built rigs consistently ever since Vista came out.
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    Let us know the result.

    If needed, we will search for the reason again, if it is really that driver, or actually a hardware component.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:07.
Find Us