Windows 10: BSOD Driver_Power_State_Failure

Discus and support BSOD Driver_Power_State_Failure in Windows 10 Drivers and Hardware to solve the problem; I've been getting this BSOD issue for quite some time now and I haven't been able to fix it. I've updated all my drivers and I'm still getting the... Discussion in 'Windows 10 Drivers and Hardware' started by Infestedfred, Jun 19, 2020.

  1. BSOD Driver_Power_State_Failure


    I've been getting this BSOD issue for quite some time now and I haven't been able to fix it. I've updated all my drivers and I'm still getting the errors. Here's what my debugger tells me this.


    Microsoft R Windows Debugger Version 10.0.19528.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\062020-37093-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff806`49600000 PsLoadedModuleList = 0xfffff806`4a22a2b0Debug session time: Sat Jun 20 00:43:10.155 2020 UTC + 8:00System Uptime: 1 days 2:14:57.815Loading Kernel Symbols..................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list............................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff806`499dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff806`4fa72b70=000000000000009fLoading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Can't set dump file contextsMachineInfo::SetContext failed - Thread: 0000011EAE7CB640 Handle: 1 Id: 1 - Error == 0x8000FFFF************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff806`49600000 PsLoadedModuleList = 0xfffff806`4a22a2b0Debug session time: Sat Jun 20 00:43:10.155 2020 UTC + 8:00System Uptime: 1 days 2:14:57.815Loading Kernel Symbols..................................................................................................................................................................................................................Loading User SymbolsPEB is paged out Peb.Ldr = 0000008b`aa1a1018. Type ".hh dbgerr001" for detailsLoading unloaded module list............................nt!KeBugCheckEx:fffff806`499dda20 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff806`4fa72b70=000000000000009f1:0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_POWER_STATE_FAILURE 9fA 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 timeArg2: ffffe1045cfc7050, Physical Device Object of the stackArg3: fffff8064fa72ba0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stackArg4: ffffe1046067a920, The blocked IRPDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on FRED-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 25 Key : Analysis.Memory.CommitPeak.Mb Value: 91 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 9fBUGCHECK_P1: 3BUGCHECK_P2: ffffe1045cfc7050BUGCHECK_P3: fffff8064fa72ba0BUGCHECK_P4: ffffe1046067a920DRVPOWERSTATE_SUBCODE: 3IMAGE_NAME: storahci.sysMODULE_NAME: storahciFAULTING_MODULE: fffff8064e7f0000 storahciBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1PROCESS_NAME: NZXT CAM.exeDPC_STACK_BASE: FFFFF8064FA72FB0STACK_TEXT: fffff806`4fa72b68 fffff806`49b6d657 : 00000000`0000009f 00000000`00000003 ffffe104`5cfc7050 fffff806`4fa72ba0 : nt!KeBugCheckExfffff806`4fa72b70 fffff806`49b6d571 : ffffe104`6067a1e8 fffff806`4fa72cc8 00000000`00000000 00000000`00367364 : nt!PopIrpWatchdogBugcheck+0xdffffff806`4fa72be0 fffff806`498368d2 : ffffe104`6067a220 fffff806`47659180 fffff806`4fa72e68 ffffe104`00000002 : nt!PopIrpWatchdog+0x31fffff806`4fa72c30 fffff806`49839d6d : fffff806`47659180 00000000`00000000 00000000`00000000 00000000`00367364 : nt!KiProcessExpiredTimerList+0x172fffff806`4fa72d20 fffff806`499e4a65 : 00000000`00000000 fffff806`47659180 fffff806`4a2f37c0 ffffa20a`c434f430 : nt!KiRetireDpcList+0x5ddfffff806`4fa72fb0 fffff806`499e4850 : fffff806`499d9b10 fffff806`49916b0a 00000000`00000000 ffffa20a`c434f2f8 : nt!KxRetireDpcList+0x5ffffa20a`c434f0a0 fffff806`499e4105 : ffffa20a`c434f430 fffff806`499dfab1 00000000`00009c34 fffff806`498c8872 : nt!KiDispatchInterruptContinueffffa20a`c434f0d0 fffff806`499dfab1 : 00000000`00009c34 fffff806`498c8872 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25ffffa20a`c434f0e0 fffff806`4993cf1a : fffff806`47659180 ffffffff`ffffffff 00000000`00000000 ffffa20a`c434f430 : nt!KiInterruptDispatchNoLockNoEtw+0xb1ffffa20a`c434f270 fffff806`498eef15 : fffff806`47659180 ffffa20a`c434f3a0 ffffa20a`c434f430 ffffe104`c2ffa080 : nt!ExpUpdateTimerConfigurationWorker+0xaaffffa20a`c434f2a0 fffff806`498ef096 : ffffe17b`3ac0f000 00000000`00000000 ffffa20a`c434f490 ffffa20a`c434f578 : nt!KeGenericProcessorCallback+0x125ffffa20a`c434f410 fffff806`4984e462 : 00000000`00000000 ffffe104`c0593080 ffffe17b`3ac0f7be ffffe104`c0593080 : nt!ExpUpdateTimerConfiguration+0x9affffa20a`c434f540 fffff806`49c376e4 : ffffe104`c0593080 00000000`00009c34 ffffa20a`c434f739 00000000`00000000 : nt!ExpUpdateTimerResolution+0xa6ffffa20a`c434f570 fffff806`499ef378 : ffffe104`c2ffa080 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtSetTimerResolution+0x104ffffa20a`c434f5d0 fffff806`499e1880 : fffff806`49a92f84 ffffe104`c0ddb040 00000000`00000001 ffffe104`c2ffa080 : nt!KiSystemServiceCopyEnd+0x28ffffa20a`c434f768 fffff806`49a92f84 : ffffe104`c0ddb040 00000000`00000001 ffffe104`c2ffa080 00000000`00000001 : nt!KiServiceLinkageffffa20a`c434f770 fffff806`49cc0b7d : ffffe104`00000000 ffffe104`c0593080 00000000`00000000 00000000`00000000 : nt!ExCleanTimerResolutionRequest+0x13abe0ffffa20a`c434f7a0 fffff806`49be8dee : ffffe104`c2ffa4b8 00000000`00000000 ffffa20a`c434f990 00000000`00000000 : nt!PspExitProcess+0xf5ffffa20a`c434f7d0 fffff806`49cf51e8 : 00000000`40010004 ffffe104`00000001 ffffa20a`c434f9e0 0000008b`aa1aa000 : nt!PspExitThread+0x5b2ffffa20a`c434f8d0 fffff806`4982a4e7 : 00000000`00000000 00000000`00000000 00000000`00000000 000524d8`00000000 : nt!KiSchedulerApcTerminate+0x38ffffa20a`c434f910 fffff806`499e1fc0 : 00000000`00000000 ffffa20a`c434f9c0 ffffa20a`c434fb80 0000021d`00000000 : nt!KiDeliverApc+0x487ffffa20a`c434f9c0 fffff806`499ef41f : ffffe104`c2ffa080 ffffe104`c2ed4360 00000000`00000000 00000000`00000000 : nt!KiInitiateUserApc+0x70ffffa20a`c434fb00 00007fff`9c40ae14 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f0000008b`a9f4fc28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`9c40ae14STACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0x9F_3_EhStorClass_IMAGE_storahci.sysOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {56abad41-1226-1f11-45f3-948c3e9f1482}Followup: MachineOwner---------

    :)
     
    Infestedfred, Jun 19, 2020
    #1
  2. Arul_D Win User

    BSOD: DRIVER_POWER_STATE_FAILURE Windows 10

    Hello,

    Thank you for contacting Microsoft Community.

    We understand the inconvenience you have experienced.

    I would suggest you to refer to the following suggestion provided by SpiritX MS MVP replied on January 25, 2016 and check if it helps. Refer to the below link:

    BSoD: DRIVER_POWER_STATE_FAILURE | Windows 10

    BSoD: DRIVER_POWER_STATE_FAILURE | Windows 10

    Hope this information is helpful. If you need any further assistance, please feel free to reply.
     
    Arul_D, Jun 19, 2020
    #2
  3. Knots23 Win User
    BSOD when running on battery - driver_power_state_failure

    ***Merged***

    Hello,

    Since a few months my laptop - MSI GS60 2PE running Windows 10 Home - started giving BSOD's with the DRIVER_POWER_STATE_FAILURE after a seemingly random time when running on the battery. As I'm using it every day for work,
    I depend on the machine and managed by just plugging it in.

    While that works, I know it should be possible to make it work on the battery...

    I've recently "reset this pc" using the build in option in Windows 10, after which I installed all "latest" drivers from the MSI site. I also re-installed all programs required to do my job and play some games.

    Yesterday, Windows wanted to install the Fall Creators Update: I did. Booting the laptop while unplugged now gave me another BSOD, though with a different message: VIDEO_DXGKRNL_FATAL_ERROR. This seems to point to the Intel HD 4600 or Nvidia
    GTX 870M.

    To sum up some other issues I was starting out with...

    Syptoms

    • When unplugged, a BSOD occurs after a seemingly random time. (driver_power_state_failure)
      • After updating to the fall creators version, it also throws video_dxgkrnl_fatal_error; feels like a coin flip which one it will show.
    • Bluetooth was failing after a couple of minutes, regardless whether I used it or not and whether the laptop was plugged in or not.
    • Shutting down Windows would sometimes just heat up the CPU, make the fan go haywire and do nothing but turning the screen off.

    I've tried / did:

    • All drivers are up to date. This was verified by using DriverView and manually going over all of the non-Microsoft drivers.
      • This step fixed symptom 2 described above. Next to the latest version there was some patch (or 3 major versions ago) that couldn't be removed by conventional means. The build in troubleshooter actually removed it and bluetooth is now working
        as it should.
      • The HD4600 drivers were removed from the device management and I installed the latest according to the Intel site.
      • DDU was used in safe mode to remove the Nvidia driver and the latest one was installed.
    • BlueScreenViewer shows the minidumps and lots of drivers.
      • The one created when the driver_power_state_failure occurred is useless, as nothing is marked but the ntoskrnl.
      • The one created when the video_dxgkrnl_fatal_error occurred shows ntoskrnl, watchdog and dxgkrnl.
    • A clean boot (disabling all non-Microsoft services and disabling all startup programs) still results in the BSOD.
    • Booting the laptop while plugged in, letting it run for a couple of minutes so everything is started and then unplugging it also seems to work.
      • Yesterday, I unplugged it and could work with it for about 2.5 hours before it called out for power: I doubt the battery is the issue.
      • I was asked to run a battery check (powercfg -energy -output ...) but that doesn't seem to show any issues. (design capacity '55031' Last full
        charge '38556'. The laptop is over three years old.)
    • Starting in safe mode with networking will not result in a BSOD. (At least not within the hour I left it on.)
    • Unchecking 'turn on fast startup' - as suggested in so many posts - in the power settings only causes issues.
      • When unchecked, windows won't shut down properly.
      • When checked, it does shut down normally. This seems to be the
        fix for symptom 3.
    • Running various Windows troubleshooters didn't do much. Only the 'Windows Update' said it had some fixes regarding the database and 'fixed' it.
    • The bios is up to date. (Version E16H2IMS.112)

    Any help would be welcome.

    Cheers!

    PS: yes this post looks a lot like my
    previous post
    , but that was marked answered because a moderator thinks all checks suggested can be performed within three days, next to a daily routine.
     
    Knots23, Jun 19, 2020
    #3
  4. BSOD Driver_Power_State_Failure

    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


    BSOD Driver_Power_State_Failure gDUxQ.png


    When I check the dump file, I get this :


    BSOD Driver_Power_State_Failure 4w1fx.png


    What I've tried:

    1. I've tried to install Windows 10 with USB and CD/DVD Drive as
      well, but the same issue happened every time.
    2. I've updated all drivers (using Driver Booster,Driver
      Reviver
      and DriverPack solution).
    3. I've changed some Power settings.

    NOTE: With Linux (Ubuntu 19.04 & Mint), everything works just fine, I've used Linux for 1 week, and I didn't face any issue with it.

    Can anyone help me to get resolve this issue, I've spent a lot of time to solve it with no success
     
    Mouaad Abdelghafour AITALI, Jun 19, 2020
    #4
Thema:

BSOD Driver_Power_State_Failure

Loading...
  1. BSOD Driver_Power_State_Failure - Similar Threads - BSOD Driver_Power_State_Failure

  2. BSOD DRIVER_POWER_STATE_FAILURE

    in Windows 10 BSOD Crashes and Debugging
    BSOD DRIVER_POWER_STATE_FAILURE: My Dell Latitude 3410 crashed while the lid is closed and the fans started to get loud and when the lid is opened, it displayed a BSOD and shows the stop code: DRIVER_POWER_STATE_FAILURE. How to resolve this problem?...
  3. BSOD DRIVER_POWER_STATE_FAILURE

    in Windows 10 Gaming
    BSOD DRIVER_POWER_STATE_FAILURE: My Dell Latitude 3410 crashed while the lid is closed and the fans started to get loud and when the lid is opened, it displayed a BSOD and shows the stop code: DRIVER_POWER_STATE_FAILURE. How to resolve this problem?...
  4. BSOD DRIVER_POWER_STATE_FAILURE

    in Windows 10 Software and Apps
    BSOD DRIVER_POWER_STATE_FAILURE: My Dell Latitude 3410 crashed while the lid is closed and the fans started to get loud and when the lid is opened, it displayed a BSOD and shows the stop code: DRIVER_POWER_STATE_FAILURE. How to resolve this problem?...
  5. DRIVER_POWER_STATE_FAILURE leading to BSOD. I have Asus G14 laptop R7 4800HS + nvidia 1650

    in Windows 10 Gaming
    DRIVER_POWER_STATE_FAILURE leading to BSOD. I have Asus G14 laptop R7 4800HS + nvidia 1650: This is the dump file: -DRIVER_POWER_STATE_FAILURE 9fA 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...
  6. DRIVER_POWER_STATE_FAILURE leading to BSOD. I have Asus G14 laptop R7 4800HS + nvidia 1650

    in Windows 10 Software and Apps
    DRIVER_POWER_STATE_FAILURE leading to BSOD. I have Asus G14 laptop R7 4800HS + nvidia 1650: This is the dump file: -DRIVER_POWER_STATE_FAILURE 9fA 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...
  7. DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+416c30 BSOD

    in Windows 10 Gaming
    DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+416c30 BSOD: Hello,Since few weeks i'm experiencing randomly BSOD on my computer on windows 11 23h2.I uploaded the minidump on the following link : https://drive.google.com/file/d/1nB5xuNzfr-aX-XSvBU5bwQ0UOrPTejFH/view?usp=sharingCan someone help me to understand how to resolve this issue...
  8. DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+416c30 BSOD

    in Windows 10 Software and Apps
    DRIVER_POWER_STATE_FAILURE ntoskrnl.exe+416c30 BSOD: Hello,Since few weeks i'm experiencing randomly BSOD on my computer on windows 11 23h2.I uploaded the minidump on the following link : https://drive.google.com/file/d/1nB5xuNzfr-aX-XSvBU5bwQ0UOrPTejFH/view?usp=sharingCan someone help me to understand how to resolve this issue...
  9. BSOD Kernel-Power Event 41 BugCheckCode: 159 DRIVER_POWER_STATE_FAILURE

    in Windows 10 Gaming
    BSOD Kernel-Power Event 41 BugCheckCode: 159 DRIVER_POWER_STATE_FAILURE: Hello, I have experienced a BSOD on my lenovo laptop. It is a LOQ 15APH8 with RTX 3050. The issue occured when I was installing a new driver version. I will upload a copy of 3 dump file as this BSOD has also occured when I tried to DDU the driver:https://we.tl/t-3Uaca9i06P...
  10. BSOD Kernel-Power Event 41 BugCheckCode: 159 DRIVER_POWER_STATE_FAILURE

    in Windows 10 Software and Apps
    BSOD Kernel-Power Event 41 BugCheckCode: 159 DRIVER_POWER_STATE_FAILURE: Hello, I have experienced a BSOD on my lenovo laptop. It is a LOQ 15APH8 with RTX 3050. The issue occured when I was installing a new driver version. I will upload a copy of 3 dump file as this BSOD has also occured when I tried to DDU the driver:https://we.tl/t-3Uaca9i06P...