Get the fix to “0x100000ea: THREAD STUCK IN DEVICE DRIVER M” error message for Windows XP, Vista, 7, 8, 8.1 or 10 operating systems.
Contents
Click on repair to fix all the erroneous graphics card drivers & Thread Stuck in Device Driver Windows 10 Acer in your system. You will also have an option to update in order to keep all your drivers updated. BSOD:: Thread Stuck In Device Driver While Playing Games? Feb 23, 2016. I getting this BDOS randomly, mostly while playing games. Here is my log file. View 1 Replies BSOD:: Thread Stuck In Device Driver Jan 31, 2016. The bluescreens are really random and like to happen out of no where.
- 1 About the “0x100000ea” error
- 1.1 Description and Symptoms
- 1.2 Causes of this Error
- 2 Fixing “0x100000ea” on Windows
- 3 More Information
About the “0x100000ea” error
The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.
Description and Symptoms
The error messages, alerts, warnings, and symptoms below are tied to this error.
Symptom 1: 0x100000ea error screen
The 0x100000ea error is encountered when a video hardware device driver enters an infinite loop and Windows has to terminate it and stop the booting process.
Causes of this Error
This error has been known to occur as a result of one or more of the following:
Cause 1: Bad or misconfigured device driver
The most common cause of this error is a faulty or outdated device driver. Alternatively, this error may appear after a driver update or after Windows was just installed.
Fixing “0x100000ea” on Windows
Fix #1: Reinstall the video drivers
Because the 0x100000ea error is usually caused by the video hardware, the video driver might not be compatible with your Windows version.
Make sure your Windows version has the correct driver for the video hardware and that the version of the driver is compatible with yoru Widnows version.
To update the driver, follow these steps:
- Click Start
- Type
devmgmt.msc
in the search box and click on devmgmt or Device Manager - Right-click on the driver
- Click Update
Fix #2: Hardware Acceleration to none
Setting the Hardware Acceleration option to None could fix the error. However, by doing so, you might reduce your video card’s functionality and performance.
Follow these steps:
- Click Start
- Type
display
in the search results - Select Display from the list
- Go to Change Display Settings
- Click Advanced Settings
- Go to Troubleshoot
- Click Change Settingsv
- Drag the Hardware Acceleration slider to None
- Click OK
- Restart your computer
Display Adapter Troubleshooter error screen
Fix #3: Replace video card
Because the 0x100000ea error is caused by a video device or driver, try replacing the video card from your computer with a new one.
More Information
Linked Entries
Support Links
- Easy Recovery Essentials for Windows – our repair and recovery disk.
It’s an easy-to-use and automated diagnostics disk. It’s available for Windows 8, Windows 7 and Windows Vista. It’s also available for Windows XP and Windows Server.Read more at Windows Recovery Disks. - The NeoSmart Support Forums, member-to-member technical support and troubleshooting.
- Get a discounted price on replacement setup and installation discs: Windows XP, Windows Vista, Windows 7, Windows 8, Windows 10.
Applicable Systems
This Windows-related knowledgebase article applies to the following operating systems:
- Windows XP (all editions)
- Windows Vista (all editions)
- Windows 7 (all editions)
- Windows 8 (all editions)
- Windows 8.1 (all editions)
- Windows 10 (all editions)
The THREAD_STUCK_IN_DEVICE_DRIVER bug check has a value of 0x000000EA. This indicates that a thread in a device driver is endlessly spinning.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
THREAD_STUCK_IN_DEVICE_DRIVER Parameters
Parameter | Description |
---|---|
1 | A pointer to the stuck thread object |
2 | A pointer to the DEFERRED_WATCHDOG object |
3 | A pointer to the offending driver name |
4 | In the kernel debugger: The number of times the 'intercepted' bug check 0xEA was hit On the blue screen: 1 |
Cause
A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle.
This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. Frequently, this is the result of a bad video card or a bad display driver.
Resolution
Use the .thread (Set Register Context) command together with Parameter 1. Then use kb (Display Stack Backtrace) to find the location where the thread is stuck.
If the kernel debugger is already connected and running when Windows detects a time-out condition. Then DbgBreakPoint will be called instead of KeBugCheckEx. A detailed message will be printed to the debugger. See Sending Output to the Debuggefor more information.
This message will include what would have been the bug check parameters. Because no actual bug check was issued, the .bugcheck (Display Bug Check Data) command will not be useful. The four parameters can also be retrieved from Watchdog's global variables by using dd watchdog!g_WdBugCheckData L5' on a 32-bit system, or dq watchdog!g_WdBugCheckData L5' on a 64-bit system.
Debugging this error in an interactive manner such as this will enable you to find an offending thread, set breakpoints in it, and then use g (Go) to return to the spinning code to debug it further.
On multiprocessor machines (OS build 3790 or earlier), you can hit a time out if the spinning thread is interrupted by a hardware interrupt and an ISR or DPC routine is running at the time of the bug check. This is because the time out's work item can be delivered and handled on the second CPU and the same time. If this occurs, you must look deeper at the offending thread's stack to determine the spinning code which caused the time out to occur. Use the dds (Display Words and Symbols) command to do this.