No amount of GPU driver updates will save you if Windows itself is holding corrupted files. When Star Wars Zero Company crashes to desktop, throws low-level fatal errors, or refuses to launch entirely, the culprit is often a damaged system component—not the game, not your graphics card, not a full drive. This guide targets that specific failure mode with the exact repair sequence that works.
The Diagnostics Hierarchy: Don’t Start With the Nuclear Option
Before you run a single repair command, establish what kind of corruption you’re dealing with. The crash reporter window itself gives you clues. If you see a Low Level Fatal Error, the game executable is having trouble talking to Windows core functions. A GPU Crash Dump Triggered error points elsewhere—but system file damage can cause that too, by corrupting the DirectX runtime dependencies the GPU relies on.
The pragmatic approach is escalation. Start with the repair that takes 90 seconds, not the one that takes 40 minutes. You will waste an afternoon if you go straight for a Windows reset.
The Core Repair Sequence: SFC and DISM Done Right
Most guides tell you to run sfc /scannowcodecodecodecodecode and move on. That’s incomplete. The System File Checker only verifies protected system files against a local cache—and if that cache is corrupted, SFC will tell you everything is fine while your game keeps crashing. The correct sequence requires two commands, run in the right order.
Open an elevated terminal: right-click Start, select Terminal (Admin), and confirm the User Account Control prompt. Run this first:
“`
sfc /scannow
“`
Wait for it to finish. If it reports corrupted files it could not repair, do not panic. That’s expected when the component store itself is damaged. Now run the DISM command:
“`
DISM /Online /Cleanup-Image /RestoreHealth
“`
This pulls fresh system files from Windows Update. It takes longer—expect 10 to 40 minutes depending on your connection and disk speed. When it completes, restart your PC and run sfc /scannowcodecodecodecodecode again. This second pass catches everything the first pass couldn’t fix, because now the local cache actually has healthy files to work from.
Why NVIDIA Drivers Worsen the Problem
Here’s the non-obvious part. After repairing system files, your next step is reinstalling your GPU driver—but only using a clean installation. The corrupted system files often leave remnants of failed driver updates scattered across the Windows driver store. These leftover files can trigger a GPU Crash Dump Triggered error even when the game and the system seem otherwise fine.
Use the Nvidia App or GeForce Experience, but select Custom Installation and check the Perform a clean installation option. For AMD users, the equivalent is the Factory Reset option in the Adrenalin installer. Intel Arc users should use the DCH driver package from Intel’s site, not a third-party updater.
This matters specifically for Star Wars Zero Company because the game’s engine compiles shaders heavily on first launch. A corrupted driver installation causes shader compilation to crash repeatedly. The stuttering and crashing you experience may have nothing to do with system files anymore—but the system file corruption caused the driver corruption. Fix them in this order or you’ll chase your tail.
When the Component Store Is Beyond Repair
If DISM fails with error code 0x800f081f or 0x800f0906, the Windows Update service can’t provide healthy files. Your machine could be behind a proxy, running an outdated Windows 10 version, or dealing with a network filter that blocks the update delivery.
The workaround: use the install.wim file from a Windows ISO, instead of Windows Update. Mount the ISO, navigate to the sourcescodecodecodecodecode folder, and run:
“`
DISM /Online /Cleanup-Image /RestoreHealth /Source:D:sourcesinstall.wim /LimitAccess
“`
Adjust the drive letter to match your ISO mount point.
If that still fails and the ISO matches your Windows version, your best move is an in-place upgrade repair. Run the setup.exe from the ISO. It reinstalls Windows while keeping your files, settings, and installed applications. It takes about an hour, but it resolves corruption that neither SFC nor DISM can touch. Back up your critical data first, regardless.
Verifying Game Files After the Repair
Once your system is healthy, verify Star Wars Zero Company’s game files through Steam. Right-click the game in your library, select Properties, go to Installed Files, and click Verify integrity of game files. This is standard advice, but the timing matters more than most realize.
If you verify before repairing system files, Steam may report everything as fine—the game files themselves are intact. The problem is in Windows, not the game. If you verify after repairing and Steam does find issues, download and install the correct files and don’t launch until Steam reports 100%.
You should also clear the DirectX Shader Cache via Windows Disk Cleanup. Corrupted shader caches cause repeated or stuck shader compilation. The first launch after clearing takes longer, because the engine rebuilds the shaders from scratch. That is normal. That lengthened launch is also a good sign—it means shader compilation is running without hitting the corrupted files the cache was holding.
The Firewall and Overlay Factor
System file corruption rarely happens in isolation. After repairing, check that Windows Firewall isn’t blocking the game’s executable. Go to Windows Security, Firewall & Network Protection, and ensure Star Wars Zero Company is allowed through on both Private and Public networks. Damaged system files sometimes reset these rules, silently breaking online connectivity and causing crashes when the game tries to reach a server.
Also disable overlays temporarily. Discord, Steam, the Nvidia App, Xbox Game Bar, and AMD software all inject code into running processes. If any of those injection points got corrupted during the system file mess, the overlay crashes the game. Test without overlays first. Re-enable them one by one after confirming the game runs stable. This isolates whether an overlay, rather than system state, is causing the issue.
When the Fix Creates a New Problem
One edge case deserves attention. After running DISM and reinstalling drivers, some users report the game launches but runs worse—lower frame rates, longer load times, occasional hitches. This isn’t a failed repair. DISM replaced system files that were actively cached in memory. The first few sessions after repair force the system to rebuild caches and the game engine to recompile shaders. Performance normalizes within several hours of use.
Pushing through is usually the right call. But if you still see crashes after everything, consider that the problem is not the system at all. Hardware instability—an overstretched overclock, failing RAM, a GPU at the edge of its thermal envelope—mimics corrupted system file symptoms precisely. Run a memory diagnostic and stress test the GPU before reinstalling Windows for the second time. The system files were never the problem; your hardware just wears the mask well.
