Minecraft crashing with mods installed? Don't worry — mod crashes are common and almost always fixable. This guide covers the most frequent causes and how to solve them, from version mismatches to memory issues.
Step 1: Read the Crash Log
The crash log tells you exactly what went wrong. Here's how to find it:
- Open your
.minecraftfolder:- Windows:
%appdata%.minecraft - macOS:
~/Library/Application Support/minecraft/ - Linux:
~/.minecraft/
- Windows:
- Open the crash-reports folder
- Open the most recent
crash-report.txt - Look for the line starting with "Description:" and the "Caused by:" section
Tip: You can also check logs/latest.log for errors that don't generate a crash report.
Step 2: Identify the Problem
Here are the most common crash causes and their fixes:
1. Version Mismatch
Symptoms: Crash on startup, error mentions "wrong Minecraft version" or "incompatible mod"
Fix:
- Check that every mod in your mods folder supports your Minecraft version
- A mod for 1.20.1 will NOT work on 1.21.1
- Download the correct version from Modrinth or CurseForge
2. Wrong Mod Loader
Symptoms: Crash on startup, mod simply doesn't load
Fix:
- Forge mods only work with Forge
- Fabric mods only work with Fabric
- NeoForge mods work with NeoForge (and some Forge mods for 1.20.1)
- Check the mod's download page to confirm which loader it supports
3. Missing Dependencies
Symptoms: Error message mentions "requires X" or "missing dependency"
Fix:
- Many mods need library mods to function — common ones:
- Fabric API (required by almost all Fabric mods)
- Architectury API, Cloth Config, GeckoLib
- Check the mod's page on Modrinth/CurseForge — dependencies are listed under "Required Dependencies"
- Download and install all required dependencies
4. Out of Memory
Symptoms: Crash with "java.lang.OutOfMemoryError" or game freezes then closes
Fix:
- Allocate more RAM to Minecraft:
- Minecraft Launcher: Installations → Edit → More Options → change
-Xmx2Gto-Xmx4G(or higher) - Prism Launcher: Settings → Java → Maximum Memory
- CurseForge: Settings → Minecraft → Java Settings → Allocated Memory
- Minecraft Launcher: Installations → Edit → More Options → change
- Recommended: 4 GB for small mod setups, 6-8 GB for modpacks
- Don't allocate more than half your total system RAM
5. Mod Conflicts
Symptoms: Works with some mods but crashes when all are installed together
Fix:
- Remove all mods from the mods folder
- Add mods back one at a time (or in small batches), launching after each addition
- When the crash happens, the last mod you added is the culprit
- Check if the conflicting mod has an update, or find an alternative
6. Wrong Java Version
Symptoms: Crash on startup, error mentions "UnsupportedClassVersionError" or "Java version"
Fix:
- Minecraft 1.20.5+ requires Java 21
- Minecraft 1.17-1.20.4 requires Java 17
- Minecraft 1.16.5 and older uses Java 8
- Download the correct Java from adoptium.net
7. Corrupted Mod File
Symptoms: Crash mentions a specific mod .jar file, or "zip file is corrupted"
Fix:
- Delete the corrupted .jar from the mods folder
- Re-download it from the official source (Modrinth or CurseForge)
- Never download mods from unofficial sites — they may contain malware or broken files
Step 3: Quick Fixes to Try First
Before diving deep, try these quick fixes:
- Update all mods to their latest versions for your Minecraft version
- Update your mod loader (Forge/Fabric/NeoForge) to the latest build
- Delete the
.minecraft/configfolder — corrupted configs can cause crashes (mods will regenerate defaults) - Update Java to the latest version for your Minecraft version
- Update graphics drivers — especially for rendering-related crashes
Using Crash Log Analyzers
Don't want to read crash logs manually? These tools parse them automatically:
- CrashPatch / Crash Assistants mods — show crash info in-game instead of closing
- Prism Launcher — highlights the problematic mod in crash reports
- Paste your crash log on community Discord servers — experienced users can often diagnose quickly
FAQ
My game crashes without a crash report — what do I do?
Check logs/latest.log in your .minecraft folder. It contains the full log of the last session and usually shows the error. Also check logs/debug.log for more detail.
Is it safe to delete the config folder?
Yes. Mods regenerate their config files with default settings when they don't find them. You'll lose any custom settings you configured, but it often fixes config-related crashes.
Can one bad mod crash the entire game?
Yes. A single incompatible or broken mod can prevent Minecraft from launching entirely. This is why the "add one at a time" method is the most reliable way to find the problem.
Should I use OptiFine with Forge mods?
OptiFine can conflict with some Forge mods, especially rendering mods. If you're crashing with OptiFine installed, try Embeddium as an alternative — it's more compatible with modern Forge mods.
