Horizon Forbidden West Shader Compilation Freezing at 0% Fix — PC Launch
Horizon Forbidden West Complete Edition
Troubleshooting Steps & Solutions
Update your GPU driver before anything else. Nvidia: GeForce Experience → Drivers → Express Install. AMD: AMD Software: Adrenalin Edition → Home → Check for Updates. Reboot after updating — don't just restart the launcher.
Disable Hardware-Accelerated GPU Scheduling. Go to Settings → System → Display → Graphics → Change default graphics settings and toggle Hardware-accelerated GPU scheduling to Off. Reboot after disabling it — this change isn't active until after a full restart.
Delete any existing shader cache to clear a corrupted partial compile. Go to C:\Users\YourName\AppData\Roaming\Guerrilla Games\Horizon Forbidden West\ and delete the ShaderCache folder if it exists. Also check C:\Users\YourName\AppData\Local\Temp\ for any HFW or GuerillaGames temp folders and delete those too.
Close all background GPU tools before launching. Close MSI Afterburner, RivaTuner Statistics Server, and GeForce Experience from the system tray. Disable the Steam and Discord overlays. The GPU needs to be as free as possible during shader compilation.
Force the game to DX11 as a temporary workaround. In the Horizon Forbidden West launcher that appears before the game opens, click Options and switch API from DX12 to DX11. This bypasses the async compute shader path that causes the freeze. You can switch back to DX12 after the shader cache has been built successfully in DX11.
If you're back in DX12 mode and want to compile shaders without the freeze, lower the in-game Graphics Quality preset to Medium before the first launch in DX12. This reduces the shader permutation count the compiler needs to process in the first batch, cutting compilation time and reducing TDR risk.
If your system is still freezing after all of the above, disable HAGS in the registry directly as a backup. Press Win + R, type regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers, and set HwSchMode to 1 (disabled). Reboot. This fully disables HAGS at the driver level rather than just through Windows settings.
Horizon Forbidden West Shader Compilation Frozen at 0% — Full System Freeze on First Launch
You launch Horizon Forbidden West for the first time, get to the main menu, and the shader compilation bar appears at the bottom of the screen. It sits at 0%. The percentage never moves. After 30 seconds to a few minutes, your entire rig locks up — mouse stops moving, display freezes on the last frame, and you can't even open Task Manager. Hard reset is the only way out. This isn't the game crashing. It's a full system hang — the GPU driver stops responding and takes Windows with it. Some players get a black screen instead of the frozen menu frame. Others see the screen flicker once before the lockup. A small number hear the audio loop for a second before everything goes silent and the machine is completely unresponsive. It happens on the very first launch only — or after a driver update that invalidates the existing shader cache. RTX 30-series and 40-series cards are the most commonly reported hardware, but AMD RDNA 2 users hit it too. DX12 mode is the consistent factor — players who force DX11 rarely experience the full system freeze.
What Triggers This Issue?
* **GPU driver timeout during shader pre-compilation** — Horizon Forbidden West's DX12 shader compilation is extremely GPU-intensive at startup. If the driver takes too long to compile a specific shader permutation, Windows triggers a TDR (Timeout Detection and Recovery) reset, which on some systems produces a full hang rather than a recovery. * **DX12 async compute conflict** — the game's shader pipeline uses DX12 async compute extensively. Specific driver versions have known issues handling async compute during bulk shader compilation, causing the GPU to deadlock. * **VRAM too small for batch shader compilation** — the game tries to compile a large number of shaders simultaneously. On GPUs with 8GB VRAM or less, the batch size overflows available VRAM and causes the GPU to stall. * **Hardware-accelerated GPU scheduling (HAGS) conflict** — HAGS, introduced in Windows 10 2004, changes how the GPU command queue is managed. On certain GPU and driver combinations, HAGS causes the shader compiler to deadlock during Horizon's first-launch batch. * **Outdated GPU driver** — older Nvidia and AMD drivers don't handle Guerrilla's shader compilation workload correctly, producing the TDR hang rather than completing the pass. * **Corrupted shader cache from a previous failed compilation** — if the game crashed during a previous shader compile attempt, the partial cache on disk can cause the next attempt to stall immediately at 0%. * **Background GPU load from overlays or monitoring tools** — GeForce Experience overlay, MSI Afterburner, and RivaTuner all put GPU load on the card. During shader compilation, any additional GPU demand from background tools increases the chance of a driver timeout.
Common Error Queries & FAQs
Does this happen every time I launch, or just the first time?
Only on the first launch in a given graphics API mode, or after you update your GPU driver (which invalidates the existing cache). Once the shader cache is built successfully, subsequent launches skip the compilation step entirely and load straight to the menu in seconds.
I compiled in DX11 and it worked. Can I switch to DX12 now without the freeze?
Yes — switch back to DX12 in the launcher options after your DX11 cache is built. When DX12 mode launches for the first time, it'll compile its own separate cache. With HAGS disabled and background tools closed, the DX12 compilation usually completes without a freeze. If it freezes again, lower the graphics preset to Medium before that DX12 first-launch attempt.
My entire PC is freezing — could this damage my hardware?
The freeze itself won't damage hardware. It's a GPU driver deadlock, not a thermal or electrical event. Hard resetting with the power button to recover from it is safe. If you're concerned, check GPU and CPU temperatures in your BIOS after the reboot to confirm everything's within normal range.
I've seen people mention increasing the TDR delay in the registry. Should I do that?
It's a legitimate workaround — increasing the TDR timeout from 2 seconds to 8 seconds gives the GPU more time to complete shader compilation without Windows killing it. Press Win + R → regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers, right-click → New → DWORD (32-bit), name it TdrDelay, and set the value to 8. Reboot. This buys time for the shader pass to finish rather than fixing the root cause, but it works for many players.
How do I stop this happening after future GPU driver updates?
After any GPU driver update, delete the shader cache at C:\Users\YourName\AppData\Roaming\Guerrilla Games\Horizon Forbidden West\ShaderCache before launching. New drivers invalidate existing compiled shaders, and launching without clearing the old cache can cause a partial recompile that's more likely to freeze than a clean compile from scratch.
Technical Analysis: Why It Happens
When Horizon Forbidden West launches for the first time in DX12 mode, it runs a batch shader pre-compilation pass — it converts its raw shader code into GPU-specific binary instructions for your exact hardware. This is normal for modern DX12 games. What's not normal is compiling hundreds of shader permutations simultaneously in one uninterrupted batch. That batch puts the GPU at or near 100% utilization for an extended period. Windows monitors GPU activity through a watchdog timer called TDR — Timeout Detection and Recovery. If the GPU stops responding to Windows' checks for more than 2 seconds (the default TDR timeout), Windows tries to reset the driver. On most games this produces a brief black screen and a "Display driver stopped responding" notification. On Horizon Forbidden West's shader compilation specifically, the reset attempt hits the GPU mid-compilation at a point where it can't cleanly recover — and the result is a full system hang instead of a clean driver reset. Guerrilla Games patched the shader compilation system post-launch to be less aggressive, but the freeze still hits players on specific driver versions and hardware combinations where the TDR watchdog interacts badly with the DX12 async compute queue during compilation. Using DX11 for the initial shader build works because DX11's shader compilation path is simpler and doesn't use async compute — it compiles sequentially at lower GPU intensity, which doesn't trip the TDR timer.
Summary
Two things fix this for most people: update your GPU driver and disable Hardware-Accelerated GPU Scheduling in Windows display settings. Both changes together reduce the TDR collision risk that causes the full system freeze during shader compilation. If you're still freezing after that, compile in DX11 mode first — switch the API in the Horizon Forbidden West launcher before loading, let it build the cache without crashing, then switch back to DX12. Before any DX12 first-launch attempt, close every background GPU tool from the tray. If freezes persist in DX12, add the TDR delay registry key (TdrDelay = 8 under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers) and delete the shader cache folder before relaunching. That combination clears it for the remaining cases.
