The intro cinematic rolls. The logo flashes. Then the screen locks. Your cursor vanishes, and the Star Wars Zero Company crash reporter appears, often citing a low-level fatal error or a GPU crash dump triggered. This is not a random crash. It happens precisely when the game transitions from a pre-rendered video to the live engine, loading world geometry and compiling shaders.
A PC troubleshooting guide covering this exact issue outlines 14 sequential fixes. Of those, four fault lines cause the overwhelming majority of post-intro freezes: corrupt shader caches, GPU driver timeouts, overlay interference, and missing runtime libraries. Star Wars Zero Company exposes all four within the first sixty seconds of runtime.
The Most Common Culprit: A Corrupted DirectX Shader Cache
The game compiles a massive library of shaders at first launch. If that cache is broken, the engine stalls, and the crash reporter fires. The source video gives a precise fix: use Windows Disk Cleanup to clear the DirectX Shader Cache.
Here is the exact workflow: search for “Disk Cleanup” in the Start menu, select your system drive, and locate the “DirectX Shader Cache” entry. Clear it, restart your PC, and launch the game again. The first launch after cleansing will take longer because the shaders must be rebuilt from scratch. This single step resolves a high percentage of stuck-launch scenarios for games built on Unreal Engine, and Star Wars Zero Company behaves identically.
GPU Timeouts and the Crash Dump Triggered Error
If the shader cache is clean, move to the GPU driver. A “GPU crash dump triggered” message usually points to a Timeout Detection and Recovery (TDR) event, where the driver fails to respond within a few seconds under heavy load. The remedy is a full driver update.
Open Device Manager, expand Display adapters, right-click your card, and select “Update driver” with the automatic search. For Nvidia, AMD, and Intel users, the official websites provide manual lookup tools. If you use a laptop with integrated and dedicated graphics, make sure the game uses the high-performance GPU. Navigate to Settings > System > Display > Graphics, find Star Wars Zero Company, select Options, and choose High Performance. A laptop that defaults to the integrated GPU will frequently freeze during the intro sequence because it runs out of graphics memory.
Overlays and Background Software That Steal Rendering Resources
An intro freeze is often a symptom of another program stealing rendering resources exactly when the GPU load spikes. The source video names the usual suspects directly: Discord, the Nvidia App, AMD Software, Steam, and Xbox Game Bar. All of them inject overlay code into the rendering pipeline. Disable them before launching the game.
Background browsers, recording software, and hardware monitoring tools are just as problematic. The fix is brutal but effective: kill everything except Steam before you start. The crash reporter on Zero Company often vanishes if you strip the system down to bare essentials. Shader compilation is memory-intensive; any competing process can push the GPU over the edge.
Verify Game Files Before You Reinstall Anything
Before you reinstall a multi-gigabyte game, run Steam’s integrity check. Right-click Star Wars Zero Company in your library, select Properties, navigate to Installed Files, and click “Verify integrity of game files.” The process repairs missing or damaged data that can trigger a freeze during the intro’s transition sequence.
The source also warns about free storage space. If either the game drive or your Windows drive is nearly full, the game cannot stream level data fast enough, causing an artificial freeze that looks like a crash. Check both drives. If the Windows drive has under 20GB free, clearing it should be your next move.
Virtual Memory and Windows Updates
Low paging file size creates system-wide instability. The source advises navigating through Advanced System Settings > Performance > Advanced > Virtual Memory and increasing the paging file size. A 16GB RAM system often needs an 8GB or larger pagefile to avoid random freezes. Games that spike past their memory budget will hard-lock without it.
In the same vein, install all pending Windows updates. System updates frequently include fixes for graphics API bugs. A single DirectX runtime patch can resolve a recurring freeze that no GPU driver change will touch.
Launch Options: DirectX Versions and Windowed Mode
Star Wars Zero Company requires specific DirectX runtime behavior. The source material shows that adding launch options to Steam can bypass unstable defaults. Right-click the game in Steam, open Properties, and under General, type one of these:
-dx11codecodecodecodecodecode for older GPUs that lack stable DX12 drivers-dx12codecodecodecodecodecode for newer hardware with raytracing support-windowed no bordercodecodecodecodecodecode to force a rendering mode that avoids fullscreen exclusive issues
Test these sequentially. Do not leave all three active at once. Some users report that the game freezes on the intro if Windows incorrectly applies Fullscreen Optimizations, so right-click the game’s EXE file, go to Compatibility, and tick “Disable full screen optimizations.” Combine that with “Run this program as an administrator” for good measure. If the freeze persists, try “Run this program in compatibility mode for Windows 8.”
Repairing Corrupted System Files
A failing system file can break any game launch. The trusted fix from the source is to open Terminal as an administrator and run sfc /scannowcodecodecodecodecodecode. Once that completes, run dism /online /cleanup-image /restorehealthcodecodecodecodecodecode. These commands repair underlying Windows corruption before it can crash a game.
The crash reporter on Zero Company is sensitive to these low-level faults. If you skip this step, the game may repeatedly freeze at the exact same frame of the intro. That consistency is a hallmark of a system-level file corruption rather than a game-specific bug. After both commands finish, restart your PC.
FAQ
Why does my game freeze specifically after the intro and not before?
The intro is a pre-rendered video. The freeze happens when the engine loads textures, compiles the shader cache, and renders the first 3D frame. If the GPU or driver trips during that load, you get the crash reporter. Corrupted shaders are the primary cause.
Will lowering in-game graphics settings fix the intro freeze?
Yes, if the freeze comes from GPU memory pressure. The source notes that improper texture quality and resolution settings directly impact stability. Lower them before the first launch to give the shader compiler an easier time. You can raise them later.
Is running as administrator necessary for Star Wars Zero Company?
It can help. Run Steam as administrator, and also run the game’s EXE as administrator by checking “Run this program as an administrator” in the Compatibility tab. This grants higher system access, avoiding permission-related locks. The source also recommends Windows 8 compatibility mode if admin alone fails.
What if none of the steps work?
The source ends with a critical command sequence: sfc /scannowcodecodecodecodecodecode followed by dism /online /cleanup-image /restorehealthcodecodecodecodecodecode. If that fails, the problem may be hardware-specific, such as an unstable RAM overclock or a failing power supply.
A Diagnostic Left Turn
The crash reporter is only a warning light. For a truly stubborn freeze, stop looking at the game and look at the Windows Event Viewer. Filter the System log for “Display” errors. The hardware ID nvlddmkmcodecodecodecodecodecode for Nvidia cards appears on repeated TDR timeouts. That gives you a definitive answer without swapping components blind. The quick fixes stop the lights from blinking; the Event Viewer tells you why the fuse blew.
