Start by separating a vanilla crash from a modded one: launch the original Stardew Valley executable without SMAPI. If the unmodded game also crashes, use the platform fixes below; if it works, the problem is usually SMAPI, a mod, or a compatibility mismatch.
The most common recoveries are deleting the game’s startup_preferences file, checking the required .NET runtime, clearing incorrect Steam launch options, correcting macOS configuration-folder ownership, and removing a stale SMAPI crash marker. Collect the crash log before asking for support so the cause can be identified rather than guessed.
As an Amazon Associate I earn from qualifying purchases.
First, identify which kind of crash you have
Do not start by reinstalling every mod or changing random graphics settings. The first diagnostic question is whether the original game can launch without SMAPI. Close Steam, your mod manager and the game, then start the official Stardew Valley executable from its installation folder (or use the normal Steam Play button with SMAPI disabled).
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match| What you observe | Most useful direction |
|---|---|
| The original executable crashes before a window appears | Use the operating-system and vanilla launch fixes. A mod is not required for this failure. |
| The original executable works, but SMAPI crashes or closes | Check SMAPI, the game version, content files and mod compatibility. |
| The game reaches the title screen but crashes while loading a save | Test without mods, then narrow down recently updated or incompatible mods. |
| The game crashes only after a recent update | Update Stardew Valley, SMAPI and every affected mod; do not assume an older mod still matches the new game build. |
| A crash log or SMAPI log exists | Save it before making more changes. The log provides the evidence needed for support or mod troubleshooting. |
Record the timing of the failure (before the window, during loading, or after entering a save), your operating system, whether SMAPI is installed, and what changed immediately beforehand. This information prevents a vanilla and modded failure from being treated as the same problem.
Fix a vanilla Stardew Valley crash on Windows
1. Remove the startup preferences file
Exit the game and Steam. Press Windows + R, enter %AppData%/StardewValley, and press Enter. Delete the file named startup_preferences (Windows may hide its extension). This resets launch preferences without requiring a full game reinstall. Start Stardew Valley again and test before changing anything else.
2. Check the .NET runtime
Stardew Valley and its supporting components require .NET 5.0 or later. If .NET is missing, damaged or older than that requirement, install or repair a current .NET runtime from Microsoft’s official distribution for your Windows edition, then restart Windows and test the game. Avoid installing an unrelated runtime architecture just because it has a similar name; use the runtime requested by the game or SMAPI installer.
3. Clear Steam launch options when SMAPI is not installed
In Steam, open Library, right-click Stardew Valley, choose Properties, and leave the Launch Options box empty for a vanilla installation. A leftover SMAPI command in that box can make Steam call a file that no longer exists or point to an old game folder. Close the Properties window and launch normally.
4. Test the Steam Compatibility branch temporarily
If the regular Windows build still fails, open the game’s Steam properties, select Betas, choose the available Compatibility branch, and test it. This is a diagnostic and recovery step, not a permanent recommendation. Once the game launches—or once you finish testing—switch the selection back to the normal current branch. Modded installations should not use this branch; follow the SMAPI section instead.
5. Verify the game files
Steam can replace a missing or altered vanilla file. In Properties, open Installed Files and select Verify integrity of game files. Wait for Steam to finish, then launch the original executable before restoring any mods. Verification can overwrite modified content files, so a modded installation must be repaired and tested separately afterward.
Rank #2
Fix a vanilla Stardew Valley crash on macOS
Correct ownership of the configuration folder
Quit Stardew Valley and Steam. Open Terminal and run this command exactly:
sudo chown -v "$USER" ~/.configEnter your macOS administrator password when prompted, then retry the game. The command gives your user account ownership of the configuration directory used by the game and related tools. If Terminal reports that the path does not exist or returns a permission error, keep the message for support rather than repeatedly running sudo commands.
Check the macOS version required by current SMAPI releases
Newer SMAPI releases require macOS 10.15 Catalina or later. If your Mac is older than Catalina, a current SMAPI build may not start even when the unmodded game does. Confirm your macOS version in Apple menu → About This Mac; use a compatible SMAPI release or remain on a vanilla installation rather than mixing an unsupported runtime with the game.
Reset preferences and retest without mods
Remove startup_preferences from the Stardew Valley configuration folder, then launch the original executable. If vanilla works but SMAPI does not, stop changing macOS permissions and continue with the modded-install checks below.
Fix a SMAPI or modded-install crash
When vanilla launches successfully, the base game is not the first suspect. Treat the modded installation as a separate program: its launcher, game files and individual mods must all agree on the same game version.
Rank #3
- For 1 to 4 players
- Ages 13+
- About 45 minutes per player
- A cooperative board game
- Based on the hit video game
1. Update the game and SMAPI together
Allow Steam or GOG to finish updating Stardew Valley, then install the SMAPI release that supports that game version. An update can invalidate a loader or a mod even when the mod’s files are still present. Restart the computer after updating if the launcher continues to use an old process.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors2. Reset content files before testing mods
Restore the game’s original content files using the platform’s file-repair or verification feature. Do this before troubleshooting individual mods; a damaged content file can look like a mod error. After the reset, launch the original executable once. Only then launch through SMAPI.
3. Do not use the Steam/GOG Compatibility branch for mods
The Compatibility branch is intended for a temporary vanilla test. Modded installations should use the normal current game branch, because SMAPI and its mods are built against the regular release. If you selected Compatibility while diagnosing a vanilla crash, switch back before launching StardewModdingAPI.
4. Start the correct launcher from the game folder
Open the Stardew Valley installation directory and run StardewModdingAPI directly. This confirms that SMAPI is installed where the game expects it and avoids a stale desktop shortcut or Steam launch command pointing to another directory. If the executable is missing, reinstall SMAPI rather than copying a launcher from a different installation.
5. Delete preferences and a stale crash marker
Delete startup_preferences from the Stardew Valley configuration directory and retry. If SMAPI created a marker that prevents another launch, close every Stardew Valley and SMAPI process, then remove:
Recommended Free Tools
smapi-internal/StardewModdingAPI.crash.markerThat marker records a previous crash; removing it does not repair the underlying mod. Relaunch once, read the new log and address the first reported error instead of repeatedly deleting the marker.
6. Isolate a mod without deleting the whole installation
Move recently added or recently updated mods out of the Mods folder to a temporary location, then launch SMAPI. If the crash stops, restore mods in small groups until the failing group is identified. Within that group, test one mod at a time. Keep required frameworks with their dependent mods, and read SMAPI’s message about an outdated or missing dependency before removing anything. A crash that remains with an empty Mods folder points back to SMAPI, the game files or the operating system.
Use the crash timing to choose the next test
Crash before any window appears
- Launch the original executable, not SMAPI.
- Delete
startup_preferences. - Check .NET 5.0 or later on Windows, or macOS ownership and version requirements.
- Clear Steam launch options and verify vanilla files.
Crash while SMAPI or the title screen loads
- Confirm that the normal game branch is selected.
- Update Stardew Valley and SMAPI as a matched pair.
- Launch
StardewModdingAPIfrom the installation folder. - Temporarily empty the Mods folder and remove the stale crash marker if present.
Crash when opening or entering a save
- Test the same save with the original executable if possible.
- Check mods that alter maps, events, characters or save data first.
- Restore mods in small groups and compare the SMAPI log after each test.
- Do not overwrite the only copy of a save while experimenting; preserve the original save files before repeated load attempts.
Crash after a game, SMAPI or mod update
Write down the update date and versions. Recheck dependencies and compatibility notes for the changed component, then test the original executable. If vanilla is stable, the update path identifies the modded branch of the investigation; if vanilla is unstable, return to the Windows or macOS fixes.
Find and preserve the crash logs
Windows
Open %appdata%/StardewValley/ErrorLogs. Copy the newest relevant file before launching again, because a later attempt can create a different log. For SMAPI failures, retain the complete SMAPI log, including the first error and the list of loaded mods.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →macOS and Linux
Look in the Stardew Valley configuration directory for the platform’s ErrorLogs folder. The exact parent location follows the operating system’s Stardew Valley configuration path, so search for a folder named ErrorLogs inside that configuration directory rather than assuming the Windows path.
Submit an SMAPI log when requesting mod help
Use the SMAPI log parser to submit the complete log and share the resulting report with the mod author or support forum. Do not paste only the final line: the loader version, game version, dependency warnings and first stack trace often explain a crash that the last line merely summarizes. Remove personal information from any unrelated text before sharing.
When the documented fixes do not work
- Reproduce the failure with the original executable and note whether it still occurs.
- Record your operating system and version, game platform (Steam or GOG), game version, SMAPI version, crash timing and the last change made.
- Attach the newest vanilla crash log or SMAPI log from the appropriate
ErrorLogsfolder. - Email Stardew Valley support with that evidence and a concise list of the steps already completed. For a mod-only crash, send the SMAPI parser report to the relevant mod author or mod-support channel as well.
A clean vanilla test, an exact version history and the complete log are more useful than reinstalling repeatedly. They also let support distinguish a permissions problem, missing runtime, damaged content file, loader mismatch and a single incompatible mod.
Quick Recap
As an optional Windows shortcut after trying the manual steps, Outbyte PC Repair can look for more than 100 common Windows issues where possible, adjust selected settings, clear temporary and cache files, and provide an app-crash log. It complements an antivirus rather than replacing one; results vary and no tool repairs every game crash. It runs on Windows 11, 10, 8 and 7, with a free trial of at least two days before a paid subscription.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
