Crash troubleshooting

A crash drops you straight back to your launcher or desktop, often with a wall of red text. It looks intimidating, but crash reports are readable once you know where to look, and most causes are a short list. This guide gets you from “it crashed” to “it’s fixed.”

Step 1: Find and read the crash report

When Minecraft crashes, it writes a crash report file. Find it in:

• Your launcher’s “View crash report” button (shown right after the crash), or
• The crash-reports folder inside .minecraft (or your instance folder if you use Prism, MultiMC, or CurseForge).

Open the newest file. You don’t need to understand all of it — read the top section:

---- Minecraft Crash Report ----
// Why did you do that?

Description: Rendering overlay
java.lang.OutOfMemoryError: Java heap space
    at net.minecraft...

Two lines tell you almost everything:

• The Description: — what the game was doing when it died.
• The exception line (e.g. OutOfMemoryError, NullPointerException, a mod’s name) — why it died.

If you see a mod name anywhere near the top of the stack trace, that mod is your prime suspect.

Step 2: Match the cause to a fix

Crash clue	Likely cause	Fix
OutOfMemoryError: Java heap space	Too little RAM allocated	Raise allocation to ~4-6 GB in launcher settings
Constant stutter then freeze	Too much RAM (GC thrash)	Lower allocation to ~4 GB
A mod name in the stack trace	Bad/outdated mod or conflict	Update, remove, or version-match that mod
Pixel format not accelerated, GL errors	GPU driver issue	Update graphics drivers from the GPU maker’s site
Crash on launch, vanilla too	Corrupt install or bad Java	Reinstall the version / repair Java
Crash only when joining the server	Outdated client or conflicting mod	Update to the current Minecraft version; test vanilla

Step 3: Isolate the problem

If the report doesn’t name a clear culprit, isolate it methodically:

1. Test with a clean vanilla profile. Make a brand-new installation with no mods and join HarvestSeason. If it works, the problem is your mods or settings — not the server or your account.
2. Re-add mods in halves. Put back half your mods and test. If it crashes, the bad mod is in that half; if not, it’s in the other. Keep halving until you find it. This is far faster than removing one at a time when you have many.
3. Check versions. Every mod must match your Minecraft version and your loader (Fabric vs Forge vs NeoForge). A mod built for a different version is the number-one crash cause. Mixing Fabric and Forge mods never works.
4. Verify file integrity. A corrupt download or resource pack can crash the game. Delete and re-download suspicious resource packs and reinstall the Minecraft version through your launcher.

Common causes, expanded

• Bad mod combination. Two mods fighting over the same system (rendering, input, world data) crash on contact. Performance and visual mods like Sodium, OptiFine, and Lunar are allowed here and are generally stable, but pairing incompatible ones (e.g. Sodium with OptiFine) crashes. Read each mod’s compatibility notes.
• Out of memory. The most common hard crash. Bump RAM up if you crash, but don’t go overboard.
• GPU drivers. Outdated or buggy drivers cause render crashes. Always get drivers straight from NVIDIA, AMD, or Intel.
• Corrupt files. A half-downloaded version, a broken resource pack, or a damaged options file. Reinstalling the affected piece fixes it.
• Outdated Java or Minecraft. Modern Minecraft bundles its own Java runtime, so this is rarer than it used to be — but custom launchers (Prism) may use a wrong system Java. See Updating Java.

How to ask for help effectively

If you’re stuck, the Discord community can help fast — but only if you give them what they need. A good help request includes:

• What you were doing when it crashed (joining, mid-game, on launch).
• The crash report itself. Don’t paste 500 lines into chat — upload it to a paste site like mclo.gs (which is built for Minecraft logs and even highlights the error) and share the link.
• Your setup: Minecraft version, mod loader, and any major mods.
• What you’ve already tried. “I tested vanilla and it still crashed” saves everyone time.

“It crashed, help” gets you nowhere. “Crashes on join, here’s my log on mclo.gs, vanilla works fine, I’m on Fabric 1.21 with Sodium” gets you an answer in minutes.

When it’s not you

If vanilla crashes on join and your account and version are current, it could be a temporary server hiccup. Check /status and try again shortly. But the overwhelming majority of crashes are client-side and fixable with the steps above — work through them in order before assuming the worst.