Mortal Shell II Official Crash Fixes and Safe Troubleshooting
Published 2026-08-22 · Updated 2026-08-22
Use the official Patch 86328 and 86845 crash history to update, reproduce, verify, and report Mortal Shell II crashes before trying riskier workarounds.
Sources
Checked on 2026-08-22. Store details and balance may change after patches.
Update before diagnosing an old crash
The official Patch 86328 notes report fixes for nine common crashes, and Patch 86845 includes additional crash fixes. That makes the installed version the first diagnostic variable. Let Steam finish downloading, unpacking, and verifying the update, then restart Steam and the computer before reproducing the problem. Record the retail App ID 2584270 and current patch context. A forum workaround written before these patches may target code that has already changed, so do not stack it on top of the current client without a fresh controlled test.
Do not overstate the official fix list
The developer does not enumerate all nine signatures in the preserved 86328 section, and the 86845 notes do not claim complete crash elimination. Therefore, the honest conclusion is that multiple known causes were fixed—not that every startup, loading, cutscene, driver, or hardware failure disappeared. Categorize your symptom by trigger: before the menu, while loading a save, entering an area, during a cutscene, after being knocked from a Shell, or after extended play. This trigger is more useful than the generic phrase 'it crashes.'
Establish one clean reproduction
Before changing settings, write down the last successful action, the exact next action, error message, and whether the crash repeats from the same save or route. Capture system time so Windows event records can be matched later. Close overlays, capture tools, browsers, and unnecessary background applications for one comparison, but do not uninstall several programs at once. If the crash does not repeat, reintroduce one variable at a time. If it repeats predictably, preserve the short sequence because it is valuable for an official report and future patch verification.
Verify the retail installation safely
Use Steam's built-in file verification for the retail product instead of deleting individual game archives or copying files from the Open Beta. Keep adequate free SSD space because patching may require download, unpack, replacement, and verification space beyond the final store listing. The retail Steam page lists Windows 10 or 11, DirectX 12, 16 GB RAM, a supported minimum CPU and GPU class, 70 GB available storage, and an SSD. Meeting the minimum is not a guaranteed frame rate, but running below it is relevant context for support.
Return settings to a controlled baseline
Remove unsupported launch arguments and temporary compatibility changes one at a time. Use the game's own options and a conservative preset for the reproduction. Keep target steering, camera shake, resolution, upscaling, and frame generation values recorded. Do not present disabling rumble as a crash fix; Patch 86328 added that option for feedback control, not as a stability claim. Likewise, Patch 86845's file reorganization was intended to reduce future patch sizes, not advertised as a universal performance improvement.
Distinguish a crash from frame drops
A crash ends or freezes the application; a frame drop reduces responsiveness while the process continues. The two can share context but require different evidence. For stutter, use the site's performance diagnostic and record scene, frame behavior, settings, and hardware. For a crash, prioritize the trigger sequence, error text, logs, and whether the same save reproduces it. Do not apply a long graphics-tuning checklist to a deterministic progression crash before updating, verifying files, and checking the official known-fix history.
Build a complete report packet
Include platform, operating system version, CPU, GPU, driver, RAM, storage type and free space, input device, retail App ID, patch context, graphics options, exact reproduction steps, frequency, error message, screenshots or video, and the last known working version. State whether Steam verification changed files and whether the crash remains afterward. Remove usernames, email addresses, file paths containing personal names, and account identifiers from screenshots and logs. A concise reproducible packet is more useful than twenty speculative fixes and helps the developer connect the case to a known signature.
Retest when SteamDB records a new build
SteamDB update history can signal that App 2584270 changed, but it cannot explain why a file or manifest changed. When a new build appears, look for an official Cold Symmetry or Playstack note. If crash fixes are named, repeat the preserved reproduction once on the new build and update the report with the result. If no official explanation exists, describe it only as observed Steam database activity. Do not publish a claim that a crash was fixed, introduced, or made worse from a changenumber alone.