Everyone says the same thing when Star Wars Zero Company crashes: update your drivers, verify game files, reinstall. That advice works for startup crashes. It works when the game won’t launch at all. But crashes that happen thirty minutes into a firefight? Those are different animals entirely. The generic fixes miss the real culprits.
What causes a game to run fine for a while, then suddenly drop to desktop? Shader compilation failures. GPU instability under sustained load. Memory leaks from overlays. Power delivery sag. These are not problems that a driver update alone solves. This guide targets the actual reasons Star Wars Zero Company crashes during gameplay — not at the menu, not during the intro, but when you are in the middle of combat.
Why “Update Your Drivers” Is Not Enough
Outdated drivers can cause crashes. That is true. But the current driver version from Nvidia (572.16 as of this writing) has known issues with Unreal Engine 4 games, which Star Wars Zero Company uses. Rolling back to an earlier driver sometimes fixes more than the latest one does.
Nvidia users: download the previous Game Ready driver from Nvidi’s website, not through GeForce Experience. Use the “custom” installation option and check “perform a clean installation.” This removes all previous driver files, including the corrupted shader cache that often triggers crashes mid-game. AMD users: use the AMD Cleanup Utility before installing the latest Adrenalin driver. A clean install wipes out the old shader cache that rebuilds incorrectly.
Shader Compilation: The Hidden Crash Trigger
Star Wars Zero Company compiles shaders at first launch and during loading screens. If that compilation fails silently, the game may crash later when it tries to render something that depends on a broken shader. The fix is not just verifying files — it is clearing the shader cache entirely.
Open Disk Cleanup (type it in the Start menu). Select “DirectX Shader Cache.” Delete it. Then restart your PC. The next launch will recompile all shaders from scratch. This takes longer, but it eliminates half of the mid-game crash causes I have seen reported on forums.
For Nvidia cards, also delete the contents of %USERPROFILE%AppDataLocalNVIDIADXCachecodecodecodecodecodecode and GLCachecodecodecodecodecodecode. AMD users should delete %USERPROFILE%AppDataLocalAMDDxCachecodecodecodecodecodecode. Do this after the driver clean install, not before.
Overlays Are Crashing Your Game — Not Just Annoying You
Steam overlay. Discord overlay. Nvidia overlay. EA app overlay. Xbox Game Bar. Each one hooks into the game’s rendering pipeline. When any of them has a memory leak — and they all do — the game runs out of VRAM and crashes to desktop without an error message.
Disable every overlay before launching Star Wars Zero Company. Steam: right-click the game, Properties, General, uncheck “Enable the Steam Overlay while in-game.” EA app: click the three lines top-left, Settings, Application, turn off “In-game overlay.” Discord: User Settings, Game Overlay, toggle off. Nvidia app: Settings, General, turn off “In-game overlay.” Xbox Game Bar: Windows Settings, Gaming, Game Bar, turn it off.
Do not just toggle them off. Close the applications entirely. Discord and Steam can still inject hooks even with overlays disabled. Kill them from the system tray before launching the game.
Frame Generation and Upscaling: Performance Gains That Break Stability
Star Wars Zero Company supports DLSS Frame Generation and FSR 3. These technologies boost frame rates, but they also increase GPU load and memory bandwidth usage. On cards with 8GB VRAM or less, frame generation can push VRAM usage over the limit during intense scenes, causing an immediate crash.
Turn off frame generation in the game’s graphics settings. Set upscaling to TSR (Temporal Super Resolution) instead of DLSS or FSR. TSR uses less VRAM and is more stable on this engine. Also disable Nvidia Reflex Low Latency — it adds input lag reduction but can conflict with frame pacing, causing stutter that leads to a crash.
If you have an Nvidia card, cap the frame rate to 60 FPS in the game settings or via Nvidia Control Panel (Manage 3D Settings, Max Frame Rate). High frame rates expose unstable GPU clock speeds that only show up after 20 minutes of gameplay.
The Config File Change That Stopped My Crashes
Inside the game’s config file, there is a setting called bNANITE_ENABLEDcodecodecodecodecodecode. Nanite is Unreal Engine 5’s virtualized geometry system. It is a resource hog. Setting it to false forces the engine to use traditional LODs, which are less demanding.
Navigate to %USERPROFILE%AppDataLocalStar Wars Zero CompanySavedConfigWindowscodecodecodecodecodecode. Open GameUserSettings.inicodecodecodecodecodecode. Search for bNANITE_ENABLED=Truecodecodecodecodecodecode. Change it to Falsecodecodecodecodecodecode. Save the file. Right-click the file, Properties, check “Read-only.” This prevents the game from overwriting the change on next launch.
If that does not help, rename the entire Configcodecodecodecodecodecode folder to Config.backupcodecodecodecodecodecode. The game will create a fresh config on next launch. You lose your graphics settings, but you also lose whatever corrupted setting was causing the crash.
Background Applications That Look Harmless
Hardware monitoring tools are common crash triggers. MSI Afterburner, RivaTuner Statistics Server, HWiNFO, and EVGA Precision X all hook into the GPU driver to read temperatures and clock speeds. That hook can interfere with the game’s own GPU access, especially during shader compilation or when the game queries the driver for available VRAM.
Close them. Not minimize — close. If you need temperature monitoring, use the game’s built-in performance overlay or the Windows task manager.
Also disconnect USB devices that are not essential. Racing wheels, joysticks, extra monitors, and USB audio interfaces can cause DirectInput or audio device conflicts that manifest as crashes during gameplay. The game polls connected controllers frequently. If a controller’s driver is buggy, the polling can hang and crash the game.
Power Delivery and GPU Clock Stability
Desktop users: if your PSU is undersized or aging, the GPU may draw more power during a heavy scene than the PSU can deliver. The GPU crashes to protect itself. Laptop users: thermal throttling causes clock speed drops that the game does not handle gracefully.
Use MSI Afterburner (ironically) to check your GPU clock speed during gameplay — but close it after checking. If the clock speed drops suddenly before a crash, you have a power or thermal issue. For laptops, elevate the rear of the machine and cap the CPU maximum processor state to 99% in Windows Power Options to disable turbo boost. This reduces heat significantly.
For desktops, try underclocking the GPU core by 100 MHz using Afterburner. If the crashes stop, your card was unstable at stock clocks — a common issue with factory overclocked cards. Return the card to stock settings in Afterburner and then apply the underclock.
The Last Resort: Reinstall to a Different Drive
If nothing works, uninstall the game. Restart your PC. Install it to a different SSD — not the same drive where your OS lives. If it was on C:, move it to D:. If it was on D:, move it to C:. The game may have corrupted files in the original installation path that a simple verify does not catch because the verification checksums are also corrupted. A fresh install on a different drive forces a full redownload of all files.
One nuance few guides mention: the EA app and Steam both store download caches that can corrupt the game files during installation. Clear those caches before reinstalling. Steam: Settings, Downloads, Clear Download Cache. EA app: click the three lines, Help, App Recovery, Clear Cache. Then reinstall.
