Fortnite DirectX 12 & D3D Crashes: The Complete Master Fix Guide (0x887A0005, Device Hung, 0xc0000005, Out of Memory)
๐ฏ Quick Answer
If you just want to get back in the game, do these three things in this exact order. This solves 80% of crashes.
TL;DR: Quick Fixes in Order
If you just want to get back in the game, do these three things in this exact order. This solves 80% of crashes.
- Nuke the Caches: Close everything. Delete
%LOCALAPPDATA%\NVIDIA\DXCache(orAMD\DxCache). Then delete%LOCALAPPDATA%\FortniteGame\Saved\DerivedDataCache,ShaderPipelineCache, andD3DDriverCache. Launch the game and let shaders compile. - Clean Driver Reinstall: Download DDU and the latest GPU driver. Boot to Safe Mode, run DDU, reboot, and install the driver fresh with the "Clean Install" option checked.
- Kill Background Apps: Before launching Fortnite, fully exit Discord, RGB software (iCUE, Armoury Crate), overclocking tools (MSI Afterburner), and browser windows. Launch from a clean system tray.
Error Code Reference Table
Use this to find your specific crash and go straight to the fix.
| Error Code / Message | What You See | Most Likely Cause | Jump to Fix |
|---|---|---|---|
| D3D Device Lost (0x887A0005) | Crash to desktop with "Graphics driver crashed" or "D3D device removed". | Corrupted shader cache, unstable GPU driver, or an unstable GPU overclock/undervolt. | Fix: D3D Device Lost & 0x887A0005 |
| D3D Device Hung | Game freezes, screen may go black, then crash. Often with "GPU crashed" message. | Windows Update driver conflicting with your manual driver install, or a true GPU instability. | Fix: D3D Device Hung |
| DX12 Out of Memory (Intel i9/i7) | "Out of video memory trying to allocate a rendering resource" on a high-end GPU (e.g., RTX 4090). | CPU instability on 13th/14th Gen Intel CPUs, not a GPU VRAM issue. Misleading error. | Fix: DX12 Out of Memory (Intel i9) |
| 0xc0000005 Access Violation | Game crashes on launch, often at the Easy Anti-Cheat screen. No error, or a generic crash reporter. | Kernel-level software conflict (RGB, monitoring apps) with Easy Anti-Cheat, or corrupted system files. | Fix: 0xc0000005 Access Violation |
| Post-Update DX12 Crash | Game was stable, then crashes after a Fortnite or driver update. Usually mid-match. | Update corrupted the shader cache or introduced a driver/game version mismatch. | Fix: Post-Update DX12 Crashes |
| Anti-Cheat Driver Conflict | Crashes with Kernel Event Tracing errors (like 0xC0000022) in Event Viewer. Stable on DX11. | Newer Nvidia drivers (566.xx+) conflicting with Easy Anti-Cheat's kernel access. | Fix: Anti-Cheat Driver Conflicts |
The Root Causes (Why This Keeps Happening)
All these errors boil down to a few core failures between your hardware, Windows, and Fortnite's aggressive use of Unreal Engine 5.
- Shader Cache Corruption: Fortnite compiles shaders for your specific GPU. If this cache gets corrupted (common after updates), DX12 tries to use bad data and crashes.
- Driver Layer Conflict: Having multiple GPU driver versions (one from Windows Update, one from NVIDIA) causes DirectX to lose the device. Easy Anti-Cheat's deep system access makes this worse.
- Kernel-Level Software War: RGB controllers, fan apps, and overclocking tools run at the same privilege level as anti-cheat. They fight over access, causing violations (
0xc0000005). - CPU Instability Misreported as GPU Error: Intel's 13th/14th Gen CPUs can have microsecond-level voltage drops under burst loads (like texture decompression). The game engine mistakes this hardware fault for a GPU memory error.
- Virtual Memory (Page File) Exhaustion: DX12 can aggressively allocate memory. If your page file is disabled or on a slow drive, you can hit a hard memory limit and crash, even with plenty of RAM.
The Universal Fixes (Do These First)
These steps apply to almost every error variant. Start here.
1. Clean GPU Driver Reinstall with DDU
When this applies: ANY D3D or DX12 crash, especially after a driver update. This is your foundation.
Steps:
- Download the latest driver from NVIDIA or AMD but do not run it yet.
- Download Display Driver Uninstaller (DDU) from Guru3D.
- Boot into Windows Safe Mode with Networking (Hold Shift, click Restart > Troubleshoot > Advanced Options > Startup Settings > Restart > Press 5).
- Run DDU. Select your GPU brand (NVIDIA/AMD/Intel) and click "Clean and restart."
- After the reboot, install the driver you downloaded. During the NVIDIA installer, select "Custom (Advanced)" and check "Perform a clean installation." For AMD, use the "Factory Reset" option in Adrenalin.
What to expect: This removes all conflicting driver remnants. Your resolution will flicker during install. After, configure your control panel settings fresh.
2. Delete All Shader & Game Caches
When this applies: Crashes mid-match, during intense effects, or after any game update.
Steps:
- Close the Epic Games Launcher completely (right-click its tray icon > Exit).
- Open File Explorer and paste this into the address bar:
%LOCALAPPDATA% - Delete the
DXCachefolder inside theNVIDIAorAMDfolder. - In the same
%LOCALAPPDATA%folder, openFortniteGame\Saved. - Delete these three folders:
DerivedDataCache,ShaderPipelineCache, andD3DDriverCache. - Launch Fortnite. You must wait for the "Compiling Shaders..." progress bar to reach 100% before joining a match.
What to expect: First launch will be slow. Stuttering may occur in the first match as shaders compile on-the-fly. Subsequent games will be smooth and stable.
3. Disable Overlays & Background Apps
When this applies: Random crashes on launch or in menus, especially 0xc0000005.
Steps:
- Discord: Settings > Overlay > Disable "Enable in-game overlay".
- Xbox Game Bar: Windows Settings > Gaming > Xbox Game Bar > Turn it Off.
- Epic Games Launcher: Settings > Scroll down > Uncheck "Enable Overlay".
- NVIDIA/AMD Overlay: Disable in GeForce Experience or Adrenalin software.
- System Tray: Before launching Fortnite, right-click and exit any of these: RGB software (Corsair iCUE, ASUS Armoury Crate, NZXT CAM), monitoring tools (MSI Afterburner, HWInfo), and chat apps like Discord or Steam.
What to expect: Eliminates hook conflicts. Launch the game from a clean desktop.
Solutions by Specific Error
D3D Device Lost (0x887A0005)
The Fix: This is usually a stability issue. After performing the Universal Fixes above:
- Remove GPU Overclocks/Undervolts: Reset all settings in MSI Afterburner or your BIOS to default. This includes any "OC Scanner" or factory overclocks.
- Force DX11 as a Test: In the Epic Games Launcher Settings > Fortnite, add the command line argument
-d3d11. If this stops the crashes, your DX12 implementation is unstable (likely driver-related). Use this while you troubleshoot. - Adjust Windows Power Settings: Open Windows Control Panel > Hardware and Sound > Power Options. Select "High Performance" or "Ultimate Performance" (if hidden). This prevents power-saving from affecting the GPU.
- Cap Your FPS: In Fortnite settings, cap your FPS to 3-5 frames below your monitor's refresh rate (e.g., 141 FPS for a 144Hz monitor). This reduces extreme load spikes.
D3D Device Hung
The Fix: This is almost always a driver conflict. The Universal Fix #1 (DDU) is critical here.
- Block Windows Driver Updates: After using DDU, prevent Windows from overwriting your driver.
- Press
Win + R, typegpedit.msc(Pro editions) or use the registry method: Win + R, typeregedit, navigate toHKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate.- Create a new DWORD (32-bit) named
ExcludeWUDriversInQualityUpdateand set its value to1.
- Lower In-Game Settings: Temporarily set Textures and View Distance to Medium. This reduces the command buffer load on the GPU, which can trigger a hang if the driver is borderline.
DX12 Out of Memory on Intel i9/i7
The Fix: This is a CPU power/voltage issue. Your GPU is fine.
- Update Your Motherboard BIOS. Go to your manufacturer's website (ASUS, Gigabyte, MSI, etc.) and get the latest BIOS. This often includes crucial microcode updates for CPU stability.
- Apply CPU Power Limits with Intel XTU:
- Download and install Intel Extreme Tuning Utility (XTU).
- Launch it and go to the Advanced Tuning tab.
- Set the following:
- Turbo Boost Short Power Max (PL2):
285W - Turbo Boost Power Max (PL1):
275W - Processor Core IccMax:
350A - Click "Apply". Test Fortnite. If stable, you can use XTU to make these settings apply at boot, but the permanent fix is to set these same values in your motherboard BIOS under CPU Power Management.
- Disable CPU Enhancement Settings in BIOS: Look for settings like "Multi-Core Enhancement (MCE)" or "ASUS Performance Enhancement" and set it to Disabled. This forces the CPU to follow Intel's stock specifications.
0xc0000005 Access Violation
The Fix: This is a software conflict, often with anti-cheat.
- Perform a Clean Boot: This isolates the conflicting software.
- Press
Win + R, typemsconfig, go to the Services tab. - Check "Hide all Microsoft services", then click "Disable all".
- Go to the Startup tab, click "Open Task Manager", and disable every startup item.
- Click OK and restart. Try launching Fortnite. If it works, re-enable services/startup items in batches to find the culprit.
- Repair Easy Anti-Cheat:
- Navigate to
C:\Program Files (x86)\EasyAntiCheat. - Run
EasyAntiCheat_Setup.exe. - Select Fortnite from the list and click "Repair Service".
- Run System File Checker: Open Command Prompt as Administrator and run:
sfc /scannow. Let it repair any corrupted Windows system files.
Post-Update DX12 Crashes
The Fix: The update left behind incompatible data.
- Roll Back Your GPU Driver: If the crash started after a driver update, use DDU to revert to the previous version you know was stable. For Nvidia, version 561.09 is a known stable point for many.
- Verify Game Files: In the Epic Launcher, go to Library > click the three dots under Fortnite > Verify. This checks for corrupted or updated game files.
- Reset Game Config Files: After deleting the caches (Universal Fix #2), also delete
%LOCALAPPDATA%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini. The game will generate a fresh one with default settings. Reconfigure your graphics settings manually.
Anti-Cheat Driver Conflicts
The Fix: Specific newer Nvidia drivers clash with EAC.
- Roll Back to Nvidia Driver 561.09: Follow the DDU process (Universal Fix #1) but install version 561.09 specifically, available on NVIDIA's driver archive. This version lacks the kernel changes that conflict with EAC.
- Disable Kernel-Mode Hardware Enforced Stack Protection: This Windows security feature can sometimes interfere.
- Go to Windows Security > Device Security > Core Isolation Details.
- Turn "Kernel-mode Hardware-enforced Stack Protection" to Off. Reboot.
- (Note: Only do this if you're certain the driver rollback isn't enough, as it lowers a security setting).
Platform-Specific Notes
NVIDIA Users: The "Clean Install" checkbox in the driver installer is not enough. You must use DDU from Safe Mode. GeForce Experience is optional and can be uninstalled if you suspect it's causing issues.
AMD Users: The "Factory Reset" option in the AMD Adrenalin installer is effective, but DDU is still more thorough for persistent crashes. Ensure "Surface Format Optimization" is Off in the Graphics settings tab.
Intel 13th/14th Gen CPU Users: The "Out of Memory" error is your primary target. BIOS update and power limiting are non-negotiable fixes. Contact your motherboard manufacturer if you need help with BIOS settings.
Diagnostic Flowchart Table
Run through these checks to pinpoint your issue.
| Symptom | Immediate Check | Result & Action |
|---|---|---|
| Crash on Launch | Open Task Manager. Are iCUE, Afterburner, or other hardware apps running? | YES: Fully close them all and try again. NO: Proceed to verify game files and repair EAC. |
| Crash Mid-Match | Check %LOCALAPPDATA%\FortniteGame\Saved folder size. | >5GB: Delete shader caches (Universal Fix #2). <3GB: Likely a driver or GPU stability issue. |
| "Out of Video Memory" on high-end GPU | Check your CPU model in System Information. | 13th/14th Gen Intel i7/i9: Apply CPU power limits immediately. Any other CPU: Check GPU VRAM usage with monitoring software; lower texture settings. |
| Crash after Driver Update | Check installed driver version vs. known stable version. | Newer than 561.09 (Nvidia): Roll back driver using DDU. Older driver: Update using DDU clean install. |
| Game Freezes then Crashes | Check Windows Event Viewer for "Display" or "nvlddmkm" errors. | Error found: This confirms a D3D Device Hung/Lost. Perform the Universal Fix #1 (DDU) and block Windows driver updates. |
What NOT to Do
- Do NOT just reinstall Fortnite through the Epic Launcher without deleting the
Savedfolder first. It leaves corrupted files behind. - Do NOT use "Driver Booster" or automatic driver update utilities. Get drivers directly from NVIDIA, AMD, or your motherboard manufacturer.
- Do NOT disable your page file (virtual memory) no matter how much RAM you have. Set it to "System managed" on your fastest SSD.
- Do NOT blindly increase GPU voltage or power limits if you're crashing. First, reset to complete stock settings.
- Do NOT skip the shader compilation wait on first launch after clearing the cache. This guarantees stutters and potential crashes.
FAQ
Q: I did all the Universal Fixes and still crash. What's next?
A: Isolate the issue. Run a memory test (Windows Memory Diagnostic). Test another graphically intensive game. If it's only Fortnite, your last resort is a clean Windows install, but that's rare.
Q: Is DirectX 11 or Performance Mode more stable?
A: Yes, absolutely. DX11 and Performance Mode use simpler rendering paths and are less prone to these low-level driver crashes. Use them if stability is your only goal, but you lose DX12-specific features like Nanite and Lumen.
Q: How do I know if my shader cache is actually corrupted?
A: The size is a clue, but the definitive test is to delete it (Universal Fix #2). If the crashes stop or the first-game stuttering is severe, it was corrupted.
Q: Will limiting FPS really help prevent crashes?
A: Yes. An uncapped FPS can cause your GPU to spike to 100% utilization with extremely high frame rates in menus or simple scenes, creating temperature and power transients that can trigger instability. A reasonable cap smooths this out.
Q: My crash doesn't match any error code here.
A: Check the Windows Event Viewer. Press Win + R, type eventvwr.msc, go to Windows Logs > Application or System. Look for errors at the time of the crash. The source (e.g., "Application Error," "Display") and error code there will give you the real clue.