Stability diagnosis
STAR WARS Zero Company Crashing or Freezing? Diagnose the Problem
A crash, a hard freeze, a stuck enemy turn and a stutter are four different failures, and telling them apart is the diagnosis. This page first works out which one you have, where the game stops, and which build you are on — then it gives you the lowest-risk path that fits, before anything is changed on your machine or in your save.
The rule this page diagnoses by
Diagnose where the game stops before trying to fix it. A crash, a hard freeze, a combat softlock and a performance stall are different failure states.
Protect the save first, before any repair step.
Official low-risk steps come before community workarounds.
A player-reported trigger is never printed as a confirmed root cause.
Start here
What Exactly Happens?
Not one of these is a diagnosis yet. Each one decides which failure state is being looked at, and where on the page it is handled.
Game closes / crash to desktop
The game quits on its own
The process ends, or you land on the desktop or console dashboard. Where it happens decides everything else.
Crash
Game completely freezes
Nothing responds any more
Input stops working and the game never returns. Check whether the whole system is affected before retrying it.
Hard freeze
Enemy turn never finishes
The AI never hands control back
Animations may still move and the menu may still open, but the battle state does not advance. That is a softlock, not a crash.
Gameplay / turn softlock
Black screen / stuck on startup
It never reaches the main menu
A black screen with sound, a black screen with nothing, and a logo freeze are three different symptoms.
Hard freeze
Crash while loading a save
Continue does not survive the load
Whether a different save loads is the single most useful fact you can give this page.
Crash
Crash during / after a mission
It happens around a Mission
Combat, a cutscene, the mission result and the return to the Den are four different stages with different risk to your save.
Crash
My save or progress is missing
The progress is not where you left it
Save state has its own section, and it comes before any repair step for a reason.
Crash
Definitions
Crash vs Freeze vs Softlock vs Stutter
The single most useful thing this page can do is stop a 30-second hitch and a permanent enemy-turn lock from sharing the word “freeze”.
Crash
The game closes, or returns to the desktop / console dashboard.
The process ends. It may or may not show an error first.
Hard freeze
The game becomes unresponsive and normal input no longer works.
No camera, no menu, no return of control — often a forced shutdown.
Gameplay / turn softlock
The game is still rendering, the camera or menu may still work, but the battle state no longer advances.
Animations continue. The enemy turn never returns control.
Performance stall
A temporary hitch or stutter, after which the game resumes.
The game keeps responding. The state still advances.
Is It a Freeze or Low Performance?
The game continues responding while the frame rate drops or hitches. That is performance, and it is not this page’s main subject.
The game state stops advancing — the turn never resolves, control never returns, or the process ends. That is the failure this page diagnoses.
Patch 1.1 included visual stutter fixes and a published performance recommendation, so a stutter is worth a patch check before anything else.
Baseline
Current troubleshooting baseline — Patch 1.1
Patch 1.1 is the latest official patch this page has seen, released September 9, 2026. It included a batch of crash and stability fixes. Stability reports still exist after it, which is why this page asks for the build and the failure state before it says anything about a fix.
Patch: 1.1 — released September 9, 2026
Official update checked: September 20, 2026
Observed pattern records: 11 (7 current reports, 4 documented as fixed)
Are you on Patch 1.1?
What the page can see
- Official patch status for the current build
- Mission, Objective and Operator records, used to name the reproduction environment
- Observed pattern records, labelled by status
- Deliberately not available: your save, your crash log, your platform telemetry
“This crash happened on this Mission, at this Objective.”
“The publisher documented this behaviour as fixed in a patch.”
“This is the publisher’s recommended order for a stability problem.”
“Other players report this happening around this trigger.”
Primary diagnostic
Where Does It Happen?
This is a more useful first dimension than the platform. Where the game stops decides which risk you are managing — a launch failure, a save failure or a battle-state failure.
Before the main menu
It crashes or freezes on launch, before the menu appears
Crash · Hard freeze
- • Confirm the build
- • Restart the game, then the device
- • Check platform service state
- • PC: verify the game files
When loading Continue / a save
The load starts and the game does not survive it
Crash · Hard freeze
- • Try a different save or a new campaign
- • Note the load percentage it fails at
- • Preserve the save before retrying it
Entering a Mission
The Mission loads and the game fails during the load
Crash · Hard freeze
- • Confirm the build
- • Verify PC game files
- • Note whether the same Mission always fails
During combat
It happens mid-battle, often around an action or an effect
Crash · Hard freeze
- • Record the last action before it happened
- • Note whether it reproduces at the same action
During the enemy turn
The AI turn does not finish, or the game fails while it runs
Gameplay / turn softlock · Crash
- • Check what still responds
- • Note the last AI action
- • Note whether it always stalls at the same point
During a cutscene
It fails while a cinematic or a scripted action plays
Crash · Hard freeze
- • Note whether it reproduces at the same cutscene
- • Check the build before replaying it repeatedly
After the Mission / returning to the Den
The Mission completes and the game fails on the way back
Crash · Hard freeze
- • Protect the save first
- • Note exactly when it fails in the transition
- • Avoid force-closing during the transition
While changing build / ability UI
It fails while you are in a menu rather than in a battle
Crash · Hard freeze
- • Confirm the build
- • Restart the game cleanly before repeating the menu path
Main tool
Crash & Freeze Diagnostic
Answer what happens, where, and on which build. The page returns the failure state it thinks you have, the first actions that fit it, and what not to do yet.
Step 1 — what exactly happens?
The game closes, or returns to the desktop / console dashboard.
Result
TECHNICAL ISSUE
This is a stability problem on your build
Follow the official low-risk order first, then reproduce the exact trigger and report it if it persists.
Why
- • Nothing in the answers points at a stall, a save split or a system-level failure, so this is treated as a stability problem on your build.
First actions
- 1. Confirm the build
- 2. Restart the game, then the device
- 3. Check platform service state
- 4. PC: verify the game files
- 5. Reproduce the exact trigger
- 6. Report it if it still reproduces
Avoid for now
- • Do not delete, replace or manually repair save files as an early step
- • Do not disable cloud sync as a first move
- • Do not stack overlays, registry edits and file replacements before the official steps are done
Related observed pattern: Black screen or freeze on launch before the main menu. It is listed in Pattern search below, labelled as a report rather than a cause.
Reproduction context
Failure: Crash Stage: Before the main menu Platform: PC · Steam Game version: Patch 1.1 Reproducibility: Intermittent Save: Standard campaign
Category 1
Game Crashes or Freezes on Startup
Launch, black screen, logo, then nothing. Startup failure is the one case where the publisher’s order is also the correct order.
Startup issue → official order
- 1. Is the build current?
- 2. Restart the game, then the device.
- 3. Is the platform service reachable?
- 4. PC: verify or repair the game files.
- 5. PC: is the graphics driver a current supported version?
- 6. Clear the supported cache.
- 7. Still reproducible → it is a current issue, not an old one.
Do not read a driver update as a universal answer
The patch updated the recommended driver baseline, so a supported driver is part of the baseline. But players also report startup crashes that began right after a patch and a driver update were installed together.
So if the problem began immediately after a driver change, record that change as part of the diagnosis instead of updating again. A rollback is a configuration-specific step and belongs after the official order, never on the first screen.
Startup failures after a successful update are treated on this page as current reports, not as something the patch was meant to have closed. The patch shipped a batch of crash fixes; that is not the same sentence as “crashes are fixed”.
Category 2
Black Screen or Logo Freeze
A black screen with audio is a different symptom from a black screen with nothing, and both are different from a machine that has lost its display.
Check in order
- Can you still hear game audio?Audio surviving points at the display or the game window rather than a full process failure.
- Can the Windows or console menu still open?If the system shell responds but the game does not, the failure is contained to the game.
- Does the display come back on its own?A display that returns is a different symptom from one that never does.
- Does only Zero Company close?A single application failing is a game-level problem; everything failing together is not.
- Does the PC need a hard reset?A machine that must be hard-reset repeatedly is a system-level symptom and should be recorded, not re-reproduced.
GAME WINDOW BLACK SCREEN
The game itself is failing to present a frame, while the system is otherwise healthy. This is a game-level troubleshooting path.
SYSTEM-LEVEL FREEZE / DISPLAY LOSS
The display or the whole machine is affected, not only the game. Stop repeating the same crash and record the system details first.
If the whole system is affected
Stop repeatedly forcing the same failure before you have recorded the system and driver details. This is not a case for voltage, BIOS or memory-profile experiments.
Category 3
Crash When Loading a Save
One question splits this category cleanly: does any other save still load?
Another save loads
Save-specific failure. A different save or a new campaign loading normally points at that save or the Mission state it holds rather than at your installation.
Nothing loads
Broader issue. If no save loads, treat it as an installation, patch or driver problem and work the official order before touching save files.
Not tried yet
Make that the next thing you do, and preserve the failing save first. It is the cheapest fact to establish and it changes everything downstream.
Do not call it a corrupted save yet
A save that fails to load, a campaign state bug and a specific Mission load crash can all look identical. This page calls the symptom a save-specific failure and does not label the file corrupted without further evidence.
Check before you retry it repeatedly
- • Was the save created before Patch 1.1?
- • Was the game force-closed at any point?
- • Is this a Beskar or other single-save run?
- • Does the crash always happen at the same load percentage?
- • Does the previous autosave still load?
Players report saves that loaded normally and later crashed during loading, sometimes with no way back into that campaign. That is why this page puts save preservation above every other step in this category.
Category 4
Game Crashes During Combat
This is one of the most active report areas. The page records the trigger and refuses to convert it into a cause.
What happened immediately before?
- • Explosion / effect
- • Ability
- • Enemy action
- • Overwatch reaction
- • Kill / death
- • Turn transition
- • Mission completion / cutscene
- • Loading a save
- • Nothing obvious
Trigger is not cause
Reproducible trigger: explosion, effect, ability or enemy action.
Cause: not established. This page does not print “particle effects cause the crash”, because the report does not establish that.
Players report combat freezes around effects and triggered actions, on PC and on consoles. It is a reported trigger, and it is labelled as one.
If a combat failure repeats at exactly the same action, that is worth a clip. The clip is what turns “it freezes in combat” into a report somebody can reproduce.
Category 5
Enemy Turn Never Ends
This is a combat-state softlock, not a crash — and the page links it to the sister troubleshooting pages rather than absorbing them.
How long has it been stalled?
Use this to describe it, not to judge it. Players report recovery anywhere from under a minute to never, so this page deliberately prints no threshold, because a fixed number of seconds would be invented.
- • Under 10 seconds
- • 10–60 seconds
- • Over a minute
- • It never resumes
Short stall → a performance or processing stall. It resumed; note it and carry on.
Never resumes → a possible combat softlock. The state is no longer progressing, which is the thing worth reporting.
Was the last AI action one of these?
- • A heal
- • An Overwatch reaction
- • A movement or an ability
- • A kill or a death
- • Unknown
Patch 1.1 documented a turn-order fault where a Captain kept acting on a target that Overwatch had already killed. If your stall looks like that pattern on the current patch, treat it as a current report — not as the old bug.
Independent tool — gameplay softlock or hard freeze?
What still works?
Tick everything that still responds. Input signals decide the verdict; background audio and animation alone do not.
An enemy turn that never returns is a state problem, so the Mission-side diagnosis lives on Mission Not Progressing. This page owns the case where the game process itself is the suspect.
Category 6
Crash After a Mission, Returning to the Den
This is the transition with the most save risk attached, which is why the page slows down here.
The transition has four steps
- 1. The tactical Mission completes.
- 2. The end-of-mission cutscene plays.
- 3. The campaign state is saved.
- 4. The Den appears.
Note which step fails. A failure before the save and a failure after it are different problems with different risk to your progress.
Save state warning
Avoid deliberately force-closing the game during a Mission-to-Den transition unless it is truly unresponsive. Patch 1.1 addressed some save corruption caused by sudden shutdowns, but that does not make a forced shutdown a normal exit.
Players report Mission completions that fail on the way back to the Den and occasionally pass on a later attempt. Retry the transition if you want — but retry it by restarting the game, not by force-closing it mid-save.
Category 7
Beskar Crash or Missing Save
A single-save run raises the cost of every wrong move, so this section is deliberately slower than the rest of the page.
OFFICIALLY ADDRESSED — PATCH 1.1
- • Temporary Beskar save deletion
- • Beskar-mode crash
- • Save corruption from a sudden / forced shutdown
If the symptom still happens on the current patch, it is a current report rather than the documented issue. Confirm the build first.
BESKAR SAVE
Do not delete, replace or manually edit your only save as an early troubleshooting step. On a single-save run that is the whole campaign.
- 1. Preserve the current state.
- 2. Confirm the current patch.
- 3. Restart safely.
- 4. Use official support or platform recovery options.
- 5. Manual file changes only after a backup exists.
Deleting a cloud save, disabling cloud sync or overwriting a local save are not default steps on this page. They are file-level operations with a single-save failure mode, and they sit below the official order.
Before you troubleshoot
Protect Your Progress First
Every crash-testing session is a chance to lose progress. This is the cheapest thing on the page to get right.
Rules
- • Avoid deliberately quitting during a save transition
- • Wait for control to return where the game still responds
- • Avoid destructive save changes while you are still diagnosing
- • Be extra cautious on a Beskar or other single-save run
Official guidance notes that progress may not have finished saving if you exit before regaining control of Hawks, and that a normal save cycle is the safe route. Patch 1.1 addressed some save corruption caused by a sudden shutdown, but that does not make force-closing a normal way to exit.
This lowers risk. It is not a promise that nothing can be lost, and this page never presents it as one.
When a Forced Shutdown Is the Only Option
If the game is genuinely unrecoverable, a forced shutdown may be the only way out. That is different from closing the game because a Mission is taking a long time.
Use a forced shutdown only when the game is truly unresponsive. Patch 1.1 addressed some corruption caused by sudden shutdowns, but preserving the normal save cycle is still preferable.
Version
What Patch 1.1 Addressed
Each row is what the patch says, followed by the boundary of that claim. A fixed issue and a similar-looking issue are different verdicts.
Various crash issues
OFFICIALLY ADDRESSED — 1.1Crashes reported across the campaign
The published wording is a batch of crash fixes, not “every crash”. This page never prints that crashes are fixed.
Various visual stutters
OFFICIALLY ADDRESSED — 1.1Hitching and stutter during play
This is a performance fix. It does not claim to resolve a hard freeze or a softlock.
Temporary Beskar save deletion
OFFICIALLY ADDRESSED — 1.1The Beskar save appeared to disappear
A temporary deletion that the patch addressed is not the same as a general save recovery promise.
Beskar-mode crash
OFFICIALLY ADDRESSED — 1.1A crash specific to a Beskar run
A Beskar crash fixed in a patch does not cover a different crash that happens to occur in a Beskar run.
Save corruption from a sudden / forced shutdown
OFFICIALLY ADDRESSED — 1.1A save damaged after the game was force-closed
The patch addressed some of this. Force-closing is still not a normal way to exit a game.
Rare main-menu softlock
OFFICIALLY ADDRESSED — 1.1The front end stopped responding
A rare softlock fix is not a general statement about menu stability.
Combat actions not processed correctly
OFFICIALLY ADDRESSED — 1.1An action did not resolve, or the turn order stalled afterwards
This is the closest documented fix to an enemy-turn stall. Similar-looking turn stalls still get reported.
The patch improved stability. It is not a statement that crashes are gone, and this page never writes one.
Observed state
What Players Are Still Reporting
Title matters here: these are current player reports, not an official known-issues list. The site has no access to a publisher defect tracker.
Combat crashes and freezes
Players report these on PC and on consoles after the patch.
CURRENT PLAYER-REPORTED
Enemy-turn softlocks
Reported through the release window and afterwards, including after a heal or reaction action.
CURRENT PLAYER-REPORTED
Startup crashes and black screens
Reported after updating the game and the graphics driver.
CURRENT PLAYER-REPORTED
Save-loading crashes
Reported as a save that loaded fine before and no longer does.
CURRENT PLAYER-REPORTED
Post-mission transition crashes
Reported on the Mission-to-Den transition, occasionally passing on a retry.
CURRENT PLAYER-REPORTED
Whole-system freeze / display loss
Reported by a smaller number of PC players. A system-level symptom, handled conservatively on this page.
CURRENT PLAYER-REPORTED
Beskar save still missing
If it happens on the current patch, it is a current report — not the issue the patch documented as fixed.
UNRESOLVED
Every pattern in the status matrix below is labelled either official or player-reported, so the two never share a row without saying which one it is.
The actual fix ladder
Official Safe Troubleshooting Order
This is the whole order. Anything past step 8 belongs to a report, not to your machine.
- Step 1
Confirm the buildofficial
Check that you are on Patch 1.1. An old symptom on an older build is a different problem.
- Step 2
Restart the game, then the deviceofficial
A full restart of the game and then the machine is the publisher’s own first step, and it costs nothing.
- Step 3
Check platform service stateofficial
Confirm the store / console service Zero Company depends on is up before reading a launch failure as a game fault.
- Step 4
Clear the supported cacheofficial
Clearing the cache through the platform’s own supported option is listed in official guidance. It is safe and reversible because the platform manages it.
- Step 5
PC: verify or repair the game filesofficial
Steam, the EA App and Epic all have a verify / repair action. Use the launcher you actually installed from.
- Step 6
PC: current supported graphics driverofficial
The patch updated the recommended driver baseline, so a supported driver is part of the baseline — not a universal fix.
- Step 7
Reproduce the exact triggersymptom-specific
Same Mission, same action, same save. This is what turns “it crashes” into a report somebody can act on.
- Step 8
Report it if it still reproduceslow-risk
A repeatable reproduction is worth more than any file-level experiment, and it is the only route to a real fix.
This is the whole recommended order. A long list of file edits, registry changes, overlays disabled one at a time and clock or voltage changes is not a troubleshooting order — it is a way to lose an evening and a save.
Platform
PC Crash Checklist
PC is the only platform with a driver, launcher and file-repair step, so it is the only one with a longer list.
In order
- 1. Is the game updated to the current patch?
- 2. Is the operating system updated?
- 3. Is the graphics driver a current supported version?
- 4. Have the game files been verified or repaired?
- 5. Is the store / EA service reachable?
- 6. Has the supported cache been cleared?
- 7. Is there enough free system storage?
Steps one to six come from the publisher’s own guidance. Anything past that should be decided by the symptom, not by a generic list.
GTX 10 / RTX 20 Performance Note
The patch notes recommend turning off Environment Geometry Detail for players on a GTX 10-series or RTX 20-series card that meets the minimum specification, to reduce complex environment geometry cost.
This is an official performance recommendation — not a universal crash fix, and not a repair step for a hard freeze.
Platform
PS5 Crash Checklist
There is no driver or launcher step to work through here, so the console sequence is genuinely shorter.
In order
- 1. Is the game updated to the current patch?
- 2. Is the PlayStation system software updated?
- 3. Has the game been restarted?
- 4. Has the console been fully restarted, not only put to sleep?
- 5. Is the platform service reachable?
- 6. Has the supported cache been cleared where the platform offers it?
- 7. Does the same point reproduce it?
Boundary
There is no driver, launcher or file-repair step on PlayStation. The sequence is update, restart, service state, cache, reproduce, report — and the reports this page cites are player reports, not a confirmed defect list.
Platform
Xbox Crash Checklist
Same shape as PS5, with one addition: restart the console properly rather than resuming from sleep.
In order
- 1. Is the game updated to the current patch?
- 2. Is the Xbox system software updated?
- 3. Has the game been restarted?
- 4. Has the console been fully restarted, not only put to sleep?
- 5. Is the platform service reachable?
- 6. Has the supported cache been cleared where the platform offers it?
- 7. Does the same point reproduce it?
Boundary
Xbox has no driver or launcher step either. Restart the console properly rather than resuming from sleep, and treat post-patch crashes as current reports rather than as something the patch was meant to have closed.
Separation
Performance vs Freeze
“The game is lagging” and “the game is stuck” send you to different parts of this site.
Low FPS / stutter
The game continues responding while the frame rate drops or hitches. That is performance, and it is not this page’s main subject.
Patch 1.1 included visual stutter fixes and a published performance recommendation, so a stutter is worth a patch check before anything else.
Freeze / softlock
The game state stops advancing — the turn never resolves, control never returns, or the process ends. That is the failure this page diagnoses.
That is what the diagnostic above and the rest of this page are for.
Maintenance table
Crash & Freeze Status
A fixed issue and a current report are two different columns, and this table never lets them look the same.
| Issue | Status | Note |
|---|---|---|
| Various launch crashes | OFFICIAL — FIXED | Addressed in Patch 1.1. |
| Beskar-mode crash | OFFICIAL — FIXED | Documented as fixed in Patch 1.1. |
| Temporary Beskar save deletion | OFFICIAL — FIXED | Documented as fixed in Patch 1.1. |
| Save corruption from a forced shutdown | OFFICIAL — FIXED | Addressed in Patch 1.1. Forced shutdowns are still not recommended. |
| Rare intro / main-menu softlock | OFFICIAL — FIXED | Documented as fixed in Patch 1.1. |
| Combat actions not processed correctly | OFFICIAL — FIXED | Fixes shipped in Patch 1.1. |
| Visual stutter | OFFICIAL — FIXED | Addressed in Patch 1.1. |
| Combat crashes and freezes | PLAYER-REPORTED | Players report these on PC and on consoles after the patch. |
| Enemy-turn softlocks | PLAYER-REPORTED | Reported through the release window and afterwards, including after a heal or reaction action. |
| Startup crashes and black screens | PLAYER-REPORTED | Reported after updating the game and the graphics driver. |
| Save-loading crashes | PLAYER-REPORTED | Reported as a save that loaded fine before and no longer does. |
| Post-mission transition crashes | PLAYER-REPORTED | Reported on the Mission-to-Den transition, occasionally passing on a retry. |
| Whole-system freeze / display loss | PLAYER-REPORTED | Reported by a smaller number of PC players. A system-level symptom, handled conservatively on this page. |
| Beskar save still missing | UNRESOLVED | If it happens on the current patch, it is a current report — not the issue the patch documented as fixed. |
Below the official order
Community Workarounds
These exist, and they are labelled. None of them is a general fix, and none of them is worth a campaign save.
Pause and unpause during an enemy-turn stall
Players report that opening and closing the pause menu occasionally restores a stalled enemy turn.
Community-reported and not reliable in every case — in the same discussions other players report it doing nothing at all.
Retry a post-mission transition
A transition crash that repeats can sometimes pass on a later attempt.
Community-reported. Do not retry a transition crash by force-closing; that risks the save it is trying to write.
Community workarounds sit below the official order on purpose. None of them is a general fix, and none of them is worth a campaign save.
Tool
Search by Symptom
Search the observed pattern records. Every result says whether it is documented as fixed or currently reported, and what the first safe action is.
Type at least three characters. The search reads the observed pattern records and returns what is officially documented as fixed, what players still report, and the first safe action.
Next step
Prepare a Bug Report
The diagnostic above already assembled the context. This builds the full report: what, where, on what, and what changed recently.
For a crash, an error message or crash code is usually worth more than a video. Note whether the game showed anything at all before it closed.
Platform: PC Game version: Patch 1.1 Failure: Crash Stage: Before the main menu Last action before it happened: Explosion / effect Expected: The game keeps running, or the turn resolves and the state advances. Actual: Not recorded Reproduction: Not recorded Reproducibility: Intermittent Save mode: Standard campaign What changed recently: Game updated Evidence available: Screenshot
Reproducibility changes the priority of a report, but this page never turns it into a bug probability. “Every time at the same point” is a stronger report than “once”; neither is a percentage.
FAQ
Crash & Freeze Questions
Why does Zero Company keep crashing?
Crashes are reported at several different points — startup, save loading, combat, and the Mission-to-Den transition — so “it crashes” is not one problem. Check the build, identify where it stops, and follow the official low-risk order before changing files. Patch 1.1 included a batch of crash fixes, but stability reports still exist after it.
Why does Zero Company freeze during combat?
Players report freezes around explosions, impacts and triggered effects. That is a reported trigger rather than a confirmed cause, so record the last action and whether it reproduces at the same action instead of assuming a hardware fault.
Why is the enemy turn stuck?
If animations and the camera are still running while the turn never ends, that is a softlock rather than a crash. A short stall can be processing; a repeatable or indefinite stall is worth recording, and how long you waited matters less than whether it ever resumes.
Why won’t the AI finish its turn?
The battle state either advances or it does not. Note the last AI action — a heal, a reaction shot, a movement or an ability — and whether it happens at the same trigger every time. That detail is what makes the report useful.
Why does Zero Company crash after a mission?
The Mission-to-Den transition has several steps: the result, the cutscene, the load and the Den itself. Which step fails decides whether your save is involved, so note the exact point before retrying.
Why does Zero Company crash when loading my save?
Check whether a different save or a new campaign still loads. If another save works, the failure is specific to that save or the state it holds. That is different from an installation or driver problem, and the fix path is different too.
Why does Zero Company crash on startup?
Start with the build, a restart of the game and the device, the platform service state, and on PC a file verification. Startup failures are also reported right after a graphics driver change, so record that change rather than immediately updating again.
Why do I get a black screen?
A black screen with audio, a black screen with nothing, and a freeze on the logo are different symptoms. Check whether the system menu still opens and whether only the game is affected — that decides whether it is a game-level or a system-level problem.
Why does my whole PC freeze?
A machine that loses display and needs a hard reset is a system-level symptom. Stop repeating the same crash, record the operating system, driver, build and point of failure, and take the official PC support path rather than changing firmware or voltages.
Did Patch 1.1 fix crashes?
Patch 1.1 shipped a batch of crash and stability fixes, including a Beskar crash, a temporary Beskar save deletion, save corruption from forced shutdowns, a rare main-menu softlock and visual stutters. That is a set of fixes, not a statement that crashes are gone.
Is Zero Company still crashing after Patch 1.1?
Yes — players still report combat crashes, startup crashes, save-loading crashes and post-mission transition crashes on the current patch. Those are player reports rather than an official known-issues list, and this page labels them as such.
How do I verify Zero Company game files?
Use the verify or repair action in the launcher you installed from — Steam, the EA App or Epic. It is one of the publisher’s own recommended steps and it is safe, so it belongs early rather than after file-level experiments.
Should I update my graphics driver?
A supported driver is part of the official baseline, and the patch notes updated the recommended driver version. But if the problem began immediately after a driver change, record that change as part of the diagnosis instead of updating a second time.
Should I roll back my graphics driver?
A rollback is a configuration-specific step, not a first-screen fix. It comes after the official low-risk steps, and it should be recorded as a change you made rather than presented as the cause.
What should I do if my Beskar save disappears?
Confirm your build first — a temporary Beskar save deletion was documented as addressed in Patch 1.1. Do not delete, replace or manually edit the only save, and do not disable cloud sync as an early move.
Can force closing Zero Company corrupt my save?
A forced shutdown is not a normal exit, and some save corruption caused by sudden shutdowns was addressed in a patch. Use it only when the game is genuinely unrecoverable, and avoid closing the game during a save transition.
Why didn’t my latest progress save?
Official guidance notes that progress may not have finished saving if you exit before regaining control of Hawks. Where the game still responds, wait for control to return or for the Mission to start before exiting.
How do I fix Zero Company crashes on PS5?
Update the game and the system software, restart the game, fully restart the console rather than resuming from sleep, check the service state, clear the supported cache where the platform offers it, then reproduce the exact point and report it.
How do I fix Zero Company crashes on Xbox?
Update, restart the game, fully restart the console, check the service state, reproduce the exact point and report it. Post-patch crashes on Xbox Series X have been reported, so do not assume the patch closed every console crash.
How do I report a reproducible crash?
Send the platform, the build, the failure type, the stage it happens at, the Mission and Objective if it is tied to one, the last action before it, what you expected, what happened, whether it reproduces, and any capture you have. The report builder on this page assembles that for you.
Related troubleshooting
Where to Go Next
Troubleshoot STAR WARS Zero Company crashes, freezes, black screens, enemy-turn lockups, loading crashes and save problems on PC, PS5 and Xbox. Check the current patch, identify when the issue occurs and follow low-risk fixes before changing files or saves.