Grounded 2 Keeps Crashing: PC Fixes and Save Checks
Fix Grounded 2 PC crashes with system checks, Steam and Xbox file repair, driver updates, save comparisons, and useful support diagnostics.
Quick answer
- Install the current game update, restart your PC, and check the game files in Steam or the Xbox app.
- Check the 16 GB RAM minimum, supported graphics hardware, DirectX 12, and available storage.
- Test without mods, update GPU drivers, and compare a separate new world with the failing save.
- Keep a copy of your saves and send Obsidian the exact error, reproduction steps, and DxDiag.txt.
Patch 0.5.0.5 fixes overview
See the September update's changes, including the crash-fix discussion around 5:03, before working through the PC checks below.
Continue reading
These related guides answer the next questions around this topic so you can keep moving.
What to do when Grounded 2 keeps crashing
If Grounded 2 keeps crashing on PC, start with the current game update, a restart, and a game-file check. Then work through hardware requirements, mods, graphics drivers, and a comparison between saves. Keep the failing save intact so you can test the same moment after each change.
Patch 0.5.0.5, released September 2, 2026, addressed crashes across platforms. Install that patch or a newer available update before trying to reproduce an older crash. A crash at startup, a failure in one world, and an entire PC restart need different follow-up checks.
Check the PC requirements and crash pattern
Compare your PC against the complete minimum specification. Having enough RAM alone does not establish that the processor and graphics card meet the requirements.
| Component | Minimum | Recommended |
|---|---|---|
| Operating system | Updated 64-bit Windows 10 or 11 | Updated 64-bit Windows 10 or 11 |
| Processor | AMD Ryzen 5 2600 or Intel i5-8400 | AMD Ryzen 5 5600X or Intel i7-10700K |
| Memory | 16 GB RAM | 16 GB RAM |
| Graphics | AMD RX 5700, Nvidia GTX 1070, or Intel Arc A580 | AMD RX 6800 XT or Nvidia RTX 3080 |
| DirectX | Version 12 | Version 12 |
| Storage | 40 GB available | 40 GB available |
Hardware below the minimum can produce poor performance and more serious problems. A file repair cannot bring an underpowered GPU up to the required specification.
Record when the failure happens before changing settings:
| Crash pattern | First useful comparison |
|---|---|
| Closes before any world loads | Check the game update, installation files, drivers, and PC requirements. Record whether it stops at the login screen. |
| Fails while loading one particular save | Preserve that save, then compare an older save and a separate new world. |
| Exits during play after visual glitches | Update the graphics driver and retest the same scene. |
| Becomes unstable after playing for a while | Check cooling, airflow, and any overclock you have applied, alongside the game and driver checks. |
| Only fails in a co-op session | Record whether you are the host or a joining player and compare a solo session. |
| Restarts or shuts down the whole PC | Check system stability and cooling; include the full-PC failure in a manufacturer support request. |
These patterns choose the next test. They do not identify a single cause on their own.
Work through the PC fixes in order
Update, restart, and preserve your saves
Install the available Grounded 2 update through your launcher and restart Windows. Before testing mods or older saves, copy your save folder to a separate backup location. Obsidian lists the Windows save directory as:
%USERPROFILE%\Saved Games\Grounded2
Close the game before making the copy. Keep the original failing save available for comparison and for a support request.
Check the installation files
For Steam:
- Open your Library and right-click Grounded 2.
- Select Properties, then Installed Files.
- Choose Verify integrity of game files and let the check finish.
- Launch the game again and repeat the action that caused the crash.
Allow several minutes for the check. Run one game's check at a time and avoid other intensive disk tasks while it runs. Steam notes that some local configuration files can fail this check normally; that message alone does not mean the installation is broken.
For the Xbox app on Windows:
- Open My Library and select Grounded 2.
- Open the more-options menu and choose Manage.
- Open Files and select Check for updates.
- When no update is available, use Verify and Repair, then launch the game again.
Test without mods
Remove installed mods using their removal instructions, retaining a copy of your saves and mod setup. Skip this step if the game is already unmodified. Grounded 2 updates can leave older mods incompatible, so reproduce the failure with the current unmodified game before reinstalling mods.
Change one thing, test the same action, and record the result. This makes it easier to tell which change helped.
Update graphics drivers and Windows
Install the current graphics driver from your GPU manufacturer's official software or support site, then restart. Check Windows Update as well and restart after installing updates.
If graphics-related crashes continue after a normal driver update, Obsidian recommends trying the manufacturer's clean-install option where available. Preserve any custom driver settings first. Use the manufacturer's installer and its instructions for this step.
Check cooling and custom performance settings
Check that the computer's air intakes and exhausts are unobstructed. Dust buildup and excessive CPU or GPU heat can cause instability. If you have applied an overclock, record the settings and test with that overclock disabled through the tool you used to configure it.
For a 13th- or 14th-generation Intel processor, also check your PC or motherboard manufacturer's support guidance for your exact model. Obsidian recommends an up-to-date BIOS for these systems. Follow the manufacturer's procedure or ask its support team to handle that step; it is a separate system-maintenance task from the game-file and driver checks above.
Separate a world problem from a PC problem
Once the game is updated and the basic checks are complete, compare the failing save with other starting points:
- Note the action and location that reproduce the crash in the affected world.
- Load an older available save without overwriting the failing one and test again.
- Create a separate new world and check whether ordinary play also crashes.
- If the failure happens in co-op, record the host, joining player, and solo-session results separately.
If a new world runs normally while the original consistently fails, include that contrast in your report. It narrows the problem to conditions associated with that world or session, without proving the save is corrupted. If every world fails, return to installation, driver, hardware, and system-stability checks.
Avoid deleting your current world as a troubleshooting step. The repeatable failing state gives support something specific to investigate.
Send a useful crash report
Open the game's official Issue Tracker and use Contact Us. Choose your PC platform, single-player or multiplayer connectivity, game version, and the Crash contact reason.
Include these details in the message:
- The exact error message, or that the game closed without one.
- Whether the failure occurs at startup, login, world loading, or during play.
- The action and location that reproduce it, plus how long play lasts before it fails.
- Whether another save or a separate new world works.
- For co-op, whether the host, a joining player, or both are affected.
- The file checks, driver changes, and unmodified-game tests you completed, with their results.
To export the PC diagnostic file:
- Press Windows + R, enter
dxdiag, and press Enter. - Wait for the DirectX Diagnostic Tool to finish collecting information.
- Select Save All Information and save
DxDiag.txtsomewhere easy to find. - Attach it to your support request along with relevant crash screenshots or a short recording.
The official contact form has a 25 MB upload limit. Provide the affected save when support requests it, preserving your separate backup.