An apex crash is often tied to drivers, files, overlays, or unstable settings, and you can usually pin it down with a fast checklist.
Crashes feel random until you treat them like clues. Did the game close to desktop with no message, hard-freeze your PC, or drop you to the launcher after a loading screen? Each pattern points to a different bucket of causes, so the fix gets faster when you name the pattern first.
This guide walks through the fixes that cover most Apex Legends crash reports on PC and console. You’ll start with the safest moves, then work toward deeper fixes that take longer but solve stubborn cases.
Why Apex Keeps Crashing And What That Usually Means
Most crashes fall into four categories. A clean close to desktop often points to corrupted game files, a conflict with an overlay, or a shader cache issue. A full system freeze leans toward GPU instability, bad RAM timings, or a driver conflict. A crash at “Loading” or right after a match can come from a broken config file, a permissions problem, or a network hiccup that the client handles poorly.
Before you change ten things at once, note three details: when it happens, what you were doing, and whether your whole system stays responsive. That tiny logbook saves time, since you can tell if a fix changed the symptom or just changed the timing.
| What You See | Most Likely Cause | First Fix To Try |
|---|---|---|
| Closes to desktop during a match | Overlay conflict or corrupted files | Disable overlays, then verify game files |
| Crashes at loading screen | Shader cache or config corruption | Clear shader cache, reset settings file |
| Hard freeze or reboot | Driver or hardware instability | Roll back driver, remove overclocks |
| Stutters for minutes, then crash | VRAM pressure or background apps | Lower textures, close heavy apps |
Don’t skip the boring checks. Many crashes come from two apps fighting for the same hook, a driver install that didn’t land clean, or a single damaged file that only gets called when a certain map asset loads.
A simple way to sort the issue is to test one match with the cleanest setup you can. Close browsers, screen recorders, chat overlays, RGB suites, GPU tuning dashboards, and any “game booster” apps. If the crash stops, bring apps back one at a time until the culprit shows itself.
Apex Crash Fix Checklist For PC, Steam, And EA App
Run this list in order and test after each step. You’re trying to find the smallest change that stops the crashes, not rebuild your whole setup. Test one change.
- Restart the PC — Close everything, reboot, then launch the game first before browsers and chat apps.
- Disable in-game overlays — Turn off Steam Overlay, EA overlay features, Discord overlay, and GPU overlay panels.
- Verify game files — Use Steam “Verify integrity” or the EA App “Repair” option to replace damaged files.
- Run as admin — Launch the client and the game with admin rights to avoid write-blocked config changes.
- Remove all overclocks — Set GPU and CPU back to stock and turn off RAM XMP as a test for stability.
- Update Windows components — Install pending Windows updates, then reboot after they finish.
- Rebuild the game settings — Rename the settings folder so the game creates fresh config files on next boot.
Reset config files the clean way
A broken setting can crash the game before you reach the lobby. You don’t need to uninstall to test this. Rename the settings folder first so you can roll back if you want your old binds.
- Close the game and client — Make sure Apex and the launcher are fully closed in Task Manager.
- Open the saved games folder — On many PCs it’s under Documents, then Saved Games, then Respawn.
- Rename the Apex folder — Add “-old” to the folder name so the game makes a fresh one.
- Launch and test — Set only your basics, then play one match before changing lots of settings.
Quick checks that catch weird crashes
- Free disk space — Keep at least 20 GB free on the drive that holds the game and Windows temp files.
- Close antivirus scans — Pause active scans and add the game folder to your antivirus allow list.
- Unplug extra USB gear — Test with only mouse, controller, and headset to rule out flaky devices.
If you’re hitting an apex crash right after character select, overlays are the first suspect. The game is switching render states and loading a lot at once, which is where overlay hooks and shader caches collide.
Where to find the fastest fixes
- Steam — Right-click the game, open Properties, then Installed Files to verify.
- EA App — Open the library, choose Manage, then Repair.
- Windows — Search “Graphics settings” and try turning Hardware-accelerated GPU scheduling off as a test.
Fixing Crashes In Apex On PC After Updates
Big patches can shake loose two common problems: old cached shaders and drivers that don’t like the new build. You’ll get fewer surprises if you treat updates as a “clean start” moment for your graphics pipeline.
- Clean-install the GPU driver — Use the vendor installer’s clean option, or remove the driver and install fresh.
- Clear the shader cache — Delete the DirectX shader cache, then let the game rebuild it on the next few launches.
- Switch to a stable driver branch — If the newest driver started the crashes, try the last known stable version.
- Reset launch options — Remove old launch commands you copied months ago and test with defaults.
Driver swaps feel scary, but they’re a clean test. If crashes vanish after a rollback, you’ve found the culprit. If nothing changes, you can move on without guessing.
Check these Windows items too
- Game Mode — Toggle it once and test both ways, since some systems behave better with it off.
- Background capture — Turn off background recording in your Xbox settings to cut extra hooks.
- Power plan — Use the Balanced plan to avoid sudden voltage spikes from aggressive boosting.
DirectX and launch options worth testing
The game can behave differently depending on render mode and launch flags. If you’ve been using custom launch commands for a long time, reset them first. Then test one change at a time.
- Force DirectX 11 — Add a DirectX 11 launch flag if your current mode crashes after updates.
- Remove frame rate flags — Delete old commands that push the engine beyond your monitor’s range.
- Disable fullscreen tweaks — Turn off Windows fullscreen optimizations for the game exe and test.
Settings That Reduce Crashes In Apex Without Killing Feel
Not each crash is a “broken PC” issue. Some rigs are fine until the game pushes VRAM too hard or hits a heavy scene that spikes frame times. The goal is to reduce pressure where it matters, not tank your visuals everywhere.
- Lower Texture Streaming Budget — Drop one step to cut VRAM use on busy maps.
- Cap the frame rate — Set a cap slightly below your typical peak to smooth spikes and reduce heat.
- Use borderless as a test — If true fullscreen triggers crashes on alt-tab, borderless can steady it.
- Turn off extra shadows — Shadow details can spike memory use in certain lighting and effects.
- Disable third-party post effects — Turn off reshade-type injectors; they often break after patches.
If the game crashes after long sessions, heat creep can be part of it. A frame cap, a tiny texture drop, and fewer background apps can keep the GPU from hitting the edge after thirty minutes of constant load.
Overlay and capture apps that commonly cause trouble
Any app that draws on top of the game can collide with anti-cheat or the renderer. If you want a clean test, close them all for one evening.
- Chat overlays — Disable Discord overlay and in-game chat pop-outs.
- FPS counters — Turn off third-party counters and stick to the game’s built-in display.
- GPU tuning tools — Close tuning panels after you set values, or uninstall them during testing.
Console And Controller Fixes When Apex Legends Keeps Crashing Mid Match
Console crashes are less about drivers and more about storage, cache, and system updates. The upside is that fixes are simple and safe, and they often work on the first pass.
Storage checks that matter on console
If your internal drive is packed, installs and updates get messy. Free some space, then let the console sit on the home screen for a few minutes so it can finish background maintenance.
- Clear at least 10 percent — Leave breathing room for updates and temp files.
- Move other games off — Shift rarely used titles to external storage or delete them.
- Avoid unplugging mid update — Let patches finish fully before rest mode or shutdown.
- Power cycle the console — Shut down, unplug for one minute, then boot and test.
- Clear reserved space — Remove temporary game storage where the console keeps cached items.
- Reinstall the game — If crashes follow one map or one mode, a reinstall can replace a bad asset.
- Update the console OS — Install system updates, then check for a game update again.
If your crash happens only when a controller disconnects or the battery dies, swap cables and test another port. Sudden disconnects can act like a fault path during intense input bursts.
Network checks that help without touching your router
- Use wired for one session — A cable test tells you if Wi-Fi drops line up with crashes.
- Reboot the modem once — A single reboot can clear a stuck state without changing settings.
- Limit downloads — Pause background downloads so the console isn’t juggling storage and network at once.
When To Escalate And What To Capture Before You Reinstall
If you’ve tried the checklist and the crashes still hit, treat it like a reproducible bug report. The trick is to capture proof without turning your PC into a science project. A small set of details can make the pattern obvious.
- Note the exact moment — Map, mode, legend, and what you clicked right before the crash.
- Grab the error text — If an error code appears, screenshot it and write it down.
- Check Windows Event Viewer — Look for an application error tied to the game at the same time.
- Run a memory test — If freezes or reboots happen, test RAM overnight to rule out instability.
- Try a clean boot — Disable startup apps, then launch only the game to find conflicts.
One crash can come from a flaky driver, but repeats at the same spot often point to a specific asset or a settings file. If you can reproduce it, you can fix it faster.
At that point, a reinstall is fine. Keep it as your last move, since it hides the real cause and takes time. If reinstalling fixes it, add back your overlays and tuning tools one at a time so you know what triggered the issue.
