VIDEO_TDR_FAILURE Blue Screen Fix In Windows 11 (2026)
VIDEO_TDR_FAILURE is a Windows blue screen with the stop code 0x116.
It means Windows tried to reset a stuck graphics driver and could not recover.
This guide follows Microsoft’s own pages and lists the checks in the order Microsoft gives them.
Quick answer
| Step | What to do |
|---|---|
| 1 | Write down the stop code and any module name shown on the blue screen |
| 2 | Remove any hardware you added just before the crashes |
| 3 | Update the display driver in Device Manager or from the graphics maker |
| 4 | Install Windows updates and patch the game or app that was running |
| 5 | Run Windows Memory Diagnostics and check cooling, power and overclocking |
| 6 | If Windows will not start, use Safe Mode or a restore point |
What VIDEO_TDR_FAILURE means
Microsoft’s bug check page says the error means Windows could not reset the display driver and recover from a timeout.
TDR stands for Timeout Detection and Recovery, the Windows feature that watches the graphics processor.
A graphics hang usually shows up as a frozen screen during heavy graphics work such as gaming.
Microsoft gives the default timeout as 2 seconds.
What happens before the blue screen
Windows first tries to reset the driver, and the blue screen appears only when that fails.
| What you see | What it means |
|---|---|
| Brief flicker, then “Display driver stopped responding and has recovered” | Windows reset the driver and recovery worked |
| Frozen picture, then a blue screen with VIDEO_TDR_FAILURE | The reset did not finish in time |
| Repeated recoveries, then the blue screen | Microsoft says multiple timeouts in a short period can also trigger it, with a default threshold of more than five in one minute |
Microsoft’s TDR page says each recovery is logged in Event Viewer.
Why the timeout happens
Microsoft says the graphics processor is taking longer than allowed to produce output.
| Cause | Detail from Microsoft |
|---|---|
| Outdated display driver | Install the latest driver, because it supports the TDR process |
| Overclocked parts | Overclocked components, such as the motherboard, can cause it |
| Wrong settings | Incorrect component compatibility or settings, especially memory configuration and timings |
| Cooling or power | Insufficient system cooling or insufficient system power |
| Defective parts | Faulty memory modules or a faulty motherboard |
| Software load | Visual effects or too many background programs may stop the video card from responding in time |
Note the module name
Microsoft’s support page says the stop code appears at the bottom of the screen, with the name of the module that was running if it is available.
A graphics driver file in that name points you to the display driver as the place to start.
Microsoft’s own sample crash analysis for this stop code names nvlddmkm.sys, an NVIDIA driver file, as the module.
That is one example from Microsoft’s page and not a rule for every PC.
Step 1: remove new hardware
Microsoft says to shut the PC down, remove any hardware added before the error started, and restart.
The bug check page adds that you should confirm new hardware is compatible with your version of Windows.
Step 2: update or replace the display driver
- Right-click Start and select Device Manager.
- Expand Display adapters.
- Right-click your graphics adapter and select Update driver.
Microsoft’s support page says to look for devices marked with an exclamation point, and to disable or uninstall the device if updating does not help.
For a driver from the graphics maker, our guide to updating an Intel graphics driver shows the steps.
If the crashes began after a new driver, our guide to rolling back an NVIDIA driver covers going back to the previous one.
Step 3: install updates and patch the game
Microsoft’s bug check page says to update graphics software, including DirectX and OpenGL.
It also says to make sure graphics-heavy programs such as games are fully patched.
To install Windows updates, select Start > Settings > Windows Update, then select Check for updates, or follow our guide to checking for updates in Windows 11.
Step 4: check Event Viewer
Microsoft says to check the System log in Event Viewer for other errors that identify the device or driver involved.
If the log names a driver, disable it or check with its manufacturer for an update.
Step 5: test the memory
- Type Memory in the Control Panel search box.
- Select Diagnose your computer’s memory problems.
- After the test, check the MemoryDiagnostics-Results entry in the System log.
Microsoft lists defective memory modules among the hardware causes, so this test rules one of them out.
Step 6: check cooling, power and overclocking
Microsoft’s list of causes names overclocking, insufficient cooling and insufficient power.
Return any overclocked parts to their normal settings.
Make sure the fans are running and that the power supply can meet the demand of the graphics card.
Microsoft also says to run the hardware diagnostics supplied by the PC maker if they are available.
If the blue screen appears during gaming, our guide to seeing which apps use your GPU shows what else is loading the graphics card.
If Windows will not start normally
Microsoft says you can do the remaining checks from Safe Mode, which loads only the minimum drivers and services.
- Open the Windows Recovery Environment.
- Select Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 for Safe Mode or 5 for Safe Mode with Networking.
Microsoft notes that you need your BitLocker recovery key if the device is encrypted.
Our guide to starting Windows 11 in Safe Mode covers the routes in more detail.
If it keeps happening
Microsoft’s support page says to keep roughly 10 to 15 percent of the drive free, because Windows needs room for swap files and other functions.
If nothing else helps, it says to use a system restore point or another option from its Recovery options in Windows 11 article.
A flickering screen without a blue screen is a different problem, covered in our guide to screen flickering in Windows 11.
Sources
Microsoft Learn: Bug Check 0x116 VIDEO_TDR_FAILURE and WDDM Support for Timeout Detection and Recovery. Microsoft Support: Troubleshooting Windows unexpected restarts and stop code errors and Windows startup settings.