The Sinking City 2The Sinking City 2Independent player notes

GuidesCrash fix

The Sinking City 2 crash fix and troubleshooting guide

Checked August 26, 2026: Hotfix 1.0.2 is the latest update label on the official Steam feed. That label is a source snapshot, not proof that a particular PC has installed the update.

One-line answer: On the Windows Steam build, first verify files, then update the display driver, test the official removable PSO launch option once, and revert it if the same crash remains before submitting the requested evidence to Frogwares.

Calvin aims a handgun at a kneeling humanoid creature in a dark room
Official gameplay art provides visual context only; it cannot diagnose a crash · © 2019–2026 Frogwares Ireland Ltd. Source: Steam store, app 2825860

Choose where the crash happens

Start with the failure stage, not a copied list of tweaks. Change one variable only after recording the symptom so you can tell what helped and reverse what did not.

Crash symptom triage before applying a change
What happensCapture firstNext route
Closes at launch or before the main menuNote the last logo or screen, whether an error appears, and whether the game has ever opened on this PC.Restore a clean baseline, then follow the verify-files and driver steps before testing the official launch option.
Crashes after difficulty selection or the Library flashbackRecord the exact transition and whether the same save or New Game attempt fails every time.This matches the stage Frogwares discussed for its temporary PSO-cache launch option; reach that step in order and remove it if it does not help.
Crashes during play or at a repeatable locationWrite down the chapter, room, action and save used; keep a screenshot or short video if the failure is repeatable.Check the official update history, verify files, retry once from a clean baseline, then report the reproducible case.
Windows restarts or the whole PC powers offRecord whether Windows rebooted, shut down or froze and whether the same system-level failure happens outside this game.Stop the game-level test ladder. Preserve the evidence and seek platform, Windows or hardware support as appropriate.

Safety boundary: Do not treat a full system restart as an ordinary game crash. A Steam launch option cannot establish the cause of a Windows or hardware-level shutdown.


Use the reversible fix ladder

Before step 1, exit the game and record existing launch options, graphics settings, mods and driver version. Temporarily return to an unmodified game where possible. Change one thing, test, record the result, then revert anything that does not help.

  1. Verify installed files: In Steam, right-click TSC2, open Properties → Installed Files, then choose Verify integrity of game files. Let Steam finish before launching again.
  2. Update the display driver: Use the graphics-card maker's official site or app, install its current stable driver, and follow its restart instruction. Keep third-party driver tools out of this baseline.
  3. Test the official PSO launch option: Add -clearPSODriverCache in Steam's Launch Options and test the same failure once. Frogwares calls this a temporary workaround and warns that it can increase level loading times and put more strain on the CPU. If it does not help, remove it from Steam's Launch Options before the next step.
  4. Reinstall only after the reversible steps: Frogwares lists a reinstall after the earlier checks and says to reboot the PC after installation. Preserve any local-data backup you need before this larger change.
  5. Send an official crash report: If the same crash remains, stop repeating changes and send the requested evidence through Frogwares Support.

Prepare the official crash report

When the same failure survives the clean test ladder, Frogwares asks for these materials:

  1. Your dxdiag.txt file. In Windows, run dxdiag, choose to save all information and keep the resulting text file.
  2. A screenshot or short video of the crash error. Include the exact message and the last repeatable action rather than only saying that the game closed.
  3. An archived copy of the local game folder at %LOCALAPPDATA%\TSC2, when Frogwares requests it.

Privacy and save boundary: The full local folder may include save and local diagnostic data. Preserve your own copy and send it only to Frogwares Support when requested. For a copy-first workflow, use the save-location and backup guide.

Submit the evidence through Frogwares Game Support. Keep the ticket focused on one repeatable symptom and list each change you tested and reverted.

Windows PC and console boundary

This procedure is for the Windows Steam build only. Do not apply this PC launch option on PlayStation or Xbox. On a console, install the platform's current game update, record the on-screen error and use Frogwares or the platform holder's support path.

A Windows crash also differs from low FPS, stutter or blur. If the game runs but performs poorly, use the dedicated settings guide rather than applying a crash command.


Continue with the right owner page

Was this crash patched?

Check confirmed official update notes, including the crash fixes in Hotfixes 1.0.1 and 1.0.2.

Check patch notes →

The game runs but performs badly

Route low FPS, stutter, blur and LOD issues through controlled one-variable settings tests.

Open the PC settings guide →

Protect local data first

Make a copy-first backup before reinstalling or sending the full local folder to support.

Back up the local folder →

Crash fix FAQ

How do I fix The Sinking City 2 crashing on PC?

Start from an unmodified Windows Steam baseline, verify the installed files, update the display driver from its official vendor, and change one item at a time. Test Frogwares' -clearPSODriverCache option only as a removable step; if the same crash remains, gather the official report materials and contact Frogwares Support.

What does -clearPSODriverCache do?

Frogwares presents -clearPSODriverCache as a temporary crash workaround. A Team Frogwares developer warns that it may increase level-loading time and CPU load. Test the same failure once and remove the launch option if it does not help.

What should I do if it crashes after choosing difficulty?

Record the exact transition, verify files, update the display driver and then test the official PSO launch option once. Frogwares has discussed difficulty-selection and post-Library-flashback crashes for this workaround, but it is not guaranteed and should be removed if ineffective.

What if the whole PC restarts or powers off?

Stop the game-level fix ladder. A Windows restart, shutdown or total freeze is a system-level symptom, so preserve the timing and error evidence and seek the appropriate platform, Windows or hardware support rather than stacking game launch commands.

What should I send in a Frogwares crash report?

Frogwares asks for dxdiag.txt, a screenshot or video of the crash error and an archived copy of the local TSC2 folder under %LOCALAPPDATA%. Submit those materials through Frogwares Support; the local archive may contain save or diagnostic data, so send it only when requested.

Sources: the current Frogwares Support crash FAQ, the pinned Team Frogwares released-game FAQ, an official developer reply describing the PSO option's tradeoffs, the official Steam update feed, and Valve's launch-options help. Sources checked August 26, 2026.