VIDEO_TDR_FAILURE Blue Screen 0x116: Why the GPU Reset Failed

Published October 23, 2026 · SJ AI Studio

VIDEO_TDR_FAILURE is Windows stop code 0x00000116 (0x116). Microsoft defines it as "an attempt to reset the display driver and recover from a timeout has failed." Windows noticed the graphics processor had stopped responding, tried to reset the display driver, and the reset did not finish in time. Microsoft's page names the usual reasons (an out-of-date display driver, hardware problems such as over-clocking, cooling, power or faulty parts, and too much running in the background) and lists seven basic checks for people without a debugger, ending with Safe Mode.

This page follows the Microsoft Learn article "Bug Check 0x116: VIDEO_TDR_FAILURE," read on 12 October 2026 and checked against the Microsoft Docs source file. Microsoft marks it as written for programmers and points customers to https://www.windows.com/stopcode. Every number and step below is from that page; where it says nothing, we say so.

What is TDR?

VIDEO_TDR_FAILURE 0x116 Timing Facts

Microsoft describes a familiar scene: the PC appears completely frozen, usually while the graphics processor is busy with heavy work, "typically during gameplay." The screen stops updating, and people tend to wait a few seconds and then hold the power button. To avoid that, Windows tries to detect these hangs and recover a responsive desktop on its own. Microsoft calls this Timeout Detection and Recovery (TDR). Under the hood, the operating system's GPU scheduler calls the display miniport driver's DxgkDdiResetFromTimeout function, which reinitializes the driver and resets the graphics processor.

When TDR works, you do not get a blue screen. Microsoft says a message appears saying the "Display driver stopped responding and has recovered." 0x116 is what happens when recovery itself fails.

When does a timeout become a blue screen?

The page gives the numbers.

FactValue (Microsoft Learn)
Default GPU timeout before TDR starts2 seconds
Blue screen if driver threads do not finish during the resetYes, 0x116
Blue screen if TDRs repeat quicklyDefault: more than five TDRs in one minute
Message when recovery works"Display driver stopped responding and has recovered"

During the reset, Microsoft explains, Windows tells the driver not to touch the hardware or memory and gives its running threads a short time to complete. If they do not, the system stops with 0x116. Separately, even successful recoveries count: if more than five happen within a minute, Windows stops with the same code.

So if you have been seeing the "stopped responding and has recovered" message before the blue screens started, that fits Microsoft's description of repeated TDRs.

Why does the graphics card stop responding?

Microsoft's "Resolution" section opens with a plain sentence: "The GPU is taking more time than permitted to display graphics to your monitor." It lists the reasons this can happen:

The 7 basic checks Microsoft lists

The 7 Basic Checks Microsoft Lists

For anyone not equipped to use the Windows debugger, Microsoft gives these basic troubleshooting steps. They are in Microsoft's order, with nothing added.

How do you start Safe Mode, per Microsoft?

TDR Thresholds

The page gives these steps:

Microsoft adds that Safe Mode may also be available by pressing a function key during boot, for example F8, and refers you to your PC maker for its specific startup options. Microsoft's page gives only this one path and does not mention Windows 11 menu names, so the labels on your PC may differ.

If the PC is stable in Safe Mode, that is consistent with a driver or a background program being involved, since Safe Mode loads only the minimum. Microsoft does not draw that conclusion on the page, so treat it as a reasonable reading, not an official verdict.

Checklist

For developers

Microsoft's debugger walkthrough uses !analyze -v, which shows the four parameters and the faulting module; in the page's example that module is nvlddmkm.sys. From there: lmvm to show the driver's details including its timestamp, dt dxgkrnl!_TDR_RECOVERY_CONTEXT on parameter 1 (with symbols) to see the timeout reason, ub on parameter 2 to land in the responsible module, and k for the stack. The four parameters are: 1, a pointer to the internal TDR recovery context, if available; 2, a pointer into the responsible driver module; 3, the error code of the last failed operation, if available; 4, internal context-dependent data, if available. In the page's worked example, parameter 3 reads ffffffffc000009a, which the debugger labels the optional NTSTATUS error code of the last failed operation, and parameter 4 reads 0000000000000004. Microsoft also links a separate page, "TDR changes in Windows 8 and later," for how the process changed in newer versions.

TDR registry keys. The 0x116 page links Microsoft's separate "TDR registry keys" page for more information, but it does not tell readers to change them to fix the blue screen, and neither do we.

Sources and how to check

Questions readers ask about VIDEO_TDR_FAILURE Blue Screen 0x116

What is stop code 0x116?

It is VIDEO_TDR_FAILURE (0x00000116). Microsoft says an attempt to reset the display driver and recover from a timeout failed.

What is TDR?

Timeout Detection and Recovery: Windows detects a hung graphics processor and tries to reset the driver. The default timeout is 2 seconds.

Why did I get the blue screen instead of a recovery message?

Microsoft says 0x116 occurs if driver threads do not finish during the reset, or if more than five TDRs happen in one minute by default.

What causes VIDEO_TDR_FAILURE?

Microsoft lists an outdated display driver, hardware issues such as over-clocking, wrong memory settings, poor cooling, insufficient power or defective parts, and too many background programs or visual effects.

How do I enter Safe Mode per Microsoft?

Settings, Update and Security, Recovery, Advanced startup, then Troubleshoot, Advanced Options, Startup Settings, Restart, and choose 4, 5 or 6.

Related articles