Why did my modded Minecraft crash?
Open the newest file in crash-reports (or
logs/latest.log) and find the error. Most modded crashes are one of these four.
Paste your crash report and Modkeel names the mod that most likely caused it.
- Minecraft froze or closed with no crash report
No file in
crash-reports: where the cause is written instead, and how to halve the mods folder. - Crash helper mods compared
Which mod names the culprit, turns it off, keeps the game open or protects the world.
- Update a modpack without losing your world
Copy the world, swap each mod for a release made for the new version, keep a way back.
- Mixin apply failed
MixinTransformerError,InvalidInjectionException. A mod could not change the game's code: usually made for another Minecraft version, or two mods change the same code. - NoClassDefFoundError, NoSuchMethodError
ClassNotFoundException,NoSuchFieldError. A mod used code the game does not have: a missing library mod or a version mismatch. - Mod loading failed
Incompatible mods found!,Mod loading has failed. A missing or wrong mod, a mod for another loader, or the same mod twice. - OutOfMemoryError: Java heap space
The game used all the memory the launcher gave it: give it more RAM, or remove heavy mods.
Let the game tell you
The Modkeel Companion reads a crash on the next start, names the mod that most likely caused it, and offers to turn it off or go back to the mods that last worked. Free and open source, for Fabric, NeoForge and Forge.
Ask your AI assistant instead
Claude, ChatGPT and other assistants can read a crash with Modkeel's lab data: add
https://api.modkeel.com/mcp as a connector (no sign-in), then paste the crash in
the chat. It names the mod, checks the rest of your pack and finds a build that works.
How to add it.
Still stuck? Write to Modkeel support with your Minecraft version, loader and the log.