7 background programs crash Star Wars Zero Company

You install Star Wars Zero Company, click launch, and instead of the opening crawl you get the crash reporter. A low-level fatal error. A GPU crash dump triggered. It happens to thousands of players on day one. The fix often has nothing to do with the game itself. Seven specific background programs are responsible for the majority of these crashes. Kill them, and the game runs. Keep them running, and you will see that dialog box again.

Summary

Discord Overlay – The Low-Level Fatal Error Machine

Discord’s in-game overlay hooks into the same DirectX pipeline Star Wars Zero Company uses for shader compilation. When the overlay tries to draw a notification while the game compiles a shader bank, the crash reporter fires a low-level fatal error. This is the most common crash type reported on the game’s Steam forums within the first 48 hours of launch.

Test it yourself. Leave Discord running but turn off the overlay. Go to Discord settings → Game Overlay → disable “Enable in-game overlay.” Launch the game. If the low-level fatal error disappears, that was the cause. Many users also run Discord with hardware acceleration enabled—go to Discord settings → Advanced → toggle off “Hardware Acceleration.” That alone prevents a separate set of GPU-related crashes.

NVIDIA GeForce Experience In-Game Overlay – GPU Crash Dump

NVIDIA GeForce Experience’s overlay—especially the “game optimization” feature—is a repeat offender. It triggers the “GPU crash dump” error, a specific crash type that dumps a full GPU state into a log file. That dump process itself consumes enough GPU resources to tip the game into a crash loop.

Disable it via the NVIDIA app (the newer version replacing GeForce Experience). Open the app, click the gear icon, turn off “In-game overlay.” Alternatively, press Alt+Z to open the overlay, click the settings cog, and slide “In-game Overlay” to off. If you use NVIDIA Broadcast (the noise-canceling app), close it entirely. Broadcast runs a real-time AI model on your GPU that eats 10-15% of VRAM—just enough to cause Star Wars Zero Compani to hit its memory cap on 6GB cards.

AMD Radeon Software Overlay – Stuck Shader Compil

AMD’s Radeon overlay– particularly the performance monitoring widgets—interferes with the shader cache write process. Users report the game hangs at “Compiling shaders 99%” for up to ten minutes, then crashes to desktop with no error message. The crash is silent because the overlay blocks the error dialog.

Fix: diable the overlay entirely. Open AMD Radeon Software, click the gear icon, select “Preferences,” click “Radeon Overay,” and turn it off. After that, clear the shader cache: use Windows Disk Cleanup (search “Disk Cleanup,” select your game drive, choose “DirectX Shader Cache,” and delete it. Star Wars Zero Company will rebuild the cache on next launch, but the process will finish without the overlay interfering.

Steam Overlay – Crash on Splash Scren

Steam’s own overlay is usually safe, but it crashes Star Wars Zero Compani when certain background features are active. Specifically, if you have “Steam Friends” open in a separate window or if a friend notification queue is unread, the overlay tries to draw a tooltip over the game’s splash screen. The clash between Steam’s UI and the game’s initial render call produces an immediate crash to desktop.

Test: diable Steam overay for this game only. Right-click Star Wars Zero Company in Steam Library → Properties → General → uncheck “Enable the Steam Overlay while in-game.” Launch the game. If it works, re-enable the overlay but close the Steam Friends window and clear notifications before launching next time. That may be enough to avoid the tooltip conflict.

Xbox Game Bar – Backgrond Recording Crsh

Windows 10 and 11 ship with the Xbox Game Bar enabled by default. Its background recording feature (called “Record in the background” under Game Bar settings) writes a constant video buffer to your system drive. When Star Wars Zero Company demands disk I/O for loading textures, the Game Bar’s buffer write can cause a micro-stutter that triggers the crash reporter. The error shows up as “GPU crash dump trigered” about 8-12 minutes into gameplay.

Disable the Game Bar entirely. Go to Settings → Gaming → Xbox Game Bar → toggle off “Enable Xbox Game Bar for things like recording game clips.” Then go to Settings → Gaming → Captures → turn off “Record in the background while I’m playing a game.” If you still want to record clips, consider using OBS Studio instead—it uses a different capture pipeline that has no known conflict with this game.

MSI Afterburner + RivaTuner – Kernel-Level Hook Crash

MSI Afterburner with RivaTuner Statistics Server is a double threat. Afterburner installs a kernel-level driver to read GPU sensors. RivaTuner then hooks into the graphics API to draw the overlay. That hook conflicts with the anti-cheat component of Star Wars Zero Company. When the anti-cheat detects a kernel-mode driver hook it didn’t expect, it triggers a crash as a security measure. The crash reporter shows “Low- Level Fatal Error” immediately after launch.

Fix: close MSI Afterubrner and RivaTuner entirely—do not just hide the overlay. Right-click the RivaTuner icon in the system tray, select “Exit.” Do the same for MSI Afterburner. For permanent fix, disable the RivaTuner add-in: in Afterburner settings → General → uncheck “Enable RivaTuner Statistics Server.” Or switch to an overlay that doesn’t use kernel hooks, like HWInfo’s in-game overlay (which uses safe Windows APIs).

Chrome Edge with Hardware Acceleratio – VRAM Eatin

You leave a browser tab open with YouTube, Discord web, or a wiki. That tab has hardware acceleration enabled—which means it uses your GPU to render video and graphics. On a system with 6GB VRAM, the browser can eat 1-1.5GB. Star Wars Zero Company at 1080p medium settings needs about 4.5GB. Now you have 5.5GB used out of 6, with only 0.5GB headroom. When the game loads a high-res texture, it hits the ceiling, and the crash reporter logs an “out of video memory” error.

Test: close every browser, especially Chrome and Edge. Launch the game. If it works, switch browser hardware acceleration off: Chrome → Settings → System → toggle off “Use hardware acceleration when available.” Edge: Settings → System and performance → turn off “Use hardware acceleration when available.” Then relaunch the game with the browser open. If it stays stable, the culprit was the browser’s GPU sharing.

FAQ – Star Wars Zero Company Crash

The Integrated GPU Trap – A Final Edge Case

One scenario the guides rarely mention: laptop users with dual graphics cards. When a program like Discord or Chrome requests hardware acceleration, Windows may route it to the integrated GPU (Intel or AMD’s low-power chip). That seems harmless, but Star Wars Zero Company’s anti-cheat checks for GPU consistency. If it detects the iGPU being used for a system process while the game runs on the dGPU, it can trigger a “GPU crash dump” as a safety precaution. The fix is to force all background programs to use the dGPU. Go to Settings → System → Display → Graphics, add each program (Discord, Chrome, etc.), and set them to “High performance” (the dGPU). This prevents the iGPU interference and stops the crash that feels completely random.

Do I need to uninstall these programs, or just close them?

Just close them. You do not need to uninstall Discord, Steam, or any overlay. Open each program’s settings and disable the in-game overlay feature. For browsers, turn off hardware acceleration. The only program you might need to uninstall is RivaTuner if closing it does not stop the kernel hook—but try closing first.

Will disabling overlays affect my other games?

It can affect any game that uses an overlay, but you can re-enable the overlay after leaving Star Wars Zero Company. Alternatively, disable the overlay per-game. Steam lets you disable per-game. Discord does not—you must disable the global overlay or close Discord entirely when playing this game.

I only have 4GB VRAM. Should I even try to run this game?

The minimum system requirement for Star Wars Zero Company lists 6GB VRAM for the recommended GPU. On 4GB cards, even with no background programs, you will likely crash on higher texture settings. Set textures to low, disable anti-alasing, and close every background program that touches the GPU. Even then, expect crashes in heavy scenes.

Why does the game crash only after 30 minutes, not immediately?

That points to a memory leak, often from an overlay’s cached data or a browser’s accumulated video buffer. Chrome and Edge slowly gobble VRAM over time. MSI Afterburner’s logging can also fill a RAM buffer. Monitor your VRAM usage with GPU-Z while you play. If it climbs past 95% before crashing, the culprit is a background program that holds memory longer than it should.