Elden Ring is built on FromSoftware’s heavily modified branch of Unreal Engine 4, and its startup routine stacks multiple subsystem checks before rendering a single frame: Easy Anti-Cheat handshake, DirectX 11 device initialization, shader pipeline compilation, and configuration file loading. When the game crashes on startup, the failure almost always occurs at one of those chokepoints rather than deep inside the engine itself. That distinction matters because it narrows your diagnostic path considerably. You are not hunting for a corrupted save or a broken mod. You are looking at a launch-sequence failure, and most of them trace back to a handful of well-understood conflicts.
- Likely Causes
- Fix 1: Verify integrity of game files
- Fix 2: Disable overlay software
- Fix 3: Clean reinstall GPU drivers
- Fix 4: Reinstall Easy Anti-Cheat
- Fix 5: Delete shader cache and config files
- Fix 6: Install or repair Visual C++ redistributables and DirectX
- Fix 7: Add exclusion to Windows Defender or antivirus
- Fix 8: Force windowed or borderless launch
- Fix 9: Run as administrator and set compatibility mode
- If Nothing Works
- FAQ
The Shadow of the Erdtree expansion pushed hardware requirements upward, and many players who previously launched without issue now encounter silent exits or Windows “Elden Ring has stopped working” dialogs before the title screen appears. Below is a structured approach ordered from the simplest intervention to the most invasive. No single fix guarantees success because the root cause varies per system, but the sequence below reflects the relative frequency these crashes occur in community reports and support threads.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Corrupted or missing game files | Steam > Library > right-click Elden Ring > Properties > Installed Files > Verify integrity of game files; look for “files failed to validate” output | Low |
| Overlay software conflict (Steam, Discord, MSI Afterburner) | Game launches with overlays disabled but fails with them active; check for DLL injection errors in Windows Event Viewer under Application | Low |
| Outdated or broken GPU driver | DDU shows no clean driver; game crashes with DirectX Device Hung event in Event Viewer | Medium |
| Easy Anti-Cheat service failure | Error string “Failed to initialize Easy Anti-Cheat” or game window never appears; check EAC service in services.msc | Medium |
| Corrupted shader cache or config files | Crash occurs only after a driver update or Windows feature update; deleting %LOCALAPPDATA%\EldenRing resolves it temporarily | Low |
| Missing or outdated Visual C++ / DirectX runtimes | Windows Event Viewer shows “VCRUNTIME140.dll” or “d3dcompiler_47.dll” missing | Medium |
| Antivirus or Windows Defender quarantining EAC binaries | Defender protection history shows a blocked file from the EAC folder; re-enabling the file and whitelisting the folder stops the crash | Medium |
Fix 1: Verify integrity of game files
How to check
Steam may have downloaded a partial update, or a file sync conflict corrupted a single asset. Open Steam, right-click Elden Ring in your Library, select Properties, go to Installed Files, and click “Verify integrity of game files.” Watch the output for any files flagged as invalid.
What to do
If Steam reports failed validations, let it re-download. After verification completes, launch the game immediately without closing Steam first. If the crash persists with a clean verification log, move to the next fix.
How to undo it
Nothing to undo. Verification only replaces files that fail checksum comparison. It is safe to repeat as often as needed.
Fix 2: Disable overlay software
How to check
Steam’s in-game overlay injects a DLL at process start. Discord’s overlay does the same. MSI Afterburner’s RivaTuner Statistics Server attaches to DirectX swapchains. Any of these can race with Elden Ring’s initialization and cause a hard crash before the title screen renders.
What to do
Open Steam > Settings > In-Game and uncheck “Enable the Steam Overlay while in-game.” In Discord, go to Settings > Game Overlay and toggle it off. If you run Afterburner, exit it from the system tray. Launch Elden Ring and observe. If it loads, re-enable overlays one at a time to identify the specific offender.
How to undo it
Re-enable each overlay individually in its respective settings panel after you have isolated the conflict.
Fix 3: Clean reinstall GPU drivers
How to check
Open Device Manager and confirm your GPU reports no yellow triangle. Then check Windows Event Viewer > Windows Logs > System for “Display driver nvlddmkm stopped responding” or equivalent AMD entries. A partial driver update or leftover registry keys from a prior GPU can cause DirectX initialization to fail silently.
What to do
Use Display Driver Uninstaller (DDU) in Safe Mode to strip all GPU driver traces, then install the latest driver from your GPU vendor’s website. For NVIDIA, the Game Ready branch is what FromSoftware typically tests against. After installation, reboot once before launching.
How to undo it
Install a previous driver version if the new one introduces a different regression. DDU makes rolling back straightforward since it clears the slate each time.
Fix 4: Reinstall Easy Anti-Cheat
How to check
Navigate to your Steam install path, then to steamapps\common\EldenRing\EAC\. If the folder is missing, empty, or its files are dated well before the last game update, the EAC installation is broken. You can also check services.msc for “Easy Anti-Cheat” and confirm it can start.
What to do
Right-click EACSetup Installer in that folder and choose Run as administrator. Click Uninstall, wait for it to finish, then click Install. Reboot the system. Launch Elden Ring through Steam normally.
How to undo it
If reinstalling EAC causes a different error, verify game files again. Steam will restore the EAC folder to its expected state.
Fix 5: Delete shader cache and config files
How to check
Navigate to %LOCALAPPDATA%\EldenRing\Saved\ (contains config and save data) and %LOCALAPPDATA%\EldenRing\ (contains shader cache subfolders). If you recently updated drivers or installed a major Windows feature update in 2026, cached shaders compiled against the old driver ABI may cause the render pipeline to abort during initialization.
What to do
Close Steam completely. Rename the EldenRing folder inside %LOCALAPPDATA% to EldenRing_backup. Launch the game; it will regenerate all config and shader files from scratch. First launch may take an additional 60-90 seconds for shader compilation. If the game loads, you can compare your backup EldenRing.ini to the new one and selectively restore display settings.
How to undo it
Delete the newly generated EldenRing folder and rename EldenRing_backup back to EldenRing. Your original configuration and shader cache are restored.
Fix 6: Install or repair Visual C++ redistributables and DirectX
How to check
Open Event Viewer > Windows Logs > Application and look for entries with faulting module names like VCRUNTIME140.dll or d3d11.dll. Alternatively, attempt to launch eldenring.exe directly from the game folder; if Windows shows a “missing DLL” popup rather than a silent crash, the runtime is the culprit.
What to do
From Microsoft’s website, install the latest Visual C++ 2015-2022 Redistributable (both x86 and x64 editions). Then run the DirectX End-User Runtime Web Installer to ensure d3dcompiler_47.dll and related components are present. Reboot and launch.
How to undo it
Use Windows Settings > Apps to uninstall the redistributables if they cause a conflict with another application. This is rare but possible with certain older software that pins a specific CRT version.
Fix 7: Add exclusion to Windows Defender or antivirus
How to check
Open Windows Security > Virus & threat protection > Protection history. Look for recently quarantined items from paths containing “EldenRing” or “EAC.” Third-party antivirus logs are vendor-specific; check their quarantine or event log similarly.
What to do
Restore any quarantined files, then add the entire Steam\steamapps\common\EldenRing folder to your antivirus exclusion list. This prevents real-time scanning from killing the EAC handshake mid-launch.
How to undo it
Remove the folder exclusion and re-enable real-time scanning. Understand that without the exclusion, the crash will likely recur since the scanner is doing exactly what it was configured to do.
Fix 8: Force windowed or borderless launch
How to check
Some monitors or multi-GPU configurations cause DirectX 11 fullscreen mode initialization to hang or crash. If the game window never appears at all (not even a black screen), display mode negotiation is a plausible failure point.
What to do
Open Steam > Library > Elden Ring > right-click > Properties > Launch Options. Type: -windowed -w 1280 -h 720. Launch the game. Once the title screen is visible, navigate to Graphics settings and switch to Borderless Window. After saving, remove the launch options. The game will remember the windowed mode preference in its ini file.
How to undo it
Clear the Launch Options field. If the game now remembers Borderless Window in its config, change it back in-game or edit %APPDATA%\EldenRing\EldenRing.ini and set Fullscreen=1.
Fix 9: Run as administrator and set compatibility mode
How to check
Right-click eldenring.exe in the game folder, select Properties > Compatibility. If “Run this program as an administrator” is unchecked and your user account has restricted write permissions to the game directory or to %LOCALAPPDATA%, EAC or shader writes may silently fail.
What to do
Check “Run this program as an administrator.” Apply and confirm. Also check the Steam shortcut under Properties > Installed Files > Browse and confirm the entire folder is not marked read-only (right-click > Properties > uncheck Read-only, apply to subfolder).
How to undo it
Uncheck the administrator option. If you changed folder permissions, reapply the original ACL via the Security tab in Properties or simply verify files through Steam to reset any permission drift.
If Nothing Works
If you have worked through every fix above and the crash persists, the remaining diagnostic options are narrower. Check whether the game crashes on a different user account on the same PC; if it does not, your profile registry or AppData is corrupted beyond the EldenRing folder alone. Test whether the game launches on a secondary monitor or a different GPU output port, as some display driver versions exhibit device enumeration bugs that affect only the primary output. Finally, consider whether a background application you use daily (RGB software, hardware monitoring, virtual audio cables) injects a global hook. A clean boot in Windows (disable all non-Microsoft services and startup items) isolates this possibility. If the game launches in clean boot state, reintroduce services in halves to find the conflict.
FAQ
Does Elden Ring use DirectX 11 or DirectX 12?
Elden Ring runs exclusively on DirectX 11. There is no DX12 toggle or launch option. The engine is FromSoftware’s proprietary branch of Unreal Engine 4.24-era code, not the stock Epic release, which is why some standard UE4 launch parameters (like -vulkan) either have no effect or cause immediate termination.
Will my save file be safe if I delete the config and shader cache?
Your progression data lives in %APPDATA%\EldenRing\ in files named S0000.dcchr, S0000.bak, and related slots. The folder you rename for the shader cache fix is %LOCALAPPDATA%\EldenRing\, which contains only display settings, shader binaries, and the game’s internal logs. Renaming or deleting %LOCALAPPDATA%\EldenRing does not touch your save progress, but it does reset your display configuration to defaults.
Why did Elden Ring start crashing after the Shadow of the Erdtree update?
Shadow of the Erdtree raised minimum hardware expectations and introduced new shader permutations. Players on GPUs that were already near the previous minimum sometimes find the expanded shader set exceeds available VRAM during initialization, or the EAC update replaced binaries that their antivirus subsequently flagged. If your crash began at that update, focus on the shader cache and antivirus exclusion fixes first.
Can a mod cause a startup crash even if I have not launched it yet?
Yes. Some modding frameworks (such as the MOD Engine or certain EAC bypass loaders) inject a DLL into eldenring.exe via a modified executable or a dinput8.dll proxy placed in the game folder. If a mod’s DLL is present but the game binary has been updated since, the injection will fault before the engine initializes. Check the game’s install folder for unexpected DLL files and temporarily move them out before testing.
