Apex Crashing On Startup | Fix Launch Crash In Minutes

Guide / By

apex crashing on startup often comes from bad files, drivers, or overlays; verify files, repair anti-cheat, then launch again.

If Apex drops to desktop before you see the lobby, you’re not alone. Startup crashes tend to come from a small set of repeat offenders: a bad update patch, a broken file in the install, a driver conflict, or a background app that hooks into the game.

This walkthrough keeps things practical. You’ll start with fast checks that don’t touch your settings, then move into deeper repairs that solve the most common launch-crash patterns on Windows for Steam and the EA app. No need to reinstall Windows to test.

Why Apex Can Crash On Startup

Apex has to load anti-cheat, initialize DirectX, compile or reuse shaders, read config files, and pull in device drivers before you ever touch a menu. If one piece fails, the game can exit with no message or toss a short error window.

What You See Likely Trigger Fast Check
Easy Anti-Cheat splash, then desktop Anti-cheat service or blocked files Repair anti-cheat and reboot
Black screen, then closes Driver, shader cache, overlay hook Disable overlays and update GPU driver
Immediate crash with no window Corrupted game file or config Verify files, then reset config folder
Error about missing DLL VC++ runtime or system file issue Repair Visual C++ packages

Common Error Messages You Might See

Some startup crashes show a short code or a one-line window. Treat it like a clue. Write down the message before you change anything so tell whether a step changed the behavior.

  • DXGI Device Removed — Often ties to GPU drivers or unstable GPU clocks; test with stock settings and a clean driver install.
  • Engine Error — Can point to a damaged asset file; verifying files is the first move.
  • 0xc0000005 — A generic access violation; overlays, antivirus hooks, and broken runtimes are common triggers.
  • Easy Anti-Cheat Not Installed — Repair the anti-cheat service from the install folder, then reboot.
  • MSVCP140 Or VCRUNTIME Missing — Repair the Microsoft Visual C++ packages, then restart Windows.
  • 0x887A0006 — A DirectX device hang; driver rollback and shader cache clearing often help.

Crash Before The Anti-Cheat Screen

This pattern often points to the game install itself, a missing runtime, or a config file that Apex can’t parse. It can also happen when a security tool quarantines a file inside the install directory.

Crash Right After Anti-Cheat Loads

If you see the Easy Anti-Cheat splash and it drops to desktop, treat it like an anti-cheat handshake failure. A repair pass plus a restart fixes a lot of these cases, especially after Windows or driver updates.

Crash After A Long Pause On A Black Screen

A long pause usually means the game is trying to initialize graphics, reuse old shader data, or attach to an overlay. When the hook fails, the process can close without a clean error.

Apex Crashing On Startup After An Update

Updates change files that sit right on the launch path. If an update is interrupted, or a patch doesn’t apply cleanly, Apex can crash every time you hit Play. The fix is almost always a clean file check plus clearing the small bits of cached data that can keep breaking the launch.

Start by rebooting once. It sounds plain, yet it clears stuck services and driver modules that keep hanging around after an update. Then work through the steps below in order so you don’t repeat work.

Clear Launcher Cache After A Patch

If an update applied cleanly and Apex still crashes at launch, stale launcher cache can keep serving bad data. Clearing the cache is safe, and it stops a loop where the launcher keeps “preparing” the same files.

  1. Clear Steam Download Cache — In Steam Settings, open Downloads and clear the download cache, then sign in again.
  2. Clear EA App Cache — In the EA app, open Help, choose App Recovery, then clear cache and restart the app.
  3. Restart Your Router — Power-cycle your router once to drop stuck sessions that can break patch downloads.
  1. Reboot Windows — Shut down fully, start back up, then launch Apex before opening extra apps.
  2. Pause Sync Tools — Temporarily stop OneDrive syncing for Documents and Saved Games so Apex files don’t get locked.
  3. Run The Launcher As Admin — Right-click Steam or EA, choose Run as administrator, then start the game once.

Fast Checks That Fix Most Launch Crashes

Do these first. They’re low-risk and they solve a big chunk of “it worked yesterday” crashes. Try one change, launch, then move to the next if it still fails.

  1. Verify Game Files — On Steam, use Properties → Installed Files → Verify. On EA, use Manage → Repair.
  2. Disable In-Game Overlays — Turn off Steam Overlay, EA overlay, Discord overlay, and GeForce Experience overlay, then relaunch.
  3. Remove Launch Options — Delete custom arguments like -novid or renderer flags, then test with a plain launch.
  4. Unplug Extra Controllers — Disconnect gamepads, steering wheels, and USB hubs, then start with mouse and standard controls only.
  5. Check Free Disk Space — Keep at least 20 GB free on the drive that holds Apex and on your Windows drive for shader and temp files.
  6. Switch To Windowed Mode — If you can reach a splash once in a while, set windowed, close the game, then launch again.

Steam File Check Notes

If Steam finds and reacquires files, launch right away. If it keeps reacquiring the same file every time, antivirus or a disk issue is in play, so jump to the security and disk steps later in this guide.

EA App Repair Notes

EA’s repair can take a while on slower drives. Let it finish, then restart the EA app before launching. If the app stalls on “preparing,” clear the EA app cache, then retry the repair.

Repair Steps For Corrupted Settings And Anti-Cheat

When quick checks don’t work, reset the game’s local config and repair Easy Anti-Cheat. This keeps your account progress safe, since that lives on EA servers. You may lose local video settings and control-bind tweaks, so take a screenshot of your sensitivity and control binds first.

  1. Back Up The Config Folder — Open Saved Games\Respawn\Apex\local, copy the folder to your desktop.
  2. Reset Local Settings — Rename the local folder to local_old, then launch Apex to force a fresh config.
  3. Repair Easy Anti-Cheat — In the Apex install folder, open the EasyAntiCheat setup and run Repair Service.
  4. Allow Apex Through Security Tools — Add exclusions for r5apex.exe and the Apex install directory, then relaunch.
  5. Run System File Check — Open a terminal with admin rights and run sfc /scannow, restart, then try again.

Windows Security Settings That Can Block Apex

Windows can block game writes in the background. If Controlled folder access is on, Apex may fail when it tries to write new config or shader files. Check Windows Security, then allow Apex if it’s being blocked.

  • Review Protection History — Open Windows Security and check Protection history for blocked actions tied to r5apex.exe.
  • Allow Through Controlled Folder Access — If Controlled folder access is enabled, add Apex and the launcher as allowed apps.
  • Temporarily Disable Third-Party AV — Turn it off for a quick test, then re-enable it and set proper exclusions if Apex launches.

What To Do If Apex Still Crashes After Resetting Local

If a fresh local folder doesn’t change anything, the issue is less likely to be settings. Move on to driver cleanup and overlay checks, since those can crash the game before it can even rebuild a new config.

Driver And Overlay Conflicts That Break The Launch

Startup is when Apex talks to your GPU driver, audio stack, and any apps that inject an overlay. A driver that’s been updated over an older install, or an overlay that hooks in with an out-of-date DLL, can cause instant crashes.

  1. Update Your GPU Driver — Install the latest driver from NVIDIA, AMD, or Intel, then reboot.
  2. Clean Install The GPU Driver — If you recently upgraded drivers, use the vendor clean install option to replace old components.
  3. Turn Off Capture Apps — Close OBS, Xbox Game Bar capture, and third-party recorders, then test a launch.
  4. Disable RGB And Tuning Tools — Exit apps like MSI Afterburner, RivaTuner, and motherboard RGB suites, then launch.
  5. Reset GPU Overclock — Set GPU and VRAM back to stock settings in your tuning tool before you test Apex.

Shader Cache And DirectX Notes

If the game crashes after a long black screen, a shader cache rebuild can help. In your GPU control panel, clear the shader cache, then launch once and let the first load take its time.

Audio Drivers Can Matter Too

Less common, yet real: broken audio drivers or virtual audio devices can crash games at launch. Disable unused playback devices, unplug USB headsets to test, then update the audio driver from your laptop or motherboard maker.

When Nothing Works: Clean Boot, Reinstall, And Useful Logs

If you’ve verified files, reset local config, repaired anti-cheat, and cleaned up overlays, it’s time to isolate background conflicts. A clean boot tests Apex with only Microsoft services and core drivers running.

  1. Do A Clean Boot — Use msconfig to hide Microsoft services, disable the rest, restart, then launch Apex once.
  2. Create A New Windows User — Test Apex on a fresh profile to rule out permission and profile-level conflicts.
  3. Move Apex To A Different Drive — Reinstall to another SSD if you can, since failing sectors can mimic “corrupt files.”
  4. Reinstall Visual C++ Runtimes — Repair the 2015–2022 packages from Microsoft, restart, then launch again.
  5. Reinstall Apex Cleanly — Uninstall, reboot, delete the leftover Respawn folders, then install again.

If you need something concrete to share with EA help or a tech forum, grab the game’s crash folder and your Windows Event Viewer entry. The config and crash files often live under Saved Games\Respawn\Apex, and Windows logs crashes under Application in Event Viewer.

If the crash happens in full-screen, force borderless windowed mode by adding -fullscreen 0 -windowed in launch options, then remove them once the game loads and you change settings inside Apex.

One last note for repeat crashes: if Apex crashes on startup only after a GPU-heavy driver update, roll back one driver version and test. If it stops, wait for the next driver release and update again.

Once you’re back in, set your overlays one at a time. Launch after each change. That way, if apex crashing on startup returns, you’ll know what triggered it and you can keep playing without a full reinstall.

If you’re still stuck, write down exactly when it crashes, what you see on screen, and what changed on your PC right before it started. Those details turn a guess into a fix.