VIDEO_TDR_FAILURE after a Windows 11 update is one of the clearest cause-and-effect blue screens in Windows: the update changed something in the graphics stack, the GPU driver started hanging, Windows’ timeout watchdog fired, and the recovery failed. The screen usually names the driver — nvlddmkm.sys for NVIDIA, amdkmdag.sys for AMD, igdkmd64.sys for Intel — which is both the diagnosis and the to-do list.
Because the trigger was an update, the fix path has two prongs: repair the driver situation the update created, and deal with the update itself if needed. Work both prongs in the order below.
Why this happens
- Windows Update installed a bad or mismatched graphics driver over your working one.
- The update changed GPU power management behavior that the old driver depended on.
- Stricter TDR timeout enforcement in the new build exposing a driver that was already marginal.
- Corrupted driver files from the update process itself.
- Conflicting integrated + discrete GPU drivers after the update touched only one of them.
- Overheating or dust — the update is coincidental, and the GPU was already on the edge.
How to fix it
Work through these in order, from quickest to most involved.
Fix 1: Confirm the driver and the update timeline
Establish the link before treating it.
- Open Settings → Windows Update → Update history and note the date of the latest update versus when crashes began.
- Install WinDbg Preview, open the latest dump in
C:\Windows\Minidump, run!analyze -v, and confirm the named driver is graphics-related. - In Device Manager, check the display adapter’s Driver tab for the driver date — a date matching the update confirms Windows Update replaced it.
- If the timeline doesn’t match any update, suspect thermals or hardware instead and jump to Fix 6.
Fix 2: Clean-reinstall the graphics driver (DDU method)
The core fix — remove what the update installed, install what works.
- Download the last known-good driver version (or the latest stable) from NVIDIA , AMD , or Intel .
- Boot into Safe Mode , run Display Driver Uninstaller (DDU), and wipe the graphics driver completely.
- Restart normally and install the downloaded driver. Choose Custom → Clean installation in the NVIDIA/AMD installer for good measure.
- Test with the workload that crashed — if it’s stable for several days, the driver was the whole story.
Fix 3: Roll back or pause the Windows update
If the driver is fine but the update’s other changes broke TDR behavior, address the update.
- Go to Settings → Windows Update → Update history → Uninstall updates and remove the most recent cumulative update.
- Restart and test for a few days. Stable? The update was the trigger.
- Pause updates for 2–3 weeks to avoid immediate reinstallation while Microsoft ships fixes.
- Before unpausing, update the GPU driver to the newest stable — the combination of fixed update + fresh driver usually holds.
Fix 4: Stop Windows Update from replacing your driver
Windows Update will happily reinstall the bad driver the moment you look away.
- After your clean driver install, open System Properties (
sysdm.cpl) → Hardware → Device Installation Settings → No. - In Settings → Windows Update → Advanced options → Optional updates, uncheck any offered graphics drivers.
- Note your working driver version (Device Manager → display adapter → Driver tab) so you can spot silent replacements.
- Re-enable driver updates after a month or two — permanent blocks leave security-relevant driver fixes undelivered.
Driver-update fights like this are also behind many driver power state failures — same prevention steps apply.
Fix 5: Adjust TDR behavior (targeted workaround)
When the driver is the best available but still trips timeouts, give the GPU more slack.
- Press Win + R, type
regedit, and navigate toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. - Create a DWORD (32-bit) named TdrDelay and set it to 8 (seconds, up from the default 2).
- Optionally create TdrDdiDelay set to 10 as well.
- Restart and test. If crashes stop, the GPU was just slow to respond, not broken — but keep this as a workaround while watching for a better driver, and document the change.
Fix 6: Rule out heat and hardware
Updates make convenient scapegoats; verify the GPU is actually healthy.
- Monitor GPU temperatures under load — sustained temps above 85–90°C on a laptop GPU invite TDR timeouts.
- Clean vents with compressed air and ensure the laptop sits on a hard surface during heavy use.
- Run a GPU stress test (FurMark, 20 minutes) on the clean driver — artifacts or crashes here suggest hardware, not the update.
- If TDR failures happen in Safe Mode or on the basic display driver, that’s a hardware red flag — software TDR issues don’t occur without the real driver loaded.
Fix 7: Repair system files and the update components
A damaged update can leave the graphics stack half-migrated.
- In Terminal (Admin), run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealth. - Reset Windows Update components:
net stop wuauserv→net stop bits→ren C:\Windows\SoftwareDistribution SoftwareDistribution.old→net start wuauserv→net start bits - Reinstall the latest cumulative update fresh from Settings → Windows Update.
- Re-verify your graphics driver version afterward — updates love to “help” with drivers.
Fix 8: In-place repair install for a corrupted graphics stack
When clean drivers and update surgery both fail, refresh the OS layer.
- Back up your files.
- Run setup from official Windows 11 media inside Windows, keeping files and apps.
- Install the known-good GPU driver before Windows Update runs.
- Block driver replacement (Fix 4) until you’ve confirmed a week of stability.
Closing
VIDEO_TDR_FAILURE after an update is Windows telling you exactly what happened: the update disturbed the graphics driver, the driver hung, the watchdog fired. Clean out the driver with DDU, handle the update (roll back or update past it), and stop Windows from reinstalling the bad driver behind your back. It’s a software problem with a software fix — no new GPU required. And next time an update lands, check the GPU driver version afterward; thirty seconds of verification beats a week of blue screens.
