STATUS_POWER_STATE_INVALID (0XC00002D3) Fix for Windows 10/11

Cause 1: USB Selective Suspend is the Most Common Culprit

I know this error is infuriating. It shows up out of nowhere — a blue screen, a sudden reboot, or a freeze when you plug in a USB device. The system log says STATUS_POWER_STATE_INVALID (0XC00002D3), and it feels like a ghost in the machine. But almost always, the root cause is a power management feature called USB selective suspend. Windows tries to save power by putting idle USB ports to sleep. Problem is, some devices — especially external drives, USB hubs, and older keyboards or mice — don't wake up properly when you need them again.

This tripped me up the first time too. I spent hours swapping hardware before I realized it's a Windows setting. Here's how to kill it:

1. Open Control Panel (search for it in the Start menu).
2. Go to Power Options.
3. Click Change plan settings next to your active power plan (usually Balanced or High Performance).
4. Click Change advanced power settings.
5. Scroll down to USB settings → USB selective suspend setting.
6. Set it to Disabled for both "On battery" and "Plugged in".
7. Click Apply, then OK. Reboot.

After this, plug in the device that was causing the crash. If the error disappears — you're done. This fix works for about 70% of cases. If not, move to the next cause.

Cause 2: A Faulty or Incompatible Device Driver

Sometimes the issue isn't power management — it's a driver that can't handle the transition. This is especially common with external storage enclosures (like USB-to-SATA adapters), certain Bluetooth dongles, and older graphics cards that use USB passthrough for VR headsets. The error triggers when you try to wake the system from sleep or hibernate, and a device driver returns an unexpected power state.

The real fix is to update or roll back the driver for the offending device. But how do you find it? Open Event Viewer (search for it), go to Windows Logs → System, and look for the error with source BugCheck or Kernel-Power. The event details often list the device instance path. It'll look something like \Device\0000004a or PCI\VEN_...&DEV_.... Copy that path.

Now open Device Manager. Click View → Devices by connection. Scroll through the tree, and look for a device matching that path. Right-click it → Properties → Driver tab. If you recently updated the driver, click Roll Back Driver. If it's an old driver, check the manufacturer's website for a newer version. For USB devices, try uninstalling the device (check "Delete the driver software for this device") and then reconnecting it to let Windows reinstall a fresh copy.

Skip generic driver update tools — they often install the wrong driver or a bloated package. Go straight to the vendor's support page.

Cause 3: Power Supply or Hardware Issues

Less common, but I've seen it plenty in corporate environments. If you've disabled USB selective suspend and updated all drivers, the problem might be a failing power supply unit (PSU) or a motherboard power rail that's giving inconsistent voltage. This causes connected devices to report invalid power states. The error tends to occur under load — when you plug in a high-power USB device (like a bus-powered external drive) or when the system is waking from sleep.

Here's the test: try the device on a different USB port — preferably a port directly on the motherboard back panel, not a front panel or hub. If it works there, the issue is likely a weak USB header on the motherboard. If the error persists across all ports, especially with multiple devices, suspect the PSU.

For desktops, check the PSU wattage using a tool like HWMonitor while the system is idle and under load. If the +5V or +3.3V rail drops below spec (by more than 5%), replace the PSU. For laptops, this is harder to fix — try running on battery only (unplug AC) to see if the error stops. If it does, the charger or charging circuit is faulty.

One more thing: some Thunderbolt 3/4 docks have known power state bugs. Check the dock's firmware — manufacturers like Dell and Lenovo have released updates specifically for this error on models like the WD19 and ThinkPad Thunderbolt 3 Dock.

Quick-Reference Summary Table