Minecraft Exit Code 1 means the Java Edition game process closed with an error, but the code does not identify the cause by itself. Check the end of latest.log or the crash report, then test a fresh installation of the same game version. That quick comparison helps separate a profile or mod problem from a Java, memory, graphics, or game-file issue.
This guide is for Minecraft: Java Edition. It avoids one-size-fits-all fixes: the right step depends on what the log says and whether you use mods or a custom launcher.
The launcher reports the process exit status after the game stops. “Exit Code 1” and “An unexpected error has occurred” are broad failure messages, not proof that Java is outdated or that Minecraft ran out of RAM. Treat log messages as clues to investigate, not diagnoses on their own.
| Log clue | What to check next |
|---|---|
OutOfMemoryError | Memory pressure, the profile’s -Xmx value, and other running applications. |
UnsupportedClassVersionError or a Java runtime error | A manually selected Java executable or a third-party launcher’s required runtime. |
Could not create the Java Virtual Machine or an unrecognized option | Malformed or outdated JVM arguments and any custom Java path. |
| A mod ID, dependency, or mixin in the stack trace | Mod, loader, dependency, and Minecraft version compatibility. |
GLFW, OpenGL, or graphics-driver messages | Graphics drivers, supported hardware, and the game’s graphics setup. |
One log can mention several mods or systems, so confirm a suspected cause by testing one change at a time.
Close Minecraft and the launcher. Copy the saves folder from the game directory to another location before changing versions, resetting settings, or moving files. With the standard launcher, the usual game directory is %appdata%\.minecraft on Windows, ~/Library/Application Support/minecraft on macOS, and ~/.minecraft on Linux. A custom game directory or another launcher can use a different location, so check its profile settings first. Minecraft Help recommends backing up worlds before troubleshooting or changing game settings.
Do not delete the whole .minecraft folder as an early fix. It can contain worlds, screenshots, resource packs, and other local data.
Open the game directory and look in logs/latest.log. If Minecraft created a crash report, check the newest file in crash-reports as well. The latest log records the launch sequence; a crash report may contain a stack trace and system details such as the Java version and installed mods. These files are more useful than the exit code alone.
Start near the bottom of latest.log, then search upward for words such as Error, Caused by, OutOfMemoryError, or a mod name. For more detail on where logs are stored and how to read crash reports, see Fabric’s log guide and crash-report guide. Their paths for third-party launchers may differ.
In the official Minecraft Launcher, select Minecraft: Java Edition, open Installations, and create a new installation using the same game version as the one that crashes. Give it a clear name such as “Vanilla test.” Launch it without adding mods or custom JVM arguments.
If the clean profile starts, the original installation’s settings, mods, or other downloaded files are more likely to be involved. Minecraft’s launcher troubleshooting instructions recommend this same-version test and explain how to compare its default settings with the older profile. Back up the world before opening it, especially if you are testing a different game version.
If you use Fabric, Forge, NeoForge, a modpack, or shaders, test the clean profile first. Then close the game and temporarily move the relevant mod files or shader packs out of their folders; keep a backup so you can restore them. Add them back in small groups until the crash returns. Check that each mod targets your exact Minecraft version and mod loader, and install its listed dependencies.
A mod name in a stack trace is a starting point, not always proof that the named mod is solely at fault. Two mods can conflict, or a missing dependency can cause a failure that appears under another mod’s name. If the crash happens only with one loader or pack, consult that project’s documentation and provide the matching log.
For a standard official-launcher installation, Minecraft manages the Java runtime used by its game version. Installing a random Java release or forcing the launcher to use a system-wide Java path can create a mismatch. If you previously edited the profile’s Java executable field, restore the launcher’s normal runtime selection or compare it with a newly created profile. With a third-party launcher or custom game version, follow that launcher’s documented Java requirement rather than guessing a version number.
Minecraft’s version notes explain that the default launcher setup downloads the runtime required for that release; custom Java setups must match the game’s requirements. See the official Java Edition release notes for an example of that distinction.
If the log shows an out-of-memory error, or you intentionally changed memory settings, open the affected installation’s edit screen and select More Options. Copy the entire JVM arguments field into a text file before editing it. Change only the -Xmx memory value; do not replace the full argument string with a single example, and avoid adding old “optimization” flags from forum posts.
The right allocation depends on your available system memory and game version. Mojang’s current memory-allocation guide says 64-bit systems should generally keep Minecraft’s allocation at or below half of installed RAM. It also notes that the default changed for newer snapshots, so check the value actually shown in your profile instead of assuming it is always 2 GB. For example, -Xmx4G means a maximum allocation of 4 GB; it is not a universal fix. If you are unsure, restore the saved arguments or copy defaults from a fresh installation.
If the failure mentions OpenGL, GLFW, a display adapter, or a driver, install operating-system updates and the latest graphics driver supported by your computer from its manufacturer. Restart the computer and test again. Avoid downloading individual DLL files from third-party sites. Minecraft’s video and graphics support guide covers graphics-related troubleshooting.
If the log points to a mod, Java argument, or memory issue instead, updating a graphics driver is unlikely to address that cause. Keep the troubleshooting tied to the evidence you found.
When a clean game profile still fails before Minecraft starts, update the official launcher and use your operating system’s app repair option if available. If needed, reinstall it from the official Minecraft download page or Microsoft Store. Reinstalling the launcher is different from deleting the game directory: preserve your backup and do not remove .minecraft just to test the launcher.
Launch the same profile after each adjustment and note whether the error changes. If it still fails, revert the last change before trying another one. That keeps the original evidence intact and makes it easier to identify which fix mattered.
Share the exact Minecraft version, operating system, launcher, mod loader and pack, the latest log, and any crash report with Minecraft Support or the relevant mod or loader support channel. Before posting a log publicly, review it for your Windows account name, file paths, server addresses, or other personal details. Do not share account tokens, passwords, or launcher data folders.
For official guidance, use Minecraft Help’s fresh-install troubleshooting steps and memory instructions. If the trace identifies a mod or loader, include that project’s version details with the log.
No. It is a generic process failure status. A Java runtime mismatch is one possibility, especially with a custom executable or third-party launcher, but the log and a clean-profile test provide better evidence.
Not as a blanket fix. The required runtime depends on the Minecraft release and launcher setup. The official launcher normally manages the runtime for its standard game installations; use a manual Java installation only when your custom launcher or game setup requires it.
It might remove a damaged setting, but it can also erase worlds and other local files. Back up saves and test a fresh installation profile first. This preserves your data while helping determine whether the original profile is the source of the crash.
Set Super Smash Bros. Ultimate Quickplay to prefer hazards-off stages. Follow the Preferred Rules menu steps and learn why matchmaking may not always honor them.
Enable Server Latency and Packet Loss in Warzone to monitor connection quality, read the overlay, and use recurring spikes to guide troubleshooting.
Learn how to carry from mid lane in League of Legends by setting up waves, choosing safe roam windows, reading side lanes, and converting pressure into objectives.
Fix Minecraft Evoker spell problems with a safe vanilla test, version checks, log review, and a step-by-step way to isolate mod or datapack conflicts.
Fix PUBG stuck on Initializing on Steam with a focused checklist for PC service notices, launch options, game files, downloads, and connection issues.
Fix Brawl Stars stuck at 92% loading with an ordered checklist for service notices, network tests, safe updates, Android cache, and account-safe reinstalling.
Best Dead by Daylight visual filter settings start with a small Gamma lift, neutral color and contrast, and a quick check for dark corners, fog, and bright lights.
Find the Steam and EA app fields for Apex Legends launch options, use EA’s documented FPS command, and see why +exec autoexec.cfg remains unverified.
Reduce input lag on a Nintendo Switch dock for Smash Ultimate with TV Game Mode, a direct HDMI test, controller checks, and online-latency troubleshooting.
Find the best EA SPORTS FC audio settings for a clearer referee whistle: tune Stadium Ambience and Commentary, then troubleshoot output or timing issues.
