Mortal Shell 2 Crash Fix

Keeps crashing? Install the crash hotfix first (Fix 1)

When the game keeps crashing every few minutes, the first crash fix is already published. During Advanced Access — the August 17 window that let Devout Edition pre-orders play up to 72 hours early — Playstack shipped Hotfix 1 for the frequent PC crashes players were reporting.

It was first offered on the Steam patch-preview branch — Mortal Shell II in your library, Properties, then Betas. It has since been rolled out to all players as a standard patch, so if the game keeps crashing today, the default branch already includes the fix: update fully and relaunch before trying anything else.

• Hotfix 1 targets the frequent PC crashes reported during Advanced Access
• It was initially opt-in via the patch-preview beta branch (Properties > Betas)
• It is now available to all players as a standard patch

Keyboard Bindings crash: the official save-file workaround (Fix 2)

A second confirmed crash has a specific trigger: opening the Keyboard Bindings menu in Settings. Playstack has confirmed receiving several reports of exactly that. While a permanent fix is being worked on, the publisher published this official workaround:

• Close Mortal Shell II completely
• Navigate to \Users\[Your Username]\AppData\Local\MortalShell2\Saved\SaveGames
• Delete EnhancedInputUserSettings.sav and SpartaGameSettings.sav
• Launch the game again

Crash on load: full lock-ups and the shader cache fix (Fix 3)

The officially confirmed loading-screen problem is a full lock-up: the game freezes solid, including on the loading screen after a death. For those lock-ups and crashes, Playstack's community manager recommends raising the shader cache limit — open the NVIDIA Control Panel app, go to 3D Settings, and set Shader Cache Size to "Unlimited".

An independent guide reaches the same conclusion: LagoFast lists the Shader Cache Size change (NVIDIA Control Panel or the AMD Software equivalent) as the most effective fix for the game's stuttering, which points at the same underlying shader-compilation behavior.

• NVIDIA Control Panel > 3D Settings > Shader Cache Size > Unlimited
• AMD owners: the equivalent setting lives in AMD Software

After the Week 1 Update (August 29): frame gen, freezes, and your saves

The Week 1 Update reworked frame generation by Playstack's own notes: it now applies only after a reload, no longer activates before the world has loaded, and NVIDIA frame generation now covers a much wider range of cards. The same patch added a Geometry Budgets graphics option and a crash diagnostics option, moved the shader-compilation hitch into the main menu, and reduced enemy counts in the busiest areas. On paper, that is a straight improvement for the problems on this page.

The community picture one week in is rougher. In the pinned Week 1 discussion thread, multiple players report frame generation broken after updating — including one who had uninstalled mods, toggled frame gen off and on, and restarted repeatedly without fixing it — and others describe severe freezes and frame drops on hardware that ran a stable 120–140 FPS before the patch: down to 80, dipping to 20, with freezes lasting up to 20 seconds. A third independent report adds a driver-level wrinkle: the NVIDIA app lists the game but refuses to change its settings (the shipping executable sits in a directory the app doesn't recognize), with frame gen dead after the patch.

What to actually do, in order: fully quit and relaunch first, because the reworked frame generation only applies after a reload and an old session can run half-applied; confirm the patch fully downloaded; then disable frame generation and play without it while the reports are unresolved — that is the only framegen state with consistent community confirmation behind it right now. Keep the shader cache fix above for lock-ups, try the new crash diagnostics option if crashes persist, and when you report, include your build number (pause menu, bottom right) in the bug-report thread so Playstack can triage it.

Save files deserve their own caution. The Week 1 notes contain one official save improvement — an interrupted save can no longer destroy your save file — but reports of saves vanishing entirely have continued since, including wipes right after a crash. There is now an official recovery path: Playstack's pinned Known Issues post lists a missing-saves workaround built on the automatic WorldState_Backup save file — full steps in the save FAQ at the bottom of this page. The prevention stays manual: copy the SaveGames folder at \Users\[Your Username]\AppData\Local\MortalShell2\Saved\SaveGames somewhere safe before installing any update, and if a save vanishes after a patch, restore that folder copy before doing anything else.

Playstack also shipped a ~1 GB PC hotfix on September 1, 2026. Its official notes were posted on the developer's Reddit and Discord rather than Steam News, and they list six fixes — Devout/Pre-Order Shell Shades, the FSR world-map problem, Citadel Annex spider traversal, enemies not reacting, collision areas, and Minibeacon visuals — with nothing for frame generation, freezes, crashes, or saves. The full entry is on the patch notes page.

• Official (Week 1 notes): frame gen reworked — applies after a reload, wider NVIDIA card support; new Geometry Budgets and crash diagnostics options
• Community reports (pinned Week 1 thread): framegen still broken for some players even after clean restarts; freezes dropping rigs from 120–140 FPS to 20
• Official (September 1 hotfix notes): six fixes, none of them framegen, freeze, crash, or save related
• Workaround-first: quit fully, relaunch, then disable frame generation until an official fix lands
• Saves: back up \Users\[Your Username]\AppData\Local\MortalShell2\Saved\SaveGames before installing any update

Random crashes that survive every patch: what the community has confirmed

Past the officially confirmed crashes above sits a bigger cluster: random crashes reported since launch that no patch has eliminated. The game's largest active Steam discussion — "Am I the only one being plagued by crashes?", 140+ replies and flagged answered — collects the pattern: hard lock-ups that take the whole PC down with no error text, crashes on alt-tab, and reports persisting "even after the updates". The community has not agreed on a cause — several repliers report zero crashes on comparable hardware — but a handful of workarounds now have confirmed successes attached, and the September 1 hotfix explicitly did not touch this cluster.

September 5 patch status: the update claims only "several crash fixes and optimisations" with no itemized list, and as of September 9 its post-patch record is two unconfirmed Bug Reports threads — crashes every 5–10 minutes on an Intel Arc B580 rig that ran crash-free before the update, and crashes tied to Genessa encounters — with no confirmation or rebuttal from other players in either direction. The claim stays unverified here: this page makes no fixed-or-broken call until a confirmation wave or an itemized fix list lands.

September 24 hotfix status: the hotfix's performance work — the new Low Latency Mode option (covered in its own section below), a corrected VSync tooltip when frame generation is active, and hub shadow and texture optimizations — plus its elevator-lift fall prevention all shipped without an itemized fix for this cluster. The cluster's current shape got a fresh data point the day before that announcement: a September 23 Bug Reports thread describes crashes roughly every 30 minutes whose Windows error stack bottoms out in D3D12, the game's DirectX 12 render interface, naming D3D12Submission.cpp and its ForEachQueue/ProcessInterruptQueue functions — a graphics-queue crash class rather than any specific in-game trigger. The thread's lone fix suggestion sits unanswered, and nothing since the patch has confirmed or cleared the cluster either way, so the workarounds below remain the only tools with confirmed successes attached.

• Lower graphics settings and turn off ray tracing — the one player-confirmed fix so far: crashes stopped entirely after this change on a rig that had run max settings smoothly
• Cap the frame rate at 60 and keep frame generation off — the standard advice across the crash threads, pairing the framegen workaround above with a strict cap
• Start at 1080p Lowest and step up — crash sufferers report beginning at the floor and raising one setting at a time to find what their build tolerates
• DDU driver resets and stress-testing the rig — recurring advice for the hard-freeze variant; attributed suggestions, not confirmed fixes
• Save files: players in the crash threads report crashes corrupting saves — one counts three corrupted saves from crashes alone, four including the beta — which makes the backup routine in the Week 1 section above the only documented protection

Stuttering fixes beyond the hotfix (attributed)

For stuttering and frame drops specifically, the settings-level fix with the strongest support is the shader cache change above — LagoFast independently calls it the most effective fix for the game's stuttering. Beyond that, everything else is attributed opinion rather than official guidance: the settings box on this page collects LagoFast's additional suggestions — disabling in-game V-Sync, capping the frame rate externally, a High Performance power plan, lower Shadow Quality, DLSS/FSR in Balanced mode, and a community-reported launch option — with full attribution so you can weigh them yourself.

One million people played the beta across Steam, PS5 and Xbox — announced by the development team on August 17 — so launch-week reports cover an enormous range of hardware. Treat any single settings list, including LagoFast's, as a starting point to test rather than a guarantee.

One new face in the September 8 bug reports: a single player describes performance degrading progressively after roughly half an hour of play — stutter that eventually reaches the audio — with restarts not preventing recurrence. It is one unconfirmed report, and its reporter ties it to no specific patch.

Screen tearing: the V-Sync trade-off (attributed)

Screen tearing — horizontal tears in the image when a frame lands mid-refresh — has no officially confirmed fix in Mortal Shell 2. The attributed guidance from LagoFast runs against instinct: disable the in-game V-Sync and cap the frame rate externally instead (for example at 60 FPS via a tool like RivaTuner). The logic is to let one frame-rate governor handle pacing rather than stacking the game's own V-Sync on top of it.

As with every attributed setting on this page, treat it as a test rather than a guarantee: change one thing, re-test, and keep what your hardware actually responds to.

Resolution capped below your monitor's native height? The Windows scaling cause (community-confirmed)

One more display problem has a community-confirmed cause rather than a fix: the game's resolution list stops short of the monitor — a 4K panel seeing its options top out at 2560×1440 with native 4K absent, and one ultrawide reporter describing restrictions on a 32:9 display with the same suspicion attached. The Bug Reports thread (open since August 17) settled on a cause through the reporter's own experiments: Windows custom scaling. At 100% scaling the full resolution list returned; at 300%, the in-game cap reportedly dropped as low as 720p. That attribution is player-confirmed, not official — a Playstack team member logged the issue with the team ("I have updated the ticket"), no patch notes have claimed it, and the September 24 hotfix's only display-adjacent addition is the latency option below.

What to try, in order of support: set Windows display scaling to 100% (Windows Settings > Display > Scale), relaunch, and re-check the game's resolution list — the reporter-confirmed lever. If you run a higher scaling deliberately, the thread's second lever is single-report only: enabling DPI compatibility on the game's launch file. Neither is an official fix; if one ships, it will be on the patch notes page.

Low Latency Mode: the September 24 hotfix's official latency option

The September 24 hotfix shipped Mortal Shell 2's first official latency lever: a new Low Latency Mode graphics option, built on NVIDIA Reflex on GeForce cards and AMD Anti-Lag 2 on Radeon ones — the two GPU vendors' input-latency-reduction technologies, which keep the GPU from queuing frames far ahead of the display so your inputs reach the screen sooner. If the game feels laggy on the controls rather than choppy in the frame rate, this is the settings-page lever to try first — an official one, unlike the attributed settings above it. The hub shadow and texture optimizations from the same hotfix are automatic and need no settings change.

One honest scope note: the hotfix notes announce the option alongside a corrected VSync tooltip (the tooltip previously misdescribed V-Sync while frame generation was active) and fixes that stop players falling through elevator lifts, but they claim nothing about the crash cluster or the stutter reports above. Treat Low Latency Mode like every other lever on this page — one change at a time, re-test, keep what your rig actually responds to. The complete hotfix list lives on the patch notes page.

Compiling shaders: why the stutter happens and what the cache does

Much of Mortal Shell 2's mid-fight stutter points at the same underlying shader-compilation behavior the lock-up fix addresses: when the game meets visual effects it has not compiled yet, that compilation lands in the middle of play as a hitch. The fix with the strongest support is the same one Playstack's community manager recommends for lock-ups — set Shader Cache Size to Unlimited in the NVIDIA Control Panel (or the AMD Software equivalent) so compiled shaders are kept instead of being recompiled.

LagoFast additionally lists the community-reported -UseFixedTimeStep Steam launch option as a thing to try for shader stutter. That one is community-reported only — it is not an official recommendation, so weigh it accordingly. The forum's own pinned [PC NVIDIA] stutter thread makes the same cache recommendation as Fix 3 — clear the shader cache and raise its size — and a separate thread asks why the game reserves so much space for shaders in the first place; both point at the same lever.

Won't launch? Check the requirements before anything else

If the game won't launch at all, start with the blunt possibility: the machine may sit below the floor that Steam publishes. The listing sets a clear minimum for PC players, and two details are easy to miss — the game wants 70 GB of space and an SSD is required, not merely recommended.

Two of the listed numbers trip people up in practice: the GPUs on the minimum list carry 8 GB of VRAM, and the storage note says SSD required — a spinning drive is below minimum no matter how much space is free.

The PC release is also Windows-only: there are no macOS or Linux listings, so if you are trying to launch it there, that is the whole story.

Once the game runs clean, the boss guide maps the ten fights ahead.

• OS: Windows 10 / 11 (Windows-only release)
• CPU: Intel Core i7-10700K @ 3.8 GHz or AMD Ryzen 5 3600 @ 3.6 GHz
• RAM: 16 GB
• GPU: NVIDIA GeForce RTX 2060 SUPER 8 GB or AMD Radeon RX 6600 8 GB
• DirectX: Version 12
• Storage: 70 GB available space — SSD required

Black screen: what is confirmed — and what isn't

Black screens sit in a gray zone. Publisher channels have confirmed frequent crashes, the Keyboard Bindings crash, and full lock-ups including loading-screen freezes, but no black-screen-specific fix has been announced. What you can honestly do is run the confirmed stack — the crash hotfix, the save-file workaround if the crash has that trigger, the shader cache change, and the requirements check — because those are the fixes that exist.

Anything beyond that list is not yet official. If you report a black screen in the Devout Edition bug-report megathread, include your build number — it is readable on the pause menu, bottom right. That thread and the Steam news page are where Playstack posts fix notes first, and this page gets rechecked when they do.

How do you stop Mortal Shell 2 from crashing?

Install Hotfix 1 — it is now a standard patch on the default branch, so a normal update applies it. If the crash happens when opening Keyboard Bindings, delete EnhancedInputUserSettings.sav and SpartaGameSettings.sav as described in Fix 2. For full lock-ups, set Shader Cache Size to Unlimited in the NVIDIA Control Panel (Fix 3). If random crashes survive all of that, the crash threads' one player-confirmed success is lowering graphics settings and turning off ray tracing. Apply one change at a time and re-test after each, so you know which fix your crash actually responded to.

How do I fix Mortal Shell 2 crash on load?

Set Shader Cache Size to Unlimited in the NVIDIA Control Panel — Playstack's community manager recommends exactly that for the confirmed loading-screen lock-ups after a death. Frequent general crashes are covered by Hotfix 1, and no other cause has been officially named.

How do I fix Mortal Shell 2 stuttering?

Set the shader cache to Unlimited — it has the strongest support: LagoFast independently calls it the most effective stuttering fix, and Playstack's community manager recommends the same change for lock-ups. LagoFast's further suggestions (disabling in-game V-Sync, capping the frame rate externally, a High Performance power plan, lower Shadow Quality, DLSS/FSR in Balanced mode, and the community-reported -UseFixedTimeStep launch option) are attributed opinion, collected in the settings box on this page.

Why won't Mortal Shell 2 launch?

Check Steam's minimum specs first: Windows 10/11, an Intel Core i7-10700K or AMD Ryzen 5 3600, 16 GB of RAM, an RTX 2060 SUPER or RX 6600 with 8 GB, DirectX 12, and 70 GB on an SSD. The PC build is Windows-only, so there is no macOS or Linux version to launch.

How do I fix the Keyboard Bindings crash in Mortal Shell 2?

Delete EnhancedInputUserSettings.sav and SpartaGameSettings.sav in AppData\Local\MortalShell2\Saved\SaveGames, then relaunch — that is Playstack's official workaround. It is not a permanent fix: the publisher says one is in progress, and the page's pending-verification box tracks that status.

How do I fix screen tearing in Mortal Shell 2?

No screen-tearing fix has been officially confirmed. The attributed guidance is to disable the in-game V-Sync and cap the frame rate externally — for example at 60 FPS — so a single governor handles frame pacing. Change one setting at a time and re-test after each.

Did the Week 1 Update break frame generation?

It broke for some players, yes. The Week 1 Update officially reworked frame generation (it now applies after a reload, and NVIDIA frame gen covers a much wider card range), but the pinned Week 1 discussion thread collects multiple reports of frame generation not working after updating — including from a player with mods uninstalled who toggled it off and on and restarted repeatedly. There is no official fix announcement yet. Until one lands: fully quit and relaunch (the rework only applies after a reload), confirm the patch downloaded completely, and if it still misbehaves, play with frame generation disabled. The September 1 PC hotfix did not touch frame generation — its six fixes, listed on the patch notes page, are all visual and traversal items — so the workaround stands.

Mortal Shell 2 save file disappeared after the update — what now?

Start with the official recovery path. Playstack's pinned Known Issues post (last edited September 3, 2026) lists a missing-saves workaround: in \Users\[Your Username]\AppData\Local\MortalShell2\Saved\SaveGames, rename WorldState_Backup_0_[N].sav — the [N] is a number — to WorldState_0.sav and relaunch the game. If your settings were affected too, the same post says to delete EnhancedInputUserSettings.sav and SpartaGameSettings.sav from that folder, and the save itself can also be re-downloaded from Steam's remote storage page (store.steampowered.com/account/remotestorage). Playstack has also replied "we are aware and are looking into this" on a player's save-wipe report, so the bug is officially acknowledged. One more recovery path exists, and it comes straight from the publisher: in a September 30 reply on the same thread, a Playstack team member pointed a player to the in-game option Main Menu > Load Game > Restore Save — a path that appears in neither the pinned post's Missing Saves list nor Steam's remote-storage page, so treat it as a companion to the rename workaround and your own folder backup, not a guaranteed fix.

Two caveats before you rely on it: the rename only works when a WorldState_Backup file actually exists — at least one wiped player reports their SaveGames folder held no backup file at all, only Steam Cloud files, leaving the workaround unavailable in that case, and a second player on the same thread reports a recovery attempt failing outright ("Tried doing the backup save and didn't work, game just crashed and lost my save file") — and none of these recovery paths are a substitute for your own backup. Copy the SaveGames folder somewhere safe before every update; if a save disappears right after one, restore your folder copy before relaunching. If you have neither a backup nor a WorldState_Backup file, report it in the bug-report thread with your build number — do not start overwriting saves first.

There is now also an official intake channel for wiped saves. In a September 24 save-wipe thread, a Playstack reply asks affected players to zip their SaveGames folder (\Users\[Your Username]\AppData\Local\MortalShell2\Saved\SaveGames) and send it to the publisher — through Discord or at support@playstack.com with the subject line "Mortal Shell II Missing Save". The same thread adds two useful confirmations: a player who lost a save verified the rename workaround above genuinely worked for them ("Renaming the backup was a successful workaround. It was an older save but way better than having nothing"), and a follow-up Playstack reply asked players to "please do make a back up while we're still looking into these issues" — the investigation is officially ongoing. The wipe reports have not stopped either: hours after the September 24 hotfix announcement, another player reported 80+ hours and 87 levels erased by a freeze on leaving a beacon, and a separate report the same week describes a 60-hour save vanishing with Steam Cloud recovery failing — posted after an announcement is not the same as caused by the patch, and no link between the hotfix and either wipe is claimed here.

Stuck in a falling loop or a locked arena?

The newest movement blocker in Bug Reports is the falling loop: a player who died in the Holding Cells well dungeon got dropped into a permanent falling loop by the Egon's Stone revive teleport, with no load spot to catch them. Three escapes are on record in that thread, none official. First, the "return to the hub" item breaks the loop but costs all of your currently-carried Gloom — the same loss as dying, so the spend-down-at-a-Beacon habit from the farming guide's death-loss answer is worth keeping between risky dungeons. Second, one player reports a shader-cache reset cleared the loop for them; the step-by-step lives in the forum's pinned [PC NVIDIA] shader thread (sources below), the same cache lever as Fix 3 above. Third, the cheapest one: a later reply confirms you can just quit to the main menu and continue — the game spawns you back at the start of the dungeon normally, with no Gloom cost and no settings change.

Arena locks are the other shape, with two September reports. Re-entering the royal tomb whose boss fight unlocks the Lazlo shell after patching — with the boss killed before the patch — raises thorn walls that seal the arena with no exit, because the thorns don't register the boss as already dead. That report has a matching reply and no fix, so the only prevention is not re-entering a tomb you have already cleared. The softer variant self-resolves: a player softlocked by the corruption wall right after picking up the Lazlo shell reports a quit-and-restart cleared the wall. Until fixes land, a restart is the fallback for every case here.

Patch status (September 14 hotfix): the hotfix notes list "Fixed dungeons not loading correctly after using Egon's Stone" — the falling loop's trigger — and "Fixed issue that could trap players in the dungeon after claiming Lazlo", which is the corruption-wall shape. On a fully updated client both locks are therefore expected fixed, which reframes the escapes above as the fallback for un-updated clients and for whatever the notes don't cover. Community confirmation is still thin, so treat "expected" as exactly that — and if you still hit a loop or a lock after updating, report it in the bug threads with your build number. The royal-tomb re-entry lock has no named hotfix line; whether the hotfix's dungeon fixes caught it too is unconfirmed (tracked in the pending box below).