Quick fix: PNP_DETECTED_FATAL_ERROR after adding hardware means the USB hub or device’s driver enumeration triggered an unhandled exception in the Plug-and-Play manager. Disconnect the new hub, boot to Safe Mode, run verifier /reset to clear any debug verifier flags, and reconnect through a different USB port (preferably a direct one, not through a hub).
You connected a new USB hub to the laptop. Within seconds Windows BSODs with PNP_DETECTED_FATAL_ERROR (0x000000CA). It happens every time you connect that specific hub. Other USB devices work normally; only this hub triggers it. The hub’s driver enumeration is failing the PnP manager’s sanity check.
Affects: Windows 11 with USB hubs (typically multi-port or powered hubs).
Fix time: 20 minutes.
What the bug check means
The PnP manager validates device enumeration data. When a hub enumerates devices behind it, each port reports a hardware ID, vendor/product code, and capabilities. If any of this data is malformed (the hub firmware is buggy) or violates PnP expectations (duplicate device IDs, conflicting power states), the manager bug-checks rather than load the bad data.
Method 1: Boot to Safe Mode and remove the hub from Device Manager
- If you can boot normally, disconnect the hub first.
- Open Device Manager. View → Show hidden devices.
- Expand Universal Serial Bus controllers and Universal Serial Bus devices. Look for any entries related to the hub (greyed out or with yellow flags).
- Uninstall those entries (check “Delete driver software” if available).
- Reboot.
- Reconnect the hub. Watch for the BSOD.
Method 2: Reset Driver Verifier and check for verifier-triggered crashes
- If you previously ran Driver Verifier for debugging, it may be more sensitive to PnP issues.
- Open elevated Command Prompt and run
verifier /reset. - Reboot.
- Reconnect the hub. If the BSOD doesn’t happen, Verifier was unnecessarily strict.
Method 3: Test the hub on a different port or different OS
- Try the hub on a different USB port (USB 2.0 vs USB 3.0/USB-C).
- If still crashes, the hub itself has buggy firmware.
- Check for firmware updates on the hub manufacturer’s site.
- If no firmware fix exists, return the hub.
Verification
- Connect the hub without BSOD.
- Devices behind the hub enumerate correctly.
- WhoCrashed or BlueScreenView analysis of the .dmp file confirms the failing driver isn’t USBHUB3.sys.
If none of these work
If different USB ports also crash, the hub firmware is the culprit. Cheap USB hubs (especially with many ports and Ethernet or display extensions) often have rushed firmware that fails PnP validation. Replace with a hub from a reputable brand (Anker, Plugable, Caldigit).
Bottom line: PNP_DETECTED_FATAL_ERROR from a hub = bad enumeration data. Remove the hub from Device Manager first, then physically replace if firmware updates don’t exist.