Why Your Game Keeps Crashing After a GPU Driver Update
Game crashing with DXGI_ERROR_DEVICE_HUNG after a GPU driver update? Most likely a timeout from the driver resetting itself. I'll show you the real fixes.
1. The Most Common Cause: TDR Timeout After a Driver Glitch
You just updated your GPU driver — maybe to the latest NVIDIA 572.16 or AMD Adrenalin 24.12.1. Now your game crashes within 10 minutes with DXGI_ERROR_DEVICE_HUNG. I know this error is infuriating because the game ran fine before the update.
Here's what's happening: The driver reset itself. Windows has a built-in watchdog called TDR (Timeout, Detection, and Recovery). When the GPU takes longer than 2 seconds to respond to a command (like a complex shader compilation or a sudden frame spike), Windows thinks the GPU hung and resets the driver. Your game gets the error and crashes.
The fix? Increase the TDR delay. This doesn't solve the root driver issue, but it lets the GPU finish its work without being killed. Here's how.
Set a Custom TDR Delay via Registry
- Press Win + R, type
regedit, hit Enter. Accept the UAC prompt. - Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers - Right-click in the right pane, select New > DWORD (32-bit) Value.
- Name it
TdrDelay. Set the value to10(decimal). That's 10 seconds instead of 2. - Optional but helpful: Create another DWORD named
TdrDdiDelayand set it to10as well. - Restart your PC.
Don't set this above 30 seconds — you risk masking a genuine hardware issue. Also, some games with anti-cheat (like Valorant or Fortnite) may flag registry edits. If so, revert after testing.
If the crashing stops, the problem was a borderline timeout. But this is a band-aid, not a cure. Let's find the real cause.
2. The Second Cause: Corrupted Shader Cache from the Old Driver
Game engines like Unreal Engine 5 and Unity compile shaders the first time you run a scene. After a driver update, the old shader cache is stale. The GPU tries to use it, fails, and you get a crash. I've seen this hit hard in Cyberpunk 2077 and Call of Duty: Black Ops 6 after driver updates.
Clear the Shader Cache
- For NVIDIA GPUs: Open NVIDIA Control Panel > Manage 3D Settings > Shader Cache Size — set to Off. Apply. Then set it back to Driver Default. This forces a rebuild.
- For AMD GPUs: Open AMD Software: Adrenalin Edition > Gaming > Graphics > toggle Shader Cache to Disabled. Apply, then re-enable it.
- Manual cleanup (works for both): Delete these folders after closing all games:
C:\Users\[YourUsername]\AppData\Local\NVIDIA\DXCache C:\Users\[YourUsername]\AppData\LocalLow\NVIDIA\PerDriverVersion\DXCache C:\Users\[YourUsername]\AppData\Local\AMD\DxCache - Also clear the game's own shader cache: look for a folder named
ShaderCacheorShadersin the game's installation directory (e.g.,Steam\steamapps\common\GameName\). - Restart the game. It will rebuild the cache — the first load may be longer, but crashes should stop.
Skip this if you're running a game that's not GPU-bound (like 2D indie titles) — they rarely need shader caches.
3. The Third Cause: A Dirty Driver Install (Overlapping Old Files)
When you update drivers through GeForce Experience or AMD Software, it often installs over the old driver. This leaves behind registry entries and DLLs that conflict. The result: unstable GPU behavior. I've diagnosed this on Windows 10 22H2 and Windows 11 23H2 repeatedly.
Do a Clean Driver Install Using DDU in Safe Mode
- Download DDU (Display Driver Uninstaller) from the official site (Guru3D).
- Reboot into Safe Mode. The easiest way: hold Shift while clicking Restart, then Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 for Safe Mode.
- Run DDU. Select your GPU vendor (NVIDIA or AMD) and click Clean and restart.
- Once back in normal Windows, Windows Update may auto-install a basic driver. Disable internet temporarily if needed.
- Install the latest driver fresh, using Custom (Advanced) install and check Perform a clean installation.
- Reboot again.
I've seen this fix crashes that survived every other attempt. It's your nuclear option — only do it if steps 1 and 2 failed.
Important: If you have an overclock (CPU or GPU), reset to stock before this step. Unstable overclocks can mimic driver crashes.
Quick-Reference Summary Table
| Cause | Symptom | Fix | Time Required |
|---|---|---|---|
| TDR timeout | Crash after 5–10 minutes of gameplay, error code appears | Set TdrDelay registry value to 10 seconds |
10 min |
| Corrupt shader cache | Crash on first load of a new area or after a driver update | Clear shader cache via GPU control panel or delete folders manually | 15 min |
| Dirty driver install | Crash persists even after driver update, random times | DDU clean install in Safe Mode, then install fresh driver | 30 min |
Pro tip: If you're on a laptop with a dual-GPU setup (Intel + NVIDIA), also check that your game is running on the dedicated GPU. Go to Graphics settings in Windows, find the game .exe, and set it to High performance. The wrong GPU can cause TDR crashes too.
One last thing — if none of these work, run a GPU stress test like FurMark for 15 minutes. If it crashes there too, you're looking at a hardware issue — maybe a failing PSU or a GPU that's overheating. But for 9 out of 10 cases, one of the fixes above will get you back in the game.
Was this solution helpful?