VIDEO_TDR_FAILURE (0x116): Your Graphics Driver Timed Out
In plain English
If you hit VIDEO_TDR_FAILURE with stop code 0x116, Windows is telling you the graphics driver stopped responding long enough that the system gave up and crashed. A lot of people see a frozen picture, a black screen, or a quick flicker first.
First safe step
The first steps here are simple and safe: check what changed, rule out heat or loose connections, then do a clean graphics-driver reinstall.
Stop when the screen stays up through the work that used to crash it.
If you hit VIDEO_TDR_FAILURE with stop code 0x116, Windows is telling you the graphics driver stopped responding long enough that the system gave up and crashed. A lot of people see a frozen picture, a black screen, or a quick flicker first. If you need the wider picture, start with the full stop code guide for blue and black screens.
This is usually a driver timeout problem, not a screen-resolution or display-settings problem. In plain English, Windows tried to reset the graphics driver through TDR (Timeout Detection and Recovery), but the reset failed, so the PC showed a blue or black crash screen instead of recovering normally.
The first steps here are simple and safe: check what changed, rule out heat or loose connections, then do a clean graphics-driver reinstall. If your PC will not stay on long enough to do that, you may need how to get into Safe Mode when Windows will not boot before you continue.
What VIDEO_TDR_FAILURE (0x116) means
VIDEO_TDR_FAILURE with 0x116 means Windows tried to recover from a graphics timeout and could not. TDR stands for Timeout Detection and Recovery. In plain English, your graphics driver stopped responding long enough that Windows treated it as a crash instead of a short glitch.
The usual pattern is easy to recognize. The picture freezes, flickers, or turns black, then the PC either restarts or shows a blue screen. That is different from a simple display setting problem, where the screen may look wrong but Windows keeps running.
This code points first to the display driver and the graphics system around it. It does not usually mean your screen resolution is set wrong, and it does not mean the monitor itself is always the cause. If your PC keeps hanging before the crash, you may also want to compare the pattern with the freeze-then-crash stop code page or, if another driver code appears instead, the driver crash page for 0x0A.
Because the timeout happens in the graphics path, the fix usually starts with the graphics driver. If the PC will not stay on long enough to work normally, use how to get into Safe Mode when Windows will not boot, then come back here for the clean driver reinstall path.
1 Signs this is a graphics driver timeout, not a screen setting problem Free
If this problem fits your PC, the pattern is usually obvious. The screen may freeze for a few seconds, flicker, turn black, come back briefly, or restart the computer. In many cases the crash happens while opening a game, watching video, using hardware-accelerated apps, or waking the PC from sleep.
You may also see the display recover once before Windows gives up and crashes. That is different from a picture that is simply too large, too small, blurry, or on the wrong monitor. A resolution or scaling problem changes how the screen looks, but it does not usually lock the PC, blank the display, and end in a stop code.
This page is for the crash path. If your screen looks wrong but Windows stays usable, you want a display-settings or device-specific fix instead, not this stop-code guide. If your PC freezes and then crashes after a driver or system change, you may also want what to do in the first 30 minutes after a crash.
If the symptom is a freeze that ends in a blue or black screen, you are in the right place. If the code later turns out to be different, compare it with the freeze-then-crash stop code page or, if another driver is involved, the driver crash page for 0x0A. And if Windows will not stay up long enough to work, use how to get into Safe Mode when Windows will not boot.
2 First safe checks before you touch the driver Free
- Before you change the driver, take one minute to spot the pattern. Write down what you were doing right before the crash, such as a game, a browser video, waking the PC, or plugging in a second screen. Also note whether it happens in one app every time, or whether the whole PC can crash anywhere.
- Next, think about what changed recently. Common triggers are a new graphics driver, a Windows update, a monitor or dock, an overclocking or GPU tuning tool, or a laptop being moved between battery and charger use. If the crash started right after an update, see what to do in the first 30 minutes after a crash before you go further.
- If Windows is still usable, do one plain restart first. Save your work, restart, and test the same app or action again. One restart will not fix a broken driver, but it can clear a one-time hang and tell you whether the problem repeats in the same place.
- If the PC will not stay up long enough to test, use how to get into Safe Mode when Windows will not boot. If you start seeing other crash patterns instead of
0x116, compare them with the driver crash page for0x0Aor the freeze-then-crash stop code page. Then move on to the clean reinstall steps below.
3 Reinstall the graphics driver cleanly Free
This is the main fix for 0x116. The goal is simple: remove the broken or unstable graphics driver, restart so Windows falls back to a basic display driver, then install a fresh stable one from the right source.
If Windows will not stay up long enough to do that, use how to get into Safe Mode when Windows will not boot first. If the crashes began right after a patch, keep what to do in the first 30 minutes after a crash open in another tab, because the timing can help you decide whether to reinstall or roll back.
- Start by removing the current driver. Open
Device Manager, expandDisplay adapters, right-click your graphics device, then selectUninstall device. If you see a checkbox to remove the driver software, select it. - Some PCs also install the graphics driver through the PC maker's app or the GPU vendor's installer. If the driver came with software such as NVIDIA, AMD, or Intel graphics tools, uninstall that package from installed apps too if the first removal does not stick. Then restart the PC normally.
- After restart, the screen may look larger, lower-resolution, or plain. That is expected. Windows is usually using a basic display driver for the moment, which is what you want before installing a fresh copy.
- Now install the latest stable driver from your laptop or desktop maker first, especially for laptops and all-in-one PCs. If your PC maker does not offer a newer stable driver, use the driver from the GPU maker's official site instead. Do not use a driver-updater tool, a random download site, or a beta build unless the vendor specifically says it fixes your exact problem.
- If the crashes started right after a graphics-driver update, the newest version may be the problem. In that case, install a known-good earlier driver instead of chasing newer test releases. Many
VIDEO_TDR_FAILUREcases are fixed by going back one version. - After installation, restart again and test the exact app or task that used to trigger the crash. If the stop code changes to something driver-related such as the driver crash page for 0x0A, or the machine still hangs before crashing like the freeze-then-crash stop code page, move to the next checks rather than reinstalling different drivers over and over.
✓ Screen stable? You can stop here.
4 If the crash keeps coming back
If 0x116 comes back after a clean reinstall, look past the driver itself. On a desktop, check that the graphics card is seated fully, any GPU power plugs are firmly connected, and the video cable is not loose or damaged. Heat can cause the same freeze, black screen, and crash pattern, so make sure fans are spinning and vents are not packed with dust.
If the newest driver still crashes, try a different version instead of assuming newer means better. A slightly older stable driver from your PC maker or GPU maker can hold better than the latest release, especially if the problem started right after an update. If the crashes began after Patch Tuesday or a driver push, see what to do in the first 30 minutes after a crash for the fast checks around recent updates.
It is also possible that the driver is only the messenger. A weak power supply, failing graphics card, bad system memory, or an unstable overclock can all look like a TDR timeout. If the stop code changes and the screen now names something else, follow that code instead, such as the driver crash page for 0x0A or the freeze-then-crash stop code page when the pattern shifts.
If Windows will not stay up long enough to test, go back to Safe Mode and remove extra variables one at a time. Disconnect nonessential displays and docks, turn off GPU tuning tools, and test with the simplest setup you can. If even that does not change the pattern, the problem may be hardware and not something a driver reinstall can fix at home.
5 When to stop and get more help
If VIDEO_TDR_FAILURE keeps coming back after a clean driver reinstall, stop there and get more help. Repeated crashes after a fresh driver usually mean the problem is deeper than the driver itself.
Watch for signs that point to hardware trouble, like screen artifacts, random shutdowns, or crashes that happen with more than one graphics driver. If you also saw the same pattern after trying the driver crash page for 0x0A or the freeze-then-crash stop code page, that is another clue the fault may be broader than one bad install.
Before you ask for help, save the stop code, the driver version you tried, and any recent changes such as a new monitor, dock, update, or GPU tool. If Windows will not stay running long enough to do that, use how to get into Safe Mode when Windows will not boot and write the details down from there.
Keep the note short and practical. The more exact the crash pattern is, the easier it is to tell whether you need a different stop-code page or hands-on repair.
Frequently asked questions
Does a single 0x116 crash mean my graphics card is failing?
No. One crash often points to a bad or mismatched graphics driver. Hardware becomes more likely if crashes return after a clean reinstall, or if you see lines, broken colors, or shutdowns with no warning.
Will a clean graphics driver reinstall delete my files?
No. Removing and reinstalling the graphics driver does not delete documents or photos. Windows may look larger or blurry on a basic driver until the fresh driver is installed and the PC restarts.
What should I do if the stop code changes after the reinstall?
Follow the new code, not this page. A different code points to a different cause, so note the exact code and when it appeared before you try another fix.
The short version
VIDEO_TDR_FAILURE (0x116) after a freeze or black screen is usually a driver problem you can fix at home. The clean reinstall is the test that matters. If Windows runs normally after it, keep the driver version that worked and note what changed before the crash.
If the same code returns, or you see broken colors, lines on the screen, or shutdowns with no warning, stop reinstalling drivers. Save the code, the driver version, and when it happens, then get the hardware checked. That record saves time and avoids guessing.
Different number on screen?
Type it exactly as it appears and get the plain-English answer.
Pop-up telling you to call?
That is a scam. Microsoft never asks you to phone a number.