PNP_DETECTED_FATAL_ERROR Blue Screen: Every Fix That Actually Works in 2026

PNP_DETECTED_FATAL_ERROR (stop code 0x000000CA) is a Windows blue screen error triggered when the Plug and Play (PnP) manager detects a fatal inconsistency — most commonly caused by a driver conflict, a recently installed or updated driver, or a new hardware device that is not initializing correctly.

This BSOD can usually be fixed without reinstalling Windows.

Part 1. Identify the Trigger Before Fixing

The most important first step is understanding what changed on your system immediately before the BSOD started appearing.

💡 Tip: Check Windows Event Viewer for the exact driver name. Press Win + X → Event Viewer → Windows Logs → System. Filter for Critical and Error events near the time of the crash. Look for entries referencing a specific .sys driver file — that is your target.

If you recently added new hardware or a Windows Update was installed, you have a strong starting point for identifying the culprit.

Part 2. Boot into Safe Mode

If Windows keeps crashing before you can do anything, Safe Mode loads Windows with only essential drivers — preventing the problem driver from loading.

Method 1: If Windows can start partially. Press and hold Shift, then click Start → Power → Restart. In the blue boot menu, choose Troubleshoot → Advanced Options → Startup Settings → Restart → Press F4 for Safe Mode.

Method 2: If Windows cannot start at all. Force shutdown 3 times in a row (hold the power button until the PC turns off). Windows will automatically enter the WinRE recovery environment. From there: Troubleshoot → Advanced Options → Startup Settings → Restart → F4 for Safe Mode.

⚠️ Important: While in Safe Mode, do not install new software or drivers. Only use Safe Mode to remove the problematic driver or run diagnostic tools.

Part 3. Roll Back or Uninstall the Problem Driver

Once in Safe Mode or normal Windows, roll back or uninstall the driver that caused the issue.

Step 1: Open Device Manager. Press Win + X → Device Manager. Look for devices with a yellow warning icon, or expand categories for the hardware you recently changed.

Step 2: Roll back the driver. Right-click the device → Properties → Driver tab → Roll Back Driver. This reverts to the previous driver version.

Step 3: If Roll Back is greyed out, uninstall the driver. Right-click the device → Uninstall device → check "Delete the driver software for this device" → Uninstall. Restart Windows.

Step 4: For Windows Update-installed drivers. Open Settings → Windows Update → Update History → Uninstall Updates. Find the update that matches your driver update date and uninstall it.

🗣️ r/techsupport user: "PNP_DETECTED_FATAL_ERROR started after a Windows Update. Found it was an AMD chipset driver update in Windows Update history. Uninstalled that specific update and installed the driver manually from AMD's site instead. BSODs gone."

Part 4. Run SFC and DISM to Repair System Files

If the driver rollback does not fix the BSOD, corrupted Windows system files may be responsible. The SFC (System File Checker) and DISM tools can repair them.

Step 1: Run SFC scan. Open Command Prompt as Administrator (press Win + X → Windows Terminal (Admin)).

sfc /scannow

Wait for the scan to complete. It may take 10–20 minutes. SFC will automatically replace any corrupted system files it finds.

Step 2: If SFC reports errors it could not fix, run DISM.

DISM /Online /Cleanup-Image /RestoreHealth

DISM downloads replacement files from Windows Update to repair the component store. This requires an internet connection and may take 20–30 minutes.

Step 3: Run SFC again after DISM completes. DISM repairs the component store that SFC uses. Running SFC after DISM often fixes errors that SFC alone could not resolve.

💡 Tip: If you cannot run SFC from within Windows due to constant crashes, boot from a Windows 11 USB drive, choose Repair your computer → Troubleshoot → Advanced Options → Command Prompt, and run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows with the appropriate drive letter.

🗣️ r/WindowsHelp user: "Ran DISM then SFC and it fixed the PNP_DETECTED_FATAL_ERROR on my laptop. Turns out a Windows Update had partially installed and left corrupted driver packages. DISM replaced them from the clean source. Took about 45 minutes but saved me a reinstall."

Part 5. Check for Recently Installed Hardware

If the BSOD started after physically adding new hardware (RAM, GPU, PCIe card, USB device), that hardware's driver or initialization process may be causing the PnP conflict.

Step 1: Remove the recently added hardware and test if the BSOD stops.

Step 2: If the BSOD stops, the hardware or its driver is the issue.

• For the device: Update to the latest driver from the manufacturer's official website
• For RAM: Test with MemTest86
• For GPU: Use DDU (Display Driver Uninstaller) to cleanly remove and reinstall GPU drivers

Step 3: If the BSOD continues without the new hardware, the issue is pre-existing — proceed with SFC/DISM and driver updates for existing components.

Part 6. Data Loss from BSOD? Recover with Ritridata

Repeated BSODs can occasionally cause file system corruption, and recovery attempts (like Startup Repair or Windows reinstall) can sometimes delete personal files.

Before making any major system changes, back up your important files. If the system is too unstable to boot, Ritridata provides a bootable USB recovery tool that lets you access and recover files even when Windows will not start.

Ritridata can recover documents, photos, and other files deleted or made inaccessible by system crashes, formatting, or accidental deletion during repair processes.

FAQ

Q: What does PNP_DETECTED_FATAL_ERROR actually mean? A: PNP stands for Plug and Play — the Windows subsystem that manages hardware detection and driver loading. A "fatal error" in PnP means Windows found an inconsistency so severe that it had to crash to prevent data corruption.

Q: Can a USB device cause PNP_DETECTED_FATAL_ERROR? A: Yes. A faulty USB device, a USB hub with power issues, or a USB device driver can trigger this BSOD. Try disconnecting all USB devices (except keyboard and mouse) and test if the BSOD stops.

Q: Does this BSOD always require a Windows reinstall? A: No. The majority of PNP_DETECTED_FATAL_ERROR BSODs are resolved by rolling back or uninstalling a driver, running SFC/DISM, or removing a problematic hardware device.

Q: How do I find which .sys file is causing the crash? A: In Event Viewer (Windows Logs → System), look for Critical events near the crash time. The event details often name a specific .sys file. You can also analyze the memory dump file with WinDbg for more detail.

Q: Can Windows Update cause PNP_DETECTED_FATAL_ERROR? A: Yes, this is a known occurrence. Windows Update sometimes installs GPU, chipset, or storage drivers that are incompatible with specific hardware combinations. Rolling back the problematic update from Windows Update History typically resolves it.

References

• Microsoft Docs: Bug Check 0xCA PNP_DETECTED_FATAL_ERROR
• Microsoft Support: SFC scannow — system file checker
• Microsoft Support: DISM — repair Windows image
• WinDbg — Windows Debugger for BSOD analysis
• Ritridata Data Recovery