How to Fix Minecraft Mod Crashes: The Complete 2026 Troubleshooting Guide

Most modded Minecraft crashes come from one of three problems: the wrong mod loader (a Forge mod dropped into a Fabric pack, or a loader with no mods at all), a missing dependency like Fabric API or Kotlin for Forge, or not enough RAM allocated. Check those three first, read the crash report in .minecraft/crash-reports, and half of all crashes are solved within ten minutes.

Learning how to fix Minecraft mod crashes is mostly about reading one text file and checking three things in order. The crash almost never means your world is ruined. It means one piece of the puzzle doesn’t fit, and the game gives you a written report that says which piece. This guide shows you where that report lives, how to read it, and what to fix, in the order that actually solves crashes.

Read the crash report before changing anything

Every time modded Minecraft crashes to desktop, the game writes a crash report. Open that file first. Guessing at the cause without reading it is how a five-minute fix turns into a lost afternoon.

Find the reports here:

• Windows: press Win + R, type %appdata%\.minecraft\crash-reports, and press Enter.
• macOS: ~/Library/Application Support/minecraft/crash-reports
• Linux: ~/.minecraft/crash-reports

If you use a third-party launcher like CurseForge, Prism, or MultiMC, look inside that launcher’s instance folder instead. The folder name is the same: crash-reports. Pick the file with the newest date and time in its name.

Open the report in Notepad or any text editor. The top of the file has the useful part: a short description and the error name. Common ones:

• java.lang.OutOfMemoryError: Java heap space — the game ran out of memory.
• Mixin transformation failed or DependencyResolutionException — a missing dependency or two mods fighting.
• java.lang.UnsupportedClassVersionError — wrong Java version for the game.
• A line naming a mod file and saying it needs a language provider, or a “duplicate mod” listing — a loader mismatch or the same mod installed twice.

If the game crashes but no report is written, the fallback is logs/latest.log in the same .minecraft folder. It records everything the game printed before it died, and the last 30 lines usually hold the cause.

The most common causes, in order

These are the causes I see over and over. Work down the list until the game launches.

The mod is for a different loader than the one installed

This is the single most common cause. Minecraft has several loaders (Forge, NeoForge, Fabric, Quilt), and a mod built for one does not run on the others. A Forge mod dropped into a Fabric pack produces a “Mod loading error” screen saying the file needs a language provider (javafml), which is Forge’s loading system.

Symptoms: crash during the loading screen, the error names one specific mod file, and mentions a language provider or mod loading error.

How to confirm: open the mod’s page on CurseForge or Modrinth, go to Files/Versions, and check the listed loader for the exact file you downloaded. Compare it with the loader in your launcher.

Fix: either download the mod version built for your loader, or install the loader the mod needs. If you are not sure which loader to commit to, my comparison of Forge vs Fabric vs NeoForge covers which one fits which modpack.

A dependency is missing

Many mods do not work alone. They need a library mod installed next to them: Fabric API for Fabric mods, Kotlin for Forge for some Forge mods, Architectury for others. The mod’s page lists these under dependencies, and the crash report usually names the missing piece directly.

Symptoms: the report or error screen names a second mod you do not recognize, with words like “requires”, “missing”, or a DependencyResolutionException.

How to confirm: search the crash report (Ctrl + F) for “requires” or “missing”. The line tells you exactly which mod is absent.

Fix: download the named dependency from CurseForge or Modrinth, making sure it matches your Minecraft version and loader, and drop it in the mods folder next to the mod.

The mod is for the wrong Minecraft version

A mod built for 1.20.1 will not run on 1.21.1, even if the loader matches. Some mod pages list files for several game versions side by side, and it is easy to grab the wrong one. This also covers loader drift: a mod built for a newer Forge or Fabric Loader than the one installed crashes with a class-not-found or mixin error.

Symptoms: crash right when the game starts loading mods, or an error naming a class that “was not found”.

How to confirm: check the mod file name. Most mod files carry the game version and loader in the name, for example modname-1.20.1-forge-47.2.0.jar.

Fix: download the mod file built for your exact game version, or update your loader to the version the mod expects. The version rules are covered in detail in the Java Edition mod installation guide.

Two mods conflict with each other

Two mods that rewrite the same game code can crash each other. The classic example is running OptiFine and Sodium together: both replace the rendering code, and neither tolerates the other.

Symptoms: the crash report names two mods, or the game crashes when a specific pair is present but works with either one alone. Mixin errors often point here.

How to confirm: remove one of the two suspects and launch. If it works, you found the pair.

Fix: keep one of the two and drop the other, or check the mod pages for a known compatibility patch. If it is a rendering conflict, my Sodium vs OptiFine comparison picks a winner so you do not need both.

The same mod installed twice

Two copies of one mod in the mods folder stop the game with a duplicate-mod error. It happens after a manual update: you download the new file but forget to delete the old one.

Symptoms: an error screen listing the same mod twice, with two different file names. Confirm it by opening the mods folder and looking for two files from the same mod, or an old leftover file for a mod you thought you removed.

Fix: delete the older file. Keep the one matching your game version.

The wrong Java version

Minecraft needs a specific Java version depending on the game version, and this has changed over the years. The Minecraft Wiki’s update guide lists the requirements: Java 8 for 1.16.5 and below, Java 17 for 1.18 through 1.20.4, Java 21 for 1.20.5 through 1.21.x, and Java 25 for 26.1 and newer. Run a mod on the wrong Java and it dies with an UnsupportedClassVersionError, often on launch.

Symptoms: crash at or before the loading screen, with “UnsupportedClassVersionError” or “compiled by a more recent version of the Java Runtime” in the log. Check which Java your launcher uses against the chart above.

The official launcher bundles the right Java automatically; this mostly bites people on third-party launchers with a custom Java path.

Fix: point the launcher at the correct Java version. In the official launcher, go to Installations, select the profile, click More Options, and check or change the Java Executable path. Third-party launchers have a Java settings page with the same choice.

Not enough RAM allocated

Modded Minecraft needs more memory than vanilla. Too little, and the game throws java.lang.OutOfMemoryError: Java heap space, or the launcher shows exit code -805306369, which is Windows’ way of saying the process ran out of memory.

Symptoms: the game loads for a while, then dies with no clear mod name in the report, or crashes when you join a world with lots of mods loaded.

How to confirm: search the report for “OutOfMemoryError”. If it is there, memory is the problem.

Fix: raise the maximum RAM in the launcher’s JVM arguments. In the official launcher: Installations, select the profile, More Options, and in the JVM Arguments field change -Xmx2G to -Xmx4G or -Xmx6G. A pack of 50 or so mods usually wants 4 to 6 GB; a heavy pack with 200+ mods wants 8 GB. Keep the game under about three quarters of your computer’s total RAM. And know that more RAM fixes crashes, not frame rates: if lag is the issue, performance mods like Sodium do more for your frame rate than memory ever will.

Outdated GPU drivers

Sometimes the crash is not a mod at all. Outdated or missing graphics drivers produce a GLFW error 65542 or “Pixel format not accelerated”, and the game dies when it tries to open the window. This often happens on a PC with a fresh Windows install that never got its drivers.

Symptoms: crash before the title screen, with a GLFW or OpenGL error in the report, and no mod name mentioned.

How to confirm: search the report for “GLFW” or “OpenGL”. If those show up, the problem is the graphics driver, not a mod.

Fix: update the graphics driver from the manufacturer’s site (NVIDIA, AMD, or Intel), or through Windows Update.

The mod-bisect method: find a bad mod in any pack

When the crash report does not name a mod, or you have 100 mods and no clue which one breaks, bisect the pack.

1. Move half of the mods out of the mods folder into a temporary folder on your desktop. Keep track of which half you removed.
2. Launch the game. If it still crashes, the bad mod is in the half that is still installed. If it launches, the bad mod is in the half you removed.
3. Put the “bad” half back and split it in half again. Repeat.
4. Keep halving until one mod remains. Test it alone to confirm it crashes on its own.

With 128 mods, this takes at most seven launches. It beats removing mods one at a time every time.

One tip that saves time: if a pack behaves strangely after you reshuffle mods, delete the config folder before launching. Some mods leave config files that reference removed mods, and the game rebuilds the folder cleanly on next launch.

How to fix Minecraft mod crashes using exit codes

When the launcher shows an exit code instead of a report, the code itself narrows the cause:

Exit code	What it usually means	First thing to try
1	Generic crash: the Java runtime failed, most often a broken mod, wrong Java, or a bad JVM argument.	Check the crash report; then check Java version and mod versions.
-1	Often a driver or native library problem, especially on systems where the graphics driver is missing or broken.	Update the GPU driver; check the latest.log for GLFW errors.
-805306369	Out of memory. The game asked for more RAM than it had.	Raise -Xmx to 4-6 GB in the JVM arguments.
134	The Java process was aborted, usually a hard crash in native code (graphics or a mod’s native library).	Update the GPU driver and Java; remove recently added mods.

Exit codes are hints, not diagnoses. The crash report is still the authority.

Prevention checklist: stop crashes before they happen

• Download every mod from CurseForge or Modrinth. Never use aggregator or repack sites; their files are often outdated or tampered with.
• Match the mod’s game version and loader to your instance before downloading. Check the file name and the mod page’s Files tab.
• Install every listed dependency. If a mod page names Fabric API, Kotlin for Forge, or another library, it is not optional.
• Delete the old file when you update a mod manually. Two copies of one mod crash the game.
• Allocate enough RAM from the start: 4 GB for a small pack, 6-8 GB for a big one. Keep it under three quarters of total system RAM.
• Keep one Java version per game version if you play several modpacks. Launchers like Prism let you assign a different Java to each instance.
• Back up your world before changing mods. Copy the saves folder somewhere safe.

Still crashing after everything

If every mod matches, the dependencies are all there, Java is right, RAM is fine, and the game still dies, do this:

• Start a fresh instance. Create a new profile or instance with a fresh .minecraft or instance folder, install the loader, and add the mods one group at a time. A corrupted config or a broken launcher file outside the mods folder is sometimes the real problem, and a fresh instance sidesteps it.
• Test with zero mods. If the loader alone crashes, the problem is the loader, Java, or the drivers, not any mod.
• Ask the mod’s community. Paste the full crash report to the mod’s GitHub issues page or its Discord, with the loader version, game version, Java version, and the full mod list. A report with those details gets an answer; “it crashes, help” usually does not.
• Check the mod’s recent updates. If a crash started after a mod update, roll that mod back one version. Regressions happen, and mod authors usually fix them in days.

FAQ

Why does Minecraft crash when I add a mod?

The game crashes when something in the new mod does not match your setup: the wrong loader, a missing dependency, wrong game version, a conflict with another mod, or not enough RAM. Read the crash report in .minecraft/crash-reports; the top of the file almost always names the cause.

What does exit code 1 mean in Minecraft?

Exit code 1 means the Java runtime crashed for a generic reason: a broken mod, the wrong Java version, or bad JVM arguments. It is the most common code modded players see. The crash report, not the code, tells you which of those it is.

How do I know which mod is crashing my game?

The crash report usually names it in the first few lines. If it does not, use the mod-bisect method: remove half your mods, launch, and keep halving the crashing half until one mod is left. It finds the culprit in a handful of launches no matter how big the pack is.

Can two mods conflict with each other?

Yes. Two mods that rewrite the same game code (like two rendering mods, or two mods editing the same screen) can crash each other. The fix is to use one of them, or look for a compatibility patch on the mod pages.

How much RAM should I give modded Minecraft?

Give a small pack (under 50 mods) 4 GB, a medium pack 6 GB, and a heavy pack with 200+ mods 8 GB, by raising -Xmx in the launcher’s JVM arguments. Do not give it more than about three quarters of your computer’s total RAM, and do not expect more RAM to raise your frame rate.

Will removing a mod delete my world?

Removing a mod does not delete the save file, but if the mod added blocks or items, loading the world without it can remove those blocks or corrupt chunks. Always back up the saves folder before removing mods from a world you care about.