locked
POWER_STATE_FAILURE BSOD Possibly Due To Graphics Driver? RRS feed

  • Question

  • My computer has been crashing for months. i've went to two other forums for help but to no avail. I have run WhoCrashed and it said that the crash was caused by an unknown driver casing a power state failure. Any help is appreciated.

    Thanks!

    • Moved by Carey FrischMVP Saturday, August 13, 2011 3:05 AM Moved to more appropriate forum category (From:Windows 7 Miscellaneous)
    Saturday, August 13, 2011 1:55 AM

Answers

  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa8007b58060, Physical Device Object of the stack
    Arg3: fffff8000443e748, Functional Device Object of the stack
    Arg4: fffffa8008b5e010, The blocked IRP
    Debugging Details:
    ------------------
    DRVPOWERSTATE_SUBCODE:  3
    DRIVER_OBJECT: fffffa8006ba51f0
    IMAGE_NAME:  usbhub.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15
    MODULE_NAME: usbhub
    FAULTING_MODULE: fffff880050ac000 usbhub
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  mscorsvw.exe
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`0443e6f8 fffff800`03105cd2 : 00000000`0000009f 00000000`00000003 fffffa80`07b58060 fffff800`0443e748 : nt!KeBugCheckEx
    fffff800`0443e700 fffff800`030a35fc : fffff800`0443e830 fffff800`0443e830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`0443e7a0 fffff800`030a3496 : fffff800`03242f00 00000000`00132cd2 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`0443e810 fffff800`030a337e : 0000002d`a4e44534 fffff800`0443ee88 00000000`00132cd2 fffff800`03211cc8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`0443ee60 fffff800`030a3167 : fffff800`0320dec1 fffffa80`00132cd2 fffffa80`06a62a30 00000000`000000d2 : nt!KiTimerExpiration+0x1be
    fffff800`0443ef00 fffff800`0309a765 : 00000000`00000000 fffffa80`06362b60 00000000`00000000 fffff880`03d3cdb0 : nt!KiRetireDpcList+0x277
    fffff800`0443efb0 fffff800`0309a57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0a241be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys
    BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys
    Followup: MachineOwner
    ---------
    ----------------------------------------------------------------------------------------
    Your BSOD was caused by usbhub,sys driver. Possible that you have hardware problems with your USB ports.
    Start updating your chipset driver and check again. If this does ot help, I recommend contacting your manufacturer Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    • Marked as answer by Arthur Xie Tuesday, August 23, 2011 9:10 AM
    Friday, August 19, 2011 3:32 PM
  • Just to add, the problem may be "MotioninJoy":

    Arg4: fffffa8008b5e010, The blocked IRP

    : kd> !irp fffffa8008b5e010
    Irp is active with 13 stacks 10 is current (= 0xfffffa8008b5e368)
     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
    >[ 16, 2]   0 e1 fffffa8007b58060 00000000 fffff80003084430-fffffa8005f914d0 Success Error Cancel pending
            \Driver\usbhub nt!IopUnloadSafeCompletion
       Args: 00041100 00000001 00000001 00000002
     [ 16, 2]   0 e1 fffffa80078b6e20 00000000 fffff80003084430-fffffa8005346af0 Success Error Cancel pending
           Unable to load image \SystemRoot\system32\DRIVERS\MijXfilt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MijXfilt.sys
    *** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
     \Driver\MotioninJoyXFilter nt!IopUnloadSafeCompletion
       Args: 00041100 00000001 00000001 00000002
     [ 16, 2]   0 e1 fffffa80078bfe20 00000000 fffff80003084430-fffffa8005be06d0 Success Error Cancel pending
           Unable to load image \SystemRoot\system32\DRIVERS\xusb21.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for xusb21.sys
    *** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
     \Driver\xusb21 nt!IopUnloadSafeCompletion
       Args: 00041100 00000001 00000001 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005e2a1c0   

       Args: 00000000 00000000 00000000 00000000

     

    So, if problems persist uninstall MotioninJoy.

    Same software, same problem in following link:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/bsod-driver-power-state-failure-after-woken-from/1b1d380a-2a18-4822-9041-6a9ec0962136

     

     



    • Marked as answer by Ninemas Thursday, August 25, 2011 4:02 PM
    Tuesday, August 23, 2011 4:56 PM

All replies

  • Hi Ninemas,

    WhoCrashed will give you more information if you enable full kernel dump instead of mini-dump, which is the default.

    Please see this article about dumps, and how to enable a full dump on your machine:

    http://support.microsoft.com/kb/254649

    I'm sure we can help.  Please post the exact BSOD error here.


    If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer".
    Saturday, August 13, 2011 3:31 AM
  • Thanks for your help!

     

    Here is everything WhoCrashed tells me about both mine-dumps and the kernel dump:

    Crash Dump Analysis



    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.


    On Sat 8/13/2011 3:53:19 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081211-29874-01.dmp
    uptime: 02:16:27
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8006921060, 0xFFFFF80000B9C518, 0xFFFFFA8005D36B80)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 8/13/2011 3:53:19 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    uptime: 02:16:27
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8006921060, 0xFFFFF80000B9C518, 0xFFFFFA8005D36B80)
    Error: DRIVER_POWER_STATE_FAILURE
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Sat 8/13/2011 1:35:51 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081211-29140-01.dmp
    uptime: 03:31:11
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA800690A060, 0xFFFFF80004441518, 0xFFFFFA800913B6B0)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 8/12/2011 10:04:08 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\081211-28704-01.dmp
    uptime: 00:27:28
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8006898060, 0xFFFFF80000B9C518, 0xFFFFFA8008DCD010)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    Saturday, August 13, 2011 8:29 PM
  • According to the MSDN documentation, this describes your problem:

    "If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error."

    To confirm this, boot up in:

    1. Safe mode ...and see how long the pc stays up for

    2. Clean mode ...and see if the problem goes away.

    For more info on booting in 'Clean Mode', (all non-Microsoft drivers disabled), please post back here.


    If you found this post helpful, please give it a "Helpful" vote. If it answered your question, remember to mark it as an "Answer".
    • Edited by Bigteddy Sunday, August 14, 2011 6:44 AM Typos
    • Proposed as answer by pkn2011 Friday, August 19, 2011 1:10 PM
    Sunday, August 14, 2011 5:55 AM
  • Hi, well perhaps you've an LPM incompatability? see the following thread for more details..

    http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/74656f79-6642-4ba5-9129-820e8a5c1901

     

    Regards, pkn


    If my post was helpful - give it a Vote. If it helps solve your problem - propose it as Answer. ;-)
    Sunday, August 14, 2011 6:40 AM
  • I looked at the thread and disabled an ATI High Def driver. If my computer crashes again I will try to boot in both Safe Mode and Clean Mode and give you guys an update.
    Monday, August 15, 2011 2:12 AM
  • Hello,

    Bug CHeck Code 0x9F: http://msdn.microsoft.com/en-us/library/ff559329(VS.85).aspx

    Please use Microsoft Skydrive to upload dump files (c:\windows\minidumps). Once done, post a link here.

    You can also contact Microsoft CSS.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    • Proposed as answer by pkn2011 Friday, August 19, 2011 1:11 PM
    Monday, August 15, 2011 9:35 AM
  • Here is the link to the dumps: 

    https://skydrive.live.com/redir.aspx?cid=9f5509103fa2b919&resid=9F5509103FA2B919!102&authkey=pB3OuV6s*Zs%24

     

    Disabling that driver did not help sadly.

     

    However, I entered Safe Mode and my computer did not crash for hours cauing me to believe it definitely is due to a driver.


    Monday, August 15, 2011 8:59 PM
  • Hi, you said.. "Disabling that driver did not help sadly."

    You can try turning OFF the 'Link State Power Management' in advanced power settings, under PCI express. Until you can track which driver is causing the problem.

    Hopefully Mr X can post that dump in here for us to look at soon too. :)

     

    Regards, pkn


    If my post was helpful - give it a Vote. If it helps solve your problem - propose it as Answer. ;-)
    Monday, August 15, 2011 9:13 PM
  • You may boot in Clean Boot Mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Proposed as answer by pkn2011 Friday, August 19, 2011 1:11 PM
    Tuesday, August 16, 2011 6:32 AM
  • I tried memtest, but it stopped running twice in the middle of the test.

    I also turned off Link State Power Management for both plugged in and not plugged in and my computer still crashes.

    Thursday, August 18, 2011 11:03 PM
  • *******************************************************************************
    *                                                                             *
    *                        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: fffffa8007b58060, Physical Device Object of the stack
    Arg3: fffff8000443e748, Functional Device Object of the stack
    Arg4: fffffa8008b5e010, The blocked IRP
    Debugging Details:
    ------------------
    DRVPOWERSTATE_SUBCODE:  3
    DRIVER_OBJECT: fffffa8006ba51f0
    IMAGE_NAME:  usbhub.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c15
    MODULE_NAME: usbhub
    FAULTING_MODULE: fffff880050ac000 usbhub
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x9F
    PROCESS_NAME:  mscorsvw.exe
    CURRENT_IRQL:  2
    STACK_TEXT:  
    fffff800`0443e6f8 fffff800`03105cd2 : 00000000`0000009f 00000000`00000003 fffffa80`07b58060 fffff800`0443e748 : nt!KeBugCheckEx
    fffff800`0443e700 fffff800`030a35fc : fffff800`0443e830 fffff800`0443e830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`0443e7a0 fffff800`030a3496 : fffff800`03242f00 00000000`00132cd2 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`0443e810 fffff800`030a337e : 0000002d`a4e44534 fffff800`0443ee88 00000000`00132cd2 fffff800`03211cc8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`0443ee60 fffff800`030a3167 : fffff800`0320dec1 fffffa80`00132cd2 fffffa80`06a62a30 00000000`000000d2 : nt!KiTimerExpiration+0x1be
    fffff800`0443ef00 fffff800`0309a765 : 00000000`00000000 fffffa80`06362b60 00000000`00000000 fffff880`03d3cdb0 : nt!KiRetireDpcList+0x277
    fffff800`0443efb0 fffff800`0309a57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
    fffff880`0a241be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    STACK_COMMAND:  kb
    FOLLOWUP_NAME:  MachineOwner
    FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys
    BUCKET_ID:  X64_0x9F_3_IMAGE_usbhub.sys
    Followup: MachineOwner
    ---------
    ----------------------------------------------------------------------------------------
    Your BSOD was caused by usbhub,sys driver. Possible that you have hardware problems with your USB ports.
    Start updating your chipset driver and check again. If this does ot help, I recommend contacting your manufacturer Technical Support.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator 

    • Marked as answer by Arthur Xie Tuesday, August 23, 2011 9:10 AM
    Friday, August 19, 2011 3:32 PM
  • I updated my chipset driver and am now waiting to see if another crash occurs.

     

    Thanks for all your help guys.


    Tuesday, August 23, 2011 2:37 PM
  • Just to add, the problem may be "MotioninJoy":

    Arg4: fffffa8008b5e010, The blocked IRP

    : kd> !irp fffffa8008b5e010
    Irp is active with 13 stacks 10 is current (= 0xfffffa8008b5e368)
     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
    >[ 16, 2]   0 e1 fffffa8007b58060 00000000 fffff80003084430-fffffa8005f914d0 Success Error Cancel pending
            \Driver\usbhub nt!IopUnloadSafeCompletion
       Args: 00041100 00000001 00000001 00000002
     [ 16, 2]   0 e1 fffffa80078b6e20 00000000 fffff80003084430-fffffa8005346af0 Success Error Cancel pending
           Unable to load image \SystemRoot\system32\DRIVERS\MijXfilt.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MijXfilt.sys
    *** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
     \Driver\MotioninJoyXFilter nt!IopUnloadSafeCompletion
       Args: 00041100 00000001 00000001 00000002
     [ 16, 2]   0 e1 fffffa80078bfe20 00000000 fffff80003084430-fffffa8005be06d0 Success Error Cancel pending
           Unable to load image \SystemRoot\system32\DRIVERS\xusb21.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for xusb21.sys
    *** ERROR: Module load completed but symbols could not be loaded for xusb21.sys
     \Driver\xusb21 nt!IopUnloadSafeCompletion
       Args: 00041100 00000001 00000001 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005e2a1c0   

       Args: 00000000 00000000 00000000 00000000

     

    So, if problems persist uninstall MotioninJoy.

    Same software, same problem in following link:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/bsod-driver-power-state-failure-after-woken-from/1b1d380a-2a18-4822-9041-6a9ec0962136

     

     



    • Marked as answer by Ninemas Thursday, August 25, 2011 4:02 PM
    Tuesday, August 23, 2011 4:56 PM
  • The problem was MotioninJoy!

    Thank You!

    Thursday, August 25, 2011 4:03 PM
  • You're welcome.

    Thursday, August 25, 2011 9:23 PM