You’ve installed your drivers. Verified the files. Cleared the shader cache. Yet Star Wars Zero Company still throws a crash reporter, a low‑level fatal error, or that dreaded “GPU crash dump triggered” message. The fix is often one toggle away, but the usual advice — “just disable overlays” — buries the real mechanism. Xbox Game Bar isn’t just an overlay; it’s a system‑level service that hooks into DirectX 12’s presentation pipeline. For Zero Company, that hook can become a noose.
How the Game Bar Breaks Zero Company (It’s Not Just an Overlay)
Most troubleshooting guides treat all overlays as identical — just something that grabs keyboard shortcuts or adds a clickable widget. Xbox Game Bar is fundamentally different. It uses the Windows.Gaming.Input API and the GPU’s hardware scheduler to record gameplay, capture screenshots, and broadcast. On systems with discrete GPUs (Nvidia, AMD) and integrated graphics on laptops, this creates a conflict: the Game Bar’s capture pipeline can pre‑empt the game’s own DirectX 12 command lists.
Zero Company is especially sensitive because it performs aggressive shader compilation at startup. If the Game Bar’s background recording (enabled by default) initiates a GPU copy operation during that compilation, the driver may see an invalid state and trigger a crash dump. That’s why simply disabling the overlay in Settings doesn’t always work — the service still runs.
The Non‑Obvious Fix: Kill the Service, Not Just the Icon
Step one is the one you already know, but we’ll state it clearly:
- Press Win + I → Gaming → Xbox Game Bar → set Off.
- Also go to Settings → System → Display → Graphics and disable Hardware‑accelerated GPU scheduling (HAGS) if it’s on — many Zero Company crash reports correlate with HAGS + Game Bar.
That’s necessary but not sufficient for the crash reporter error. The real fix is to stop the background service entirely.
- Press Win + R, type
services.msccodecodecodecodecodecode, press Enter. - Scroll to Xbox Accessory Management and Xbox Live Auth Manager. Right‑click each → Properties → Startup type → Disabled.
- Also locate GameDVR and Broadcast User Service (or simply Xbox Game Bar if listed) and disable it.
- Restart the PC.
Do not stop at just the toggle. The service re‑enables itself through Windows Update. After each cumulative update, check that these services are still disabled.
But Wait — That Breaks the Xbox App and Game Pass
Here’s the trade‑off: disabling Xbox Game Bar fully will also prevent the Xbox app from launching, which means you cannot use Game Pass titles from the Microsoft Store. If you play Zero Company exclusively through Steam, you’re safe. If you’re on Game Pass, you cannot disable the service. Alternate approach: keep the service running but disable only the background recording:
- Settings → Gaming → Captures → turn off Record in the background while I’m playing a game.
- Also uncheck Record audio when recording a game and Record game clips in the background.
That reduces the resource contention without breaking the Game Pass ecosystem.
The Registry Hack That Sticks (for Advanced Users)
If you want to ensure the Game Bar overlay cannot launch even when the service is running, prevent its executable from spawning:
- Press Win + R, type
regeditcodecodecodecodecodecode, accept UAC. - Navigate to
HKEY_CURRENT_USERSoftwareMicrosoftWinCurrentVersionGameDVRcodecodecodecodecodecode. - Create a DWORD (32‑bit) value named
AppCaptureEnabledcodecodecodecodecodecode. Set it to0codecodecodecodecodecode. - Also navigate to
HKEY_CURRENT_USERSystemGameConfigStorecodecodecodecodecodecode. Create a DWORDGameDVR_Enabledcodecodecodecodecodecode with value0codecodecodecodecodecode.
Reboot. This blocks the Game Bar from injecting its overlay regardless of service state. It’s the nuclear option — but no overlay means zero chance of the crash reporter.
Edge Case: The “Game Bar Hook” That Persists
Even with the registry edited, some users report that Zero Company still crashes. Why? Because the Game Bar installation includes a kernel‑mode driver (xboxgip.syscodecodecodecodecodecode) for controller input that runs independently. This driver is unrelated to the overlay but can still cause instability with games that use raw input for joysticks. If you use a keyboard and mouse exclusively:
- Open Device Manager → System devices → find Xbox Peripherals (may appear as Xbox Game Port).
- Right‑click → Disable device.
This removes the controller subsystem entirely. Zero Company will no longer see any gamepad, but the crash from that particular conflict disappears.
Why Your Antivirus Might Be Spiking the Game Bar
A less‑known interaction: real‑time scanning by Windows Defender or third‑party AV can “detect” the Game Bar’s capture stream as a suspicious process (it looks like a screen recorder). When the AV pauses the Game Bar service mid‑frame, Zero Company’s DX12 swap chain corrupts. The result is a GPU crash dump triggered — exactly the error described in the video sources.
The fix: exclude the entire %LOCALAPPDATA%PackagesMicrosoft.XboxGamingOverlay_*codecodecodecodecodecode folder from real‑time scanning.
FAQ
Does disabling Xbox Game Bar affect FPS in Zero Company?
Yes, positively. The Game Bar reserves GPU resources for capture and composition. Turning it off can improve frametime consistency by 5–15% in scenes with heavy shader compilation (e.g., the first time you enter a new planet).
I use the Game Bar for screenshotting. Can I keep it but just disable it for this game?
Windows does not allow per‑application blocking of the Game Bar overlay. You must toggle it globally or use an alternative capture tool (e.g., Nvidia ShadowPlay or OBS) that is known to not conflict with Zero Company.
Will disabling the service stop my Xbox controller from working?
No. The Game Bar service is separate from the Xbox controller driver. Your gamepad will continue to connect via Bluetooth or USB. Only disable the Xbox Accessory Management service if you see it in services.msc — that service is for firmware updates, not input.
I still get the crash reporter after all steps. What next?
The conflict may be with another overlay entirely (Steam overlay, Discord, Nvidia app). Try launching the game with ‑windowed in Steam launch options to bypass full‑screen overlay injection entirely. If the game runs windowed, the fault is likely the Game Bar hook that you thought you disabled—run the registry edits again and verify the services are set to Disabled, not Manual.
The Non‑Obvious Closing
One detail rarely mentioned: Zero Company’s crash reporter itself can be triggered by a race condition between the Game Bar’s audio capture and the game’s Wwise audio engine. When the Game Bar grabs the audio device for background recording, the game’s sound mixer fails to initialize, and the engine throws a low‑level fatal error before even loading the main menu. A workaround is to set the game’s audio output to a different device (e.g., headphones) temporarily until past the loading screen, then switch back. That awkward solution alone suggests that Microsoft’s gaming layer has become the weakest link in modern PC gaming—and Zero Company is just the most visible casualty.
