Graphics and display errors

THREAD_STUCK_IN_DEVICE_DRIVER (0x000000EA)

Stop code 0x000000EA, also written 0xEA. Here is what it means, what usually causes it, and the safest order to work through fixes on Windows 11 and Windows 10.

In short

A driver got stuck in a loop, often waiting for hardware that stopped responding. Graphics drivers are common.

What THREAD_STUCK_IN_DEVICE_DRIVER means

A device driver stayed in an endless loop, usually while waiting for hardware to become idle. Graphics drivers and GPU hardware are the most frequent cases, so the display may freeze for a while before the blue screen appears.

Common causes

A faulty or outdated graphics driver
A GPU that has become unresponsive from heat, power problems or hardware faults
An unstable overclock
An incompatible driver after a major Windows update

How to fix THREAD_STUCK_IN_DEVICE_DRIVER

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

Reinstall the graphics driver cleanly. Download the latest driver for your exact GPU from NVIDIA, AMD or Intel (or the laptop maker for notebooks), then install it using the vendor's clean-install option. If the newest driver is the one that started the crashes, install the previous release instead.
Return the PC to stock settings. Reset the BIOS to defaults, then leave XMP or EXPO, CPU or GPU overclocks and undervolts (including per-core offsets such as Curve Optimizer) switched off while you test. If the crashes stop, re-enable one setting at a time to find the unstable one.
Watch temperatures under load. Use a monitoring tool to log CPU, GPU and drive temperatures while you reproduce the problem. Sustained high readings, loud fans or thermal throttling point to dust, failed fans or poor airflow rather than a software fault.
Check the GPU slot and power. Power off and unplug the PC, reseat the GPU in its PCIe slot, reconnect its power cables, and confirm the card is fully seated and screwed in.
Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).

When to stop and protect your data

If the display freezes or shows artifacts before each crash even with a clean driver, test the GPU in another system.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other graphics and display errors

Frequently asked questions

What does THREAD_STUCK_IN_DEVICE_DRIVER mean?

A driver got stuck in a loop, often waiting for hardware that stopped responding. Graphics drivers are common. A device driver stayed in an endless loop, usually while waiting for hardware to become idle. Graphics drivers and GPU hardware are the most frequent cases, so the display may freeze for a while before the blue screen appears.

What usually causes THREAD_STUCK_IN_DEVICE_DRIVER?

Typical causes: A faulty or outdated graphics driver; A GPU that has become unresponsive from heat, power problems or hardware faults; An unstable overclock; An incompatible driver after a major Windows update.

How do I fix THREAD_STUCK_IN_DEVICE_DRIVER (0x000000EA)?

A sensible order is: 1) Reinstall the graphics driver cleanly; 2) Return the PC to stock settings; 3) Watch temperatures under load; 4) Check the GPU slot and power. If the display freezes or shows artifacts before each crash even with a clean driver, test the GPU in another system.

Use this guidance carefully

A stop code can have several causes, and these steps are general guidance rather than a diagnosis of your PC. If your data matters, back it up before repairs. If the problem continues, a hardware technician can test the parts.

See our testing methodology·Read our editorial policy