Mortal Shell 2 Fix Center
Game crashing? Start here. Every known issue, sorted by how quickly a fix can be applied — 30 seconds, 2 minutes, or 5 minutes — with honest status labels and zero content-farm advice.
Why crash fixes matter in Mortal Shell 2
52 tracked PC issues (22 triaged + 30 recently reported) — and most of them share the same root causes.
Mortal Shell 2 launched with more stability issues than most players expected. Across the first two weeks of release, the community documented 19 distinct PC crash types — ranging from hard exits to desktop to soft-lock audio loops. The single largest category is D3D12 GPU crashes, which account for the majority of reports on Steam and Reddit. Right behind that, Frame Generation stands out as the most reliable trigger: toggling DLSS 3 Frame Generation on almost any RTX 40-series GPU causes a hard crash within the first 10–30 minutes of gameplay. These are the crash fixes most players land here looking for.
Shader compilation is another major pain point. When the game compiles its shader cache on first launch (or after a driver update), the process can stall, consume excessive VRAM, or crash the rendering pipeline entirely. Shader compilation crash fixes are the second-most-reported category after D3D12 GPU crashes. These crash fixes are particularly important because they affect players before they even reach the main menu. The good news: most crash fixes for the game are straightforward — toggle a setting, update a driver, or delete a local cache file. The crash fixes here cover every known stability issue, and applying the right ones early saves hours of frustration.
Steam Deck players have a different but related set of concerns. The game earned a Playable rating on the Deck, which means it runs but needs manual configuration. The Steam Deck crash fixes in this hub cover Proton version selection, graphics parameter unlocks, and FSR/TSR tuning to keep the handheld stable. These crash fixes are essential because the Deck's limited VRAM makes it more susceptible to the same D3D12 issues that affect desktop GPUs. The crash fixes for the Deck are compiled separately since Proton requires different steps than native Windows. Applying the right crash fixes on the Deck will save you hours of trial and error.
How the triage flow works
Every crash fix in Mortal Shell 2 is sorted into one of three categories.
The crash fixes on this site follow a strict triage system. Each of the 22 triaged issues is labeled with one of four statuses (the 21 recently reported items carry their own status labels in the community section of the crashing page):
- Fixed — The developer patched this in an update. If you're running the latest patch (Hotfix 1.000.012, October 14), every fixed entry below is already applied. You don't need to do anything except keep your game updated.
- Workaround — No patch exists yet, but a reliable player-side crash fix is available. These are the crash fixes you'll use most. They range from 30-second setting toggles (like disabling Frame Generation) to 5-minute cache clears (like deleting the shader compilation folder). Every workaround is tested and confirmed by multiple community reports.
- Pending — No crash fix exists on either side. These are issues that require a code-level change from the developer. The best you can do is report them and avoid the trigger condition. Pending crash fixes are tracked in the "Still broken" section below so you can see exactly what's waiting on a patch.
- Partially fixed — The developer targeted the issue and most players are clear, but some configurations still report it. Treat the remaining workaround as insurance until a later patch closes it out.
The triage flow for these crash fixes is designed for Frank-type users — players who crashed, searched, and landed here with one goal: stop the crashing. Start with the Crashing card below, apply crash fixes in order of time investment (30 seconds first), and check the Pending section last. Most Mortal Shell 2 crash fixes will resolve your issue in the first two steps.
Start here
Two entry points, one triage flow.
Game Crashing — All 52 Tracked Issues
The complete crash fixes index. Covers shader compilation freezes, D3D12 GPU crashes (the most common category), Frame Generation hard exits (the single biggest trigger), GC memory errors, save corruption on quit, and every other documented crash. Each crash fix is tagged with its triage status, time-to-apply estimate, and the specific game version that addressed it. If the game is crashing on your PC, this is where every crash fix lives — sorted fastest-first. These crash fixes cover all 52 tracked issues, including recently reported community items.
Steam Deck — Best Setup
Mortal Shell 2 runs on Steam Deck with a Playable rating, but it needs the right configuration to stay stable. These crash fixes and setup guides cover Proton 11.0-2RC, the SteamDeck=0 graphics parameter unlock that prevents the game from forcing desktop-quality settings on handheld hardware, TSR upscaling, a 30 FPS lock for battery life, and tested battery profiles. Every crash fix here is specific to the Deck's AMD APU and Proton translation layer — these are not generic PC crash fixes. Applying these correctly is the difference between a stable session and constant crashing.
Patch summary: what's been fixed so far
Three updates in the first week. Here's what each one did for crash fixes.
Mortal Shell 2 received three post-launch patches within its first six days. Understanding what each patch addressed helps you avoid applying crash fixes for problems that are already solved. Here's the breakdown:
Hotfix 1.0 (August 17, 2026) — The day-one emergency patch. This update targeted the most urgent fixes, including a hard crash that occurred during the opening cinematic and a D3D12 device-removed error that affected NVIDIA GPU owners. Several fixes in this patch were specific to DirectX 12 validation failures on certain driver versions. If you installed the game on launch day, this hotfix resolved roughly a third of the documented issues.
Hotfix 2.0 (August 18–19, 2026) — The largest stability update so far. This patch delivered the bulk of the crash fixes that this hub documents. Key crash fixes addressed shader compilation hangs (the game no longer stalls indefinitely when building its PSO cache), reduced the frequency of D3D12 GPU crashes during area transitions, and improved memory management to prevent GC-related crashes during extended play sessions. For most players, this is the version where the game became genuinely playable on PC. The current game version on this site reflects the Adaptive Difficulty update (Build 25133113, September 5), which follows the Week 1 Update (1.000.008).
Balance Patch 1 (August 22–23, 2026) — Primarily a gameplay balance update, but it included a handful of additional crash fixes. These crash fixes targeted edge cases: a rare save-file corruption trigger on specific hardware configurations, a crash that occurred when opening the inventory during certain boss animations, and a memory leak tied to the shell-swap mechanic. While the fixes in this patch are narrower in scope, they matter for players who experienced these specific scenarios. For the community-reported long-session leak that remains unpatched, see the dedicated Mortal Shell 2 memory leak fix guide.
Together, these patches resolved six of the tracked problems. The remaining crash fixes that still require player-side workarounds or are pending a developer patch are tracked in the sections below. Always check which patch version you're running before applying fixes — you may already be covered. For the full entry-by-entry history of every update, see our Mortal Shell 2 patch notes timeline.
Hotfix & patch timeline
What the developer has already fixed — so you don't re-fix solved problems.
Improvements to address various crashes and other issues reported since launch. No detailed changelog — the developer said it resolved several of the crashes.
Misc crash fixes + stability and performance improvements; equipping the Slayer Seal from the Beacon menu no longer locks the UI; fixed Riposte 'stealing' enemy weapons.
PS5 adds input settings/save bug fixes, cult robe + weapon switch crash, and Change Equipment Slayer Seal crash fixes. Xbox includes all PS5 fixes + Devout Edition/pre-order skin entitlement fixes.
Economy, boss/enemy/weapon balance, Guard mechanics, Tarstone tuning + additional crash fixes. Buffed Parasitic, Grudge and Bulwark (damage reduction); Clerik's and Squall also buffed.
The first major patch. Economy rework: Glimpses and Tarcores are no longer finite. New Fragile Tarstones join the pool (Glimpse Stone, Egon's Stone; Justicar and Gloombound become Fragile variants), and Mether's Severance can now be handed to Zhirelle to reset a Shell's Bond. Heavy weapons get a broad boost — Obsidian Hammer and Great Martyr's Blade tuned up, the Trebuchaxe reworked, i-frames added to the Axatana. Many crash fixes (enemy spawning, audio, save loading, shutdown), a shader-stutter fix, a reworked Frame Generation, plus a new day-only Beacon and fast-travel point.
Console builds shipped as 1.000.008 on Sep 1 with the same content, including fixes for three progress softlocks: Vatra's Temple locking permanently after exploring it, potential crashes and softlocks during Lazlo's Rekindle, and a dialogue softlock with the tavern barkeep between Gragu's shell dying and reclaiming it. Known issue after the patch: the Malborn Offspring bug.
Hotfix addressing several bug reports: missing Shades, the FSR world-map issue, the giant spider blocking passage in the Citadel Annex, enemies not responding, collision fixes, and a Minibeacon visual fix.
Adds an experimental, opt-in Adaptive Difficulty setting (off by default, under Game > Game Settings): winning streaks raise enemy damage, health and stagger resistance beyond the usual difficulty ceiling, while struggling lowers them and caps how much of your health a single hit can take; Night Mode only ever steps up. The patch also fixes an Infinite Seal consecutive-block window, lets riposte get-ups apply status effects, buffs Sariel's Thornfall, Affliction and Agonize, stops a Genessa Augmentation interaction from granting unlimited Resolve, makes broken Fragile Tarstones return Tarcores, fixes Gloombound, and improves Gloom drop logic.
Community-reported (unconfirmed): players report an undocumented rebalance of the Duality Stone; exact values unconfirmed.
Steam News announcement (corroborated by Rock, Paper, Shotgun coverage) ↗
A cross-platform hotfix dedicated to bug fixes. Shells: Proxima no longer sticks in the Biosampler animation, and Lazlo's Temperament perk infinite glitch is fixed. Items & Stones: Mether's Severance works at the Genessa trainer, the Colossus Stone ability can be canceled mid-execution, Justiciar/Gloombound durability issues are fixed, an Egon's Stone Gloom exploit is closed along with the dungeon-loading bug it caused, and Grisha Remnant/Summon Stone spawning and targeting are corrected. Enemies & Bosses: Hexapod's diving attack no longer fires after death, frozen enemy/boss issues are fixed, the Twin Sester fight can no longer be left after she spawns, and Starved Harridan no longer gets stuck and dies. NPCs: Zhirelle interacts again in NG+, only one Mutton spawns in the hub, sidearms can no longer damage certain NPCs, and Genessa dialogue/training tutorials are fixed. World: Citadel Annex traversal camera, Ashen Cathedral death volumes, the post-Lazlo dungeon trap, burn/stasis hazard values, and several collision issues are fixed, plus general crash and stability improvements.
A cross-platform hotfix. Major bug fixes: dungeons not loading correctly when using Egon's Stone, trophy/achievement issues with "Seeking the Past" and "Bring My Ova Back to Me", Egon's Stone removing Gloom dropped in the open world, several fixes to prevent players falling through elevator lifts when walking into walls, an issue that could cause Orrem, the Reclaimed to be killed instantly, and enemies becoming aggroed during miniboss fights. Player: a soft lock when cancelling Mether's Severance with a gamepad, Stray Genessa not being interactable after using Mether's Severance, an issue with Genessa's Faithful Doubles when using Lost Clotstone, Clockwork Scythe elemental effects not applying correctly, Harbinger shades and masks not displaying in the level-up tab, the player continuing sheep attacks after transforming back into their shell, a bug that made the Slayer Seal unresponsive, and small parts of Lazlo's leg clipping through armor. Enemies and bosses: tweaked the final boss's fire ring attacks, adjusted The Warden's jump timing and trigger boxes to be more responsive, adjusted The Warden's positioning so it no longer jumps through walls, several fixes and improvements to The Warden, and fixed the player being pushed outside the Hexapod arena. UI: added UI support for Adaptive Difficulty tiers, and updated the Adaptive Difficulty indicator with new, improved icons and made the night mode icon easier to see. Optimization: added a Low Latency Mode option to the menu (NVIDIA Reflex and AMD Anti-Lag 2), fixed the missing VSync tooltip while Frame Generation is enabled, optimized shadows in the Hub, texture optimizations, and other optimizations and improvements.
Announcement body carries no version number; 1.000.011 is console-build confirmation from MP1st (level 4). Section structure follows the announcement's five blocks (Major Bug Fixes / Player / Enemies and Bosses / UI / Optimization) — see conflicts CF-R4-01. Achievement fix scope: only the two named achievements are confirmed fixed — see conflicts CF-R4-02.
A cross-platform hotfix. Player and gameplay: fixed Barrage + Solnir Shard Tarstone dealing damage to allies, the Parasitic Stone exploit when switching between sheep and shell form, an issue where unequipping Egon's Stone could prevent Gloom loss, Tarstones not granting EXP for kills by player summons, Black Needle throw and infused stone being unable to aim or interact, several Slayer Seal/Punch issues, canceling Proxima's Shell ability stopping weapons being re-equipped, an issue that blocked Gragu from being possessed, Astral Clones not attacking when summoned close to an edge, Lost Clotstone for Genessa Clones using Obsidian Hammer getting stuck and staying forever, Cursed Child and Grisha summons being hit and targeted by Biosampler, Cursed Child summons being targeted by Sidearm, and spawned summons causing collision issues on big enemies and bosses. Tiltshot projectile now spins and moves forward; force feedback tweaks and changes; cleaned up melee attack logic. Enemies and bosses: Final Boss HP reduced, player cosmic disease resistance doubled and his grab attack now has more anticipation; fixed issues around the main bosses' phase change; improved Droeg, the Conqueror's hitboxes; fixed Bor, the Deluded Monarch's lock-on location and Biosampler interaction; improved how the Monolith works with Proxima Biosampler; adjusted Orrem, the Golem's triple slam; Necrite run attack timing tweak. Dungeons: players can now collect 3 extra ovas in the final slice dungeon when playing NG+; fixed the enemy count on The Last Siege; a fix for slow-streaming dungeons when \"seamless dungeon streaming\" is enabled; a fix for double dungeon loading. UI: Mether's Breath now has multiple warning prompts, and backing out of Mether's Breath's second warning no longer soft-locks the game. Audio: fixed Lucian, the Thirsting Knight's dodge audio and Magdelena, Lady of the Woods' unparryable slam attack audio triggering multiple times. VFX and animation: new VFX for Tiel's Shadow Clones plus tweaks and fixes for Tiel's Poison Shadow Clones, a new explosion version for Droeg, the Conqueror, a Giant Spider FX pass with more feedback, force feedback, and camera shakes, and a new shell summon handshake animation with a small Gragu height tweak. Camera: improvements to camera collisions. Environment and performance: environment and collision bug fixes; general optimizations including castle stairs, mine pillars, tomb floors, and catacomb/iron maiden collision; optimized bear traps and fixed the wrong trap rotation during the disarm animation; rebuilt shader (PSO) caches and world HLODs.
Announcement body carries no version number; 1.000.012 is console-build confirmation, multi-sourced as of Oct 18: MP1st, UpdateCrazy's 1.000.012 page, and Asumetech's report agree (CF-R6-01 closed); the PC build number stays null. Section structure follows the announcement's eight blocks (Player & Gameplay 16 / Enemies & Bosses 7 / Dungeons 4 / UI 2 / Audio 2 / VFX & Animation 4 / Camera 1 / Environment and Performance 4) — see conflicts CF-R6-02. Numeric magnitudes not published by the developer (Final Boss HP reduction amount, ova-count context) stay null. A third party headline misdating 1.000.012 to the Sept 24 notes is logged as not adopted — see conflicts CF-R6-03.
A PS5 patch announced by the developer on Reddit (no Steam news announcement at verification time). Two named fixes: stuttering addressed, including around death and pick-up moments, and "Fixed softlock when interacting with the collector" (verbatim from the notes). The same announcement re-confirms Bring My Ova Back to Me is still not fixed, with a fix planned for next week's patch, and says Xbox and PC patches are coming shortly. The announcement itself carries no build number; the console build was confirmed as 1.000.013 by two secondary sources (MP1st and UpdateCrazy, both Oct 16).
Version adjudicated Oct 18 (CF-R8-01, resolved half): 1.000.013 is double-sourced at the secondary level (MP1st + UpdateCrazy), following the 1.000.011/1.000.012 precedent, so the number is now written as 1.000.013 (PS5). Still open under CF-R8-01: whether the missing-trade-UI form of #54 (UI never appears, versus the named softlock form) is covered by this patch has not been stated by anyone. Fix lines follow the announcement's own wording; the stutter fix scope is stated only as covering death and pick-up moments. UpdateCrazy's claim that the patch is already live on PS5, Xbox and PC contradicts the developer's PS5-first wording and is not adopted (CF-R9-01); Xbox/PC stay pending. Related entry updates: fixes #54 (PS5 fix published, PC/Xbox pending — status stays investigating) and #24 (Ova still unfixed, fix planned next week — status stays partial). Upgrade path: when the Steam-side announcement or PC patch notes land, re-verify wording and bump source_level.
Rotten Autumn, a large free content update, is now live. A new Photo Mode lets players capture and frame their runs. Fifteen new dungeons join the game, expanding the dungeon pool from 36 to 51 (nearly a 50% increase; the 36-to-51 figure follows the press transcription of the announcement). Every Shell receives new Shades. Ten new Tarstones are added, including one exclusive to the Sheep. A New Alternative Soundtrack performed by Sakis Tolis, vocalist of Rotting Christ, replaces the original score. On the graphics side, the update adds a Nightmode lighting preset and a new Overkill setting. Seasonal treats include a pumpkin helmet for the Harbinger and an Impervious Lute skin with a new track, and lost Shell ghosts can now leave cryptic notes. The update also ships polish and bug fixes, and the announcement closes by teasing more to come.
Follows the PS5 Hotfix 1.000.013 (Oct 16) sequence as the first cross-platform major version since 1.000.011-013. Numerical values beyond the announcement's own counts (15 dungeons, 36-to-51 pool, 10 Tarstones) are null pending in-game verification. The announcement's closing line 'there is no sheep dungeon' is a developer joke, not a content line. More content is teased in the announcement; no schedule given.
Still broken (pending developer fix)
Report these to Cold Symmetry — no player-side fix exists yet.
The crash fixes listed below are issues where neither a patch nor a reliable workaround exists. These are the hardest crash fixes to address because they require changes to the game's code, not just settings adjustments. If your crash matches one of these, the best course of action is to report it through the appropriate channels and avoid the trigger condition until a future patch delivers proper crash fixes for these remaining issues.
Phase 1 — Quick Wins
30 seconds each · 0 matching issues
Phase 2 — Deeper Fixes
2 minutes each · 3 matching issues
D3D12 GPU Crash Dump
Symptom: D3D12 GPU Crash Dump — 'GPU Crash dump Triggered' FD3D12DynamicRHI::TerminateOnGPUCrash
Cause: DX12 GPU driver crash; targeted by HF1.0 but some players still report it. Developer-acknowledged (Steam Discussions, Aug 25 & Aug 28): the developer confirmed it is "actively working on this issue and are looking into a fix." Players report this crash did not occur during advanced access and started appearing after the early hotfixes — and new reports of the same crash dump continued after the September 5 Adaptive Difficulty patch (Sept 9–10). One player traced the dump to INVALID_POINTER_READ in SetShaderParametersOnContext (community analysis, unconfirmed).
Fix / workaround:
- DDU clean driver reinstall
- Remove GPU overclocks
- Last resort: -dx11 launch option (may cause visual glitches on some systems)
Note: The Oct 14 hotfix rebuilt shader (PSO) caches and world HLODs; this may relate to shader-related crashes, but the developer did not name any crash fix in the notes. Status unchanged — monitor for recurrence (Steam event comments follow-up scheduled).
GC exception crash
Symptom: GC exception crash — EXCEPTION_ACCESS_VIOLATION 0x00000000000002c8 in a GarbageCollection stack
Cause: UE5 GC bug; may correlate with unstable Intel 13th/14th-gen CPUs A Steam-side i7-14700K report (Aug 21) shows the same Oodle shader-decompression signature; see issue #1 for the shader-compile workaround set.
Fix / workaround:
- Disable FG + Ray Tracing
- Cap FPS — One Linux/NVIDIA player measured the Xid 13 fault rate scaling with frame cap (community-reported, measured by one player, Aug 22–23, before the Week 1 patch): roughly one fault per ~19 minutes at ~175 fps, one per ~3 hours at ~100 fps, and zero faults in 2 hours at a 60 fps cap. This is one player's self-test on their own hardware, not a general crash rate; the developer logged the report (post-Sept-24 status unknown).
Note: The Oct 14 hotfix rebuilt shader (PSO) caches and world HLODs; this may relate to shader-related crashes, but the developer did not name any crash fix in the notes. Status unchanged — monitor for recurrence (Steam event comments follow-up scheduled).
Black screen after shader compile
Symptom: Black screen after shader compile — audio plays, no picture
Cause: Known issue, developer-acknowledged
Fix / workaround:
- No confirmed fix yet
- Try: clean driver reinstall, verify files, disable overlays
Phase 3 — Advanced
5 minutes each · 1 matching issue
Fast-travel / Beacon interaction crash
Symptom: Fast-travel / Beacon interaction crash — UE error when teleporting or leaving a Beacon
Cause: Regression bug, more frequent after HF2.0
Fix / workaround:
- No player-side fix yet
- Report to the developer
Not recommended (SEO-farm advice to avoid)
When to check back for crash fix updates
This hub stays current — here's the update cadence.
This Fix Center is maintained on a 24-hour hotfix SLA: when the developer releases a new patch for Mortal Shell 2, the fixes on this site are updated within one day. That means crash fix statuses get flipped from Workaround to Fixed, new fixes are added for any freshly reported issues, and the game version stamp at the top of this page is refreshed. The "Last verified" date in the page header tells you exactly when the crash fixes were last checked against the live game build.
If you applied fixes from this hub and the game is now running smoothly, bookmark this page and check back after any major game update. New patches sometimes introduce regressions — fixes that were working can break when the rendering pipeline changes. The fixes here are always tested against the version listed in the page header, not speculative future builds. Staying current is the best way to avoid new issues after an update.
For Steam Deck users specifically, crash fixes may shift when Proton updates land. A Proton version bump can resolve some crash fixes (better translation layer compatibility) or create new ones (shader translation changes). The Steam Deck crash fixes page tracks the specific Proton version that each workaround was tested against, so you can match your environment to the tested configuration. Whether you need crash fixes for desktop or Deck, this hub is your single source of truth.