Star Wars Zero Company Crashing: PC Fix Guide

For Star Wars Zero Company crashing on PC, install the current update and repair or verify the game files, then repeat the action that failed. If only one save crashes, preserve it and compare another existing save; if the game fails before the menu, test a clean launch without mods or overlays. Use the trigger table below to choose one change at a time.

Patch 1.2: distinguish a crash from a stuck objective

EA Patch 1.2, rechecked October 26, lists further crash and progression fixes. If Retake Luunata stopped after saving in its elevator, or Speak with Kabb failed to resolve when its conversation was unavailable, update and retry that exact objective before changing graphics settings. These are documented progression triggers.

If the game closes to desktop, follow the crash branches below and keep the last working save. A remaining failure is easier to report with the installed version, mission step and the exact action. See the selected 1.2 fixes and keep the September Hotfix as historical context.

Start with the crash trigger

These are troubleshooting branches, not diagnoses. A save-specific failure does not by itself establish that the campaign is corrupted.

1. Update and verify files

Close the game, let the launcher finish the current update, then use its file verification or repair function. EA's current troubleshooting guide recommends repairing files, updating graphics drivers and checking launcher problems. The September Hotfix is historical context; use your current installed version for the test.

Keep campaign saves intact. If verification keeps replacing the same files, check free storage and antivirus quarantine before repeating it.

Check the same trigger after repair: if the menu now opens, load the same mission; if a particular attack caused the crash, repeat that attack once. Repair followed by a different scene cannot tell you whether the original failure changed. If the launcher itself is failing, follow EA's linked cache-clearing instructions for your specific client; keep launcher cache separate from campaign save files.

2. Isolate mods and overlays

Disable mods with their original installation method and test the clean game. Switch off overlays or capture tools for one comparison run, then re-enable them individually if the crash disappears. Keep a copy of any save dependent on mods. Do not save over your only campaign while testing a changed mod list.

A successful clean run narrows the investigation; it does not prove every overlay or every mod is incompatible.

3. Check drivers and graphics carefully

Use the GPU vendor's current stable driver and restart after installation. On laptops, check that the game uses the intended high-performance GPU. Avoid third-party driver packs.

EA's Patch 1.1 notes recommend turning Environment Geometry Detail off to improve framerate on NVIDIA GTX 10-series and RTX 20-series minimum-spec configurations. That is a targeted performance recommendation, not a confirmed universal crash fix.

If a graphics-related failure remains, reduce one setting and repeat the same scene. Where your configuration exposes frame generation, compare it off for one run; do not assume the feature is present on every GPU. Compare your hardware with the system requirements before choosing a more demanding graphics preset.

4. Protect the campaign and submit a useful report

Keep the last working save and note whether the failure also affects a different existing save. Avoid deleting configuration or save directories without a backup and a documented reason.

Record the store, installed version, Windows build, GPU, driver, mission, last action and mod status. Include the exact error or crash ID when available. Follow official support instructions for log locations and remove personal information before sharing files.

If one change solves the failure, repeat the same trigger once before restoring other variables. This gives you a usable result instead of an unexplained collection of changed settings.

Sources and review

EA's current troubleshooting advice and Patch 1.2 notes checked October 26, 2026. The linked Patch 1.1 recommendation remains relevant to the named older GPUs; it is not a new benchmark. Trigger comparisons, mod isolation and the report checklist are our editorial troubleshooting process. Use the saving guide when the issue is missing progress rather than a game crash.