How to Fix Minecraft "Exit Code 1": Game Crashed Before Starting

You press Play, the dirt-screen loading bar creeps along… and then the game just dies. The launcher drops you back to the screen with the dreaded message: "Exit Code: 1". No useful explanation, no suggestion of what to do — just a cold number and a crashed game. If this is your first time seeing it, it feels random and hopeless. It's neither.

In plain English, exit code 1 means the Java program running Minecraft crashed before the game could finish starting. "Exit code 1" is a generic "something went wrong" code — the real reason is hiding in the crash log, but you don't need to read it, because in practice the causes are almost always the same handful of things: outdated graphics drivers, the wrong Java version, a broken or mismatched mod, or corrupted game files. The 9 fixes below are ordered from most likely to fix it to most involved. Work through them in order — most players are back in their world by Fix 3.

What causes Minecraft exit code 1?

Exit code 1 is the signature crash of Minecraft: Java Edition failing during startup. The usual culprits:

• Outdated graphics drivers — the single most common cause. Minecraft's rendering engine talks directly to your GPU, and old drivers crash it on launch.
• Wrong Java version — different Minecraft versions need different Java versions (Java 8, 17, or 21). Point the game at the wrong one and it dies immediately.
• Broken or mismatched mods — a mod built for the wrong game version, two mods fighting each other, or one corrupted mod file will kill the game during startup.
• Not enough RAM allocated — modpacks and big worlds can starve on the launcher's default 2GB and crash before the title screen.
• Corrupted game files — a damaged options file, config, or world data can crash the game the moment it tries to load.
• Shader or resource pack conflicts — especially heavy shaders on weaker graphics cards.
• Antivirus or security software blocking Java — security tools sometimes silently block the Java process Minecraft needs.

1Update your graphics drivers

This is the fix that works most often, so start here. Minecraft's renderer leans hard on your GPU, and an outdated driver is the classic reason the game crashes the instant it tries to draw anything. NVIDIA users: open GeForce Experience (or the NVIDIA app) and install the latest Game Ready driver. AMD users: open AMD Software: Adrenalin Edition and check for updates. Intel users: use the Intel Driver & Support Assistant. Laptop users: check your laptop maker's support page too, since some laptops need manufacturer-customized drivers. Restart your PC after installing — don't skip the restart — then launch Minecraft again. If you've been putting off driver updates for months, there's a good chance this alone fixes exit code 1.

2Use the correct Java version

Minecraft: Java Edition runs on Java, and different game versions demand different Java versions. Getting this wrong produces exit code 1 almost every time. The rules are simple:

• Minecraft 1.16 and older → needs Java 8
• Minecraft 1.17 through 1.20.5 → needs Java 17
• Minecraft 1.20.6 and newer → needs Java 21

The official launcher normally handles this itself using a bundled Java runtime — and that's the safest option. In the launcher, go to Installations, click the … next to your profile, choose Edit, then More Options, and check the Java executable path. If you've manually pointed it at some random Java on your system, switch it back to the launcher's bundled runtime (it lives in the launcher's own runtime folder). If you play through a third-party launcher instead, install the matching standalone Java from a trusted source and select it there.

3Remove recently added mods

If exit code 1 started right after you installed or updated a mod, that mod is your prime suspect. Mods are the second most common cause of this crash after drivers. Open your .minecraft/mods folder and move the recently added mods out of the folder (don't delete them yet — just park them on your desktop). Launch the game. If it starts, you've found the culprit: re-add mods one at a time, launching between each, until the crash returns — that last mod is the broken one. Also check that every mod matches your exact Minecraft version and mod loader (Forge, Fabric, NeoForge, or Quilt). A mod built for 1.19 dropped into a 1.21 game will crash it instantly, and a Forge mod in a Fabric setup won't even load properly.

4Audit your full mod list for version mismatches

Sometimes the crash isn't from the newest mod but from an older one that quietly became incompatible after you updated Minecraft or your mod loader. Go through your mods folder and check each mod against your exact game version. Look for red flags: mods with version numbers that don't match your game (e.g. "1.19.x" when you play 1.21), mod loader files meant for the wrong loader, and dependency mods (libraries like Architectury or Cloth Config) that are missing or outdated. Update every mod to its latest version built for your game version, and make sure your mod loader itself is current — an old Forge/Fabric with a new Minecraft version is a classic exit code 1 recipe. When in doubt, test with a clean mods folder first: if vanilla launches, the problem is 100% in your mod list.

5Allocate more RAM to Minecraft

The launcher gives Minecraft just 2GB of RAM by default. That's fine for vanilla, but modpacks, large worlds, and heavy shaders can starve on it and crash with exit code 1 before the title screen appears. To raise it: in the launcher, go to Installations → … → Edit → More Options and find the JVM arguments box. Look for -Xmx2G and change it — -Xmx4G for light modpacks, -Xmx6G or -Xmx8G for heavy ones. Two rules: never set it above half your system's total RAM (starving Windows causes its own crashes), and if you have 8GB or less total, stick to 4GB or below. Save the profile and relaunch. If the game was crashing while generating a world or loading a big modpack, this is very often the fix.

6Delete corrupted game files

A single damaged file — a mangled options.txt, a broken config, a half-written world save — can crash the game every time it tries to load. The safe way to test: open your .minecraft folder and rename options.txt to options-backup.txt, then launch. Minecraft generates a fresh settings file, and if the game starts, your old settings file was corrupted (reconfigure your keybinds and video settings afterward). If that doesn't help, rename the entire config folder the same way — mods will regenerate their configs on next launch. Also try loading a brand-new world: if new worlds work but one specific world crashes, that world's save data is damaged, and restoring it from a backup (or your saves folder copy) is the way forward. And don't forget: back up saves before you delete or rename anything.

7Disable shaders and resource packs

Shaders are beautiful — and they're brutal on graphics cards. If you recently enabled a shader pack (or cranked up a high-resolution resource pack), try launching with them off. In the launcher, temporarily remove shader/resource pack files from the shaderpacks and resourcepacks folders, or disable them from the in-game menu if you can get that far. If the game launches cleanly without them, the pack was too heavy for your GPU or incompatible with your Minecraft version. You can then try a lighter shader, update your driver (Fix 1 helps here too), or accept vanilla graphics for a stable game. This fix is especially relevant if exit code 1 appeared right after you installed something like BSL, SEUS, or Complementary Shaders.

8Whitelist Minecraft in your antivirus

Security software occasionally decides that the Java process Minecraft runs on looks suspicious — and instead of warning you, it silently blocks it, producing exit code 1. Open your antivirus settings and add exclusions for the Minecraft launcher executable and the Java executable your game uses (the bundled runtime in the launcher's runtime folder, or your standalone Java install). Windows Defender users: go to Virus & threat protection → Manage settings → Exclusions. Don't disable your antivirus — exclusions are the safe way to do this. After adding them, relaunch the game. This one is rare, but it's a two-minute check that saves a lot of head-scratching when everything else looks fine.

9Reinstall Minecraft cleanly

If nothing above worked, start fresh — something in the installation itself is broken beyond targeted repair. First, back up your worlds: copy the entire .minecraft/saves folder to your desktop. Also back up screenshots and resourcepacks if you care about them. Then uninstall the Minecraft launcher through Windows Settings, and delete the .minecraft folder completely (type %appdata% in the Windows search bar to find it). Restart your PC, then download the launcher fresh from the official Minecraft website — never from third-party download sites — and install it. Drop your saves backup back into the new .minecraft folder, and your worlds return exactly as you left them. A clean reinstall wipes out every corrupted file, stale config, and half-broken mod at once, which is why it's the last resort that almost always works.

Quick checklist to keep exit code 1 away

• Keep your graphics drivers updated — check for new ones every month or two.
• Let the official launcher use its bundled Java runtime instead of a manually chosen Java.
• Only install mods built for your exact Minecraft version and mod loader.
• Download mods only from CurseForge, Modrinth, or the mod's official page.
• Give modded games enough RAM — but never more than half your system's total.
• Back up your saves folder before installing new mods or updating Minecraft.
• Update your mod loader (Forge/Fabric/NeoForge/Quilt) when you update the game.

Frequently asked questions

For most players, exit code 1 is gone by Fix 3 — a driver update, the right Java, or removing a broken mod. Work through the list in order and you'll be back in your world soon. And if you're waiting on a long modpack download meanwhile, the free browser games here on GameAdda need no Java, no launcher, and no troubleshooting at all. 🎮