Minecraft exit code 1 in a modpack: what it means and how to fix it
"Game crashed, exit code 1" tells you almost nothing on its own. Here's what it really means in a modpack, where the real error is, and the usual fixes.
· 3 min readThe short answer
Exit code 1 only means Minecraft closed because of an error; it isn't the error itself. In a modpack the real cause is in logs/latest.log or the crash-reports folder, and it's usually a mod for the wrong version or loader, a missing dependency, the wrong Java (1.21.1 needs Java 21), too little memory or two clashing mods.
Your launcher, often the CurseForge app, says the game crashed with exit code 1 and offers nothing else. You search for it and find a hundred pages telling you to update your graphics drivers. Here's what exit code 1 actually means, and how to find and fix the real problem in a modded pack, on NeoForge, Forge or Fabric.
What exit code 1 means
An exit code is the number a program hands back when it closes. 0 means "closed normally". 1 just means "something went wrong". That's all. Exit code 1 isn't an error in itself; it's the launcher telling you the game stopped because of an error it didn't explain.
So the fix is never "fix exit code 1". The fix is finding the error that caused it, which is almost always written down somewhere.
Where the real error is
Open your pack's folder (the launcher's "Open folder" button on the pack) and look in:
crash-reports/for a crash report from the time it happened.logs/latest.logfor everything the game printed, including errors from before it could write a crash report.
Search the log for ERROR, Exception or Caused by. The last Caused by line is usually the real cause. Our guide to finding the mod that crashes your pack explains how to read it.
The usual causes in a modpack
A mod for the wrong version or loader
The most common cause in home-made packs. A mod built for a different Minecraft version, or for Fabric or Forge instead of NeoForge, can stop the game during loading. Check the mods you added most recently.
A missing dependency
A mod needs another mod (often a library) that isn't installed. NeoForge usually shows a screen listing missing dependencies, but sometimes the game exits before you see it, and the list ends up in the log instead.
The wrong Java
Minecraft 1.21.1 needs Java 21. Launchers pick the right one by default, but if you once pointed your launcher at a specific Java install, that setting can stick around and break newer versions.
Out of memory
If the log mentions OutOfMemoryError, the pack needs more memory. See how much RAM a modpack needs.
Two mods that clash
Two mods changing the same part of the game can crash at startup. Look for Mixin in the log, or halve your mods to find the pair.
Graphics driver problems
Less often in modded crashes than the internet suggests, but real. If the log mentions OpenGL, GLFW or your graphics card, update your drivers. Shader mods and rendering mods are the usual trigger.
A quick checklist
- Open
latest.logand find the lastCaused by. - Check the mods you added or updated most recently.
- Check every mod is for 1.21.1 and NeoForge.
- Check your launcher isn't forcing an old Java.
- If none of that finds it, remove half your mods and try again.
Skip the detective work
Exit codes come from untested combinations of mods. Packspire tests the combination before you get it: every pack is started on a real server and a real game client, crashes are traced to the mod that caused them, and that mod is removed or you're told why it can't be. Updates are tested the same way, and one that stops the pack starting is held back at the version that worked.
Build a pack that's already been launched.
Frequently asked questions
What does exit code 1 mean in Minecraft?
It's a generic code a program returns when it stops because of an error. The launcher shows it when it can't tell you more. The details are in the game's log and crash report.
Is exit code 1 caused by mods?
In a modded game, usually yes: an incompatible mod, a missing dependency or two mods that clash. Java settings and, less often, graphics drivers can cause it too.
How do I fix exit code 1 in the CurseForge app?
Open the profile's folder, read the newest crash report or logs/latest.log, and fix what the last Caused by: line points at. Also check that the app's Minecraft settings aren't pointing at an old custom Java.
Can updating graphics drivers fix exit code 1?
Only when the log mentions OpenGL, GLFW or the graphics card. Most modpack exit codes come from mods, not drivers.
Sources
- Minecraft: Java Edition 1.20.5 release notes, which made Java 21 a requirement
