Apex Legends Crashing Without Error: Causes, Checks and Fixes (2026)

A crash-to-desktop with no dialog box, no error string on screen, and no “Fatal Error” popup is the most common and most maddening way Apex Legends fails. The game runs on Respawn’s fork of the Source engine, which writes shader binaries, maintains a persistent render cache, and relies on a tight handshake between the client process and Easy Anti-Cheat. When any link in that chain breaks, the engine often does not surface a human-readable message. Instead, the window simply vanishes back to your desktop, sometimes after a freeze, sometimes mid-match, sometimes on the loading screen. In the 2026 season of the game, this symptom persists across multiple patches because the underlying failure modes involve your system configuration as much as the game code itself.

Likely Causes

Fix 1: Disable All Overlays

The EA App in-game overlay, Discord overlay, and GPU vendor overlays each hook into the render pipeline. Apex’s engine is known to conflict with multiple simultaneous hooks, producing a silent CTD.

How to check

Close Apex. Open the EA App, click your profile avatar, go to Settings, and disable “In-game overlay.” Do the same in Discord (Settings > Game Overlay > toggle off) and in GeForce Experience or AMD Adrenalin.

What to do

Launch Apex and play for at least 30 minutes across two separate matches. If the crash does not recur, re-enable overlays one at a time, testing between each change, until the crash returns. That identifies the offending overlay.

How to undo it

Toggle each overlay back on in its respective application settings.

Fix 2: Verify Game Files Through the EA App

A single corrupted .bsp or .vpk file can cause the engine to fail when it reaches that asset during a match load, and the engine does not always log a readable error.

How to check

In the EA App library, right-click Apex Legends and select “Repair.” Watch the progress bar for any file flagged as replaced.

What to do

Run Repair. After completion, attempt to reproduce the crash. If it no longer occurs, a file was indeed corrupt. If it persists, continue to the next fix.

How to undo it

No action needed. Repair only restores files; it does not remove anything.

Fix 3: Delete the Shader and Render Cache

Apex writes compiled shader binaries to C:\Users\[username]\AppData\Local\Respawn\Apex\. A stale or partially written cache file causes a silent failure when the engine tries to reference it.

How to check

Navigate to the path above. If the folder exists and contains .bin or .cache files, proceed with deletion.

What to do

Close Apex and the EA App entirely (check system tray). Delete all contents inside AppData\Local\Respawn\Apex\. Relaunch the game. The first boot will recompile shaders and take noticeably longer. Play through a full match.

How to undo it

Not applicable. The game regenerates the folder automatically. If recompilation causes a longer first load, that is expected behavior.

Fix 4: Check and Resize the Windows Page File

Apex routinely uses 12 to 14 GB of committed memory. If your page file is set to a fixed size smaller than what the system needs, allocation fails and the process terminates without a dialog.

How to check

Press Win + Pause/Break, go to Advanced System Settings > Performance > Advanced > Virtual memory. Note whether the page file is system-managed or custom-sized. Also open Task Manager during a match and watch the “Commit” column under the Performance > Memory tab.

What to do

Set the page file to “System managed size” on your primary drive. If you have a secondary SSD, you can add a page file there as well. After changing, reboot and test for the crash.

How to undo it

Revert the virtual memory setting to your previous configuration and reboot.

Fix 5: Perform a Clean GPU Driver Install

A partial driver update that leaves behind mismatched .dll components can cause access-violation crashes (0xc0000005) logged silently in Event Viewer.

How to check

Open Event Viewer > Windows Logs > Application. Filter for “Error” level entries with source “Application Error” occurring within the same minute as a crash. Note the faulting module name.

What to do

Download Display Driver Uninstaller (DDU). Boot into Safe Mode, run DDU, select “Clean and restart.” Back in normal Windows, install the latest driver directly from NVIDIA or AMD’s website. Do not use the EA App or Windows Update to install drivers.

How to undo it

Roll back the driver through Device Manager > Display Adapters > Properties > Driver tab > Roll Back Driver, or reinstall your previous driver version.

Fix 6: Whitelist the Game Folder in Windows Defender and Any Third-Party Antivirus

Easy Anti-Cheat performs kernel-level reads that some security software interprets as suspicious. The block is silent from the user’s perspective.

How to check

Open Windows Security > Virus & threat protection > Protection history. Look for recent entries referencing EasyAntiCheat.exe, Eac_server.exe, or any file inside C:\Program Files\EA Games\Apex\.

What to do

Add the entire Apex install directory as an exclusion. Also add C:\Program Files\EA Games\Apex\EasyAntiCheat\ if your AV requires a separate path. If you use a third-party suite, add exclusions there too.

How to undo it

Remove the exclusion entries from your antivirus settings.

Fix 7: Disable XMP and Reduce CPU Overclocks

Unstable memory timings or a marginal CPU overclock can cause a single allocation error during a heavy scene load, triggering a CTD with no message.

How to check

Reboot into BIOS/UEFI. Note your current memory frequency and XMP profile setting.

What to do

Set memory to the JEDEC default (usually 2133 or 2400 MHz for older kits, 4800 for DDR5) and disable XMP. If you have a CPU overclock or PBO enabled, set it to default. Reboot and test for the crash.

How to undo it

Re-enable XMP and your overclock settings in BIOS. If the crash returns, your hardware is not stable at those frequencies and you should consider raising DRAM voltage slightly or lowering the frequency a notch.

Fix 8: Reinstall Easy Anti-Cheat Manually

EAC files can become inconsistent after an EA App repair or a Windows update, and the game will fail to initialize the anti-cheat handshake without showing a prompt.

How to check

Open Event Viewer and search for entries from source “Service Control Manager” mentioning EasyAntiCheat failing to start.

What to do

Navigate to C:\Program Files\EA Games\Apex\ (or your custom install path). Open the EasyAntiCheat subfolder. Run EasyAntiCheat_Setup.exe as administrator, select Apex Legends from the dropdown, and click “Repair Service.” Reboot.

How to undo it

Run the same setup utility and select “Uninstall service,” then verify game files through the EA App to restore the service.

Fix 9: Full Clean Reinstall of the Game

If none of the above resolves the crash, residual registry entries or partially deleted data in Documents\Respawn\ may be interfering.

How to check

Back up C:\Users\[username]\Documents\Respawn\Apex\Local\ (this contains your videoconfig.txt and keybinds). Note the EA App install path.

What to do

Uninstall Apex through the EA App. Delete any remaining files in the install directory. Delete the AppData\Local\Respawn\ folder. Reinstall fresh. After install, replace your videoconfig.txt with the backed-up copy if you want to preserve custom settings.

How to undo it

The reinstall itself is the terminal step. There is nothing to undo beyond reinstalling again.

If Nothing Works

If the crash persists after all nine fixes, the problem is almost certainly hardware. Run mdsched.exe (Windows Memory Diagnostic) overnight with all four passes enabled. Check your NVMe or SATA SSD for reallocated sectors using CrystalDiskInfo. If either tool reports errors, the crash is a symptom of failing hardware, not a software configuration issue. In that case, no game-side fix will resolve it permanently.

You can also submit a crash report through the EA App by launching Apex with -dev in the launch options (Settings > Advanced launch options on the game card). This forces the engine to write a detailed log to Documents\Respawn\Apex\Local\ that is more useful to Respawn’s support team than the standard submission form.

FAQ

Does Apex Legends write crash dumps I can analyze?

Occasionally. If Windows Error Reporting is enabled, check C:\Users\[username]\AppData\Local\CrashDumps\ for a file named apex.exe.[timestamp].dump. Many silent CTDs, however, produce no dump because the engine exits cleanly before Windows can capture one. The presence of a dump with faulting code 0xc0000005 (access violation) narrows the cause to a bad memory address, often pointing at a driver or cache issue.

Can lowering in-game settings stop the crash?

If the crash is caused by GPU driver instability or a specific shader compilation failure, dropping from high to medium settings changes which shaders are requested and can mask the symptom. This does not fix the root cause, but it is a useful diagnostic signal. If the crash disappears at lower settings, focus on the shader cache and driver fixes above.

Is the Steam version different from the EA App version in this regard?

The underlying engine and anti-cheat are identical. Steam adds its own overlay and cloud-save behavior, which introduces one additional variable. If you play through Steam, also disable the Steam overlay under game properties as part of Fix 1.

Will a future patch fix this?

Respawn regularly addresses known crash vectors in season updates, but silent CTDs caused by local hardware or driver misconfiguration will not be resolved by a game patch. If your crash pattern matches the shader-cache or page-file symptoms described above, a patch will likely not change your experience.