Stonewards Crashes: Causes and Fixes for the Steam Co-op Defense Game
Stonewards crashes ruining your co-op runs? Learn which hotfixes solved stability issues, how to verify game files, and what to send when reporting bugs.
Stonewards crashes have two common sources: playing an outdated build and bugs in the game's young multiplayer code, so the first steps are to update to the latest hotfix (0.1.6 shipped on August 18, 2026), verify your game files in Steam, and try the alternate graphics API launch option if your installation still offers one. Banana Tiger Studio has been shipping fixes at a rapid pace since the August 11 Early Access launch, and many issues reported by players have already been patched. This guide separates confirmed, game-specific fixes from generic PC advice so you know exactly what applies to Stonewards.
Why Stonewards Crashes Happen
Stonewards is a solo and 1-4 player co-op first-person roguelite defense game built in Unity, and like most online co-op titles in Early Access, its stability depends heavily on the version you are running. During the June 2026 demo period, players reported repeated crashes in multiplayer sessions, including one group that hit "at least 5 crashes on different games" and another player whose game "crashes a minute after I log in with a friend" alongside serious desync. The developer responded directly in the Steam forums, apologized, and confirmed they were investigating, which means many of the worst demo-era crash reports were known issues being actively worked on.
Since Early Access began on August 11, 2026, the studio has released hotfixes 0.1.3, 0.1.4, 0.1.5, and 0.1.6 in a single week. These patches fixed multiplayer progression problems, dead-player bugs, save system failures, and stuck input states. If your game is crashing today, the single most likely explanation is that you are running a build from before one of these fixes. Check the news section of the Stonewards Steam community hub to see which hotfix is newest before assuming something is wrong with your PC.
Update First: The Version You Run Matters Most
The developer has been explicit that version mismatches cause problems. In the demo update notes for 0.1.9 and 0.1.10, they warned that "you must be on the exact same version as your friends to play together," and advised that if you do not see the current version number in the bottom right corner of the screen, you should restart Steam to force the download. While that guidance was written for the demo, it reflects how the studio distributes updates, and version mismatches between players remain a plausible cause of co-op failures in Early Access.
The update-first rule also applies to crash symptoms that look like hardware problems. Hotfix 0.1.3 (August 12) fixed players becoming stuck on the end-of-run screen, hotfix 0.1.4 (August 13) patched a backup save that could not be used when the main save failed, and hotfix 0.1.6 (August 18) fixed player input that could become blocked during upgrade selections. None of these are things a driver update or settings change on your end would have solved. For background on the game's release timeline, see our Stonewards release date page.
DX11 and DX12 Launch Options: What We Know
The Stonewards demo shipped with two launch options on Steam, as recorded in SteamDB's configuration data. The first, "Play Stonewards Demo (DX11 - Recommended)", runs the game with the -force-d3d11 argument. The second, "Play Stonewards Demo (DX12 - Use only if game crashes)", runs with -force-d3d12. In other words, the developer's own demo configuration treated DX11 as the default path and DX12 as a fallback for players experiencing crashes. Note that both minimum and recommended system requirements on the Steam store page list DirectX 11, not 12.
Whether the Early Access build keeps these same launch options is unverified; they are documented only for the demo configuration. There is also a caution from the community: in a June forum thread titled "Game constantly crashing", the original poster said they "tried with and without DX12" and still crashed, though the same player later reported the crashes had stopped after subsequent testing. Treat the alternate launch option as one diagnostic step, not a guaranteed cure. If your build offers a DX12 choice and the game crashes on launch, trying the other option is free and takes seconds.
Verify Your Game Files (Generic PC Advice)
This next step is generic Steam troubleshooting, not a Stonewards-specific fix, but it rules out corrupted downloads cheaply. In Steam, right-click Stonewards in your library, choose Properties, open the Installed Files tab, and click "Verify integrity of game files". Steam will re-check the installation and re-download anything that does not match the depot. This addresses crashes caused by interrupted or corrupted updates, which can happen after any rapid patch cycle like the one Stonewards has had.
Also worth checking, again as generic advice: keep Windows updated and install current GPU drivers before blaming the game's netcode, and confirm your hardware meets the minimum spec (Windows 10 64-bit, Intel Core i5 at 2.5 GHz, 8 GB RAM, GTX 1060 or RX 480, and 5 GB of storage). The store page notes both spec tiers list DirectX 11, so systems that only support older DirectX versions are below minimum. You can read more about supported systems on our Stonewards platforms page.
Multiplayer Crashes and Desync
The crash reports that drew developer responses were overwhelmingly multiplayer ones. In the "Game constantly crashing" thread from June, one reply observed that the crash seemed to happen when a non-hosting player picked up stone or wood at the start of a game, though the original poster noted crashes continued into the third wave as well. In a separate thread, a player reported the game crashing about a minute after joining a friend, together with severe desync. Banana Tiger Studio replied to that thread in late June: "We made some fixes for co-op/desync issues. Is it better for you in the latest version, 0.1.10?"
The pattern to take away: multiplayer crashes during the demo era were acknowledged by the developer and specifically targeted with fixes, including demo update 0.1.10's multiplayer fixes and progression-blocker corrections. After Early Access launched, hotfix 0.1.3 fixed progression only being awarded to the host, character unlocks not being shared, and mission progression not tracking for connected players. If a crash today happens only in co-op, note whether you were hosting or joining, since that detail materially changes the diagnosis. For connection problems rather than crashes, our separate can't join game guide covers lobby and matchmaking issues.
Stuck and Dead-Player States Fixed by Patches
Several issues that feel like crashes or freezes were actually game states the developers have already patched. Hotfix 0.1.5 (August 14) "added an option to recover/teleport stuck dead players as a temporary safeguard" while the studio continues working on ragdoll physics issues, and fixed an issue where dead players or companions could keep gates open. Hotfix 0.1.6 (August 18) fixed an issue where player velocity was not reset on death, "which could cause players to be launched into the air after being revived", and another where input could become blocked during end-of-wave or upgrade selections.
If you have experienced a frozen screen after death, an unresponsive menu during upgrade picks, or a teammate's ragdoll behaving strangely, the answer is likely already in one of these hotfixes rather than in your PC configuration. The studio framed the stuck-dead-player teleport as a temporary safeguard, so ragdoll problems may not be fully resolved yet. For a broader overview of what the game includes at this stage of development, see our Stonewards game info page.
How to Report a Crash Usefully
When Banana Tiger Studio replied to crash reports, they told players exactly what information helps: report the issue in the bug report section of their Discord (or the Steam Discussion forums) with details on when the crash happens, whether you were host or client, the wave number, and whether DX12 was enabled. Including your game version, visible in the bottom right corner of the screen according to the demo update notes, and a description of what you were doing at the moment of the crash will speed things up further.
The studio reiterated at Early Access launch that they closely track bug reports on Discord and monitor the Steam forums, and the pace of hotfixes since launch backs that up. Reports from players during the demo demonstrably shaped fixes such as the co-op and desync corrections in update 0.1.10, so a detailed report is genuinely useful.
Sources
Frequently Asked Questions
Quick answers to the most common Stonewards questions.
Why does Stonewards keep crashing in co-op?
During the demo period, players reported crashes during multiplayer sessions, including desync issues, and the developer shipped co-op and desync fixes in demo update 0.1.10. After the Early Access launch on August 11, 2026, successive hotfixes (0.1.3 through 0.1.6) addressed additional multiplayer problems. Always update to the latest version before troubleshooting further.
Should I use the DX12 launch option to stop crashes?
The demo shipped two launch options: DX11 with '-force-d3d11' labeled Recommended, and DX12 with '-force-d3d12' labeled 'Use only if game crashes'. Whether the Early Access build keeps these launch options is unverified. One player reporting constant crashes said they tested with and without DX12 without a clear difference, so it is not a guaranteed fix.
How do I make sure I have the latest Stonewards update?
In demo update notes, the developer said the version number appears in the bottom right corner of the screen, and restarting Steam forces the download if an update has not appeared. The same version check is a reasonable first step in Early Access.
Where should I report a Stonewards crash?
Banana Tiger Studio asks players to report bugs in the bug report section of their Discord, or in the Steam Discussion forums. For crashes, include when the crash happens, whether you were host or client, the wave number, and whether DX12 was enabled.