Game Won't Launch After Driver Update: Fix 0xc0000005

That 0xc0000005 crash after a GPU driver update usually means mismatched DirectX or a corrupted shader cache. Here's the actual fix, not a reinstall-everything wild goose chase.

Quick answer: Clear the shader cache, reinstall the DirectX runtime your game actually needs, and if that fails, DDU the driver and go back one version — not the whole OS.

I know this one is infuriating. You update your GPU driver, reboot, and now every game that worked fine yesterday throws a 0xc0000005 access violation the moment the loading screen appears. Sometimes it's a black screen. Sometimes it's a crash to desktop with no error at all. Either way, the timing is the tell: it started right after the driver update, so the driver is the suspect.

Here's why it happens. Modern game launchers (Epic, Steam, Battle.net) keep a compiled shader cache keyed to your exact driver version. When you update the driver, that cache is invalid. The game tries to load a shader blob compiled for the old driver, gets garbage back, and the CPU trips an access violation trying to read it. On top of that, some driver packages install a newer DirectX runtime than the game was built against, and older DX11 titles especially can't handle the mismatch. It's not a corrupted install. It's a version conflict, and it's almost always fixable in ten minutes.

Fix 1: Wipe the shader cache

Close your game and the launcher completely. Check Task Manager for a leftover game.exe and end it.
Open File Explorer and paste this into the address bar:
```
%LOCALAPPDATA%
```
Find the folder matching your game or GPU vendor. For Nvidia, delete the NVIDIA\DXCache folder. For AMD, delete AMD\DxCache. For the game itself, look under \\Saved\ or \\Cache\ and remove anything named ShaderCache or PipelineCache.
Reboot. Not shutdown-and-fast-startup — an actual restart.

This clears 60–70% of post-driver-update crashes on its own. If it doesn't, keep going.

Fix 2: Reinstall the DirectX runtime

Every install of Windows 10 and 11 ships with a partial DirectX 9 and 11 runtime. Games that need the June 2010 redistribute will silently fail if that package was never installed — and no, updating Windows doesn't always add it. Grab the official dxwebsetup.exe from Microsoft's download page and run it. It takes two minutes and it's tiny.

If the game uses DirectX 12, you don't install that separately — it comes with the GPU driver. So the fix there is Fix 3.

Fix 3: DDU and roll back one driver version

This is the one that actually works when the first two don't. The brand new driver you just installed has a bug that your specific GPU or game hits. It happens more than people admit — Nvidia's 545.xx line broke several DX9 titles, and AMD's Adrenalin 24.3.1 caused stuttering crashes in a handful of older engines. Don't fight it, roll back.

Download DDU (Display Driver Uninstaller) from Guru3D.
Boot into Safe Mode. This matters — DDU can't fully wipe the driver from a normal session.
Run DDU, select your GPU vendor, and choose Clean and restart.
Grab the previous driver version from Nvidia's or AMD's archive page. For Nvidia, you can install via GeForce Experience by picking the older Studio Driver build. For AMD, use the manual download.

Skip the gaming vendor's auto-updater when you do this. Install manually, decline the optional components, and keep the shader cache intact this time.

If none of that works

Verify game files. Steam: right-click the game → Properties → Installed Files → Verify integrity. Epic: Library → three dots → Verify. This catches a partially downloaded .dll that got mangled when the driver installer tried to hook it.
Disable overlays. Discord, Steam, GeForce Experience, and Xbox Game Bar all inject into the render pipeline. Turn every one of them off and test. Overlays are the single most common cause of dxgi_error_device_removed on otherwise healthy systems.
Check Windows Update for a DX runtime update. Occasionally the OS ships a DirectX patch that conflicts with a fresh driver. If you see one pending, install it and reboot — the two usually reconcile.
Run the game as admin once. Right-click the .exe → Run as administrator. If it launches, you've got a permissions issue with the launcher, not the driver.

If the game worked on driver version X and broke on X+1, the problem is X+1. Don't waste a weekend reinstalling Windows. Go back to X.

Prevention: stop updating drivers on patch day

GPU driver updates are not security patches. There's no urgency. When Nvidia or AMD drops a new one, wait a week. Let the early adopters find the 0xc0000005 crashes, then decide whether the new driver actually helps you. If you're not chasing a specific game's day-one performance fix, you don't need it. Pin your current working driver, hide driver updates in Windows Update, and only move when there's a reason.

One more thing — take a System Restore point before every driver update. It saves you from exactly this situation, and it costs ten seconds.