Why Your Minecraft Server Keeps Crashing (and How to Fix It)

A step-by-step diagnosis for a self-hosted Minecraft server that won't stay running. Five most common causes, in the order you should rule them out.

First: where's the crash report?

Every Minecraft server crash leaves a trail. There are two places to look:

• logs/latest.log, the live console log, has the last few minutes of activity
• crash-reports/, written when the server crashes hard, has a structured dump including the stack trace and the mod list

The most useful line is usually near the bottom of latest.log or the top of the crash report, marked something like Caused by: or java.lang.OutOfMemoryError.

1. Out of memory (most common)

The classic, especially on modded servers. Symptoms:

• The server slows to a crawl before dying
• Crash log says java.lang.OutOfMemoryError: Java heap space
• It happens more often when more players are online or when exploring new chunks

Fix: Allocate more RAM. Vanilla and Paper servers are happy with 2-4 GB. Forge and Fabric with mods often need 4-6 GB. Heavy modpacks (RLCraft, ATM-style packs) want 6-8 GB or more.

In MC Server Manager, just bump the RAM slider on the server's settings page and restart. Manually, edit your start script and change -Xmx4G to a higher number.

2. Mod or plugin conflict

The server starts, then crashes immediately or partway through loading. Symptoms:

• Crash report mentions a specific mod or plugin in the stack trace
• The server worked yesterday, you added one new thing, and now it crashes
• Two mods that both want to modify the same vanilla feature

Fix:

1. Look at the last at packagename.ClassName line before the crash, the package name usually tells you which mod
2. Disable that mod (rename its .jar to .jar.disabled or remove it from the mods folder)
3. Start the server again. If it boots, you've found the problem mod
4. Check the mod's CurseForge page for known incompatibilities, or update it to the latest version for your Minecraft release

If you have many mods, MC Server Manager's crash auto-fixer can usually narrow this down for you in a couple of seconds rather than a manual binary search.

3. Wrong Java version

If the crash log says UnsupportedClassVersionError, your Java doesn't match your Minecraft. This is a separate, common-enough issue that we have a dedicated guide for it:

How to fix Unsupported Class Version errors →

4. Mod and Minecraft version mismatch

Subtler than #3. The server starts, but crashes when a player joins or when a specific block loads. Symptoms:

• Crash report mentions NoSuchMethodError, NoClassDefFoundError or AbstractMethodError
• You updated Minecraft but kept old mods, or vice versa
• One mod for 1.20.1 mixed in with mods for 1.21

Fix: Every mod must match your Minecraft version exactly. Check each mod's CurseForge page, the version number on the file should match your server's Minecraft version. If a mod hasn't updated yet, you have to wait for the author or pick an alternative.

MC Server Manager warns you when you try to install a mod that doesn't match your server's version, which catches this before the crash.

5. World corruption

The rarest but scariest. The server crashes immediately on world load, every time. Symptoms:

• Crash log mentions region, chunk, NBT or EOFException
• Often happens after a forced shutdown (power cut, BSOD)
• Removing mods doesn't help

Fix:

1. Restore from a backup. MC Server Manager keeps the last 5 backups automatically, take the most recent that wasn't already corrupted
2. If you don't have a backup, tools like MCEdit or NBTExplorer can sometimes salvage corrupted region files, but it's a manual process
3. Once recovered, set up scheduled restarts so the server is shut down cleanly every day, this stops most corruption before it starts

Stop crashes before they happen

• Backups, automatically. MC Server Manager backs up your world every time you stop the server. Manually, copy the world folder somewhere safe at least once a day.
• Scheduled restarts. A nightly restart clears memory leaks and reduces world corruption. The app can do this on a timer, manually you'd use Task Scheduler or a script.
• Monitor TPS and RAM. A healthy server runs at 20 TPS. Watch for it dropping under load, that's the warning sign before an OOM crash.
• Test mods before adding them all at once. Add new mods one at a time and start the server, so when something breaks you know exactly what it was.