Nothing's worse than a game crashing to desktop with a cryptic 0xc0000005 error right as you're about to win. Let's fix it.
The Fix
You'll need to do a few things in order. Don't skip steps — each one catches a different cause. I've seen people waste hours reinstalling Windows when a 30-second driver rollback did the trick.
1. Clean your GPU drivers (not just update)
A plain driver update often leaves old files behind. The 0xc0000005 error is frequently a corrupted shader cache or leftover driver DLL loading into memory it shouldn't. Use DDU to wipe clean.
- Download Display Driver Uninstaller (DDU) from Guru3D.
- Boot into Safe Mode (hold Shift while clicking Restart).
- Run DDU, select your GPU vendor, and click Clean and restart.
- Install the latest driver from NVIDIA, AMD, or Intel directly. Don't use Windows Update.
2. Repair DirectX and Visual C++ runtimes
Most modern games need DirectX 9, 11, or 12 and a handful of Visual C++ runtimes. If any are missing or broken, you'll get an access violation. Run the DirectX web installer and grab the latest Visual C++ Redistributable AIO pack from GitHub (abbodi1406's repo). Install every version from 2005 to 2022, both x86 and x64. Yes, even the old ones — plenty of games still link against them.
3. Verify game files
Steam: right-click game → Properties → Installed Files → Verify integrity of game files. Epic: click the three dots → Manage → Verify. A single corrupted DLL or asset can trigger the crash.
4. Check RAM with MemTest86
Bad RAM is the sneaky cause. If your sticks throw errors, games crash with 0xc0000005 constantly. Burn MemTest86 to a USB, boot from it, and run at least one full pass (two is better). Any error = replace the stick.
5. Disable overclocks
That XMP profile or GPU overclock might be stable in benchmarks but not in games. Reset BIOS to defaults and remove any GPU overclock via MSI Afterburner. Test the game. If it stops crashing, your OC was the problem.
Why This Works
Error 0xc0000005 means access violation — a program tried to read or write memory it doesn't own. In games, that's usually because:
- A driver (usually GPU) handed back a bad pointer or corrupted memory.
- A required DLL (DirectX, VC++ runtime) is the wrong version or missing.
- Physical RAM is faulty, so data gets corrupted in transit.
- An overclock pushed the memory controller past stability.
Cleaning drivers removes bad DLLs. Reinstalling runtimes gives games the exact libraries they expect. Memory tests catch hardware faults. Killing overclocks restores stock stability. Each step targets a real, common culprit.
Pro tip: If you're on Windows 11 24H2 and seeing 0xc0000005 in older games, check for a game-specific patch. Some titles need a compatibility shim because of kernel changes.
Less Common Variations
Antivirus interference
Third-party AVs like Avast or Bitdefender sometimes inject hooks into game processes. That can cause an access violation. Temporarily disable real-time protection and test. If it fixes it, add the game folder to exclusions.
Corrupt Windows system files
Run these in an admin Command Prompt:
sfc /scannow
dism /online /cleanup-image /restorehealthThen reboot. It's rare but I've seen a busted ntdll.dll cause 0xc0000005 across multiple games.
Specific game engine quirks
Unreal Engine 4 titles sometimes crash with this code if Engine.ini has a bad setting. Delete %LOCALAPPDATA%\YourGame\Saved\Config\WindowsNoEditor\Engine.ini and let the game rebuild it.
Laptop hybrid graphics
On laptops with Intel + NVIDIA, the game might try to use the wrong GPU. Force it in NVIDIA Control Panel → Manage 3D settings → Program Settings → select the game → set to High-performance NVIDIA processor.
Prevention
- Don't install GPU drivers via Windows Update. Always grab them from the vendor.
- Keep Visual C++ runtimes updated — they're tiny and prevent tons of crashes.
- Test any overclock with OCCT or Prime95 for at least an hour before gaming.
- Run MemTest86 once a year if you push your RAM hard.
- Create a restore point before big driver updates. Saves your butt when a new driver breaks everything.
That's it. Nine times out of ten, the DDU + runtime reinstall combo kills 0xc0000005 dead. If it doesn't, MemTest86 will tell you why.