Unreal Engine 5 Shader Cache Corruption Crash Fix (All Games)

What is Unreal Engine 5 Shader Cache Corruption?

Unreal Engine 5 keeps three layers of shader cache to avoid recompiling pipeline state objects (PSOs) every launch: the DirectX Shader Cache maintained by Windows, the engine pipeline cache stored per game in %LOCALAPPDATA%\<GameName>\Saved\ShaderCache, and the per-game DDC (Derived Data Cache) in %LOCALAPPDATA%\<GameName>\Saved\DerivedDataCache. When any one layer holds stale or corrupted entries — most commonly after a GPU driver update, a Windows cumulative update, or a game patch — UE5 attempts to bind a PSO that no longer matches the current driver ABI and crashes with Fatal error! Unhandled Exception: EXCEPTION_ACCESS_VIOLATION or GPU Crash Dump Triggered.

Confirmed by June 2026 community reports across Stalker 2 (Heart of Chornobyl), Path of Exile 2, Silent Hill 2 Remake, Battlefield 6, Avowed, Clair Obscur: Expedition 33, and Senua's Saga: Hellblade II: clearing the full three-layer cache resolves roughly 90% of recurring "no clear cause" UE5 crashes. The catch is most online guides clear only one layer, which leaves the corrupted cache to regenerate from the remaining stale data. The script in step 3 below wipes all known UE5 cache paths atomically.

When does it occur?

• After installing a new Nvidia (581.x), AMD (Adrenalin 26.6.x), or Intel Arc driver
• After a Windows 11 cumulative update (KB5094126 in June 2026 is a frequent trigger)
• After a game receives a patch that changes shader permutations (POE2 June 2026 endgame, Stalker 2 patch 1.6)
• During cutscenes that trigger a new shader pipeline that wasn't precompiled
• On first launch after switching DirectX 12 to Vulkan or vice versa
• After moving the game install between drives (paths in cache become stale)
• When the cache disk is full or has bad sectors

Common causes

• Stale PSO entries in %LOCALAPPDATA%\D3DSCache referencing an older driver compiler
• Engine pipeline cache (*.upipelinecache, *.shk) corrupted by an interrupted shader compilation
• Per-game DDC entries built against a different engine minor version
• Antivirus quarantining a freshly written shader during compilation (Defender SmartScreen, Norton, Bitdefender)
• Disk-full preventing the cache from completing a write, leaving a half-written file
• Wrong UE5 graphics RHI selected (DX12 vs Vulkan) producing an unusable cache
• Custom Engine.ini r.ShaderPipelineCache.StartupMode=0 disabling the precache

Step-by-step fixes

1. Close ALL UE5 games and the Epic / Steam launcher — caches stay locked while the process is running; deletion will silently fail and the file regenerates from stale data. Use Task Manager → Details to confirm no *-Win64-Shipping.exe is alive.
2. Clear the Windows DirectX Shader Cache (clean way) — Right-click This PC → Properties → Storage → Temporary files → check DirectX Shader Cache → Remove files. Or run admin PowerShell: Remove-Item "$env:LOCALAPPDATA\D3DSCache\*" -Recurse -Force and Remove-Item "$env:LOCALAPPDATA\NVIDIA\DXCache\*" -Recurse -Force and Remove-Item "$env:LOCALAPPDATA\NVIDIA\GLCache\*" -Recurse -Force.
3. Run the universal UE5 cache-wipe batch script — paste into a new .bat file and run as Administrator:

@echo off
echo Clearing UE5 shader caches...
del /q /s "%LOCALAPPDATA%\D3DSCache\*" 2>nul
del /q /s "%LOCALAPPDATA%\NVIDIA\DXCache\*" 2>nul
del /q /s "%LOCALAPPDATA%\NVIDIA\GLCache\*" 2>nul
del /q /s "%LOCALAPPDATA%\AMD\DxCache\*" 2>nul
for /d %%G in ("%LOCALAPPDATA%\*") do (
  if exist "%%G\Saved\ShaderCache" rd /q /s "%%G\Saved\ShaderCache"
  if exist "%%G\Saved\DerivedDataCache" rd /q /s "%%G\Saved\DerivedDataCache"
)
echo Done. Launch your UE5 game now and allow shader precompilation to finish.
pause

1. Verify the per-game cache paths got wiped — check %LOCALAPPDATA%\<GameName>\Saved\ (e.g. Stalker2, PathOfExile2, BF6, Avowed). The ShaderCache and DerivedDataCache folders should be either empty or absent.
2. Force the correct RHI — for each game, set the graphics API explicitly. POE2: launcher → Settings → Graphics → DirectX 12. Stalker 2: in-game Video → DX12. Avowed: Engine.ini → [/Script/WindowsTargetPlatform.WindowsTargetSettings] → DefaultGraphicsRHI=DefaultGraphicsRHI_DX12. Wrong RHI generates an incompatible cache that crashes on first PSO bind.
3. Allow the precompile pass to complete — first launch after clearing will spend 2-15 minutes precompiling. Do NOT alt-tab or close. If the game has a "Precompiling shaders" splash (Avowed, Stalker 2), wait. Interrupting it leaves you back at step 1.
4. Exclude the cache folders from antivirus real-time scanning — Windows Security → Virus & Threat Protection → Manage settings → Exclusions → add %LOCALAPPDATA%\D3DSCache, %LOCALAPPDATA%\NVIDIA\DXCache, and each game's Saved\ShaderCache. Real-time scanning can corrupt files mid-write during precompile.
5. Move the cache to a different drive if disk is full or failing — set the environment variable UE_SHADER_CACHE_DIR to a path on a healthier drive (e.g., D:\UE5Cache). System Properties → Environment Variables → System variables → New. UE5 will use this for the engine cache and stop fighting a saturated C: drive.

If it still doesn't work

If the crash returns after a successful precompile, the bad layer is upstream of the cache — your GPU driver is shipping a broken shader compiler. Check the [Nvidia RTX hotfix display stability fix](/en/errors/nvidia-rtx-hotfix-june-2026-display-stability-crash-fix) or roll back AMD Adrenalin to 25.12.1. If the precompile itself crashes, you're likely hitting the [Hardware-Accelerated GPU Scheduling crash wave](/en/errors/hardware-accelerated-gpu-scheduling-game-crashes-fix-june-2026) — disable HAGS, then re-run the cache wipe.

Game-specific symptoms after a clean cache: Path of Exile 2 still crashing on Vulkan boot → see [POE2 Vulkan crash startup fix](/en/errors/path-of-exile-2-vulkan-crash-startup-fix). Battlefield 6 still crashing to desktop with no code → see [BF6 crash to desktop](/en/errors/battlefield-6-crash-desktop-no-error-code). Avowed throwing Fatal Error! UE-Alabama → see [Avowed UE-Alabama fatal error](/en/errors/avowed-fatal-error-ue-alabama-crash-pc). Clair Obscur: Expedition 33 fatal error → see [Expedition 33 fatal error crash](/en/errors/clair-obscur-expedition-33-fatal-error-crash). Each of those has the title-specific follow-up steps that picking up from the shader-cache reset alone cannot fix.