Windows 10: DRIVER_POWER_STATE_FAILURE 9f

Discus and support DRIVER_POWER_STATE_FAILURE 9f in Windows 10 Drivers and Hardware to solve the problem; Hey everyone, My laptop Dell Precision 5530 blue screened yesterday: Drive Power State Failure. I am trying to figure out what is causing it. The... Discussion in 'Windows 10 Drivers and Hardware' started by MichaelTitone1, Feb 13, 2020 at 1:22 PM.

  1. DRIVER_POWER_STATE_FAILURE 9f


    Hey everyone,


    My laptop Dell Precision 5530 blue screened yesterday: Drive Power State Failure. I am trying to figure out what is causing it. The computer was plugged in to a thunderbolt docking station Dell WD15 which had two monitors attached to it. While restarting the laptop, it blue screened.


    Looks like a USB 3.0 issue of some kind, but I thought I would post it here in case anyone knows how to drill down for more information.




    DRIVER_POWER_STATE_FAILURE 9f
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
    Arg2: 000000000000012c, Timeout in seconds.
    Arg3: ffff8c8b57f95040, The thread currently holding on to the Pnp lock.
    Arg4: fffff80117401800, nt!TRIAGE_9F_PNP on Win7 and higher

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

    Implicit thread is now ffff8c8b`57f95040

    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

    SYSTEM_MANUFACTURER: Dell Inc.

    SYSTEM_PRODUCT_NAME: Precision 5530

    SYSTEM_SKU: 087D

    BIOS_VENDOR: Dell Inc.

    BIOS_VERSION: 1.15.0

    BIOS_DATE: 12/25/2019

    BASEBOARD_MANUFACTURER: Dell Inc.

    BASEBOARD_PRODUCT: 0NFGCT

    BASEBOARD_VERSION: A00

    DUMP_TYPE: 1

    BUGCHECK_P1: 4

    BUGCHECK_P2: 12c

    BUGCHECK_P3: ffff8c8b57f95040

    BUGCHECK_P4: fffff80117401800

    DRVPOWERSTATE_SUBCODE: 4

    IMAGE_NAME: UsbHub3.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4b5abbef

    MODULE_NAME: UsbHub3

    FAULTING_MODULE: fffff80128240000 UsbHub3

    CPU_COUNT: c

    CPU_MHZ: a20

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: a

    CPU_MICROCODE: 6,9e,a,0 F,M,S,R SIG: C6'00000000 cache C6'00000000 init

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x9F

    PROCESS_NAME: System

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: DESKTOP1

    ANALYSIS_SESSION_TIME: 02-13-2020 09:09:52.0047

    ANALYSIS_VERSION: 10.0.18362.1 x86fre

    STACK_TEXT:
    fffff801`174017c8 fffff801`1429c3ee : 00000000`0000009f 00000000`00000004 00000000`0000012c ffff8c8b`57f95040 : nt!KeBugCheckEx
    fffff801`174017d0 fffff801`14593976 : 00000000`00000002 fffff801`14575400 00000000`00000001 00000000`00000019 : nt!PnpBugcheckPowerTimeout+0x8a
    fffff801`17401830 fffff801`141039e9 : fffff801`14575400 00000000`000000ff fffff801`17401a18 00000000`00000008 : nt!PopBuildDeviceNotifyListWatchdog+0x16
    fffff801`17401860 fffff801`14104937 : 00000000`00000008 00000000`00989680 fffff801`14575400 00000000`00000019 : nt!KiProcessExpiredTimerList+0x159
    fffff801`17401950 fffff801`141d13aa : 00000000`00000000 fffff801`124ac180 00000000`001a6550 fffff801`14575400 : nt!KiRetireDpcList+0x4a7
    fffff801`17401b60 00000000`00000000 : fffff801`17402000 fffff801`173fb000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


    THREAD_SHA1_HASH_MOD_FUNC: 0efaf37e6601d7f65db9dbe50a219f0403a414f7

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 12d850c4ea804313b7c46e2f9fbbe8962c331702

    THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

    FOLLOWUP_NAME: MachineOwner

    IMAGE_VERSION: 10.0.17763.1

    STACK_COMMAND: .thread ; .cxr ; kb

    FAILURE_BUCKET_ID: 0x9F_4_rtux64w10_IMAGE_UsbHub3.sys

    BUCKET_ID: 0x9F_4_rtux64w10_IMAGE_UsbHub3.sys

    PRIMARY_PROBLEM_CLASS: 0x9F_4_rtux64w10_IMAGE_UsbHub3.sys

    TARGET_TIME: 2020-02-12T23:15:26.000Z

    OSBUILD: 17763

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 1979-05-30 19:50:38

    BUILDDATESTAMP_STR: 180914-1434

    BUILDLAB_STR: rs5_release

    BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

    ANALYSIS_SESSION_ELAPSED_TIME: 3726

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x9f_4_rtux64w10_image_usbhub3.sys

    FAILURE_ID_HASH: {26abe9d5-50b4-2d3d-cd98-02411775cc60}

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

    :)
     
    MichaelTitone1, Feb 13, 2020 at 1:22 PM
    #1

  2. BSOD DRIVER_POWER_STATE_FAILURE (9f) HELP

    A. Analysis Results

    File Name: 012419-10859-01.dmp

    DRIVER_POWER_STATE_FAILURE (9f)

    IMAGE_NAME: nwifi.sys

    *** WARNING: Unable to verify timestamp for VBoxNetLwf.sys

    B. Third Party Drivers

    VBoxNetLwf.sys - Virtual Box

    Driver Date - 8-Nov-2018

    C. Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    2. Update your Virtual box to latest. Your driver date is 8-Nov-18 and see if you get a driver later than this. If Virtual box is not required, get it uninstalled.
     
  3. Blue Screen of Death - DRIVER_POWER_STATE_FAILURE (9f)

    My computer started crashing with DRIVER_POWER_STATE_FAILURE (9f).

    I analyzed the dump files but cannot resolve which driver is resulting in this error. I also used google but not many errors of this type seem to occur and I was not able to find any with this specific driver.

    I hoped someone could clear this up for me.

    Here is the dump file:

     
    Robert-Bayer, Feb 13, 2020 at 1:30 PM
    #3
  4. Humpix Win User

    DRIVER_POWER_STATE_FAILURE 9f

    DRIVER_POWER_STATE_FAILURE (9f) usbccgp.sys

    Hi and thank you for your answer!

    I spend the whole night, learning how to read dmp - files.

    usbccgp.sys (I also have found a BSOD with UsbHub3.sys) is the one who crashed, but why?

    I found this very useful article:

    Bug Check 0x9F DRIVER_POWER_STATE_FAILURE - Windows drivers

    Sample 1:

    • WinDbg -> File -> Open Crash Dump -> c:\windows\minidump\xxx.dmp
    • BugCheck 9F, {3, ffff9002b91f86c0, ffffa7018acff960, ffff9002bcd4e9f0}
    • UsbHub3.sys
    3: kd> !devstack ffff9002b91f86c0

    !DevObj !DrvObj !DevExt ObjectName

    ffff9002b91f0e20 *** WARNING: Unable to verify timestamp for Wdf01000.sys

    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys

    \Driver\USBHUB3 ffff9002b91ed310 InfoMask field not found for _OBJECT_HEADER at ffff9002b91f0df0
    ffff9002b9218a00 \Driver\ACPI ffff9002b4de38b0 InfoMask field not found for _OBJECT_HEADER at ffff9002b92189d0
    > ffff9002b91f86c0 \Driver\USBHUB3 ffff9002b91ef310 Cannot read info offset from nt!ObpInfoMaskToOffset
    !DevNode ffff9002b91c4d30 :

    DeviceInst is "USB\VID_174C&PID_3074\5&1cc0e58a&0&21"

    ServiceName is "USBHUB3"

    Google tells me that this may be my onboard USB Hub (Asmedia) of my Asus X99 Mainboard.

    It could also be an internal USB Hub of some of my devices.

    Im not sure but I think they are connected at the intel usb ports.

    The Asus Sabertooth X99 has an additional Asmedia USB3.1 controller, but as far as I know without a hub...

    Sampe 2:

    • BugCheck 9F, {3, ffffd58f2a7e28d0, ffffac800ddff960, ffffd58f2d8e1580}
    • usbccgp.sys
    1: kd> !devstack ffffd58f2a7e28d0

    !DevObj !DrvObj !DevExt ObjectName

    ffffd58f2ad4de20 Unable to load image \SystemRoot\System32\drivers\ocusbvid111.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for ocusbvid111.sys

    *** ERROR: Module load completed but symbols could not be loaded for ocusbvid111.sys

    *** WARNING: Unable to verify timestamp for Wdf01000.sys

    *** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys

    \Driver\OCUSBVID ffffd58f2ad4ae10 InfoMask field not found for _OBJECT_HEADER at ffffd58f2ad4ddf0
    > ffffd58f2a7e28d0 \Driver\usbccgp ffffd58f2a7e2a20 Cannot read info offset from nt!ObpInfoMaskToOffset

    !DevNode ffffd58f2a891260 :

    DeviceInst is "USB\VID_2833&PID_0211&MI_00\7&2017bc24&0&0000"

    ServiceName is "OCUSBVID"

    This is from the Oculus Rift...

    With also have an internal USB Hub and is connected to one of the Intel USB ports with internal Hub.

    Im not sure if I have done it right, but I try to use the Asmedia USB3.1 ports for Oculus Rift the next days. I also will deactivate all power saving features on the device... Maybe this woraround helps, until all drivers are fixed.

    Please correct me, if I have undestand something wrong!

    BR!

    Mathias
     
Thema:

DRIVER_POWER_STATE_FAILURE 9f

Loading...
  1. DRIVER_POWER_STATE_FAILURE 9f - Similar Threads - DRIVER_POWER_STATE_FAILURE

  2. Help with Win10 BSoD DRIVER_POWER_STATE_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    Help with Win10 BSoD DRIVER_POWER_STATE_FAILURE: I've recently encountered a BSoD when trying to reboot my machine. Dump and nfo included in this link: https://1drv.ms/u/s!AngxJNDLcS3xgxn4NVg22WEMbpN8?e=pqN5zg I've also been getting the message "A disk read error has occurred, press Ctrl+Alt+Del to restart" when trying...
  3. BSOD: DRIVER_POWER_STATE_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    BSOD: DRIVER_POWER_STATE_FAILURE: I specially get this crash when loading a specific game it's accompanied with disk active time constantly at 100% i've tried driver verifier but when it crashes it gives me the same stop code not the verifier detected violation. i've tried some solution for the ntoskrnl.exe...
  4. Intermittent DRIVER_POWER_STATE_FAILURE BSOD when going to sleep

    in Windows 10 BSOD Crashes and Debugging
    Intermittent DRIVER_POWER_STATE_FAILURE BSOD when going to sleep: I have been getting intermittent BSOD when desktop goes to sleep. This has been going on for approx 4-6 weeks. Sometimes it will happen multiple times in a day or it may go a day or two with no BSOD. No driver is being called out only ntoskrnl.exe. I cannot pinpoint anything...
  5. BSOD : DRIVER_POWER_STATE_FAILURE

    in Windows 10 Drivers and Hardware
    BSOD : DRIVER_POWER_STATE_FAILURE: I have a laptop ASUS X550JK, I get the BSOD with DRIVER_POWER_STATE_FAILURE, it happens randomly, Before the BSOD occurs, I notice a rise in CPU temperature and the fan makes noise, What I've tried: I've tried to install Windows 10 with USB and CD/DVD Drive as well, but the...
  6. BSOD DRIVER_POWER_STATE_FAILURE after forced shutdown in Sleep Mode while Applications were...

    in Windows 10 BSOD Crashes and Debugging
    BSOD DRIVER_POWER_STATE_FAILURE after forced shutdown in Sleep Mode while Applications were...: My specs are: - Windows 10 Pro - Version: 10.0.18363 - System Modell: E6431 MD60109 Medion x64 - BIOS Version: American Megatrends Inc. 206, 24.06.2016 UEFI - SMBios Version: 3.0 I've encountered a really bad bug on my Medion Akoya E6431 Laptop: I think the problems...
  7. Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock

    in Windows 10 BSOD Crashes and Debugging
    Surface Book 2 BSOD - DRIVER_POWER_STATE_FAILURE 9f - Suspect Surface Dock: Hi, I recently purchased a Surface Dock and since then I have started to have DRIVER_POWER_STATE_FAILURE 9f BSODs when the system is idle, I assume when trying to hibernate. The crash dump below suggests that this is related to the dock ethernet drivers. The msux64w10...
  8. BSOD (DRIVER_POWER_STATE_FAILURE)

    in Windows 10 BSOD Crashes and Debugging
    BSOD (DRIVER_POWER_STATE_FAILURE): I updated my bios, it failed but my PC still works so here are the BSOD informations (these are different) : (1) IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: f525018 MODULE_NAME: pci FAULTING_MODULE: fffff80059080000 pci (2) MODULE_NAME: dxgkrnl...
  9. Getting BSOD Error with error as, Driver_power_State_failure. (A device object has been...

    in Windows 10 Drivers and Hardware
    Getting BSOD Error with error as, Driver_power_State_failure. (A device object has been...: I have previously uploaded the same question, but I didn't get any satisfactory answer. Please Help me out! Regards, Ashish Papanai https://answers.microsoft.com/en-us/windows/forum/all/getting-bsod-error-with-error-as/19ca71c5-5df7-4f7b-b15b-cdc3a890947a
  10. Blue screen error: DRIVER_POWER_STATE_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    Blue screen error: DRIVER_POWER_STATE_FAILURE: Hi, recently I've been unable to restart Windows. I get the spinning wheel that never ends. I end up having to shut off the computer using the power switch and turning it back on in order to get back into Windows. If I wait a while, sometimes I get a BSOD with the following...