Minecraft Exit Code 1: How to Fix Game Crashed Errors

What does Exit Code 1 mean in Minecraft?

Exit Code 1 means the Java process running Minecraft ended with an error – it's a generic "something went wrong" code, and the real cause is written in the game's log or crash report. The launcher only sees that the game closed unexpectedly and passes on the number the process returned. Two players with Exit Code 1 can have completely different problems: one has a broken mod, the other the wrong Java version, a third an outdated graphics driver.

So the fastest way to a fix is not guessing but reading the log. It takes less time than reinstalling the game, and it usually names the mod or file at fault.

Negative numbers on Windows are system error codes shown as signed numbers. A crash in native code (graphics driver, OpenGL, a program injecting into the game) doesn't go through Java's normal error handling, so there is often no crash report – but Java writes an hs_err_pid<number>.log file into the game folder.

Where are the Minecraft logs and crash reports?

In the game folder: logs/latest.log holds the whole last session, crash-reports/ holds a report for each crash with the cause at the top.

• Official launcher on Windows: press Win + R, type %appdata%\.minecraft and press Enter. On macOS it's ~/Library/Application Support/minecraft, on Linux ~/.minecraft.
• CurseForge, Modrinth App, Prism Launcher and other launchers: every modpack or profile has its own folder. Use the launcher's option to open the profile or instance folder, and look for logs and crash-reports there.
• Official launcher's own log: if the game crashes before it even writes anything, the "Game crashed" screen in the launcher shows the last lines of the game output. Copy it before closing the screen.
• Forge and NeoForge also write logs/debug.log with more detail.

How to read a crash report

Open the newest file in crash-reports and read three things: the Description: line, the first Caused by: line, and any mod names in the stack trace. You don't have to understand Java to spot the culprit.

1. Description – a short summary, for example "Initializing game" or "Ticking entity". It tells you when the crash happened (during loading, in the world, on a block…).
2. The exception and Caused by: – the actual error. A few common ones:
   • java.lang.OutOfMemoryError – the game ran out of the RAM you allowed it.
   • NoClassDefFoundError / ClassNotFoundException – a mod expects another mod (or another version of it) that isn't there.
   • UnsupportedClassVersionError – a mod was built for a newer Java than the one running the game.
   • Errors mentioning Mixin (for example MixinApplyError) – two mods, or a mod and the game version, don't fit together.
3. Names in the stack trace – lines below the error often contain mod package or file names. The mod that appears near the top is the first suspect.

If there's no crash report, open latest.log, scroll to the end and look at the last lines marked ERROR or FATAL. For a native crash (negative exit codes), open the hs_err_pid file – the "Problematic frame" line often names a graphics driver file (for example from NVIDIA, AMD or Intel).

Fixes that solve most Exit Code 1 crashes

Work from the cause the log names; if you can't tell, go in this order: mods, Java, RAM, graphics driver. Every step can be undone.

1. Mods: wrong version, missing dependency, duplicates

Most crashes in modded Minecraft come from mods, not from the game.

• Every mod must match your Minecraft version and your mod loader. A Fabric mod doesn't load on Forge, a 1.20.1 mod doesn't load on 1.21. NeoForge and Forge are separate loaders for newer versions – see Forge vs NeoForge vs Fabric.
• Install the dependencies. Many mods need a library mod (for example Fabric API on Fabric). The mod's download page lists them.
• No duplicates. Two versions of the same mod in the mods folder cause crashes. Keep only the newest one.
• OptiFine with Forge must exactly match the Forge version; Forge reports a mismatched copy as "an incompatible version of OptiFine". On Fabric, OptiFine doesn't fit with mods like Sodium – pick one.
• Don't know which mod? Move half of the mods out of the mods folder and start the game. If it starts, the culprit is in the half you removed; if it doesn't, it's in the other half. Repeat until you find it. With a modpack, reinstall the pack in the launcher instead of mixing your own mods into it.

2. Java version

Each Minecraft version needs a specific Java version, and modded setups are less forgiving than vanilla.

The official launcher downloads the right Java for vanilla by itself. Problems start when a profile is set to a custom Java executable (in the profile settings under "More options"), or a third-party launcher uses whatever Java is installed system-wide. UnsupportedClassVersionError in the log is a clear sign of a Java that's too old. Remove the custom Java path, or let your launcher manage Java automatically.

3. RAM in the launcher

Too little RAM crashes big modpacks with OutOfMemoryError; far too much RAM can crash or freeze the game as well.

• Official launcher: "Installations" → hover the profile → "…" → "Edit" → "More options" → "JVM arguments". The -Xmx2G part is the maximum RAM (2 GB). For a modpack, -Xmx6G (6 GB) is a reasonable start; large packs may need 8 GB.
• CurseForge, Modrinth App, Prism Launcher: they have a memory slider or setting in their options.
• Don't give the game more than your PC can spare. Windows and other programs need memory too – on a PC with 8 GB, giving 7 GB to Minecraft makes things worse. With 32-bit Java you can't allocate more than about 1–1.5 GB at all; use 64-bit Java.

4. Graphics driver

Crashes right after the launcher, on the loading screen or with negative exit codes are very often graphics driver problems.

• Install the newest driver from the GPU maker's website (NVIDIA, AMD or Intel), not only through Windows Update.
• Laptop with two GPUs: in Windows "Graphics settings" add javaw.exe from the Java folder the game uses and set it to "High performance", so the game doesn't run on the weaker chip.
• Turn off overlays and tools that hook into games (recording, FPS counters, RGB software) for a test.
• Shaders and shader mods also go through the driver; remove them for a test.

5. Clean start without losing worlds

If nothing above helps, back up the saves folder (your worlds), screenshots and options.txt, then rename .minecraft to .minecraft-old and start the launcher. It downloads a fresh game. If vanilla works, the problem was in mods or settings; copy your worlds back.

Minecraft server stopping with an exit code

A server shows an exit code for the same reason as the game: the Java process ended, and the server console and logs/latest.log show the cause just before the end. Look at the last lines before the process stopped.

• Error during startup (before the Done ( line): usually a mod missing on the server, a client-only mod in the server's mods folder, a world from a newer Minecraft version, or the wrong Java version. Client-only mods (minimaps, shaders, GUI tweaks) don't belong on a server – see how to make a modded Minecraft server.
• Exit code 137 on Linux: the process was killed with SIGKILL (137 = 128 + 9). On servers and containers that most often means the system ran out of memory and killed Java. Lower -Xmx so it fits into the server's memory, or give the server more RAM.
• Exit code 143 on Linux: the process got SIGTERM (128 + 15), which is a normal stop request – someone or something stopped the server.
• "A single server tick took 60.00 seconds" before the stop: the server's watchdog shut it down because the main thread froze. Look for a mod or plugin named in the thread dump right after this line.

Crashes on a Spot.gg server

The Spot.gg panel reads your server's logs and explains the most common crash causes in plain language, so you don't have to start with a stack trace.

• Bug icon in the server panel. It turns red when the logs since the last start contain a problem. Click it to open "Detected errors". Among the errors it recognises are "Server crashed", "The engine process crashed during start/restart" (with hints to check the world files, the add-ons' compatibility and the Java version), "Java compatibility", "Plugin incompatibility" naming the plugin, "World files are corrupted" and "Performance issues".
• Java version in one place. In "Configuration" → "Server" → "JAVA version" the default is "Auto", which picks the Java the engine or modpack needs. If a mod needs a different Java, choose it from the list and save. If the server can't start after the change, set it back to "Auto".
• "Open console" in the same window takes you straight to the console, and "Ask the assistant" starts the AI assistant, which can read files such as logs/latest.log on your server and point at the mod causing trouble.
• Modpacks install in one click. When you choose a ready modpack, the panel installs the matching loader, mods and configuration, so there's no mod-version puzzle to solve on the server. Packs marked as tested were checked to start on our servers without extra configuration.

You can run a modded Minecraft server on Spot.gg free for 24 hours; modpack servers start from $7.55 per month with 6 GB RAM.

FAQ

What does "Game crashed" with Exit Code 1 mean?

Minecraft's Java process ended with an error. The code itself is generic – the cause is in logs/latest.log or the newest file in crash-reports in your game folder.

How do I fix Exit Code 1 with Forge or a modpack?

Check that every mod matches your Minecraft version and loader, install missing dependencies, remove duplicate mods and give the game enough RAM (6–8 GB for most packs). For a modpack, reinstalling the exact pack version in your launcher is often the quickest fix.

What is Exit Code -1073741819 in Minecraft?

It's the Windows code 0xC0000005, an access violation in native code. In Minecraft it most often points at the graphics driver or a program hooking into the game, not at a mod. Update the driver and turn off overlays.

Does Exit Code 1 mean I need more RAM?

Only if the log shows java.lang.OutOfMemoryError. Giving more RAM doesn't fix a broken mod or the wrong Java version, and giving far too much can cause new problems.

Where do I find the crash report?

In the crash-reports folder inside your game folder (%appdata%\.minecraft with the official launcher on Windows, or the instance folder of your modpack launcher). The newest file belongs to the last crash.

Can a server crash give players Exit Code 1?

No. If the server crashes, players are disconnected and see a connection error, while their own game keeps running. Exit Code 1 on your screen always means your own game crashed.