How to fix "DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time."

Question

Ive build a PC with these components:

• AMD Ryzen 7 7800X3D 5,0GHz AM5
• ASUS ROG Strix X670E-F Gaming Wifi
• ASUS ROG Strix 1200W Gold Aura Edition
• AMD Radeon RX 7900 XTX 24 GB
• G.Skill Trident Z 5, 2x 32GB, DDR5 RAM
• 3x M.2 SSD (one has the system on it)
• 1x SSD
• 1x HDD
• AIO and several fans

At first the PC had Windows 10 and tons of BSOD's, all the same "driver power state failure". I went to a Service and they told me to switch out the RAM (was Corsair Dominator Titanium DDR5-6400, CL32, Intel XMP, 2x 32GB) as that was incompatible with my build. After the RAM switch we installed Windows11 and everything worked fine without any BSOD's for a couple weeks.

Now, out of nowhere, the BSOD's came back. Again, the Driver Power State Failure. It only happens after I start my Computer within 2-3 Minutes. When it doesnt Bluescreen, everything works fine for hours without any problems ever. The BSOD's dont appear on every restart and sometimes will appear 3-5 times in a row (Bluescreen, restart, bluescreen, restart, ...).

I thought it might be some drivers or the things i have plugged into my pc. So i disconnected a lot of it and uninstalled all drivers that seemed suspicius to me. Nothing changed, every other restart is a BSOD. Doesnt seem to be a cold start problem either since it doesnt always happen on cold starts. Ironically the last 2 times when I brought the Computer to the service, they couldnt trigger the bluescreen for many tries and hours. The moment i go back home and start it up, it bluescreens. Could be (un)lucky or maybe an indicator?

It could technically be my mouse, keyboard, monitor or microphone, but i really dont know.

I have run the latest minidump file through WINdbg and got this result. I dont see anything pointing towards the reason though. Any suggestions are welcomed and thank you in advance for your help.

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

Microsoft (R) Windows Debugger Version 10.0.27704.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\101924-14453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff807`37600000 PsLoadedModuleList = 0xfffff807`382134b0
Debug session time: Sat Oct 19 19:43:00.953 2024 (UTC + 2:00)
System Uptime: 0 days 0:05:42.741
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000087`5f951018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`37a14df0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa901`642b7b20=000000000000009f
6: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: ffffc505a2c7b060, Physical Device Object of the stack
Arg3: ffffa901642b7b68, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc505af0bf010, The blocked IRP

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1796

    Key  : Analysis.Elapsed.mSec
    Value: 11357

    Key  : Analysis.IO.Other.Mb
    Value: 18

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 28

    Key  : Analysis.Init.CPU.mSec
    Value: 156

    Key  : Analysis.Init.Elapsed.mSec
    Value: 60292

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 99

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x9f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x9f

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x9F_3_ACPI_IMAGE_pci.sys

    Key  : Failure.Hash
    Value: {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : Stack.Pointer
    Value: NMI

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc505a2c7b060

BUGCHECK_P3: ffffa901642b7b68

BUGCHECK_P4: ffffc505af0bf010

FILE_IN_CAB:  101924-14453-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffc505bfbae080

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

MODULE_NAME: pci

FAULTING_MODULE: fffff8073c650000 pci

BLACKBOXACPI: 1 (!blackboxacpi)

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  L-Connect-Serv

DPC_STACK_BASE:  FFFFA901642B7FB0

STACK_TEXT:  
ffffa901`642b7b18 fffff807`37b80906     : 00000000`0000009f 00000000`00000003 ffffc505`a2c7b060 ffffa901`642b7b68 : nt!KeBugCheckEx
ffffa901`642b7b20 fffff807`37b807dc     : 00000000`00000002 ffffe680`42bc0180 ffffc505`af0f5280 ffffa901`642b7c99 : nt!PopIrpWatchdogBugcheck+0x122
ffffa901`642b7ba0 fffff807`37811b4b     : ffffc505`00000005 ffffc505`00000001 ffffa901`00000000 00000000`00000002 : nt!PopIrpWatchdog+0xc
ffffa901`642b7bd0 fffff807`37812ed9     : b56f7253`00000052 00040f01`0000700c 00000000`00000001 fffff807`34b544c8 : nt!KiProcessExpiredTimerList+0x1eb
ffffa901`642b7d00 fffff807`37a1e665     : f018321c`000a341c 00000000`00000000 ffffe680`42bc0180 00000000`000000c8 : nt!KiRetireDpcList+0xaf9
ffffa901`642b7fb0 fffff807`37a1e60f     : ffffa901`6a8c6969 fffff807`37816075 00000000`00000000 ffffc505`a0010000 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffa901`6a8c68d0 fffff807`37816075     : 00000000`00000000 ffffc505`a0010000 fffff807`37600000 ffffc505`b16ba290 : nt!KiPlatformSwapStacksAndCallReturn
ffffa901`6a8c68e0 fffff807`37a1dd9b     : ffffc505`bfbae080 ffffc505`c268d7e0 ffffc505`a72fe640 fffff807`3786784c : nt!KiDispatchInterrupt+0xd5
ffffa901`6a8c69d0 fffff807`37a17941     : 00000000`68747541 ffffc505`c268d7e0 00000000`00000001 fffff807`3786af70 : nt!KiDpcInterruptBypass+0x1b
ffffa901`6a8c6a00 fffff807`3f0f109a     : ffffa901`6a8c7141 fffff807`3783c397 ffffc505`a72fe640 fffff807`3f0f5700 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
ffffa901`6a8c6b90 ffffa901`6a8c7141     : fffff807`3783c397 ffffc505`a72fe640 fffff807`3f0f5700 68747541`0000000d : cpuz158_x64+0x109a
ffffa901`6a8c6b98 fffff807`3783c397     : ffffc505`a72fe640 fffff807`3f0f5700 68747541`0000000d 69746e65`444d4163 : 0xffffa901`6a8c7141
ffffa901`6a8c6ba0 fffff807`3f0f58fe     : 00000000`00005867 00000000`00000000 00000000`0000000a 00000000`00000000 : nt!IofCompleteRequest+0x17
ffffa901`6a8c6bd0 00000000`00005867     : 00000000`00000000 00000000`0000000a 00000000`00000000 00000000`00000000 : cpuz158_x64+0x58fe
ffffa901`6a8c6bd8 00000000`00000000     : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5867

IMAGE_VERSION:  10.0.22621.1402

STACK_COMMAND:  .process /r /p 0xffffc505bf26c080; .thread 0xffffc505bfbae080 ; kb

FAILURE_BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

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

Answer 1

Hello, xaya712

Welcome to the Microsoft Community.

Hello, thank you for your feedback here on the issue you posted. The “DRIVER_POWER_STATE_FAILURE (9F)” error is a blue screen of death (BSOD) related to driver power management, which typically occurs when a device or driver fails to respond correctly when the system goes into hibernation, shuts down, or switches power states.

This issue may involve hardware, driver, or power management settings.

I will provide you some detailed steps, troubleshooting and fixing steps:

1. Update all drivers

Graphics Card Driver: You are using AMD Radeon RX 7900 XTX, make sure to use the latest driver. Visit the official AMD website to update your graphics card drivers.

Motherboard Drivers: Make sure you have the latest chipset drivers installed, which are critical for power management. Visit the official ASUS website to download and install the latest drivers.

Network drivers: If you are using a wireless card, make sure to update the wireless drivers.

Storage controller drivers: Check if the drivers for M.2 SSDs and other storage devices are the latest versions.

Updates can be made through Device Manager or by using Windows Update:

Right-click “This PC” -> Select “Manage” -> Open “Device Manager” -> Right-click related hardware -> Select “Update Driver”. Driver”.

2. Disable Fastboot

Fast startup can cause some devices to not wake up properly during power management. You can try to turn it off:

Go to Control Panel -> Power Options.

Click on “Select Power Button Functions” on the left side.

Click on “Change settings that are currently unavailable”.

Uncheck “Enable fast startup” and then save the changes.

3. Disable unnecessary startup items and devices

If the blue screen occurs within a few minutes after startup, some devices or external hardware may be causing the problem. Disconnect all unnecessary external devices (e.g. USB devices, printers, etc.) and check if the blue screen still occurs.

Disable certain startup items or services that are not commonly used, which can also be managed through the Task Manager's Startup tab. 4.

4. Check the power management settings

In the Device Manager, make sure that the “Allow computer to power down this device to save power” option is not enabled on your devices (especially display adapters, hard drives and network adapters):

Right-click on the hardware in Device Manager (e.g., network card, graphics card, hard drive, etc.).

Select “Properties” and switch to the “Power Management” tab.

Uncheck “Allow computer to turn off this device to save power”.

5. Check hardware compatibility

Even though you have replaced your RAM, some hardware may still not be fully compatible. Especially with your DDR5 RAM, even after replacing the RAM, there may still be some potential compatibility issues, especially in terms of power management.

You can try to test if the system still blue screens when certain hardware is not plugged in (e.g. graphics card, external hard disk, USB devices, etc.). If there is no blue screen, it may be triggered by a certain hardware component.

6. Check power settings and power supply

You are using an ASUS Gold power supply, which is usually of high quality, but it is still recommended that you make sure it is working stably, especially under heavy load. Check that the power supply is supplying stable power and that the power connections are correct.

You can try reconnecting the power supply plug to make sure that the output voltage of the power supply is within the normal range. You may also consider using a power supply diagnostic tool to check if the power supply is healthy.

7. Run System File Check

Run System File Check (sfc/scannow) and Disk Check (chkdsk):

Press Win + X to open the menu and select “Command Prompt (Administrator)”.

Enter the following command to check the integrity of system files:

sfc /scannow

Also run the Disk Check command to check for disk errors:

chkdsk C: /f

Disclaimer: Running Microsoft Safety Scanner can help you check if the system is disturbed or malicious software exists. To avoid any trouble for you, please back up all your personal files first to ensure you do not lose data.

Disclaimer: Running chkdsk can check the file system and file system metadata of a volume for logical and physical errors. To avoid any trouble for you, do not cancel or interrupt chkdsk, and back up important data.

More information please refer to this chkdsk | Microsoft Learn.

You can refer to the above steps for some troubleshooting, and if you have any progress you can share it here and I'll analyze it further for you.

Best regards

Bobhe | Microsoft Community Support Specialist

Answer 2

Hello Bobhe,

Unfortunately you havent replied to me anymore.

On October 29 I had the idea to check for another BIOS Update. There was one, so I updated my BIOS.

I was Bluescreen-free for over a week until now, sadly. Again, ntoskrnl.exe is the problem. At this point im pretty sure my CPU, Motherboard or RAM is faulty so I will give my PC to some Service and have them figure out the defect hardware.

One day i will hopefully be bluescreen-free forever...

Answer 3

Hello again Bobhe,

Unfortunately it happened again.

I was Bluescreen-free for 3 days. Until i decided to install VALORANT. After installing VALORANT and restarting my PC, i got these Bluescreen Loops again.

I was not patient enough to wait for the actual bluescreen and always manually shut of my pc.

I spoke to the RIOT Support about this, but they only say I should update all my drivers, which is not very helpful.

I uninstalled VALORANT. The next couple restarts were all BlueScreen-Free, so Valorant must have been the reason for these crashes.

After i spoke with the RIOT Support, I installed their "Riot Repair Tool". I kept this tool on my PC until today:

Today, I got another system crash immediately after starting my PC. But this time, i decided to wait for the actual bluescreen. After around 10 Minutes (!!!!) I got the Bluescreen (same BSOD as always). I am suspecting, that the Riot Repair Tool might have been the cause for that. I checked my Taskmanager, and saw that a "Riot" driver was in autostart (probably because of the tool). I uninstalled it now as well.

I have the MiniDump File, but WinDbg cannot read it for some reason. BlueScreenView was able to tell me, that a driver called "ntoskrnl.exe" was the reason for the BSOD. I dont know if that driver is connected to RIOT or not. Maybe you know more?

I can share the information I have about the crash and I would appreciate further help.

Is this a Problem caused by RIOT software / drivers or is there something wrong with my PC?

BlueScreenView:
Bug Check String: DRIVER_POWER_STATE_FAILURE
Bug Check Code: 0x0000009f
Parameter 1: 00000000`00000003

Parameter 2: ffffc081`0322e060

Parameter 3: fffff804`2f2ae010

Parameter 4: ffffc081`0cc47010

Caused by driver: ntoskrnl.exe
Caused by Address: ntoskrnl.exe+4b8680
Crash Address: ntoskrnl.exe+4b8680

Properties of ntoskrnl.exe:

Address in Stack: ntoskrnl.exe+58990d
From Address: fffff804`9cc00000

To Address: fffff804`9e04f000

Size: 0x0144f000

Time Stamp: 0xcb0fa9da

Time String: 15.12.2077 15:42:50

EDIT ~1h later:

I did a Memory Check with the "MdSched"-Tool and there were no errors or anything found.

Answer 4

Hi,xaya712

Thank you for your reply, it seems that the blue screen is not appearing at the moment, thanks for updating me on the new progress. If it's convenient for you please rate my reply, please click yes so that the rest of the community can quickly locate this thread for some advice.

Of course, if you continue to experience the blue screen in the future, you can continue to share your logs and other information here and I will continue to help you.

Best regards

Bobhe | Microsoft Community Support Specialist

Answer 5

Hi Bob. Thank you for your help.

I have every Software for the necessary drivers installed and theyre all up-to-date. (AMD-Adrenaline, Armoury Crate, Samsung Magician , L-Connect, ...)

Yesterday, even before you sent the answer to my post, I realized that my fast boot was enabled. I assumed it was disabled but to my surprise it wasnt. I disabled it in the windows settings and also in my BIOS. I didnt get any BSOD since yesterday.

I was unable to find the Prompt you explained at your 4. fix.

Ive ran the "scannow" and "chkdsk" for my System harddrive and the SSD and HDD. No Problems. But i cant find the Log for the Check on my System Disk anywhere.

Since I havent suffered from any Bluescreen since the Fast Boot change, i will wait and see if everything works. Should I get another BSOD, ill update here and check every device that is plugged into my PC. Like I said, I had already removed every unnecessary device other than my Mouse, keyboard and mic.

Again, thank you for your fast reply. I really appreciate your help. Ill be updating this post once I have new information.