Mortal Shell II NVIDIA Stutter Shader Crash Fix
The most reported NVIDIA fix is the Shader Cache Size setting. Here is the exact path, what to do if it still crashes, and the mistakes that keep the problem alive.
The core problem: On NVIDIA cards, Mortal Shell II can crash during shader compile, lock up after death or loading, or hitch mid-fight because new effects compile on the fly. The game compiles shaders (and PSO/cache data) as you hit new effects and areas. If the driver cache is capped (often 4 GB default), it evicts old shaders and recompiles mid-fight. That is the hitch, lock-up, or crash loop NVIDIA players keep reporting. The fix is setting the Shader Cache Size to Unlimited so compiled shaders stay cached.
1The Fix Players Report Most
-
1
Close the game completely
Not just to desktop overlay. Fully exit.
-
2
Right-click the desktop and open NVIDIA Control Panel
-
3
Left sidebar: Manage 3D Settings
-
4
Stay on the Global Settings tab
-
5
Find Shader Cache Size and set it to Unlimited
-
6
Click Apply
Fully quit NVIDIA Control Panel, then reboot the PC if the game still crashes on the next launch.
2If It Still Crashes or Stutters
Work these in order. Change one thing, then test 10-20 minutes of actual combat or area travel.
-
1
Turn Frame Generation off
DLSS Frame Generation is the other crash trigger NVIDIA players keep naming (hard crash within 10-30 minutes, freezes on beacon teleport). Disable FG in-game, restart the game after changing DLSS/FG. Test stability before you turn FG back on.
-
2
Clear a corrupt shader cache, then rebuild it
Windows search, Disk Cleanup, C: drive, tick DirectX Shader Cache, Clean up. Optional extra: delete contents of
%LOCALAPPDATA%\NVIDIA\DXCacheand%LOCALAPPDATA%\NVIDIA\GLCache(close every game and browser first). Then launch Mortal Shell II once and let the shader/PSO pass finish. Do not alt-tab spam during that first compile. -
3
Update or clean-install the Game Ready driver
Use Custom, Perform a clean installation (not Express). Express can carry broken shader/driver files forward. Reboot after install, then set Shader Cache Size again because driver installs often reset it.
-
4
Last-resort launch option: -dx11
Steam, Mortal Shell II, Properties, Launch Options:
-dx11. Use this when DX12 shader compile crashes the game. It can look worse and drop features. Use it only to get in; go back to DX12 after a driver/cache reset if DX12 holds. -
5
Disable overlays
Turn off Steam overlay, Discord overlay, NVIDIA overlay, and Instant Replay for a test session. Several crash reports pair overlays with D3D12 device-removed and shader-compile deaths.
3Symptom to Fix Map
-dx11 or clean driver reinstall.Common Mistakes to Avoid
- Changing Shader Cache on a per-program profile and leaving Global at default. Use Global, or add an explicit Mortal Shell II profile with the same Unlimited value.
- Expecting the hitch to vanish on the first launch after Unlimited. The cache has to refill. The second and third sessions are the real test.
- Leaving Frame Generation on while debugging crashes. You cannot tell if the cache fix worked.
- Express driver install after a crash loop. Use Custom and Perform a clean installation. Express can carry broken files forward.
- Stacking Engine.ini stutter mods with read-only files while FG is on. Later patches broke FG for people who left Engine.ini read-only. Delete a custom Engine.ini if you added one, let the game regenerate it, then re-enable FG only after a clean restart.
- Using -dx11 as the first step. It hides the DX12 path the game is built around. Use it only as a last resort to get in.