0X00000116
What it means
The graphics driver stopped responding and failed to recover — usually a driver issue, sometimes an unstable GPU overclock.
Also seen as: VIDEO_TDR_ERROR, VIDEO_TDR_FAILURE, 0x116
Quick fix steps
- Update your graphics driver to the latest version from NVIDIA/AMD/Intel directly.
- If you overclock your GPU, revert to stock settings and retest.
- Check GPU temperatures for overheating during the activity that triggers the crash.
For the full step-by-step walkthrough, see How to Read and Respond to Any Blue Screen.
Frequently Asked Questions
Does VIDEO_TDR_FAILURE always mean a graphics card problem?
Yes, essentially by definition — this stop code is specifically tied to a graphics driver failing to recover after a timeout, distinct from the milder "display driver stopped responding and recovered" event.
Is my graphics card damaged if I see this?
Not necessarily — an outdated or unstable driver is a more common cause than physical GPU damage, so updating the graphics driver is the sensible first step rather than assuming hardware failure.
Other error codes
0X0000001A — MEMORY_MANAGEMENT
Points to a problem with how memory is being handled — faulty RAM, a driver mismanaging memory, or disk corruption.
0X0000000A — IRQL_NOT_LESS_OR_EQUAL
Almost always a driver issue — most commonly network, audio, or graphics drivers.
0X000000EF — CRITICAL_PROCESS_DIED
A core Windows process crashed unexpectedly — often tied to a recent update or corrupted system files.
0X0000001E — KMODE_EXCEPTION_NOT_HANDLED
A driver running in kernel mode hit an error it couldn't recover from — usually a specific faulty or outdated driver.