Use the failure pattern to choose the next test. A crash to desktop needs the current build, file verification and a repeatable trigger; a short hitch in the same world location may be traversal stutter; a long first-run hitch after a driver update may be shader compilation. Start with Frame Generation and hardware ray tracing off, then change one variable at a time. A save that cannot enter the world belongs to the separate recovery path.
Match the symptom before changing settings
These patterns lead to different tests. A lower preset cannot repair every crash, and a cache rebuild cannot repair a broken save.
Record the error, location and build. Update, verify files, disable Frame Generation and retest the same trigger.
Run the same route twice. Independent testing still observed traversal stutter even when average performance was strong.
NVIDIA says a new driver clears its shader cache, so the first run can stutter while shaders are rebuilt.
Stop repeated launches, preserve SaveGames and use the dedicated backup-first guide.
How this was checked
Evidence and limits
Method: Compared the Week 1 developer notes and official community troubleshooting with NVIDIA's shader-cache documentation and independent PC testing across multiple GPUs.
Evidence boundary: This site did not run a controlled hardware benchmark. The decision tree separates developer-confirmed changes, independently measured behavior, and player-reported symptoms instead of presenting one universal fix.
Read the full editorial standard →Do this first
- Install the newest game update and restart Windows.
- Verify the game files in Steam, then test with overlays and Frame Generation off.
- Use a conservative preset with ray tracing off and an appropriate DLSS/FSR mode.
- For NVIDIA shader symptoms, follow the linked official-community procedure and expect the first run to rebuild shaders.
- If the crash remains, capture the build string, crash text, GPU driver, location, and repeat steps.
Separate a crash from traversal stutter
A crash closes the game or freezes the system; traversal stutter is a short hitch while moving through the world. DSO Gaming tested eight GPUs on a Ryzen 9 7950X3D system and still reported traversal stutters despite generally strong frame rates. That comparison matters: lowering every quality slider may reduce GPU load without removing a world-streaming hitch.
- Crash to desktop or hard freeze: prioritize updates, file verification and a reproducible trigger
- A hitch at the same boundary on repeated runs: record the location and compare the second pass
- A one-time hitch after a driver update: allow shaders to rebuild before judging the result
- Loading-screen crash: use the dedicated loading and save-recovery guides
What Week 1 changes
The update lists crash fixes across spawning, audio, attribute changes, interface loading, save loading and shutdown. It also removes settings linked to graphics-driver crashes and adds a crash-diagnostics option. These changes reduce old causes but do not prove every current crash is fixed.
Why Frame Generation is a diagnostic switch
Week 1 reworks Frame Generation so a change applies after a reload and no longer switches on before the world finishes loading. The developer also warns that updating with mods installed or Engine.ini locked read-only can interfere with Frame Generation. Off is the clean crash-isolation baseline; it is not a claim that the feature is broken on every GPU. Use the dedicated Frame Generation guide for unavailable, inactive and crash-only failure states.
What NVIDIA's cache documentation actually supports
NVIDIA documents that shader compilation can cause gameplay stutter, that the cache reuses compiled shaders, and that installing a new driver clears that cache. This supports expecting a rough first run after a driver update. It does not prove that every Mortal Shell II hitch is a cache problem, so follow the game-specific community-manager procedure only when the symptom matches and preserve its cautions.
What not to do first
Do not delete the SaveGames folder, paste unknown Engine.ini tweaks, disable Windows exploit protection, or clear unrelated application data as a first step. Back up saves before touching files, and prefer developer-listed workarounds over generic Unreal Engine advice.
Evidence log
Sources checked
External sources are linked for verification. Community reports describe symptoms and are not treated as universal fixes.
OfficialGlobal release known issuesOfficial community-manager issue list and current workarounds.
↗OfficialNVIDIA shader-cache troubleshootingNVIDIA-specific procedure with an explicit warning that results are not guaranteed.
↗PlatformThe Week 1 UpdateCurrent official crash, performance, save and graphics-option changes.
↗OfficialNVIDIA Shader Cache Size referenceNVIDIA documentation for shader-cache behavior and the first run after a driver update.
↗SpecialistMortal Shell 2 PC performance analysisIndependent multi-GPU test that distinguishes strong average performance from remaining traversal stutter.
↗Found a build mismatch?
Help keep this page current.
Send the page URL, platform, pause-menu build string, and a reproducible observation through the corrections desk. Game bugs still belong in the official developer channels.
Open corrections guidance →