
VIDEO_TDR_FAILURE (bug check 0x116) is the end of a chain. Windows gives the graphics processor about 2 seconds to finish or pause its current job. When it doesn’t, Timeout Detection and Recovery (TDR) resets the graphics driver, the screen blinks and you may see Display driver stopped responding and has recovered. The stop screen, which may be black instead of blue on Windows 11 version 24H2 and later, comes only when that reset itself fails, or when Windows has had to recover more than five times within a minute.
So the crash is rarely the first sign: brief freezes, black flashes and apps that suddenly render black often come first, and Windows records each one.
The quickest split: the file under What failed names the graphics vendor, and the moment of the crash (under heavy load, at the desktop, or only on a dock) tells you whether to look at the driver, at heat and power, or at the dock.
Try these first
- Write down the file under What failed: nvlddmkm.sys is NVIDIA, a name starting igdkm is Intel, and one starting amdkm or atikm is AMD.
- Crashes began after an update? Roll back the display driver in Device Manager; otherwise install your model’s driver from the PC maker (or the chip maker, for a card you added).
- Remove any GPU or CPU overclock, including tuning-app profiles, and return clocks to default.
- Clean dust from the vents and check that the fans spin while the GPU is busy.
- Crashing during video calls or streaming? Turn off graphics acceleration in the browser as a test.
- Run a day without the dock or DisplayLink adapter to see if the crashes stop.
Which graphics chip failed: read the file name
If the PC restarted before you could read the file under What failed, the blue screen of death guide shows how to find the code in Reliability Monitor and open the minidump, where IMAGE_NAME in the !analyze -v output gives the same file name.
| File named | Graphics chip | Where the driver should come from |
|---|---|---|
nvlddmkm.sys | NVIDIA GeForce, RTX or Quadro; an nvlddmkm.sys video TDR failure points here | Laptops and pre-built business desktops: the PC maker first. Add-in cards you bought separately: NVIDIA. |
igdkmd64.sys, igdkmdn64.sys or igdkmdnd64.sys (seen on Arc cards) | Intel integrated or Arc graphics, behind an igdkmd64.sys video TDR failure or an igdkmdn64.sys video TDR failure | The PC maker first; for an Arc card you added yourself, Intel. |
amdkmdag.sys, amdkmpag.sys, atikmdag.sys or atikmpag.sys | AMD Radeon, including Ryzen integrated graphics; an amdkmdag.sys video TDR failure or an atikmpag.sys video TDR failure means the AMD driver | Laptops: the PC maker. Desktop cards: AMD. |
dxgkrnl.sys or dxgmms2.sys | Windows’ own graphics kernel | Usually just the part that noticed the hang; look for the vendor driver in Event Viewer or the dump. |
The warnings Windows logged before the crash
In Event Viewer > Windows Logs > System, a warning with Event ID 4101 from source Display names the driver that stopped responding, usually by a short name rather than the file name: nvlddmkm for NVIDIA, a name starting igfx for Intel, or one starting amd or ati for AMD. Reliability Monitor may list the same incidents as a hardware error, LiveKernelEvent, with code 117 (a driver timeout the system survived) or 141 (a timeout in one graphics engine).
On a laptop with two graphics chips, the file name tells you which one hung. On many NVIDIA-plus-Intel laptops, the NVIDIA chip sends its frames through the Intel chip to the screen, so an outdated Intel driver can upset the NVIDIA one; update both, as the matched pair the PC maker publishes.
When it crashes points to the cause
| When it happens | Likely cause | What to do first |
|---|---|---|
| In games, 3D, CAD or video rendering, after a while under load | GPU heat, power delivery or an overclock; sometimes the driver | Default clocks, cooling and power checks, then a clean driver install |
| Within days of a driver or Windows update, in ordinary use | The new driver on your hardware | Roll Back Driver, then install the PC maker’s version |
| During video calls, streaming or browser video | Driver, or the browser’s GPU acceleration | Update the driver; test with browser acceleration off |
| Only on a dock, a DisplayLink adapter or several external monitors | Dock firmware or DisplayLink driver, plus the GPU driver | Update dock firmware and DisplayLink; test without the dock |
| At startup or right after sign-in | A damaged driver install | Safe Mode, uninstall the display driver, reinstall |
| Alongside other stop codes, or with no pattern at all | RAM, power supply or other hardware | Windows Memory Diagnostic and the PC maker’s hardware tests |
Microsoft adds one cause the table doesn’t show: so many background programs running that the graphics card can’t respond in time.
If you can’t stay signed in long enough to work, find your BitLocker recovery key, then start in Safe Mode from the Windows Recovery Environment (WinRE) as the blue screen guide shows. Safe Mode runs Microsoft’s basic display driver instead of the vendor’s. If the PC is stable there, suspect the vendor driver or something that loads with it, such as an overlay or a tuning tool that applies an overclock at sign-in. Safe Mode barely works the graphics chip, though, so it can’t rule out heat, power or a failing card.
Reinstall the right driver, cleanly
Installing over a damaged driver often carries the problem forward, so remove the old one and its settings. Download the new driver first and save it locally.
Pick the right source
Laptop makers tune graphics drivers for their panels, hybrid graphics and power limits. Intel says its generic driver isn’t validated for your specific PC and recommends the maker’s driver when it’s newer. Use a generic driver only when the maker’s version is old and still crashes, or for a card you added; if it makes things worse, roll back.
Use the vendor’s clean-install option
- NVIDIA: in the driver installer, choose Custom (Advanced), tick Perform a clean installation, then restart when it finishes. This resets NVIDIA’s settings profiles along with the driver.
- AMD: AMD’s Cleanup Utility removes AMD graphics and audio drivers but leaves chipset drivers alone. It creates a restore point and offers to restart into Safe Mode, which AMD recommends; let Windows Update finish first, or the utility stops.
- Intel: Intel’s own graphics driver installer offers Execute a clean installation after the license screen; it removes old Intel drivers and resets Intel graphics settings. No box? Use the Device Manager method below.
- Any brand without a clean-install option: remove the device and its driver in Device Manager, restart and run the installer you saved. Our screen flickering guide walks through those steps, including the fallback to Microsoft Basic Display Adapter.
Disconnect from the internet between the removal and the install so Windows Update can’t slip in a different driver, and note the version that proves stable; if crashes return weeks later, check whether Windows Update replaced it.
Heat, power and overclocks
A graphics chip that’s too hot, short of power or running past its rated clocks makes mistakes, and a stalled job is exactly what TDR catches. That’s why the same driver can be fine on one PC and crash on another.
- Go back to default clocks. Reset GPU tuning tools such as MSI Afterburner and the overclocking sections of NVIDIA or AMD software; for a factory-overclocked card, the card maker’s utility can often set reference clocks. Undo CPU overclocks and memory profiles (XMP or EXPO in BIOS setup) too, since Microsoft also lists memory timings as a cause; before changing BIOS settings, have your BitLocker recovery key ready, since some BIOS changes trigger a recovery prompt. If the crashes stop, leave them at default.
- Check temperatures. Task Manager’s Performance tab shows a temperature for many dedicated GPUs; the card maker’s software shows more. A GPU near its limit during the crash, or fans that never ramp up, points to cooling. Our computer overheating guide covers dust, fans and laptop vents.
- Check power on desktops. Shut down and unplug the PC before you open the case. Then check that every power cable on the graphics card is fully seated and that the power supply meets the card maker’s recommended wattage. Crashes that start the moment a game loads can trace to power.
- Use the right charger on laptops. A smaller USB-C charger may not power the dedicated GPU under load, so test with the laptop’s own adapter.
Rather have a technician sort it out?
With your approval, a technician can check which graphics driver keeps hanging, install the version your PC maker supports and test it with you, as long as Windows stays up long enough to connect. A GoProIT technician can connect remotely, with your permission, and fix it while you watch. $59 per fix, Mon–Fri 8am–8pm ET.
Browsers, apps and docks that trigger it
One app every time
If crashes happen in one program, update it first; Microsoft also suggests keeping DirectX, OpenGL and graphics-heavy apps fully patched. For a browser, turn off Use graphics acceleration when available in its system settings as a test; Chrome and Edge both have it. On a laptop with two graphics chips, go to Settings > System > Display > Graphics (on Windows 10, the Graphics settings link on the Display page), add or select the app and set it to Power saving so it runs on the integrated chip; a few apps choose their own GPU and ignore this. If the crashes stop, suspect the dedicated GPU or its driver, not the app.
Overlays and screen recorders hook into the graphics driver, so turn them off for a day to rule them out.
Docks and DisplayLink
A DisplayLink dock adds its own display driver, and USB-C and Thunderbolt docks add firmware between the laptop and the monitors. If crashes come only while docked, update the DisplayLink driver and dock firmware before you blame the graphics card; our second monitor guide covers dock updates, including the order Dell recommends. Lower the external monitors’ resolution or refresh rate while you test.
CAD and design workstations
CAD vendors such as Autodesk and Dassault Systèmes (SOLIDWORKS) publish lists of tested graphics cards and driver versions; install a listed driver rather than the newest gaming driver. On GeForce cards, NVIDIA points creators who prioritize reliability to its Studio Driver instead of Game Ready; RTX professional cards have a Production Branch driver.
About the TdrDelay registry tweak
Many guides suggest raising TdrDelay so Windows waits longer before resetting the driver. Microsoft documents TdrDelay (default 2 seconds) and related values under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers, but as testing and debugging settings for driver developers, and it states that end users shouldn’t change them.
A longer delay doesn’t make a hung GPU finish its work; it only makes each freeze last longer. Setting TdrLevel to 0 turns detection off, so a hang becomes a frozen PC with no recovery and no dump. The one legitimate exception is a specialist app whose vendor tells you to change the value for long compute jobs.
If someone has added these values without an app vendor asking for them, removing them restores the defaults. A wrong registry edit can stop Windows from starting, so first right-click the GraphicsDrivers key in Registry Editor and choose Export to save a backup (or create a restore point), then delete only the Tdr values under it and restart.
Several PCs, one problem
Graphics drivers can reach an office PC three ways: Windows Update, the PC maker’s update tool (such as Dell Command Update, HP Image Assistant or Lenovo System Update) and the GPU maker’s app (the NVIDIA app, AMD Software or Intel Driver & Support Assistant). With more than one active, identical PCs drift onto different driver versions unnoticed, so pick one channel per model, usually the PC maker’s tool. When several start showing 0x116 in the same week, suspect a single driver release: roll back one machine for a few days, then hold that version on the rest. The blue screen guide’s office section covers pausing a driver in Intune (and the licensing it requires) or excluding drivers from Windows Update with Group Policy.
Note the driver version and date that works for each model, plus dock firmware versions, so the next crash becomes a quick comparison. To hand driver crashes like this to someone else, our Business Support Plan includes unlimited remote help desk tickets and automated Windows patching per user, but not hardware, parts or on-site work.
When it’s the graphics card, and when to stop
Suspect the hardware when:
- Crashes continue after a clean install of a driver version that used to be stable, at default clocks, with temperatures in range.
- You see corruption on screen before the crash: colored dots, lines, checkerboard blocks or flashing textures.
- The PC maker’s hardware diagnostics report a graphics or memory error, or Windows Memory Diagnostic finds errors.
- A desktop graphics card fails the same way in another PC, or the crashes stop with a different card.
- The card’s fans don’t spin under load, or the PC shuts off completely under load instead of showing a stop code (which can also mean a power or heat problem).
On a desktop, a failed card can be swapped. On most laptops the graphics chip is soldered to the motherboard, so the fix is a motherboard repair or replacement; check whether the laptop is still under warranty before paying for one. Until then, setting apps to Power saving may keep a hybrid laptop usable on its integrated chip.
Driver installs, rollbacks, app settings and dock updates are all remote work. If you’d rather not do it yourself, this is a typical $59 remote fix as long as the PC stays up long enough to connect; a failing card or motherboard still needs hands-on repair. Here’s how our remote support works, including that every session needs your approval and you can end it at any time.
Common questions
What does TDR mean in VIDEO_TDR_FAILURE?
TDR stands for Timeout Detection and Recovery. It’s the Windows feature that notices when the graphics processor has stopped making progress and resets the graphics driver instead of leaving the screen frozen. Most of the time it works and you only see a brief black flash. VIDEO_TDR_FAILURE means a recovery attempt failed or too many happened in a short time, so Windows stopped the system.
Is VIDEO_TDR_FAILURE caused by hardware or software?
Usually software first: an outdated, mismatched or damaged graphics driver is the most common cause, especially right after an update. Hardware becomes likely when a clean install of a known-good driver doesn’t help, when the crash comes under heavy load with high temperatures, or when you see on-screen corruption. Overclocks and weak power supplies sit in between, which is why default clocks are an early test.
Can a power supply cause video TDR failure?
Yes. Microsoft lists insufficient power among the causes of 0x116. Suspect it when the crashes began after a graphics card upgrade, when they come at sudden jumps in load, such as a game loading or a scene changing, or when the PC sometimes shuts off completely instead of showing a stop code. Capping the frame rate or lowering graphics settings cuts the card’s power draw; if that stops the crashes and temperatures were normal, have the power supply checked.
Why does nvlddmkm.sys only crash when I play games?
Games keep the graphics chip near its limits for long periods, so heat, power delivery and clock stability matter far more than at the desktop. A driver bug in a particular game engine is also possible. Update the game and driver, return to default clocks, watch GPU temperature during play and check the game’s own graphics settings. If it still crashes at stock settings, test the card in another PC.
Should I worry about "Display driver stopped responding and has recovered"?
Once in a while, no: Windows did its job and you lost a second or two. If it happens daily, or several times in one session, treat it as an early warning. A recovery that fails, or six within a minute, is what produces VIDEO_TDR_FAILURE, and frequent warnings make that more likely, so update or reinstall the graphics driver and check temperatures before the warning becomes a crash.
Can a web browser cause VIDEO_TDR_FAILURE?
It can be the trigger. Browsers send video decoding and page drawing to the graphics chip, so a buggy driver may hang during streaming or video calls. Update the browser and the driver first, then test with the browser’s graphics acceleration turned off. If that stops the crashes, keep it off until a newer driver arrives, then turn it back on, since acceleration saves processor time and battery.
Should I use DDU (Display Driver Uninstaller) to fix VIDEO_TDR_FAILURE?
Only if the vendor’s own clean-install option hasn’t helped. Display Driver Uninstaller is a free third-party tool, not made by NVIDIA, AMD or Intel, and its developer describes it as meant for cases where a standard uninstall fails; Intel also suggests it as a fallback. If you use it, create a restore point, run it in Safe Mode with your BitLocker recovery key at hand, and stay offline until the new driver is installed so Windows Update can’t install its own first.
