DRIVER_POWER_STATE_FAILURE (9F)

Lanz · Monday at 9:44 AM

I've been experiencing intermittent BSODs that always occur within a few minutes of boot. The issue seems to be related to PCI/USB devices...? CPU e Motherboard are brand new: two weeeks old. I experience this kind of BSOD 3 times. Two back to back last week. Last one yesterday.

V2Log ZIP

What I've Done So Far:

Crash Dump & Event Viewer Analysis
- The first BSOD pointed to a PCIe bridge issue, which initially made me question whether this was USB-related or a deeper system-level problem.
- Checking Event Viewer, I found multiple instances of network interface resets for the Xbox adapter right before the crash.
- The log states that the hardware stopped responding to commands, which suggests a failure during device initialization.
Hardware & Connectivity Testing
- When the BSOD occurred, the Xbox adapter was not being powered by the USB port, even when I reinserted it.
- Other USB devices (mouse, keyboard, charging cable) worked fine, so the USB power rail wasn’t completely failing.
- After a reboot, the adapter started working normally again, but despite 10+ restart attempts, I haven't been able to reproduce the BSOD.
Driver & Firmware Troubleshooting (did this yesterday)
- I rolled back my USB controller drivers to a previous version in case a recent update caused instability.
- I updated the firmware on the Xbox controller to rule out compatibility issues.
- I moved all my USB devices from USB 3.1 ports (blue) to USB 3.2 ports (red, 10Gbps) in case this was linked to a specific USB controller.
Power Management Adjustments
- I disabled all USB power-saving features in Windows (Selective Suspend, etc.).
- I checked my BIOS power settings, and "ErP" is enabled to turn off RGB lighting when the system is off. Expo is enabled. Memory context restore disable. The rest is all on default.
Next Steps & Theories
- I plan to test an older Xbox Wireless Adapter to see if the issue is device-specific.
- A BIOS beta update was recently released, but I prefer to wait for a stable public version before flashing.
- I suspect this could be related to BIOS-level USB/PCIe initialization, but since I started with this BIOS version (1203), I have no previous reference point for comparison.

At this point, the BSOD only occurs shortly after boot, and if it doesn’t happen in that window, the system remains completely stable. This makes me think it's more of a driver or firmware initialization issue rather than a hardware defect. But... i'm here to hear your opinion.

Any ideas or suggestions would be greatly appreciated!

OAT · Monday at 9:47 AM

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

Lanz · Monday at 11:28 AM

I would like to emphasize that during the first two BSODs, I was not using the Xbox Wireless Adapter or the Xbox controller. However, the adapter was plugged into a USB port. There were no error messages in Event Viewer about the adapter not responding in those cases.

zbook · Monday at 5:03 PM

The computer has had a very large number of BSODs for its 2 week Windows installation.

Please place the computer in clean boot: (maintain indefinitely)

Perform a Clean Boot in Windows 11 to Troubleshoot Software Conflicts

This tutorial will show you how to perform a clean boot to start Windows 10 or Windows 11 using a minimal set of drivers and startup programs for troubleshooting application conflicts. Troubleshooting Windows can be a complex process due to the many different drivers, settings, and programs...

www.elevenforum.com

For any new BSOD while in clean boot > post a new V2 share link into the newest post

If there are 2 or more BSODS then switch to safe mode: (maintain indefinitely)

Boot to Safe Mode in Windows 11

This tutorial will show you how to boot Windows 11 into normal mode, Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt. Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default...

www.elevenforum.com

For any new BSOD while in safe mode > post a new V2 share link into the newest post

139
74
19
7E
9F
141
117
1CC

Lanz · Tuesday at 2:43 AM

The first two BSODs you see in the logs are related to a corrupted shader cache and shouldn't be taken into account. It's an issue I've already resolved.

The problem is that, in that way, I can't use the PC. Besides gaming, I also use it for work. Without active drivers, I might as well not use it and just keep it turned off.

I need something less drastic than staying in clean boot/safe mode indefinitely, at least for now. Something like that is possible only on a machine that is not in active use. I could do it on weekends.

Unfortunately, the issue here is that the BSODs are sporadic (about once a week) and occur randomly within the first few minutes after system boot.
And as I said in the OP, if it doesn’t happen in that window, the system remains completely stable for 12 hours straight ore more. If I were able to reproduce them, it would be much easier.

zbook · Tuesday at 2:53 AM

There should be no issues for clean boot.

Lanz · Tuesday at 2:57 AM

Okay, I'll try to stay in clean boot mode over the next few days. I'll report back next week, or sooner if I encounter a BSOD. It's possible that I might need to keep some services active to use certain work apps, though.

zbook · Tuesday at 2:59 AM

Code:

Event[10405]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2025-03-30T18:48:19.6030000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Lanz-PC
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff808383355060, 0xffffa4868f36f010, 0xffff8083836559a0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: f46c077b-1a59-4519-b23e-4467fcd89084.

Code:

Event[7729]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2025-03-23T15:20:05.5540000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Lanz-PC
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff808d99399060, 0xffffb280a666f010, 0xffff808d996619e0). A dump was saved in: C:\WINDOWS\Minidump\032325-19140-01.dmp. Report Id: 0855f07f-cfc6-4144-8edf-ba438b462957.

Code:

Event[7568]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2025-03-23T15:13:20.6270000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Lanz-PC
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffff9189a13a0060, 0xfffff883c9daf010, 0xffff9189a16719e0). A dump was saved in: C:\WINDOWS\Minidump\032325-19234-01.dmp. Report Id: 89c7fd51-ff4d-4375-8a9f-dd03f81f2a0c.

Code:

Event[4514]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2025-03-17T17:59:00.6510000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Lanz-PC
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff800b37350af, 0xffffdd0b67d21278, 0xffffdd0b67d20a60). A dump was saved in: C:\WINDOWS\Minidump\031725-18187-01.dmp. Report Id: 9d26df03-f7fa-4db7-abfa-2df2b6e7cc2c.

Code:

Event[4376]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2025-03-17T17:54:31.6180000Z
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: Info 
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: Lanz-PC
  Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff800d67350af, 0xffffc18769356278, 0xffffc18769355a60). A dump was saved in: C:\WINDOWS\Minidump\031725-18000-01.dmp. Report Id: b47fd6da-dde8-4dcc-abbf-599238b630a4.

zbook · Tuesday at 3:10 AM

Please run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Lanz · Tuesday at 3:16 AM

~~Do you want the TuneUp log in clean boot mode or normal mode? I'll do it tonight.~~ Thank you for your help.

Ah, okay, I see what it does and what the purpose is. It should be irrelevant whether it's done in clean or normal boot. Ok, i'll post it tonight when i get back from a business trip. Thanks again.

zbook · Tuesday at 3:20 AM

It can run in normal or clean boot.

First run:

Code:

DISM /Online /Add-Capability /CapabilityName:WMIC~~~~

zbook · Tuesday at 3:34 AM

Tuneup plus will modify settings so that it is less likely to miss BSOD.
(turns off automatic restart)

And memory dump files if needed will be more modest in size.

Code:

Event[7690]
  Log Name: System
  Source: volmgr
  Date: 2025-03-23T15:19:50.7330000Z
  Event ID: 49
  Task: None
  Level: Error
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Lanz-PC
  Description:
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Lanz · Tuesday at 11:35 AM

TuneUp Plus log

ASUS support advised me to download the firmware updates for the USB controllers (there are three of them!) and reinstall the chipset drivers. I just did it, so let's see how it goes.

Gas · Tuesday at 12:08 PM

Lanz said:
TuneUp Plus log

ASUS support advised me to download the firmware updates for the USB controllers (there are three of them!) and reinstall the chipset drivers. I just did it, so let's see how it goes.

Didn't Asus DriverHub find all drivers and chipset updates for the system?
Your BIOS version (1203) is the last one, is the correct model of MB in your PC specs? There aren't any betas after 1203.
ROG STRIX X870-F GAMING WIFI | Gaming motherboards｜ROG - Republic of Gamers｜ROG Global

Lanz · Tuesday at 1:04 PM

Gas said:
Didn't Asus DriverHub find all drivers and chipset updates for the system?
Your BIOS version (1203) is the last one, is the correct model of MB in your PC specs? There aren't any betas after 1203.
ROG STRIX X870-F GAMING WIFI | Gaming motherboards｜ROG - Republic of Gamers｜ROG Global

For driver and chipset, yes. For firmwares you need to look in the motherboard page just under the bios section.

Nope. Last beta is 1301. Is not listed in the motherboard main page, you need to look in the Asus Rog forum here.

Gas · Tuesday at 6:26 PM

Lanz said:
For driver and chipset, yes. For firmwares you need to look in the motherboard page just under the bios section.

Nope. Last beta is 1301. Is not listed in the motherboard main page, you need to look in the Asus Rog forum here.

I would never flash the BIOS of my motherboard with a non official Beta BIOS anyway, I would also download and install the "Auto-Detect and Install Driver Updates for AMD Radeon™ Series Graphics and Ryzen™ Chipsets" here . Good luck.

Lanz · 2025-04-02T02:17:07-0400

Following yesterday's firmware updates, the Event Viewer shows that the problematic device (PCI\VEN_1B21&DEV_2423&SUBSYS_24211B21&REV_01\451ECAFFFF5177A018) has been removed and reconfigured. So... I might be on the right track to resolving this issue. I'll keep you posted.

zbook · 2025-04-02T02:29:08-0400

Please post a new V2 share link.

Lanz · 2025-04-02T12:46:32-0400

New Vlog2

Anyway, indirectly, I have 99% confirmation that it's the ASM USB 4.0 hub (ASM4242). Using USBDeviceTree, under "USB 4.0 Host Router," the ACPI location ID is exactly "GPP8 U4UP U4P3," the same as the BSOD device.

I had only connected the USB dongle for my SteelSeries wireless headset, which I’ve now moved to the 3.2 port managed directly by the X870 chipset. The only way to find out if I’ve fixed it is to wait. I do not need to use USB 4.0 for something like a dongle...

Gas · 2025-04-02T13:16:15-0400

Out of curiosity can you take a look in device manager?

DRIVER_POWER_STATE_FAILURE (9F)

Member

What I've Done So Far:​

My Computer

Pragmatic Member

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

Attachments

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Similar threads

What I've Done So Far: