The common fix for laptop game crashes sounds simple: go to Windows Settings, click System, Display, Graphics, find Star Wars Zero Company, choose Options, and pick High Performance. Done. That step appears in every troubleshooting guide, including the source materials for this article. It is step eight in a 14-step list, buried between clearing shader cache and increasing virtual memory. And for a decent chunk of players, it does nothing.
Let’s be direct. That advice works only if your laptop’s graphics routing is simple, your drivers are clean, and no third‑party tool is overriding Windows’s preference. Those conditions are rarer than most guides admit. This article explains why the standard high‑performance GPU setting fails for Star Wars Zero Company on laptops, and what actually fixes the crashes.
The One‑Size‑Fits‑All Advice That Misses the Mark
Windows Graphics Settings (Settings > System > Display > Graphics) lets you assign a GPU preference per application. For Star Wars Zero Company, you click the game, hit Options, and pick “High performance.” That tells Windows to prefer the dedicated Nvidia or AMD GPU when launching the game.
The logic seems airtight. But the Star Wars Zero Company crash reporter often appears even after this setting is applied. Players see “Low‑Level Fatal Error” or “GPU Crash Dump Triggered” – the same errors that appear when the game tries to run on an integrated GPU and fails. The standard fix does not stick because Windows is not the only system that decides which GPU runs the game.
Three hidden layers almost always interfere.
Three Hidden Reasons the Standard Fix Doesn’t Work
1. Manufacturer Software Overrides Windows
On Nvidia Optimus laptops, the Nvidia Control Panel has its own per‑application GPU setting. If you set Windows to High Performance but the Nvidia Control Panel still has “Auto‑select” (or, worse, “Integrated graphics”) for the Star Wars Zero Company .exe, the Nvidia driver ignores the Windows preference.
The same happens with AMD laptops. AMD Adrenalin software’s “Graphics” tab contains a per‑app switch that can override Windows. Many users never check the Nvidia Control Panel or AMD Adrenalin because the standard guide only mentions Windows Settings.
Check both places. In Nvidia Control Panel, go to Manage 3D Settings > Program Settings, add the game’s executable (often ZeroCompany.execodecodecodecodecodecode), and set “Preferred graphics processor” to “High‑performance NVIDIA processor.” In AMD Adrenalin, navigate to Gaming > Graphics and toggle the switch from “Let Windows decide” to “High performance.”
2. The Integrated GPU Bypass – Laptops That Never Hand Off the Frame
Some laptops route all display output through the integrated GPU, even when the dedicated GPU renders the frame. The dedicated GPU writes to a buffer that the integrated GPU copies to the screen. This hybrid architecture (common on older Optimus laptops and many mid‑range AMD systems) can cause Star Wars Zero Company to crash because the game’s engine expects direct access to the GPU that does the rendering.
The Windows High Performance setting does not change that routing. You need one of two deeper fixes:
- MUX switch enabled: If the laptop has a hardware MUX switch (common on gaming laptops from ASUS, Lenovo, MSI), switch to “dGPU mode” in the manufacturer’s control center (e.g., ASUS Armoury Crate, Lenovo Vantage). This physically disconnects the integrated GPU and forces all rendering and output through the dedicated GPU. After enabling it, restart the laptop and launch the game.
- No MUX switch: Disable the integrated GPU in Device Manager only if you know the laptop’s display panel is wired directly to the dedicated GPU. Many laptops with no MUX switch will go black if you disable the integrated GPU. Safer alternative: set the Nvidia Control Panel power management to “Prefer maximum performance” and set Windows power plan to “High performance.” This forces the dedicated GPU to stay active, reducing handshaking delays that trigger the crash reporter.
3. Stale Driver Profiles and Corrupted Cache
Even if the GPU is correctly assigned, old driver profiles can cause conflicts. When you install a driver update, the installer preserves your existing per‑application settings. If an earlier driver had a corrupted profile for Star Wars Zero Company, the new driver inherits that corruption. The game tries to launch, sees conflicting GPU preferences, and throws a GPU crash dump.
Clear the driver cache before blaming the GPU setting. Use Display Driver Uninstaller (DDU) in Safe Mode to wipe all previous driver remnants. Then install the latest driver fresh. After a clean installation, set the GPU preferences again – first in the Nvidia or AMD control panel, then in Windows Graphics Settings, and finally verify that no overlay software (Discord, GeForce Experience, Steam) is interfering. The source material explicitly says to disable overlays – that step becomes even more important after a driver reset.
A Step‑by‑Step Alternative Workflow
If the standard Windows setting has not fixed your Star Wars Zero Company crashes, stop repeating it. Try this order instead:
Step 1: Open Nvidia Control Panel or AMD Adrenalin. Set the game’s .execodecodecodecodecodecode to use the dedicated GPU. Do not rely on Windows Settings alone.
Step 2: Enable the MUX switch if available. Many gaming laptops ship with the MUX defaulting to “Auto” which still uses the iGPU for display. Manualy switch to “dGPU” mode.
Step 3: Set the Windows power plan to High Performance. In Control Panel > Power Options, choose “High performance.” This prevents the CPU or GPU from downclocking under light load, which can trigger the crash reporter on launch.
Step 4: Disable all overlays. Discord, Steam, Nvidia App, Xbox Game Bar – turn them off before launching the game. The source material lists this as a separate step, but it is critical after GPU assignment because overlays often hook into rendering pipelines and force the use of the iGPU.
Step 5: Add launch options. In Steam, right‑click the game > Properties > General > Launch Options. Try -dx11codecodecodecodecodecode first. If the game still crashes, try -dx12codecodecodecodecodecode. If neither works, try -windowed -nobordercodecodecodecodecodecode. This bypasses full‑screen detection issues that can confuse GPU assignment.
Step6: Verify game files and clear shader cache (as per source). A corrupted shader cache can cause repeated crashes even on the correct GPU. Use Windows Disk Cleanup to clear “DirectX Shader Cache,” then run Steam’s verify integreity.
Only after these steps should you return to Windows Graphics Settings to confirm it is set to High Performance – but treat that as a confirmation, not a solution.
When the Standard Advice Is Actually Correct
The standard Windows Graphics Setting fix works for many players. If your laptop has a modern MUX switch that defaults to dGPU mode, if you recently performed a clean driver installation, and if no overlay software is running, then setting High Performance in Windows Settings will likely work. The advice is not wrong – it is incomplete for edge cases.
Those edge cases are more common than guides admit. On popular forums for Star Wars Zero Company, dozens of players report the same pattern: they follow the standard steps, the game still crashes, and only after digging into Nvidia Control Panel or enabling the MUX switch does the game launch without the crash reporter.
Frequently Asked Questions
Why does Star Wars Zero Company keep using the integrated GPU after I set High Performance in Windows?
Windows Graphics Settings is a preference, not a lock. Nvidia Control Panel, AMD Adrenalin, or the laptop’s power management software can override it. Check each of those tools and set the dedicated GPU as the preferred processor. Also ensure the power plan is not on “Power Saver,” which forces the iGPU regardless of Windows settings.
Should I disable the integrated GPU in Device Manager to force dedicated GPU usage?
Only if your laptop has a hardware MUX switch. Disabling the iGPU on laptops without a MUX switch usually results in a black screen because the display panel is wired through the iGPU. Instead, use the Nvidia Control Panel “Prefer maximum performance” setting, which keeps the dGPU active without disabling the iGPU.
Does enabling the MUX switch fix the crash reporter for Star Wars Zero Company?
In many cases, yes. The MUX switch bypasses the iGPU entirely, eliminating the handshaking delay that triggers the “GPU Crash Dump Triggered” error. After enabling it, restart the laptop and launch the game again.
How can I check which GPU the game is actually using?
Open Task Manage (Ctrl+Shift+Esc), go to the Performance tab, and watch the GPU usage graph for either “GPU 0 – Integrated” or “GPU 1 – Dedicated.” Launch Star Wars Zero Company and see which one spikes. If the dedicated GPU stays idle while the game crashes, the GPU assignment is wrong.
I set everything correctly but the game still crashes. What am I missing?
The crash may not be GPU‑related. The source material lists 14 other causes: low virtual memory, missing Visual C++ redistributables, corrupt system files (run sfc /scannowcodecodecodecodecodecode and dism /online /cleanup‑image /restorehealthcodecodecodecodecodecode), or insufficient free space on the game drive. GPU assignment is just one variable.
Beyond GPU Assignment: The Real Bottleneck
Even after you force Star Wars Zero Company onto the dedicated GPU, the game may still crash because of how that GPU handles the workload. Many laptops throttle under sustained load, dropping clock speeds and causing frame time spikes that trigger the crash reporter. The GPU might be selected correctly, but if thermal throttling kicks in during shader compilation, the game dies.
Monitor with MSI Afterburner or HWInfo. Watch for temperature drops (a sign of throttling) or clock speeds that fall below base levels. If you see throttling, undervolt the GPU or improve cooling (raise the laptop, clean fans, reduce ambient temperature). No GPU setting in the world fixes a laptop that hits 95°C before the main menu loads.
The standard advice assumes a stable system. Real hardware is not that kind.
