Forum Discussion
KB5121003 breaks AMD X470 USB xHCI: DRIVER_POWER_STATE_FAILURE 0x9F
I am reporting what appears to be a USB/xHCI regression immediately following installation of the August 11, 2026 cumulative update KB5121003 on Windows 11 25H2.
System information
- OS: Windows 11 25H2
- Build after update: 26200.9168
- Update: KB5121003
- Motherboard: ASUS ROG STRIX X470-F GAMING
- Chipset: AMD X470
- CPU: AMD Ryzen 7 5800X 8-Core Processor
- Affected xHCI controller PCI instance: "PCI\VEN_1022&DEV_43D0&SUBSYS_11421B21&REV_01\4&2c18e2e3&0&000B"
- Associated USB Root Hub instance: "USB\ROOT_HUB30\5&4964544&0&0"
- Windows USB driver stack involved: "USBXHCI → ACPI → USBHUB3"
All affected USB devices were working normally immediately before installation of KB5121003.
During installation, the first reboot completed normally. Windows then requested a second scheduled reboot through TrustedInstaller as part of the update servicing process.
Relevant System event log timeline
- Approximately 20:59 – first update restart initiated.
- Approximately 21:00 – first shutdown and subsequent boot completed.
- 21:01:19 – "TrustedInstaller.exe" requested another scheduled restart, reason: Operating System Update.
- 21:01:28 – Windows shut down for the second update reboot.
- Approximately 21:01–21:06 – the system remained without video output for approximately five minutes.
- Approximately 21:06:58 – Windows started again.
- 21:07:03 – "WER-SystemErrorReporting", Event ID 1001, recorded a bugcheck occurring during the preceding boot/update phase.
The bugcheck was:
DRIVER_POWER_STATE_FAILURE (0x9F)
Parameters:
"0x0000009f (0x3, 0xffff91076083edc0, 0xffffba0875fcf640, 0xffff9107601ab560)"
Minidump:
"C:\Windows\Minidump\081226-4968-01.dmp"
Analysis of the minidump shows that the Physical Device Object identified by bugcheck Arg2 belongs to the USB xHCI device stack.
The affected PCI device is:
"PCI\VEN_1022&DEV_43D0&SUBSYS_11421B21&REV_01\4&2c18e2e3&0&000B"
The reconstructed device stack is:
"USBXHCI → ACPI → USBHUB3"
The associated Root Hub instance is:
"USB\ROOT_HUB30\5&4964544&0&0"
The blocked IRP referenced by Arg4 is a power IRP:
"IRP_MJ_POWER / IRP_MN_SET_POWER"
The active device object belongs to:
"\Driver\USBHUB3"
and the Physical Device Object involved belongs to:
"\Driver\USBXHCI"
This indicates a timeout in the USB xHCI / USB Root Hub power-state transition during the second servicing reboot.
After Windows subsequently booted successfully into build 26200.9168, the affected USB Root Hub/controller remained in an error state in Device Manager.
All USB peripherals connected through the affected USB path became unavailable to Windows. This includes devices of different types that had all been working normally immediately before the update, including:
- USB keyboard
- USB audio interface
- USB webcam
- other USB-connected peripherals on the affected controller/Root Hub
The failure is therefore not limited to a particular peripheral, application, or third-party device driver. Multiple unrelated USB devices became unavailable simultaneously because the common upstream USB controller/Root Hub failed to initialize correctly.
The USB failure appeared during the reboot sequence that applied KB5121003, and the affected Root Hub has remained non-functional since that update.
The temporal relationship with KB5121003 is therefore very strong, while the crash dump independently identifies the failing subsystem as the Windows USB xHCI/USBHUB3 stack on the AMD X470 platform.
I have retained both:
- the complete System EVTX log covering the update and reboot sequence;
- the minidump "081226-4968-01.dmp" containing the 0x9F crash and affected USB device stack.
Both files are available for engineering analysis.
Please investigate a possible regression in USB xHCI / USBHUB3 power-state handling introduced by KB5121003 / build 26200.9168, particularly on AMD X470 / PCI "VEN_1022&DEV_43D0" configurations.
4 Replies
- Timothy1525Steel Contributor
Unplug all non-essential USB devices (like external hard drives, USB hubs), keeping only the mouse and keyboard to rule out peripheral conflicts.
- SBerg1980Copper Contributor
I have the same issue, uninstall the update won’t fix the issue. I added all my USB devices to another port and that works. Lets hope that MS comes with a fix.
- KellasyCopper Contributor
he KB5121003 update is a significant mandatory cumulative update for Windows 11 versions 24H2 and 25H2. It includes over 400 security fixes and was released to address a rising number of AI-powered threats.
- RafaelWellitonCopper Contributor
Exactly! It was such a significant and mandatory update that it completely broke the audio subsystem and USB controllers for countless users.I just lost an entire workday trying to figure out why my USB mixing console kept disconnecting and reconnecting every few minutes. Before Windows forced this KB5121003 update on my machine, my setup was running absolutely flawlessly, with zero issues.It doesn’t matter how many security fixes or AI threat protections they pitch if a cumulative update destroys system stability and prevents people from working with their USB audio devices and DACs. The only real solution to get back to work was to roll back and uninstall this build completely.