- Software and digital services
- Operating system
THREAD_STUCK_IN_DEVICE_DRIVER
Windows THREAD_STUCK_IN_DEVICE_DRIVER: driver stuck in a loop
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
THREAD_STUCK_IN_DEVICE_DRIVER (0xEA) means a driver kept spinning endlessly while waiting for its hardware to become idle. It is very often the graphics card or its driver: start by updating or rolling back the display driver.
Safety first
Stop and check this first
- Download graphics drivers only from the card maker, the PC maker or Windows Update.
- Before resetting Windows save your files and, if you use BitLocker, keep the recovery key at hand.
Safe checks you can perform
- Display driver version
- Roll back the graphics driver
- Flagged devices and Windows Update
- Graphics card or display added recently
Leave these tasks to a qualified professional
- Do not attempt this professional task: Find the stuck thread in the dump
- Do not attempt this professional task: Graphics card test
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Find the stuck thread in the dump
What they doThe technician opens the dump in WinDbg, runs !analyze -v, switches to the thread in parameter 1 with .thread and uses kb to see where it was spinning and which driver parameter 3 names.
They must show youthe !analyze -v output and the driver name the dump points to.
In writingthe responsible driver or device and the version or repair that solves it.
Graphics card test
What they doIf the driver is current and the crash persists, the technician tests the video card with the maker's tools or in another PC before recommending a replacement.
They must show youthe result of the graphics card test.
In writingif the card fails, the proposed part and the warranty.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Display driver version
- Who:
- you.
- How:
- right-click Start, open Device Manager, expand Display adapters and check the driver version and date in the properties; compare with the latest from your graphics card or PC maker.
- Result that matters:
- knowing whether you run an old or just-changed graphics driver.
- If a newer version exists:
- install it from the maker's website or Windows Update and watch whether the code returns.
- If it is already the latest and the crash began after installing it:
- roll back to the earlier one.
- Evidence to keep:
- screenshot with the graphics driver version and date.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0xEA THREAD_STUCK_IN_DEVICE_DRIVER
Roll back the graphics driver
- Who:
- you.
- How:
- in the display adapter properties, Driver tab, select Roll Back Driver if it is active; if Windows does not reach the desktop, do it from safe mode.
- Result that matters:
- checking whether the loop disappears with the previous version.
- If the crashes stop:
- wait for the maker to publish a fixed version before updating.
- If there is no earlier version or it persists:
- note whether it happens while gaming, watching video or idle and consult a technician.
- Evidence to keep:
- version removed, current version and when the crash occurs.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Flagged devices and Windows Update
- Who:
- you.
- How:
- check Device Manager for any other device with an exclamation point and go to Start, Settings, Windows Update, Check for updates to install what is pending.
- Result that matters:
- ruling out other problem drivers and applying published fixes.
- If another device is flagged:
- update or disable that device and watch the result.
- If nothing is flagged and everything is current:
- the graphics card becomes the main suspect.
- Evidence to keep:
- list of flagged devices and updates installed.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Graphics card or display added recently
- Who:
- you, once the PC is powered off.
- How:
- if you recently connected an external graphics card, a USB video adapter or a dock, disconnect it and start with the integrated graphics or the original monitor.
- Result that matters:
- seeing whether 0xEA depends on that hardware.
- If it does not return without it:
- contact its maker for a compatible driver or a repair.
- If it keeps happening:
- go back to your usual setup and ask for the dump analysis.
- Evidence to keep:
- what you disconnected and the behaviour afterwards.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0xEA THREAD_STUCK_IN_DEVICE_DRIVER
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x000000EA
- 0x100000EA
- 0xEA
- código de detención THREAD_STUCK_IN_DEVICE_DRIVER
- STOP 0x000000EA
- stop code THREAD_STUCK_IN_DEVICE_DRIVER
- THREAD STUCK IN DEVICE DRIVER
- THREAD_STUCK_IN_DEVICE_DRIVER_M
What it means
For Microsoft, code 0x000000EA means a device driver thread is in an infinite loop, most likely waiting for the hardware to stop being busy. It usually points to a problem with the device itself or a driver programming it incorrectly, and frequently it is a bad video card or a bad display driver. The third parameter points to the name of the driver involved, visible when the dump is analysed. The code alone does not confirm that the graphics card or any other part is broken.
Warnings and stop conditions
- Mediumsource verified
Download graphics drivers only from the card maker, the PC maker or Windows Update.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
- Mediumsource verified
Before resetting Windows save your files and, if you use BitLocker, keep the recovery key at hand.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Find your BitLocker recovery key
Symptoms and causes
Probable causes · in order
- Faulty display driverCommon
Microsoft says 0xEA is frequently the result of a display driver that programs the graphics hardware incorrectly.
Evidence: Bug Check 0xEA THREAD_STUCK_IN_DEVICE_DRIVER
- Video card not respondingPossible
The official page mentions a bad video card as a frequent origin, because the driver waits endlessly for it to become idle.
Evidence: Bug Check 0xEA THREAD_STUCK_IN_DEVICE_DRIVER
- Another device and its driverPossible
The loop can occur in any device driver, which is why it is worth checking the devices flagged in Device Manager.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0xEA THREAD_STUCK_IN_DEVICE_DRIVER
Virtual technician
Does THREAD_STUCK_IN_DEVICE_DRIVER still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Find your BitLocker recovery key
Microsoft · 2026 · official_doc
- 5
Bug Check 0xEA THREAD_STUCK_IN_DEVICE_DRIVER
Microsoft · 2026 · official_doc
Was this entry useful?