Graveyard Keeper 2 Crash and Stutter Fixes

Graveyard Keeper 2 was released on September 22, 2026, but not every graveyard keeper was able to get straight to burying the dead without trouble. Some players cannot launch the game through Steam, others get stuck while loading a save, and serious FPS drops may appear after several hours of working around the graveyard. In this guide, we'll go through different troubleshooting methods and known issues that players are reporting right now.

Before changing Windows settings, compare your PC configuration with the requirements listed on the game's Steam page. Below are the official specifications provided by the developers for the PC version.

The game looks far less demanding than many modern blockbusters, but that does not mean you should ignore system load. The more production chains and zombie workers you create as you progress, the more important overall system stability becomes.

We recommend starting with safe steps that do not affect save files or system security. Test the game after every change. That makes it much easier to identify the actual cause of the problem.

Close Graveyard Keeper 2 and fully exit Steam through Steam > Exit. Then restart your PC, open the client again, and try launching the game. This is especially useful if Steam gets stuck while preparing to launch, downloading an update, or synchronizing with the cloud.

First, download the correct driver from the official NVIDIA, AMD, or Intel website based on your graphics card model and Windows version. Install the update and restart your PC. This is one of the developers' basic recommendations for crashes and poor performance.

In your Steam Library, right-click Graveyard Keeper 2, open Properties > Installed Files, and select Verify integrity of game files. Wait for the process to finish. If any files are missing or corrupted, Steam will download them again. We also recommend running this check after an interrupted update or experiments with mods.

In Steam, open Manage > Browse local files, find the game's executable, and if necessary try launching it once as administrator. This test can be useful if Windows reports insufficient permissions. The developers also recommend launching the game from the official library rather than through questionable third-party launchers.

Open Settings > Windows Update and install any available stable updates. Then restart your PC. Graveyard Keeper 2 officially requires 64-bit Windows 10 or a newer operating system.

For testing, disable the Steam overlay in the game's properties, then turn off the in-game overlays from Discord, NVIDIA App, and AMD Software if you use them. Close recording and monitoring software that can interfere with rendering, such as MSI Afterburner and RivaTuner Statistics Server. If the game starts working, re-enable programs one at a time to find the conflict.

If your laptop has both integrated and dedicated graphics, check Windows Graphics settings and make sure the game is assigned to the high-performance GPU. If you use overclocking, return the hardware to stock clocks while troubleshooting.

One more warning about popular video guides: launch options such as -dx11, -dx12, -force-d3d12, and similar commands are often recommended for many different games without any verification. Steam lists DirectX 12 for Graveyard Keeper 2, but that does not mean every arbitrary launch parameter is actually supported by this build. Do not add such commands at random, disable Windows security globally, or delete your save folder just to test an experimental crash fix.

Below are the specific situations we were able to find in official fixes or player reports. Pay attention to your game version because some issues were tied to the September launch and have already been fixed by updates.

Sometimes, after clicking Play, Steam shows that it is preparing to launch the game and then simply returns to the original button. Online videos and guides suggest dozens of fixes, including reinstalling Windows components, but there is no single confirmed cause for this exact behavior in Graveyard Keeper 2.

On release day, some players saw a Steam message saying the game had not been released yet. Restarting the client helped clear the incorrect notice, but this should not be treated as a general cause of launch problems anymore. If Steam displays a specific numerical error code, copy it down because there is no universal Graveyard Keeper 2 launch error code.

If the window appears for a few seconds and disappears, and Windows displays a Unity crash message, first rule out installation and driver conflicts. The word Unity does not point to a specific cause because the engine is used by many games, so fixes for unrelated errors and codes should not be blindly applied here. We were unable to confirm one universal startup crash code for Graveyard Keeper 2 in published materials.

Start by updating the graphics driver, verifying the Steam files, and closing third-party overlays. If the crash continues, save Player.log and send it to the developers. The file is located in %USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2.

If the menu does not appear and you only see a black screen, first check whether the game is completely frozen or whether the problem only affects image output. If the settings are accessible, try switching between Windowed and Fullscreen modes. Then close the game, disable overlays, and restore default graphics settings. Xbox previously had a separate crash when closing the game after a black screen, which was fixed in Patch 1.007.

One of the most frustrating issues affects saved-game loading. The progress bar reaches the end, but you cannot continue playing. The developers confirmed this problem and fixed one infinite-loading case caused by an exception in the conveyor system in Update 1.008 on October 2.

If the update does not restore a specific save, the case will require individual diagnosis.

Sleeping is not only used to restore the character's energy. The bed also saves your progress. The developers fixed one crash related to this mechanic in Patch 1.008 on PC, and a similar fix was included in console version 1.009.1 on October 9.

Start by updating the game and restarting it. If you have already encountered the issue, do not power off your PC or console while save data may still be writing because that increases the risk of losing progress. Switch players have also reported freezes during sleep, but we do not recommend assuming that a PC fix applies to the console version.

If the first half hour runs normally but stuttering, FPS drops, and freezes begin later, you may be experiencing one of the known performance issues. tinyBuild explicitly warns that long play sessions can cause memory usage to build up and performance to degrade across different platforms. The official temporary recommendation is to save regularly and fully restart the game every few hours.

One player posted Steam measurements showing that RAM and VRAM usage increased sharply in Fullscreen mode, while switching to Windowed temporarily stopped the growth. Another player reported a graphics driver crash after a long session despite moving to Windowed mode.

We do not recommend trying to fix this symptom with an enormous page file or automatic memory-cleaning utilities from unverified guides. If performance degrades predictably, record the play-session length, memory usage, and GPU model for a developer report.

Frame-rate drops can happen around complex production chains and in certain locations. The developers specifically improved performance at the top of the Alchemy Tower in Patch 1.005, so if FPS suddenly drops there, make sure the game is updated. Steam Deck discussions also include reports of stuttering even at reduced settings, and some players found that limiting the frame rate to 40 FPS through the device menu helped. Keep in mind that this is a community workaround, not an official fix.

On PC, start by capping the frame rate at a value your system can maintain consistently and test the game at Medium quality. Then lower the resolution and close additional applications one at a time while checking whether the stutter disappears. On Steam Deck, you can test a 40 FPS cap. On other handheld devices, use their own frame-limit settings. If the game only begins slowing down after several hours, follow the recommendations from the previous section because the issue may be related to session length rather than one specific scene.

Zombie workers are supposed to simplify production, but in early versions they could become a problem themselves. The developers fixed a freeze that occurred when assigning a worker to a station if the previous worker was already considered invalid. The same Patch 1.009 also fixed popup errors when a zombie gardener tried to harvest a crop that no longer existed, along with cases where zombies could become stuck after delivering resources from the mine, sawmill, and other production sites.

If you see an endless error popup or a worker has stopped moving, check your game version first. This is primarily a reason to install Patch 1.009 or newer. After updating, restart the session and test the affected station again. Do not dismantle half your production chain or delete zombies just to fix the issue. The relevant logic has already been patched, and any remaining problem may have a different cause. If a zombie simply refuses to start working but no error appears, check our guide to zombie workers and production automation, since the problem may be related to assignment requirements, tools, or supply rather than a technical bug.

After release, players encountered cases where the Research Table stopped responding after an item was placed on it to gain Science Points, while the Crematorium could become stuck with a body and stop working. Both issues were confirmed in the Patch 1.005 notes from September 24. These are workstation bugs rather than signs of insufficient VRAM, so experimenting with DirectX settings or drivers is unlikely to explain them.

Check whether Patch 1.005 or a newer version is installed, then repeat the action with the affected object. If the workstation remains unavailable even after updating, save information about the quest state and take a screenshot for the developers. Without confirmation, we do not recommend deleting the object through third-party tools because that may damage quest or item references inside the save.

Another confirmed issue could appear after returning to the main menu or beginning a new playthrough. The character and interface could remain locked as if a completed cutscene or battle were still in progress. The developers included a fix in Patch 1.009 on PC and later added the same change to console update 1.009.1.

If you see this symptom, install the latest update first. Then fully quit the game and reload the save instead of trying random button combinations to bypass the lock. If the problem is reproducible, report the exact scene after which it begins. That detail is far more useful to the developers than simply saying that the game freezes.

The game has had issues with non-standard resolutions, including ultrawide displays. In Patch 1.006 on September 25, the developers reported fixing intermittent crashes in such configurations. Advice from older videos about changing resolution should therefore be viewed in light of the update that has already been released.

Update the game and check whether the crash still happens at your monitor's native resolution. If it does, temporarily switch to Windowed mode or a standard aspect ratio to determine whether the issue is tied to the display format. There is no need to change global graphics-driver settings just because one display mode is unstable.

Not every freeze is related to frame rate. Sometimes the character can still move, but the required door does not open, a quest step does not register, or a location remains inaccessible. The developers also fixed a quest issue involving inflation and mercenaries that could leave the garden bed locked. Patch 1.009 addressed soft locks after upgrading the Nun's Camp and several collision problems involving production objects. If the issue happens specifically during Agatha's storyline, check the quest order in our Agatha quests walkthrough.

First, check for updates and reload your playthrough. Do not start a new game while there is still a chance to recover the existing save.

Console versions received fixes on a different schedule from PC, so copying steps from Windows troubleshooting guides makes little sense here. Update 1.007 for PlayStation and Xbox fixed various crashes related to loading, closing the game, and interacting with objects, as well as a separate Xbox crash after a black screen. Later, on October 9, Patch 1.009.1 arrived on those platforms with a fix for crashing during sleep and worker freezes. The official known-issues list separately notes that some fixes still awaited corresponding updates on Switch and Switch 2.

If the game closes by itself, first check for an update through the console menu and system settings. Be especially careful with save files. Players have reported freezes while progress was being written and then being unable to load the file afterward. If cloud backups are available, check their status before deleting local data. On Switch, do not try to follow instructions involving Windows folders because they do not apply to that platform.

Some players reported that after sleeping and returning to the menu, the only available option was to start over instead of continuing. Others encountered infinite loading of an existing save. The most important thing right now is not to overwrite any remaining progress data.

On PC, open %USERPROFILE%\AppData\LocalLow\Lazy Bear Games\Graveyard Keeper 2 and copy the entire folder to a safe location. It contains the game's user data. Do not delete it or replace it with files from the first Graveyard Keeper, which uses a completely different directory. Players have already made that mistake. Then check that the game is fully updated and review Steam Cloud synchronization. If the local and cloud versions conflict, only choose a source after comparing timestamps and creating a backup, otherwise you may accidentally lock in an empty or outdated save.

If the issue still repeats after installing updates, it is better to send the developers a reproducible report instead of continuing to change system settings at random. On PC, you can do this directly from the game using the bug-report button in the upper-left corner of the main menu or through the pause menu. If you cannot reach either screen, use the official tinyBuild Known Issues database and the Bug Reports section on Steam. You can also check the current patch notes there to see whether your problem has already been fixed.

Include a description of the symptom, game version, PC specifications, driver version, and the sequence of actions immediately before the crash. If you suspect a save problem, back it up first and do not publish personal files openly unless necessary. A report that only says the game crashes constantly gives the developers almost nothing to investigate. Naming the exact workstation, quest, and time when the issue appears is far more likely to lead to a useful fix.