How to Read a Minecraft Server Crash Report (and Fix It)

A Minecraft server crash looks scary, but the crash report tells you almost everything you need. Here's how to read it, find the line that matters, and fix the common causes.

Where to look

Two files hold the answer: logs/latest.log (everything the server printed) and crash-reports/ (a dated file written when it hard-crashes). Open the newest one and read from the top of the stack trace.

Find the cause line

Skip past the ASCII art and find the line starting with Caused by: or the first at ... that names a mod or plugin package. That package name usually is your culprit.

Caused by: java.lang.NullPointerException
    at com.someauthor.coolmod.EntityHandler.tick(EntityHandler.java:142)

Common cause 1: out of memory

java.lang.OutOfMemoryError means the server ran out of RAM — common on modpacks. Allocate more memory in your start flags, but never give Java all the system RAM:

java -Xms4G -Xmx6G -jar server.jar nogui

Common cause 2: a bad mod/plugin

If the trace names a mod, update it to match your Minecraft + loader version, or remove it to confirm. Mismatched versions (a 1.20 mod on a 1.21 server) are the most common crash on modded servers.

Common cause 3: corrupted chunk or world

A crash tied to a specific location (ServerLevel / chunk coordinates in the trace) usually means a corrupted chunk. Restore from a backup, or use a tool like MCA Selector to delete the bad chunk.

The clean checklist

1. Open the newest crash-reports/ file or latest.log.
2. Find the Caused by: line and the first mod/plugin package.
3. Out of memory? Raise -Xmx (but leave RAM for the OS).
4. Named mod/plugin? Update it to match your version, or remove it.
5. Chunk/world error? Restore a backup or remove the bad chunk.

The crash report already names the guilty mod. Read the first "Caused by" line before changing anything else.

Common cause 4: a crash report pointing at Java or the loader itself

Sometimes the first non-Minecraft line in the crash report sits inside net.minecraft or a Forge/Fabric/NeoForge loader package rather than a third-party mod. That usually means a Java version mismatch, a corrupted server jar, or a loader bug rather than a specific mod — verify your Java version matches what the server requires (check with java -version) and re-download the server/loader jar if the crash mentions class loading or bytecode verification errors.

How to prevent Minecraft crash reports in the future

• Add one mod/plugin at a time so a crash is easy to trace to the last change.
• Run a staging/test server before pushing mod or plugin updates to the live world.
• Back up world data on a schedule so a corrupted chunk never costs real progress.
• Watch RAM headroom proactively rather than waiting for an OutOfMemoryError.
• Pin your Java and loader (Forge/Fabric/Paper) versions instead of always chasing latest.

Related Minecraft crash and performance errors

If the server stays up but lags badly instead of crashing, that's low TPS — see "Can't keep up! Is the server overloaded?". For memory-specific crashes, read Minecraft out of memory / Java heap space. If the crash report mentions an unsupported class version, see unsupported class version (Java), and for RAM sizing help see how to allocate more RAM to a Minecraft server.

Minecraft is a trademark of Mojang Synergies AB / Microsoft. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Mojang or Microsoft.