When Cyberpunk 2077 crashes immediately after an update, the root cause almost always traces back to how REDengine 4 handles cached assets and serialized settings between builds. Unlike engines that rebuild shaders lazily at runtime, REDengine 4 pre-compiles and stores a substantial cache layer on disk. A new patch can introduce altered material IDs, restructured streaming data, or modified configuration schemas that the old cache files interpret as invalid, causing the game to fault during or shortly after the loading screen. Additionally, settings.json and engine.json carry forward values that may reference toggles or quality tiers that shifted meaning between versions. If you are seeing crashes after patching in 2026, this guide walks through the specific checks that resolve the vast majority of confirmed reports.
- Likely Causes
- Fix 1: Clear the DirectX Shader Cache
- Fix 2: Reset the Game Configuration Folder
- Fix 3: Disable All Mods and Third-Party DLLs
- Fix 4: Verify Game File Integrity
- Fix 5: Clean-Reinstall Your GPU Driver
- Fix 6: Disable Overlays and Conflicting Background Software
- Fix 7: Reduce Texture Streaming and VRAM Pressure
- Fix 8: Perform a Complete Reinstall
- If Nothing Works
- FAQ
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Stale DX12 / shader cache conflicting with new executable | Crash occurs at or shortly after loading screen; crash log references “DXFence” or “PSO cache” in r6\crash\ | Low |
| Corrupted or version-mismatched settings.json / engine.json | Crash happens before the main menu loads; deleting the config folder in %APPDATA%\Cyberpunk 2077 resolves it | Low |
| Mod conflicts with updated binary | Crash only occurs with mods enabled; red4ext.dll or dll.sector present in bin\x64\mods\archive\pc\mod\ | Medium |
| VRAM or RAM pressure from new streaming assets | Crash during open-world traversal or after loading a save; Windows Event Viewer shows resource-related fault | Medium |
| GPU driver not aligned with new rendering features | Crash with specific error code in Cyberpunk2077.exe; new patch enabled or changed RT / DLSS / FSR paths | Low |
| Incomplete or corrupted download | Steam or GOG reports file mismatch on integrity check | Low |
| Overlay or background software hooking conflict | Crash timing is inconsistent; disabling Game Bar, Discord overlay, or MSI Afterburner stops the fault | Low |
| Antivirus or Controlled Folder Access blocking write to r6\cache\ | Windows Defender protection history shows a block event for Cyberpunk2077.exe around the crash timestamp | Low |
Fix 1: Clear the DirectX Shader Cache
How to check
Navigate to %LOCALAPPDATA%\D3DSCache and to the game’s own cache at bin\x64\..\r6\cache\. If files there have timestamps from before your update date, the cache is stale.
What to do
Close the game. Delete all contents of %LOCALAPPDATA%\D3DSCache. Then delete the contents of the r6\cache\shader\ folder inside your game installation directory. The game will regenerate these files on the next launch, which may add a few minutes to your first load screen.
How to undo it
No undo needed. The cache rebuilds automatically. If performance dipped after clearing, it typically recovers within two or three sessions.
Fix 2: Reset the Game Configuration Folder
How to check
Open %APPDATA%\Cyberpunk 2077\settings\ and inspect the LastWrite timestamp on settings.json and platform\PC\settings.json. If these files were written before the patch deployed, they may reference deprecated quality tier indices.
What to do
Rename the entire %APPDATA%\Cyberpunk 2077\settings\ folder to settings_backup. Launch the game. It will generate fresh default configuration files. Once the game loads successfully, you can selectively copy saved keybinds back if you had custom bindings.
How to undo it
Delete the new settings folder, rename settings_backup back to settings, and the game will read your original configuration again.
Fix 3: Disable All Mods and Third-Party DLLs
How to check
Browse to bin\x64\mods\archive\pc\mod\. If the folder exists and contains .archive files, or if red4ext.dll or dll.sector sits in bin\x64\, mods are active.
What to do
Move the entire mods folder and any loose DLL files to a location outside the game directory. Launch the game and confirm stability. If it loads, reintroduce mods one at a time across separate sessions to identify the culprit.
How to undo it
Move the mods folder and DLL files back to their original paths exactly as they were.
Fix 4: Verify Game File Integrity
How to check
Steam: right-click the game in your library, go to Properties, Local Files, click “Verify integrity of game files.” GOG: click the wrench icon on the game tile, select Manage installation, then click “Verify / Repair.”
What to do
Run the verification. If any files show a checksum mismatch, the launcher will re-download them. A partial or corrupted patch download can introduce bad executable segments that the game then attempts to execute.
How to undo it
Not applicable. This only replaces files that do not match the expected checksums. It never adds or removes content.
Fix 5: Clean-Reinstall Your GPU Driver
How to check
Open the crash log in r6\crash\ and look for a faulting module path. If it references nvoglv64.dll, nvwgf2umx.dll, aticfx64.dll, or amdkmdag.sys, the graphics driver is involved.
What to do
Download DDU or use the driver installer’s own clean-install option. Boot into Safe Mode, uninstall the current driver completely, reboot, then install the latest stable driver from NVIDIA or AMD. A clean install eliminates residual INF entries or overlay hooks that sometimes survive a standard upgrade.
How to undo it
Reinstall your previous driver version. This is rarely needed, but if the new driver introduced its own issues, roll back through Windows Device Manager driver rollback or DDU plus the older installer.
Fix 6: Disable Overlays and Conflicting Background Software
How to check
Crashes with no consistent timing, and the faulting module in the crash log points to something like GameOverlayRenderer64.dll (Steam), discor… (Discord), or RTSS.exe (RivaTuner Statistics Server).
What to do
Disable the Steam In-Game Overlay from Steam settings. Turn off Discord overlay in Discord’s settings under Voice and Video. Exit RivaTuner, MSI Afterburner, and any hardware-monitoring HUD before launching the game. If crashes stop, re-enable one at a time to isolate the offender.
How to undo it
Re-enable each overlay or background app individually and test after each change.
Fix 7: Reduce Texture Streaming and VRAM Pressure
How to check
Open the crash log. Look for “Out of video memory” or a fault address inside the game binary that correlates with a texture streaming function. Alternatively, monitor VRAM usage with HWiNFO64 during the crash scenario.
What to do
Launch the game with the -dx12 flag if you have been using DX11 (or vice versa, to rule out an API-specific path issue). In settings, lower Texture Quality by one tier and set Streaming Budget to a value below your total VRAM. If the game supports it, disable the RAM disk option in settings, which can conflict with systems that do not have sufficient physical RAM allocated.
How to undo it
Restore your original quality preset and remove any command-line launch options from the Steam or GOG properties window.
Fix 8: Perform a Complete Reinstall
How to check
All previous fixes failed, crash logs continue to reference the executable or core engine DLLs, and file verification returned no errors. This suggests engine-level corruption that partial repair cannot address.
What to do
Uninstall the game through your launcher. Manually delete any remaining folder in the installation directory, including r6\ and engine\. Reinstall fresh. Do not restore the settings folder from your backup yet; let the game generate a clean configuration.
How to undo it
There is no meaningful undo for a full reinstall beyond reinstalling again. Save your settings backup somewhere persistent so you can restore preferences once the fresh install is confirmed stable.
If Nothing Works
If all eight fixes have been attempted and crashes persist, open the latest file in r6\crash\ with a text editor. Note the faulting module, exception code, and any referenced function name. Attach that log to a support ticket with CD Projekt Red or the respective launcher. The crash log is the single most useful diagnostic artifact for this engine. Also confirm your Windows is fully updated and that no recent Windows Update introduced a known regression with DirectX 12 or shader compilation.
FAQ
How long should the first launch take after clearing caches?
Expect two to five minutes of an extended loading screen while REDengine 4 rebuilds its PSO and shader cache. This is normal and does not indicate a problem. Subsequent launches will be at their usual duration.
Can I keep my save files after resetting settings?
Yes. Saves live in %USERPROFILE%\Saved Games\Cyberpunk 2077\saves\ and are independent of the settings folder. Resetting configuration will not affect your progress, only your graphics and control preferences.
Does the game create crash logs every time it faults?
In most cases, yes. The r6\crash\ folder receives a .txt and sometimes a .dmp file per crash event. If that folder is empty despite repeated crashes, check whether antivirus or Controlled Folder Access is blocking the write.
Will disabling ray tracing fix a post-update crash?
Only if the crash log specifically references RT-related modules or a PSO compilation failure for ray-traced materials. For most post-update crashes, clearing shader cache and resetting settings addresses the root cause before RT settings become relevant.
