Skip to content
PCDecoder
0x000000EATHREAD_STUCK_IN_DEVICE_DRIVERStop codeWidely reported

THREAD_STUCK_IN_DEVICE_DRIVER (0xEA): what it means and how to fix it

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

Quick answer

This stop code means an instruction thread inside a hardware driver entered an infinite loop and stopped responding. It is most often caused by a faulty display driver or failing video card. The first thing to try is updating or reinstalling your graphics card drivers.

What it means

Windows triggers the THREAD_STUCK_IN_DEVICE_DRIVER stop code, recorded as hexadecimal value 0x000000EA (or 0xEA), when an execution thread inside a device driver enters an endless loop. Drivers manage communication between the operating system and physical hardware components. When a driver sends an instruction to a hardware component, it often waits for the hardware to finish its work and become idle before proceeding.

Why the thread gets stuck

When hardware fails to respond or when a driver programs the hardware incorrectly, the driver's thread can spin endlessly while waiting for an idle signal that never arrives. Windows monitors kernel operations with a watchdog timer. If an operation exceeds the permitted time limit without returning control to the operating system, Windows stops the system to prevent operating system corruption or lockups.

Video hardware and display drivers

While any hardware device can trigger this stop code, it frequently points to issues with a video card or a display driver. Graphical tasks demand rapid communication between the graphics processing hardware and the display driver. If the display driver sends instructions that the physical card cannot execute, or if the video card hangs and stops responding to driver queries, the watchdog registers a timeout and halts execution.

The stop code parameters

When Windows issues this bug check, it creates four diagnostic parameters to describe the hang. Parameter 1 points directly to the address of the stuck thread object. Parameter 2 references the deferred watchdog object that caught the timeout. Parameter 3 contains a pointer to the name of the offending driver file, helping identify the exact component at fault. Parameter 4 represents an internal counter used during debugging to record how many times the intercepted check occurred, displaying as 1 on standard blue screens.

Common causes

  • A display driver or other device driver programmed hardware incorrectly and entered an infinite loop.
  • A physical hardware failure, most commonly a failing video card that fails to return to an idle state.
  • Corrupted or outdated graphics card drivers running on the system.
  • Hardware interrupts colliding during processor routines, causing a timeout.
  • Third-party kernel-mode drivers causing conflicts or instability.

How to fix it

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

  1. Update your graphics and hardware drivers

    Use this as the primary fix, since this stop code is frequently caused by a faulty display driver.

    1. Visit the official website of your graphics card manufacturer or computer vendor.
    2. Locate the latest driver release specifically built for your hardware model and Windows version.
    3. Download and install the driver package according to the vendor's setup instructions.
    4. Restart your computer to ensure the updated driver is loaded by the kernel.
    Did this fix it?

  2. Roll back the device driver

    Use this if the crashes began immediately after installing a new hardware driver update.

    1. Open Device Manager by right-clicking the Start menu button and selecting Device Manager.
    2. Expand the Display adapters category or the section for the recently updated hardware.
    3. Right-click your device and choose Properties.
    4. Select the Driver tab.
    5. Click the Roll Back Driver button if it is available, and confirm your choice.
    6. Restart your computer.
    Did this fix it?

  3. Install the latest Windows updates

    Use this to ensure your operating system has the latest stability fixes and system rollups.

    1. Open the Settings app from the Start menu.
    2. Navigate to Update & Security or Windows Update depending on your version.
    3. Select Check for updates to scan for available updates.
    4. Download and install all pending cumulative updates and rollups.
    5. Restart your computer when prompted.
    Did this fix it?

  4. Update your system BIOS and firmware

    Use this when driver updates do not resolve the timeout issues between the motherboard and video hardware.

    1. Check your computer or motherboard manufacturer's support portal for firmware updates.
    2. Download the latest BIOS or UEFI firmware version intended for your exact motherboard model.
    3. Follow the manufacturer's specific instructions to apply the firmware update safely.
    4. Restart the PC and verify system stability.
    Did this fix it?

  5. Run hardware and memory diagnostic tests

    Use this if software and driver updates fail to stop the crashes, suggesting a physical hardware defect.

    1. Run hardware diagnostic tools provided by your computer or motherboard manufacturer.
    2. Execute memory testing tools to ensure system RAM is functioning without read/write defects.
    3. Inspect the physical video card connection to ensure it is seated firmly in its motherboard slot.
    4. If hardware errors are detected, replace the faulty component.
    Did this fix it?

Is it just you?

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

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

Sources

Frequently asked questions

What is the 0x000000EA error in Windows?

Error 0x000000EA is the THREAD_STUCK_IN_DEVICE_DRIVER stop code. It occurs when a hardware driver thread spins endlessly in an infinite loop while waiting for hardware to respond.

Does THREAD_STUCK_IN_DEVICE_DRIVER mean my graphics card is broken?

Not necessarily. While it can indicate a failing video card, it is frequently caused by buggy or corrupt display driver software that can be resolved with a clean driver update.

Can I find which driver caused bug check 0xEA?

Yes. Windows records the offending driver name in Parameter 3 of the crash information, which can be extracted from memory dump files using debugging tools.

More stop codes decoded