Mortal Shell 2 PC Fixes: Crashes, Performance, and Save Checks
Cautious troubleshooting that starts with safe checks and points to official patch notes before risky changes.
Troubleshoot in reversible order: record the build, verify files, test one graphics or overlay change, and back up saves before manual edits. Keep a known issue’s status and date beside the fix.
3 sources · route guidance · Forum workarounds are not treated as official fixes.- Platform and build number
- A reproducible symptom
- A save backup
The useful details at a glance
Use these rows before opening a long route. Status tells you what is confirmed and what still needs a retail check.
Do this in order
Three short actions to turn this page into a usable run. This page stays text-first because no exact visual was verified.
Write the exact symptom
Save the platform, build, driver, graphics preset, and the step that triggers the issue. A reproducible symptom is more useful than a generic crash claim.
Try reversible checks first
Verify files, change one graphics or overlay setting, and restart between tests. Do not edit saves before you have a backup.
Keep the workaround dated
Mark each fix as reported, reproduced, workaround, or resolved, then connect it to the next official patch check.
Start with build and platform
Record retail build, operating system, GPU driver, and whether the issue appeared after a patch. A Beta fix may be irrelevant to the retail app.
Safe checks first
Verify files, change one graphics setting at a time, disable overlays one at a time, and copy saves before manual file changes. Separate reversible checks from destructive advice.
Known issues need a status
Each card will show reported, reproduced, workaround, or resolved. A date is more useful than a list of forum suggestions with no context.
PC triage that does not risk the save
Write the exact symptom first: crash at launch, stutter in a specific area, input loss, or a save-load failure. Add build, OS, GPU driver, and whether it began after a patch.
Use reversible checks in order. Verify files, change one setting, disable one overlay, and restart between attempts. If the symptom is unchanged, restore the setting before trying the next test.
Only after a backup should you inspect a save or config file. A forum workaround with no retail build and no reproduction note belongs in the lead queue, not in the verified fix box.
Quick answers
What should I do before changing files?
Record the build and symptom, try reversible checks, and back up saves before manual edits.