A crash on launch is one thing. A crash when loading a save file is another animal entirely. You’ve already gotten past the hard part — the game started, you played, maybe you cleared the tutorial on Vardos or got halfway through a side quest on a Coruscant lower level. Then you quit. Later, you double-click the save, and instead of the loading screen giving way to gameplay, you get the black screen, the hard freeze, or the Star Wars Zero Company crash reporter window spawning with a low-level fatal error.
This is not a rare bug. And it is not fixed by the same checklist that fixes startup crashes.
The cause is usually one of three things: a corrupted save state that stretches back several autosaves, a shader cache that has gone stale in a way that only manifests when streaming in specific asset-heavy regions, or a driver-level issue that surfaces on heavy scene transitions. Each has a different fix, and the fixes below are ordered from least destructive to most aggressive. Start at the top. Do not skip ahead unless you are comfortable losing some progress.
Why the Crash Happens on Save Load Specifically
The game engine builds your world state from the save file on load, then kicks off shader compilation for the area. If that save references a world state with corrupted geometry data — say, an object that no longer exists in the current game version — the engine will attempt to load a missing asset and crash. The crash reporter triggers because the engine’s memory heap is left in an unstable state, not because your hardware is failing.
One concrete scenario: you saved inside a settlement right before a scripted event triggered. The game then updated. The event’s script changed between patches, but your save file still contains a pointer to the old script. The engine chokes on the mismatched reference when it tries to resolve the event on load.
The second scenario is a driver timeout. If you are running an overclocked GPU and the save loads in a visually dense area — think the rain-soaked plaza on Kijimi at night — the sudden spike in draw calls can exceed the driver watchdog timer. Windows will reset the GPU, and the game will present the crash reporter instead of reinitializing the Graphics API.
First Step: Reboot and Reload the Most Recent Autosave
Before touching any files, do the simplest thing. Restart your PC. Not shut down and boot up — restart. Windows fast startup can leave driver remnants in memory that cause issues on clean session starts.
Then launch the game and attempt to load the save. If it crashes again, try loading the previous autosave instead of the manual save. The game keeps a rolling cycle of three autosaves, and one of them is often free of the corrupted state.
Wait. That advice skips something.
If you are on Steam, your save files are being synced to the cloud. If the local save is corrupted, the cloud version might be fine — or it might be equally corrupted because Steam uploaded the bad file over the good one. Check the timestamp on your cloud save before you overwrite anything. If you have a known-good cloud save from an hour before the crash, delete the local save file and force Steam to pull the old cloud version.
The save files for Star Wars Zero Company live in your user directory under Documents. The exact folder is named Star Wars Zero Companycodecodecodecodecodecode. The extension is .savcodecodecodecodecodecode. Back up the entire folder before you delete anything.
Clear the Shader Cache Before You Blame Your Save
Shader cache corruption does not always cause crashes at launch. Often, it causes crashes the moment the engine tries to compile shaders for a new scene loaded from a save file. The game will get as far as showing the loading icon, then freeze. The crash reporter appears minutes later.
To clear the cache without third-party tools, use Windows Disk Cleanup:
- Open the Start menu and type
disk cleanupcodecodecodecodecodecode. - Select the drive where Windows is installed.
- Click “Clean up system files.”
- Check the box for “DirectX Shader Cache.”
- Run the cleanup.
That clears the global DirectX cache. Steam games have a separate per-game shader cache stored in Steamsteamappsshadercachecodecodecodecodecodecode. Delete the folder matching Star Wars Zero Company’s app ID.
The first launch after clearing will take longer. The loading screen will sit at about 60% for a while. That is the engine rebuilding shaders. Let it finish.
Verify the Save File’s Integrity via a New Save
If clearing the shader cache does not resolve the crash, test whether the save file itself is the problem. Create a new game, skip the intro cutscene, make a manual save as soon as you gain control of your character. Exit to the main menu and load that new save.
If the new save loads without a crash, the problem is isolated to your old save file. You have two options: roll back to an older save or start a new playthrough.
Rolling back means you lose progress. It is the only way to save a corrupted save file. But here is a less-known trick: load a much older save, then save again after entering a new area. This forces the engine to rebuild the world state fresh, dropping any corrupted references that carried over. It does not always work, but it has a higher success rate than trying to force-load the corrupt save.
Set the Game to High-Performance GPU Mode
Laptops with hybrid graphics are prone to a specific failure: the save loads on a screen where the engine expects the dedicated GPU, but the operating system has handed the process to the integrated GPU. This causes a driver-level conflict that ends in the crash reporter.
For Windows 11, open Settings → System → Display → Graphics. Find Star Wars Zero Company in the installed apps list. Click Options and select “High performance.” For Steam, you can also force this via launch options using the command line, though the Windows settings route is more reliable.
If the game is not listed, browse to the .exe in the installation folder and add it manually.
Driver Rollback: When the Latest Update Breaks Save Loading
Updating your GPU driver is standard advice. But bleeding-edge driver branches have a history of breaking save loading in games that use deferred rendering with packed world streaming — which Star Wars Zero Company does.
If the crash started after a driver update, roll back to the previous driver version. Nvidia’s 561.09 hotfix branch was pulled in 2024 for causing crash-on-load in several DX12 titles. If you are on that branch or newer, use Display Driver Uninstaller in safe mode, then install the previous stable branch.
For Nvidia, use the Studio Driver branch if you are on GeForce Experience’s Game Ready branch. The Studio branch is built on an older, more stable code base. For AMD, use the Recommended branch rather than the Optional branch.
Do this before you assume your save is corrupted. A driver regression can corrupt the memory state of any game when loading a save file, and it is reversible without losing progress.
Increase Virtual Memory to Stop Mid-Load Freezes
If the crash happens when the loading bar is nearly full, the game may be running out of virtual address space. Star Wars Zero Company’s save files can exceed 500 MB if you have cleared large sections of the map and the game is holding world state data. Combined with the engine’s memory overhead, this can exceed your default paging file size.
Navigate to Advanced System Settings → Performance Settings → Advanced → Virtual Memory. Disable “Automatically manage paging file size” and set a custom size. For a system with 16 GB of RAM, set the initial and maximum size to 24576 MB. For 32 GB systems, 32768 MB. This allocates more headroom for the game’s memory allocations during save loading.
This is a stopgap, not a permanent fix. But it will confirm whether the crash is memory starvation or a deeper engine bug.
Use the Command Line to Restore the Game’s Integrity
Start with the Windows built-in repair tools. They are free, and they fix a class of corruption that game launchers cannot detect.
Open a terminal as administrator. Run:
“`
sfc /scannow
“`
Wait for the process to complete. Then run:
“`
DISM /Online /Cleanup-Image /RestoreHealth
“`
Restart your PC. This repairs protected system files that can interfere with the game’s ability to allocate memory. If the load crash is accompanied by an error code referencing 0xc0000005codecodecodecodecodecode (access violation), this step has a high likelihood of resolving it. The access violation occurs when the game reads a memory address that Windows has marked as protected due to a corrupted system file.
Disable Third-Party Overlays That Interfere with Save Loading
This is a niche one, but a real one. Discord’s in-game overlay, by default, hooks into the game’s render pipeline to display the overlay on top of gameplay. When you load a save file, the game initializes the render thread. If the overlay hook has a stale reference to a now-unloaded DLL, it triggers a GPU crash dump.
The same applies to:
- GeForce Experience overlay
- AMD Software overlay
- Xbox Game Bar
- RTSS (RivaTuner Statistics Server) if you are monitoring frametimes
RTSS is the worst offender. It injects its own frame limiter into the game process, and when the game rebuilds its render state on save load, the injection can conflict. If you are running RTSS for frametime graphs, disable it before loading a save.
Edit the Engine Config to Load in Safe Mode
This is the final approach that does not require reinstalling the game. You can force the engine to skip certain asset loading on save load by editing the config file.
Navigate to DocumentsStar Wars Zero CompanyConfigcodecodecodecodecodecode and open Engine.inicodecodecodecodecodecode. Add the following lines under the [SystemSettings]codecodecodecodecodecode section:
“`
r.ShaderPipelineCache.Enabled=0
r.GPUSceneUploadEveryFrame=1
r.Streaming.PoolSize=512
“`
The first line disables the shader pipeline cache, which forces a recompile but reduces the likelihood of a stale cache entry crashing the load. The second line forces the engine to upload the full GPU scene every frame, which is slower but prevents the engine from assuming a previous scene state. The third line caps the streaming pool, which reduces memory spikes during load.
If this fixes the crash, the problem is the shader pipeline cache or the GPU scene management, not your save file.
Reinstall the Game Without Deleting Your Save
Reinstalling should be a last resort. The save files are stored outside the installation folder, so two reinstalls will not hurt them — but the removal process will clear the game’s local cache, which lives in the install directory.
Uninstall the game through Steam. Then delete the remaining folder in Steamsteamappscommoncodecodecodecodecodecode manually, even after the uninstaller finishes. The uninstaller commonly leaves the Savedcodecodecodecodecodecode folder behind. Delete it. Reinstall.
After reinstalling, launch the game and load your save. If it crashes, the problem is definitively your save file. At that point, go back to the loaded autosave you created earlier and accept the loss.
FAQ
Will I lose all my progress if my save file is corrupted?
No. The game maintains three rolling autosaves alongside your manual saves. The autosaves are separate files and are often unaffected by the corruption that hit your manual save. Attempt loading each one in order. If all of them are corrupted, the game’s cloud save system may still hold an older version.
Is this crash caused by my hardware overheating?
No. The crash reporter message can reference a GPU timeout, but that is often the driver resetting, not the hardware failing. If your GPU temperature is below 80°C in a normal gaming session, thermal throttling is not the cause.
Does DLSS or FSR make this crash worse?
Yes. Upscaling technologies rebuild the frame buffer on load, and a corrupted frame buffer reference can crash the game. Turn off DLSS or FSR entirely before loading a save. The game will run at native resolution, but the load will be more stable.
Can I recover a save that was overwritten by a newer version?
Steam Cloud keeps version history for some games. Star Wars Zero Company uses a rolling cloud sync, so you cannot fetch an arbitrary old version from Steam’s servers. Your only hope is a local backup from a file sync utility like File History on Windows.
The Autosave Is Your Safest Bet
Here is the nuance most guides miss: the game’s second autosave slot is the most stable one. The first slot is overwritten frequently and can hold a partially written state if the game crashed during a save. The second slot is older and written in a completed pass. If your manual save is corrupted, the second autosave slot is your highest-probability recovery point.
And one more detail. Star Wars Zero Company’s save system writes a binary header at the beginning of each file. If you open the file in a hex editor, the header should start with the bytes 5A 43 4Fcodecodecodecodecodecode (ZCO). If those bytes are corrupted or missing, the save is unrecoverable. Do not waste time on mods or third-party save editors for a file with a damaged header.
