Quick answer: start with EA's official order: restart the PC/console, check service status, install game/platform updates, close background software, repair or verify game files, update graphics drivers, then investigate PC-specific components such as DirectX/Visual C++ and clean-boot conflicts. Do not jump straight to random registry edits or third-party "fix" downloads.
1. Restart before changing configuration
A full restart clears stuck processes, temporary driver states and launcher problems. Close Zero Company completely, restart the device and test again before changing multiple settings. This sounds basic, but it gives you a clean baseline; otherwise you cannot tell which later change actually fixed the issue.
If the crash repeats, note where it happens: before the main menu, when loading a save, entering a Tactical Mission, during an enemy turn or after a specific graphics change. A repeatable trigger is more useful for diagnosis than "it crashes sometimes."
2. Check EA and platform service status
Zero Company is single-player, but EA notes that platform or EA services can still affect downloads, updates and account-related functions. Check EA's service status and the official Steam, PlayStation or Xbox status page if the problem involves downloading, patching or launching through a storefront.
Do not misdiagnose a store outage as corrupted hardware. If many users cannot download an update at the same time, wait for the platform service to recover rather than reinstalling Windows or the game.
3. Install pending updates
EA specifically recommends checking for game and platform updates. Steam normally downloads game patches automatically unless updates are disabled or queued. EA app and Epic users should confirm the title is fully updated through their library.
Also install relevant operating-system updates when they include platform/runtime fixes. Reboot after driver or major Windows updates so the new components are actually loaded before retesting.
4. Repair or verify game files
Damaged or incomplete game files can cause startup crashes, black screens, missing assets and hangs. Use your storefront's built-in verify/repair function rather than downloading replacement DLLs from an unknown website.
On Steam, use the installed game's Properties/Installed Files verification flow. EA app and Epic provide their own repair/verify options. If verification replaces files, launch the game before making another unrelated change so you can isolate the result.
5. Update GPU drivers
EA recommends the latest available NVIDIA, AMD or Intel graphics driver for your hardware. A clean driver update is particularly relevant when the crash occurs during rendering, after changing graphics settings or after a game patch that expects a newer driver path.
Use the GPU manufacturer's official download/update tool. Avoid third-party "driver updater" programs, which add another variable and may install incorrect packages.
6. Intel Arc users: verify Resizable BAR
EA specifically tells Intel Arc owners to enable Resizable BAR for better FPS performance. While ReBAR is primarily a performance recommendation, an incorrectly configured or unusually slow Arc system should be checked against the official requirement before deeper troubleshooting.
Firmware settings can be risky if changed without understanding the motherboard, so follow your hardware manufacturer's documentation rather than copying a generic BIOS screenshot.
7. Lower graphics only when the symptom points to rendering load
If the game launches but becomes unstable or extremely slow in demanding scenes, test a lower preset and the recommended TSR/DLSS/FSR path. EA says the game is comparatively CPU-bound, so reducing every graphics option may not cure a CPU-side hang or stutter.
Change a small number of variables at a time. If a specific setting reliably triggers the crash, document it for a bug report; that is more actionable than changing ten options simultaneously.
8. Close background and overlay software
EA includes background-program conflicts in its PC troubleshooting. Temporarily close nonessential capture tools, overlays, hardware monitoring utilities and high-load applications. If the crash stops, re-enable them one at a time to identify the conflict.
A clean boot is the stronger version of this test. It helps isolate third-party services that launch with Windows. Use Microsoft's normal clean-boot procedure and restore your regular startup configuration after testing.
9. DirectX, Visual C++ and DLL errors
If an error message names DirectX, Microsoft Visual C++ or a missing DLL, use Microsoft's official runtime installers or Windows repair mechanisms. Do not download individual DLL files from random DLL-hosting sites. A missing-runtime error is a component installation problem, not an invitation to place unknown binaries inside the game folder.
The game's official requirements use DirectX 12. Confirm Windows and the GPU driver are current enough for the required feature path.
10. Save-specific or mission-specific crashes
If only one save or one mission crashes, first create a backup if the platform allows it, then test an earlier save or restart the mission. StarWars.com's beginner guide confirms that missions can be restarted. If the problem is reproducible at the same encounter, collect the mission name, Cycle, squad composition and any unusual ability/animation that immediately precedes the crash.
Do not delete all saves as an early troubleshooting step. Preserve evidence until you know the problem is actually corrupted save data.
11. Report a reproducible bug
EA provides official forums/support routes for bug reports. A useful report contains platform/storefront, OS, CPU, GPU, RAM, driver version, game version, exact error text, reproduction steps and whether file verification or a clean boot changed the result.
Screenshots and crash logs are valuable when the support flow requests them. Avoid including passwords, personal account secrets or unrelated private files.
Fast checklist
| Symptom | First actions |
|---|---|
| Won't launch | Restart, update, verify files, drivers, runtimes |
| Crash to desktop | Verify files, driver update, background-app test |
| Black screen | Update/verify, driver check, graphics reset |
| Freeze/hang | Background apps, CPU/load check, mission reproduction |
| Poor FPS/stutter | Recommended upscaler, ReBAR for Arc, CPU/background diagnosis |
| Download/install issue | Platform status, network, cache/update state |
What this guide intentionally does not recommend
It does not recommend pirated executables, cracked files, registry-cleaner software, random DLL downloads, disabling security software permanently or installing an unknown "performance patch." Those steps create more risk than they solve and are not part of EA's official troubleshooting path.