VIDEO_TDR_FAILURE blue screen in Windows 11: how to fix it

Applies to: Windows 11 (and Windows 10) PCs that crash with VIDEO_TDR_FAILURE, usually while gaming, rendering, watching video or waking from sleep. If you only saw a sad face and a QR code, our guide on finding the stop code after a crash shows where Windows records it.

What VIDEO_TDR_FAILURE means

TDR stands for Timeout Detection and Recovery. Windows keeps an eye on the graphics processor (GPU), and if a task keeps it busy for too long, the desktop would look frozen. Microsoft’s TDR documentation explains that the default limit is two seconds. When the GPU goes past it, Windows asks the display driver to reset the card and rebuild the desktop. When that works, you see a brief flicker and, sometimes, the message “Display driver stopped responding and has recovered.”

A blue screen happens when that rescue goes wrong. Microsoft’s bug check 0x116 reference describes it as a case where “an attempt to reset the display driver and recover from a timeout has failed.” Its cause section gives two routes: the driver doesn’t finish its work in time once Windows tells it to stop, or the card hangs repeatedly, by default more than five times within one minute.

So the stop code doesn’t say the graphics card is dead. It says the GPU took too long and its driver couldn’t recover. Microsoft’s resolution list points at an outdated display driver first, then at hardware: overclocked parts, wrong memory settings or timings, not enough cooling, not enough power, and defective components. It also mentions too many background programs slowing the PC down.

Which file is named on the blue screen

File in the crash	Graphics driver
nvlddmkm.sys	NVIDIA GeForce, RTX and Quadro
atikmdag.sys or atikmpag.sys; amdkmdag.sys on some newer drivers	AMD Radeon
igdkmd64.sys (newer Intel drivers use similar names starting with igdkmd)	Intel integrated graphics or Intel Arc
dxgkrnl.sys or dxgmms2.sys	Windows’ own graphics kernel; the vendor driver is still the usual suspect

A related code, VIDEO_TDR_TIMEOUT_DETECTED (0x117), records a GPU hang that Windows did recover from. Microsoft’s TDR page says the PC bug checks after five or more hangs within a minute. The fixes below apply to both.

Match your situation

What you see	Likely cause	Start with
Crashes began after a driver update or a new graphics card	The driver, or leftovers from an older one	Fix 2
Crashes only in games or 3D apps, after some time under load	Heat, power or an unstable overclock	Fix 3, Fix 4, Fix 5
You use a factory-overclocked card, a tuning tool, XMP or EXPO	Clocks or memory settings the card can’t sustain	Fix 3
Crashes at the desktop, during video, or after sleep	The driver or the card’s power state	Fix 2, Fix 5
Different stop codes each time	RAM, power supply or other hardware	Fix 5, Fix 7
The crash happens before you can sign in	The graphics driver loading at startup	The section below

If Windows crashes before you can sign in

Safe Mode starts Windows with a basic display driver instead of the NVIDIA, AMD or Intel one, which Microsoft’s bug check page recommends for isolating this error. It’s also the best place to remove the faulty driver.

1. After two failed starts in a row, Windows normally opens the blue Choose an option screen. From the sign-in screen, you can also hold Shift while you select Power and then Restart.
2. Select Troubleshoot > Advanced options > Startup Settings, then Restart.
3. Press 4 for Safe Mode, or 5 for Safe Mode with Networking if you need to download a driver.

If the recovery screen doesn’t appear, our WinRE guide covers opening recovery when Windows won’t start. If the PC is stable in Safe Mode, the graphics driver or the card under load is almost certainly involved; go straight to Fix 2.

Fix 1: Confirm the driver and when it crashes

Microsoft’s first step is to check the System log for other errors that point to a device or driver. A few minutes here tells you which fix to try first.

1. Right-click Start, open Event Viewer and go to Windows Logs > System. Look for a BugCheck entry with code 0x00000116. Warnings from source Display shortly before it, saying the driver stopped responding and recovered, show the GPU had been hanging for a while.
2. Search Start for Reliability Monitor. Its timeline shows each crash by date, which makes it easy to line them up with driver updates, game installs or warm weather.
3. Small crash dumps are saved in C:\Windows\Minidump. In WinDbg, !analyze -v shows the faulting module; Microsoft’s own 0x116 example names nvlddmkm.sys.

Crashes only under heavy 3D load point toward heat, power or clocks; crashes at idle or during video point more toward the driver.

Fix 2: Do a clean reinstall of the graphics driver

Installing a new driver over an old one keeps old settings, profiles and sometimes old files. A clean reinstall removes all of that first, which is why it often works where a normal update didn’t. Microsoft’s guidance is to get an update from the driver’s maker, and that’s the source to use here, not a third-party driver updater.

Download the right driver first

1. Note your graphics card model under Display adapters in Device Manager.
2. Download the current driver from NVIDIA, AMD or Intel, or, on a laptop, from the laptop maker’s support page. Laptop makers sometimes customize graphics drivers for switchable graphics, so their version is the safer first choice.
3. If the crashes started right after a driver update, also download the previous version, so you can go back if the newest one doesn’t help.
4. Save the installer, then disconnect from the internet if you can, so Windows Update doesn’t slip its own driver in.

Remove the current driver

1. Ideally in Safe Mode, open Device Manager, expand Display adapters, right-click the card and choose Uninstall device.
2. Tick Attempt to remove the driver for this device and select Uninstall. The screen may flicker and drop to a lower resolution; that’s the basic Microsoft display driver taking over.
3. Restart.

Some people use Display Driver Uninstaller (DDU), a free third-party tool not made by Microsoft or the GPU makers, for a deeper cleanup in Safe Mode. If you try it, set a restore point first. For most PCs, Device Manager plus the installer’s clean option is enough.

Install the driver cleanly

Run the installer you downloaded. NVIDIA’s installer has typically offered a Perform a clean installation option under custom or advanced install, and AMD’s installer a Factory Reset option. Option names change between versions, so pick whichever choice removes previous settings. Restart, then reconnect to the internet.

If the clean install of the newest driver still crashes, repeat it with the previous version. Once you find a stable one, you can stop Windows Update replacing your graphics driver until a newer release fixes the problem.

Fix 3: Remove GPU, CPU and memory overclocks

Microsoft lists overclocked components and incorrect memory configuration and timings as causes of this stop code. A graphics card pushed past its stable clocks can stall long enough to trip the timeout, and it may only do so when it’s hot or heavily loaded.

1. Reset any GPU tuning tool, such as MSI Afterburner or the tuning page in NVIDIA’s or AMD’s own software, to default clocks, voltage and power limit. Then remove the tool from startup.
2. If your card is factory overclocked, some makers’ utilities offer a silent or default mode with lower clocks. Try it as a test.
3. Turn off CPU overclocks and undervolts, and XMP or EXPO memory profiles, in the BIOS/UEFI setup.

Warning: changing firmware settings can trigger a BitLocker recovery prompt on the next start. Make sure you can find your recovery key before you change anything, and write down the settings you change.

Our IRQL guide shows how to switch off XMP, EXPO and CPU overclocks step by step. If the crashes stop, bring settings back one at a time or leave them at default.

Fix 4: Rule out overheating

Insufficient system cooling is on Microsoft’s list. A hot GPU slows itself down, and an overheating one can stop responding outright, which is why heat-related crashes tend to come after 20 or 30 minutes of gaming rather than right away.

1. Open Task Manager (Ctrl + Shift + Esc), select Performance and then your GPU. On many PCs with a dedicated card, a GPU temperature reading appears there. Your GPU vendor’s app usually shows it too.
2. Watch the temperature while the game or app that crashes is running. Compare it with the maximum your card’s maker publishes; readings that sit at or near that limit point to a cooling problem.
3. Shut down, unplug, and clean dust out of the case filters, the card’s fans and heatsink, and laptop vents with short bursts of compressed air.
4. Check that every fan spins, that the case has airflow in and out, and that a laptop sits on a hard surface, not a bed or cushion.

Capping the frame rate in the game or the GPU software also lowers heat and power draw, and it’s a quick test: if crashes stop with a cap, cooling or power is a likely cause. Replacing thermal paste or pads can affect the warranty, so leave it to the maker or a repair shop if in doubt.

Fix 5: Check power and the card’s connection

Insufficient system power is another cause Microsoft names. A graphics card’s power draw can spike sharply under load, and a power supply that’s too small, aging or poorly connected may not keep up for those moments.

1. Check that the power supply’s wattage meets or beats the card maker’s recommendation.
2. Make sure every power connector on the card is pushed fully home. Where the card needs two or more connectors, separate cables from the power supply are generally preferred over one cable with a split end.
3. Shut down, unplug and reseat the card in its slot, and check that the monitor cable is connected to the graphics card, not the motherboard.
4. On a laptop, test with the original charger plugged in and Windows set to a balanced or best-performance power mode.

Warning: only open a desktop PC if you’re comfortable doing so. Unplug it first and touch a metal part of the case to discharge static. Opening a laptop or a PC under warranty may void the warranty; contact the maker instead.

Fix 6: Update Windows, games and firmware

Microsoft’s page asks you to check that graphics software such as DirectX and OpenGL is up to date and that games and other graphics-heavy apps are fully patched.

1. Install updates under Settings > Windows Update, including anything listed under Advanced options > Optional updates that isn’t a graphics driver you just replaced.
2. Update the game or app that crashes, and verify its files through its launcher if it offers that option.
3. If only one game crashes, lower its graphics preset and turn off settings such as ray tracing or an in-game overclock, then raise them again one at a time.
4. Close background apps you don’t need while gaming, especially overlays, screen recorders and RGB or monitoring tools. Microsoft notes that too many background programs can leave the card unable to respond in time.
5. Check your PC or motherboard maker’s support page for a newer BIOS and chipset driver, and follow its instructions exactly.

If the crashes started right after a Windows update rather than a driver update, you can remove it under Settings > Windows Update > Update history > Uninstall updates while you wait for a fixed release.

Fix 7: Test memory and repair Windows files

Microsoft lists defective memory modules among the causes and suggests Windows Memory Diagnostic. Our MEMORY_MANAGEMENT guide covers testing your RAM step by step, including where Windows logs the result, so it isn’t repeated here.

To repair damaged Windows files that the graphics stack relies on, open Terminal (Admin) and run these one at a time, DISM first:

DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow

Fix 8: TdrDelay (last resort, read the warning)

Many guides suggest raising the TDR timeout in the registry. Microsoft’s TDR registry keys page describes these values as tools for driver testing and debugging, and says plainly that “end users shouldn’t manipulate these registry keys.”

A longer timeout doesn’t fix a hot, unstable or underpowered card, or a buggy driver. It only gives the GPU more time before Windows steps in, so a real hang can last longer and look like a frozen PC. The one case where it makes sense is a known, legitimate long-running GPU job, such as some rendering or compute software, whose maker documents the change. For games, it usually just hides the symptom.

Warning: editing the registry incorrectly can stop Windows from starting. Create a restore point first, change only the values below, and never set TdrLevel to 0, which turns detection off entirely. Undo the change if the crashes continue.

1. Press Windows + R, type regedit and press Enter.
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers.
3. Right-click in the right pane, choose New > DWORD (32-bit) Value and name it TdrDelay. Set it to a modest number of seconds in Decimal, such as 8. Microsoft gives a default of 2 seconds.
4. Restart and test.

Microsoft’s page also lists TdrDdiDelay (default 5 seconds), the time Windows allows driver threads to finish before it raises 0x116. Some guides raise it as well; the same warning applies. To undo either change, delete the value you created and restart.

When the graphics card itself is failing

If a clean driver, default clocks, normal temperatures and a known-good power supply all still end in 0x116, the card may be faulty. Microsoft names defective parts as a cause and suggests the system maker’s hardware diagnostics.

• If your CPU has integrated graphics, remove the card, connect the monitor to the motherboard and use the PC for a while. If the crashes stop, the card is the likely fault.
• Run the PC or laptop maker’s hardware diagnostics, often in the firmware or a support app.
• If the card or PC is under warranty, contact the maker with the crash dates from Reliability Monitor.

Known issues

As of November 2026, Microsoft’s Windows 11, version 25H2 release health page lists no known issue involving VIDEO_TDR_FAILURE, graphics drivers or stop errors. After a new graphics driver, check the GPU maker’s release notes and known issues list too.

Related guides

• Your PC ran into a problem and needs to restart: how to fix it
• How to stop Windows 11 from updating your graphics driver
• IRQL_NOT_LESS_OR_EQUAL blue screen in Windows 11: how to fix it
• PAGE_FAULT_IN_NONPAGED_AREA blue screen in Windows 11: how to fix it
• DPC Watchdog Violation on Windows 11 and 10: how to fix it
• Black screen on Windows 11 or 10? How to fix it
• Second monitor not detected in Windows 11: how to fix it

Official sources

• Microsoft: Bug check 0x116 VIDEO_TDR_FAILURE
• Microsoft: Timeout detection and recovery (TDR)
• Microsoft: Testing and debugging TDR (TDR registry keys)