Minecraft Exit Code 1: How to Actually Fix It (Read the Log, Not the Error)

Exit code 1 is the most useless error message in Minecraft. The launcher shows a window that says "Game crashed, exit code 1", you click OK, and you know exactly nothing. That's because exit code 1 isn't an error. It's just Java saying "I died, don't ask me why."

The good news: after helping a few thousand people with this, I can tell you it's one of about five causes, and you can find yours in ten minutes if you stop guessing and read the right file.

Step 0: stop reinstalling the game

Reinstalling Minecraft fixes exit code 1 maybe one time in twenty. Deleting mods, changing the Java version and bumping RAM at random is how you end up with a broken instance and still no answer. Do this first instead.

Step 1: read the actual crash log

The real error is always in a file. Open your game folder and look in two places:

• crash-reports/ (a file named like crash-2026-10-12_14.33.07-client.txt)
• logs/latest.log

If there is no fresh file in crash-reports/, the game died before Minecraft itself started, which means a Java or launch-argument problem. In that case latest.log is the one you want.

Open it and scroll to the very bottom. Search for the words Caused by, Exception or Error. The first Caused by line is your real problem. Everything below is just Java listing where it happened.

Here is what the common ones mean.

What the log says → what to do

`UnsupportedClassVersionError` or "class file version 65.0"

Wrong Java. Minecraft 1.20.5 and newer (including all of 1.21.x) needs Java 21. 1.18 to 1.20.4 needs Java 17. 1.17 needs Java 16. Anything up to 1.16.5 runs on Java 8. If you launch 1.21 with Java 17, it dies instantly with exit code 1. This is the single most common cause for people who just updated the game or a modpack.

To check what you have, open a terminal and type:

java -version

If it says 17 and you're on 1.21, install Java 21 (Temurin from adoptium.net is the one I'd use) and point the launcher at it.

`Could not reserve enough space for object heap` or `Invalid maximum heap size`

You asked for more RAM than the system can give. Common on 32-bit Java and on PCs with 4 or 8 GB where someone set 8 GB because "more is better". Set the maximum to roughly half of your physical RAM. For vanilla, 3 to 4 GB is plenty. For a 100-mod pack, 6 to 8 GB is where it stops helping, and going past 10 GB actually makes stutters worse because garbage collection pauses get longer.

`Mixin apply failed` or `InvalidMixinException`

A mod is trying to change game code that doesn't exist in your version, or two mods are fighting over the same method. The log tells you which mod: look for a name in the line right above the error, usually something like mixins.sodium.json. Remove or update that mod. If you just updated Minecraft, 90% of the time you simply have an old mod build for the previous version.

`Mod X requires mod Y` or `Incompatible mods found`

Fabric and Forge are polite about this. They print exactly what is missing. Most often it's Fabric API not installed (it is a separate download, and about half of Fabric mods need it) or Architectury / Cloth Config missing.

`java.lang.NoClassDefFoundError` with an OpenGL or GLFW word in it

Graphics driver trouble. Update your GPU driver from NVIDIA, AMD or Intel directly, not through Windows Update. On laptops with two GPUs, force Java to use the dedicated one in Windows Settings → System → Display → Graphics.

Log is empty or just stops mid-line

Something killed the process. Antivirus is the usual suspect (Avast and Kaspersky especially), or a third-party overlay. Try closing Discord overlay, MSI Afterburner / RivaTuner and NVIDIA's in-game overlay, then launch again.

The 3-minute fallback if you can't read the log

If you want a quick test that tells you which side the problem is on:

1. Make a new clean profile with the same Minecraft version and no mods.
2. Launch it. If it works, the problem is a mod or config in your old profile.
3. Copy your mods back in halves: put half the mods in, launch, then narrow it down. This "halving" approach finds a bad mod among 100 in seven launches instead of a hundred.

If even the clean profile crashes, it's Java, RAM, drivers or antivirus. Go back up through the list above.

Things that people try that don't help

• Reinstalling Windows (yes, people do this)
• Deleting the .minecraft folder before checking the log, because now you've also lost the log
• Running as administrator. It almost never changes anything and it can create files that normal launches can't write to later
• Installing Java 8 "because it's stable". It will not run anything newer than 1.16.5

Quick summary

Exit code 1 means nothing by itself. Open logs/latest.log, find the first Caused by, and match it: wrong Java version, too much RAM requested, a mod that doesn't fit your version, a missing library mod, or a GPU driver issue. Fix that one thing and the game starts.

If your log shows something that isn't covered here, paste the first 15 lines of the Caused by into our support chat on the site and we'll tell you what it is.