You're 40 minutes into a raid, the screen freezes black for two seconds, then drops to desktop with "Display driver stopped responding and has successfully recovered" or a blue screen tagged 0x00000116. I know this error is infuriating — especially when the game was running fine last week. It's almost never the game's fault. It's your GPU driver, Windows' timeout watchdog, or power delivery.
Work through these in order. Each one kills a specific failure mode. Skipping ahead wastes time.
Cause 1: Windows TDR timeout is too aggressive (and your driver is too slow to respond)
This is the single most common cause of "display driver stopped responding" in 2024-2026 builds. Windows runs a watchdog called TDR (Timeout Detection and Recovery). If your GPU doesn't respond to the OS within 2 seconds by default, Windows resets the driver. On modern cards running heavy shader compilation, ray tracing, or a memory-heavy game like Cyberpunk 2077 with Path Tracing on, 2 seconds isn't enough. The driver gets killed mid-operation.
The tell: it happens during scene transitions, loading a new area, or the first few minutes of a session. Not random — contextual.
Bump the TDR delay. This is a registry change, so back up first.
reg add "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v TdrDelay /t REG_DWORD /d 10 /f
reg add "HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" /v TdrDdiDelay /t REG_DWORD /d 20 /fReboot after. This sets the timeout to 10 seconds instead of 2. If crashes stop, that was it. If it still crashes, the driver isn't just slow — it's actually broken, and you need Cause 2.
Don't go crazy with TdrDelay values like 60. If a driver is genuinely hung, a long timeout just means a longer freeze before the eventual crash. 8-10 seconds is the sweet spot.
Cause 2: A corrupted driver install from an upgrade
Second most common. You updated from one driver version to another — or worse, went from AMD to NVIDIA or vice versa — and leftovers from the old install are fighting the new one. Windows' own "Uninstall device" leaves DLLs, registry entries, and services behind. NVIDIA's update installer sometimes does too, especially if it crashed partway through.
The real fix is a full clean with DDU (Display Driver Uninstaller). Not Device Manager. Not the vendor's "clean install" checkbox, though that's a distant second. DDU.
- Download DDU from Wagnardsoft's official site. Grab the latest version.
- Download the new driver package from NVIDIA, AMD, or Intel first so you're not stuck without a driver after the wipe.
- Boot into Safe Mode. Search "Advanced startup" in Settings, or run
msconfigand check Safe Boot. DDU works in normal mode but Safe Mode is cleaner. - Run DDU, select your GPU vendor, click Clean and restart.
- Install the driver you downloaded. Choose Custom, not Express, and uncheck GeForce Experience or Adrenalin extras if you don't use them.
Do not install a driver older than 6 months unless you've got a specific reason. Old NVIDIA drivers before 552.xx have known TDR issues with DirectX 12 games on Ada Lovelace cards. Old AMD drivers before 24.5.1 have similar problems with RDNA 3.
Also: skip "beta" and "optional" drivers unless the release notes specifically mention a game you're playing. They're for enthusiasts, not for people who want their games to work.
Cause 3: Power delivery failing under game load
Third cause, and it's the one people refuse to check because it might mean buying a part. If your GPU driver crashes only under gaming load — never at idle, never in a browser — and the TDR bump from Cause 1 doesn't help, you've got a power problem.
Specifically: transient power spikes. A 30-series or 40-series NVIDIA card can spike 2x its rated wattage for a few milliseconds. If your PSU can't handle the spike, the GPU dips on the 12V rail and the driver crashes. You'll often see Event ID 4101 in the Event Viewer or a crash in nvlddmkm.sys or amdkmdag.sys right before the reset.
Check these, in order:
- PSU wattage vs GPU requirement. An RTX 4070 Ti needs a 700W PSU minimum from a reputable brand. A 3080 needs 750W. A 3090 needs 850W. If you're running a 600W no-name PSU with a 3080, that's your crash.
- PCIe power cables. Use separate cables from the PSU to the GPU. Not one cable with a daisy-chained split. The split connector can't carry the transient load. This is a 60-second change that fixes a shocking number of crashes.
- Aging PSU. Capacitors degrade. A 5-year-old 650W is really a 500W in disguise. If the crashes started this year and nothing else changed, suspect the PSU.
- PCIe slot power. Reseat the GPU firmly. If you're using a riser cable, check it supports PCIe 4.0. A 3.0 riser on a 4.0 card causes intermittent crashes that look exactly like driver failures.
You can verify with HWiNFO64 — watch the +12V rail under load. If it dips below 11.4V, you've found it.
Other things worth trying (in this order)
- Disable XMP/EXPO in BIOS. Unstable RAM overclocks masquerade as GPU driver crashes constantly. Test with it off for a day. If crashes stop, your memory OC was never stable.
- Roll back a Windows update. Certain Windows 11 24H2 builds shipped with DirectX issues that broke drivers from all three vendors. If crashes started right after a Windows update, that's your culprit.
- Run
sfc /scannowandDISM /Online /Cleanup-Image /RestoreHealth. A corrupted system file in the graphics stack will crash any driver. - Check GPU temps. HWiNFO64, GPU hotspot over 105°C = thermal throttle and crash. Repaste if it's an older card.
Quick reference
| Symptom | Most likely cause | Fix |
|---|---|---|
| Crash during scene load or shader compile | TDR timeout too short | Set TdrDelay to 10 in registry |
| Crash after driver update or GPU swap | Corrupted driver install | DDU + fresh install |
| Crash only under heavy gaming load | PSU / power delivery | Separate PCIe cables, check rail voltage |
| Crash since a BIOS change | Unstable RAM OC | Disable XMP/EXPO |
| Crash started after Windows update | OS-level DirectX regression | Roll back the update |
| Crash on a card over 3 years old, high temps | Thermal throttle | Clean and repaste the GPU |
If you've done all three main causes and it still crashes, check the Event Viewer for the actual BSOD code. 0x00000116 points at the display driver itself. 0x00000124 is a hardware fault — usually CPU or RAM, not GPU. 0x0000003B is often a driver interacting badly with something else, and you'll want to check what you installed right before crashes started.
One more thing — if the crash happens only in one specific game, and every other game runs fine, stop blaming your driver. That's the game's bug, and you'll be waiting on a patch, not a fix.