You’re ready to jump into Star Wars Zero Company on your Windows 11 PC. You click launch. The screen goes black for a few seconds. Then the crash reporter appears — a dialog box that offers no real help, just a shrug from the game engine. Most players immediately blame their GPU or their drivers. They download the latest Nvidia or AMD driver, restart, and try again. The crash returns. Here’s the counterintuitive truth: the fix that works in more than half these cases has nothing to do with your graphics driver version. It’s deleting a hidden folder of compiled shader data that the game stored on your SSD.
Shader caches are supposed to make loading faster. When they corrupt — and they do, especially on Windows 11’s newer graphics stack — they cause exactly the kind of compile-time crash that Zero Company throws at you. The crash reporter you see isn’t a generic “your system sucks” error. It’s a shader compilation failure that looks like a GPU fault but isn’t.
This article walks through six fixes that actually resolve the most common crashes, freezes, and startup failures for Star Wars Zero Company on Windows 11. We’ll start with the one that saves the most time.
Fix #1: Clear the Shader Cache Immediately
Why This Works
Star Wars Zero Company compiles shaders on first launch. If that process is interrupted — by a crash, a power loss, or even a background system update — the cache becomes corrupted. Windows 11 caches DirectX shaders separately in the system’s disk cleanup tool. Clearing that cache forces the game to rebuild everything from scratch.
How to Clear It
Open Windows Disk Cleanup (search for “Disk Cleanup” in the Start menu). Select the drive where Windows is installed. In the list of files to delete, scroll down and check “DirectX Shader Cache.” Click OK and delete the files. Restart your PC.
Important nuance: The very next launch of Zero Company will take longer — sometimes three to five minutes. Most players assume the game is stuck and force-quit it. Don’t. Let it finish. The shader compilation progress bar may pause at 70% for a minute, but it will complete if you leave it alone. If you kill the process, you re-corrupt the cache.
Fix #2: Disable All In-Game Overlays
The Obvious Fix That’s Easy to Skip
Overlays are the second most common cause of Star Wars Zero Company crashes. Windows 11 comes with the Xbox Game Bar enabled by default. Steam’s overlay, Discord, Nvidia GeForce Experience, AMD Adrenalin, and even hardware monitoring tools like MSI Afterburner can inject code into the game’s rendering pipeline. That injection conflicts with Zero Company’s DirectX 12 implementation, triggering the “GPU Crash Dump Triggered” error.
What to Turn Off
- Steam overlay: In your library, right-click Star Wars Zero Company, go to Properties > General, and uncheck “Enable the Steam Overlay while in-game.”
- Discord overlay: Settings > Game Overlay > toggle off.
- Xbox Game Bar: Windows Settings > Gaming > Game Bar > turn off.
- Nvidia/AMD overlays: Open their respective apps and disable the in-game overlay option.
- Any recording or monitoring software: Shut them down entirely before launching.
Fix #3: Verify Game Files — Then Verify Again
Why One Pass Isn’t Enough
Steam’s “Verify Integrity of Game Files” function catches missing or corrupt files. But for Zero Company, a single pass sometimes misses a partial download or a file that the crash reporter itself corrupted. Run it twice. The first pass will repair a few files. The second pass often finds more.
Steps
Right-click Star Wars Zero Company in your Steam library. Select Properties > Installed Files > Verify Integrity of Game Files. Let it finish. Launch the game. If it still crashes, run verify again. After the second pass, restart your PC.
Fix #4: Force DirectX 11 or Windowed Mode
Launch Options That Break the Cycle
Zero Company defaults to DirectX 12. DX12 is more resource-efficient on modern hardware, but it’s also less forgiving of driver quirks. Forcing DX11 through a launch parameter resolves many “Low Level Fatal Error” crashes. Windowed mode eliminates fullscreen optimization conflicts that Windows 11 introduces.
How to Add Launch Options
In Steam, right-click the game, select Properties, and under General look for “Launch Options.” Enter one of the following (try them in this order):
-dx11codecodecodecodecodecode-dx12codecodecodecodecodecode (if DX11 doesn’t help)-windowedcodecodecodecodecodecode
After adding a parameter, launch the game. If it crashes, swap to the next one. Remove the parameter before moving to other fixes — leaving outdated parameters can cause new issues.
Fix #5: Increase Virtual Memory (Even If You Have 32GB of RAM)
The Windows 11 Paging File Trap
Windows 11 is aggressive about memory compression. Even with abundant physical RAM, the system’s paging file can become too small for Zero Company’s memory allocation patterns during shader compilation. The result is a crash that appears random — often at the same point in the loading sequence. Increasing virtual memory gives the game a safety buffer.
How to Adjust
Search for “Advanced system settings” in Windows. Under the Advanced tab, click Settings under Performance. Go to Advanced > Virtual Memory > Change. Uncheck “Automatically manage paging file size.” Select your fastest drive (preferably an NVMe SSD). Choose “Custom size” and set both initial and maximum size to 1.5× your physical RAM. For a 16GB system, that’s 24576 MB. For 32GB, use 49152 MB. Click Set, then OK, and restart.
Fix #6: Run the Game Executable as Administrator — With a Catch
Why It Works (and When It Backfires)
Running the .exe as administrator gives the game priority access to system resources. It can bypass some Windows 11 security restrictions that block file writes during shader compilation. The catch: if you also run Steam as administrator, the overlay may behave differently. The best approach is to run only the game’s executable as admin, not Steam.
How to Set It
Go to the game’s install folder (right-click game in Steam > Manage > Browse Local Files). Find ZeroCompany.execodecodecodecodecodecode (or whatever the executable is named). Right-click > Properties > Compatibility > check “Run this program as an administrator.” Click Apply. Launch the game directly from the executable at least once to test — if it works, you can then launch from Steam normally.
FAQ
Q: Why do I get a “Low Level Fatal Error” when launching Star Wars Zero Company?
A: That error almost always comes from a corrupted shader cache or a mismatch between the game’s DirectX version and your GPU driver. Clear your shader cache (Fix #1) and force DX11 (Fix #4). If the error persists, update your GPU driver from the manufacturer’s website — not through Windows Update.
Q: Do I need to clear the shader cache every time I launch the game?
A: No. Only clear it when you see repeated crashes at the same loading point or a “shader compilation stuck” message. After a successful launch, the cache is valid. Clearing it unnecessarily only wastes the three-minute compile time.
Q: The game crashes to desktop without any error message. What should I try first?
A: Disable overlays (Fix #2). Silent crashes with no dialog are often overlay conflicts. Steam overlay and Discord are the most common culprits. If that doesn’t help, run a file verification (Fix #3) and increase virtual memory (Fix #5).
Q: Will updating Windows 11 to the latest version fix these crashes?
A: It can help, but it’s not a silver bullet. Windows updates include GPU driver rollouts and DirectX runtime fixes. Always keep your system updated, but be aware that a Windows update itself can sometimes clear or corrupt the shader cache. If crashes start after a Windows update, run Disk Cleanup for DirectX Shader Cache.
Q: Should I reinstall the game completely?
A: Rarely necessary. Only reinstall if you’ve tried all six fixes here and the crash persists. Before reinstalling, also check your drive’s free space — Zero Company needs at least 50 GB free on the install drive, and Windows 11 needs another 20 GB free on the system drive for paging file overhead.
A Final Consideration: The Anti-Cheat Factor
One edge case that doesn’t fit the standard troubleshooting script: Star Wars Zero Company uses a kernel-level anti-cheat system that interacts with Windows 11’s Virtualization-Based Security (VBS). If you’ve enabled Memory Integrity (Core Isolation) in Windows Security, the anti-cheat driver may fail to load, causing the game to crash before it even initializes the graphics engine. This is rare — it affects only systems where VBS was manually turned on, not the default Windows 11 install. But if you’re a power user who tweaked security settings, try turning off Memory Integrity temporarily (Windows Security > Device Security > Core Isolation > Memory Integrity > Off) and restart. If the game launches, the anti-cheat was your problem. Re-enable Memory Integrity afterward and check for a game patch — the developer may have updated the driver by then. That nuance — the collision between security features and game code — is the kind of conflict that generalist guides miss, because it lies outside the usual “update driver / verify files” loop. Star Wars Zero Company runs on a live-service engine; its crash landscape changes with every patch. The fixes here work today. Tomorrow, they may need one more step you’ll have to discover for yourself.
