Skip to content
0x000001D5DRIVER_PNP_WATCHDOGStop codeWidely reported

DRIVER_PNP_WATCHDOG (0x1D5): what it means and how to fix it

Updated Nov 15, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

The DRIVER_PNP_WATCHDOG error occurs with stop code 0x000001D5 when a device driver fails to complete a Plug and Play operation within an allowed time limit. It is most often caused by a malfunctioning, incompatible, or hanging device driver or a faulty hardware device. The first thing to try is disconnecting recently added external hardware and updating your drivers.

What it means

Windows relies on a subsystem called Plug and Play (PnP) to automatically detect, configure, and communicate with internal hardware and external peripherals. When a device is connected, initialized, or placed into a different power state, the PnP manager issues instructions to the corresponding device driver.

The role of the watchdog timer

To keep the entire operating system responsive, Windows sets an internal timer, called a watchdog, whenever a PnP task begins. If the device driver executes its routine, reports back, and finishes within the permitted window, the watchdog is disarmed and system operation continues smoothly.

If the driver hangs, becomes completely unresponsive, or encounters an internal deadlock while handling a PnP task, the timer runs out. Because Windows cannot wait indefinitely without risking total system instability, it stops execution and displays the DRIVER_PNP_WATCHDOG blue screen with the bug check value 0x000001D5.

What happens during the crash

When this crash occurs, Windows records crash details into memory and dump files. These parameters include information such as the service name linked to the device node that failed, the thread executing the task, and the total milliseconds that elapsed since the watchdog timer was armed. On Windows 10 RS4 and newer editions, the crash also tracks a triage structure specifically for PnP watchdogs.

For standard users, this indicates that a specific piece of hardware or its software driver took far too long to answer Windows. The issue frequently surfaces during hardware initialization, device state transitions, or when a faulty driver prevents the operating system from properly configuring connected components.

Common causes

  • A device driver hung or became unresponsive while processing a Plug and Play operation.
  • Recently attached hardware or a failing external peripheral is timing out during initialization.
  • A newly installed or updated driver is incompatible with the system.
  • Underlying disk corruption or a virus infection is interfering with driver file access.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Disconnect recently added hardware

    Use this as the first troubleshooting step if the error started appearing after you plugged in a new device or component.

    1. Shut down your computer completely.
    2. Unplug all non-essential external devices, including external drives, webcams, and USB adapters, leaving only your keyboard and mouse.
    3. If you recently installed new internal components, safely disconnect or remove them.
    4. Turn on the computer and monitor if the crash still occurs.
    5. Check with the hardware manufacturer to see if any firmware updates or patches are available before reconnecting the hardware.
    Did this fix it?
  2. Inspect Device Manager for driver warnings

    Use this when Windows boots to the desktop and you need to identify which device driver is failing.

    1. Right-click the Start menu button and select Device Manager.
    2. Browse the list of categories to see if any devices are marked with an exclamation point (!).
    3. Right-click any marked device and select Properties.
    4. Open the Events tab in the properties window to check for recent faulting driver events.
    5. Return to the Driver tab, click Update driver, and follow the prompts to install the latest version.
    Did this fix it?
  3. Check the System Log in Event Viewer

    Use this to identify which driver or service timed out right before the blue screen occurred.

    1. Right-click the Start button and select Event Viewer.
    2. In the left pane, expand Windows Logs and select System.
    3. Look through the list for critical errors or warning messages logged at the exact time the blue screen occurred.
    4. Click on relevant entries to view details, noting any specific device names, drivers, or system services mentioned.
    5. Update or remove any faulty driver or service identified in the log.
    Did this fix it?
  4. Remove or update recently added drivers and services

    Use this if the crash began immediately after a new driver, software utility, or system service was installed.

    1. Determine what software, driver, or service was installed immediately before the crash started.
    2. Open Settings, go to Apps, and select Installed apps.
    3. Find the recently added program or utility and select Uninstall.
    4. If a specific device driver was updated, open Device Manager, right-click the component, and choose Properties.
    5. Under the Driver tab, click Roll Back Driver if available, or choose Uninstall device and restart your computer to let Windows reinstall the basic driver.
    Did this fix it?
  5. Run a full virus detection scan

    Use this to eliminate malware, as hard disk infections and boot record corruption can trigger system bug checks.

    1. Open Windows Security from the Start menu.
    2. Select Virus & threat protection.
    3. Click on Scan options.
    4. Choose Full scan to check all files and running programs on your hard disks.
    5. Ensure your security program is configured to scan the Master Boot Record for infections, then start the scan.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Nov 11, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does DRIVER_PNP_WATCHDOG mean?

It means a device driver failed to finish a Plug and Play operation within the specific time limit set by Windows. Because the driver remained unresponsive, Windows triggered a blue screen to avoid further system issues.

Can external USB devices cause stop code 0x1D5?

Yes. If an external drive, dock, or accessory fails to respond when Windows attempts to detect or configure it, the watchdog timer can expire and cause the crash.

How do I find which driver caused DRIVER_PNP_WATCHDOG?

You can check Device Manager for devices displaying a yellow exclamation point, review critical errors in the Event Viewer System log around the time of the crash, or analyze a memory dump using the !analyze extension in WinDbg.