How to Read a Minecraft Crash Report to Find the Mod

When Minecraft crashes, it almost always leaves a text file behind that tells you exactly what broke. You don’t need to be a programmer to read it. You just need to know where to look and which lines actually matter, because most of the file is noise you can skip.

The short version: find the crash report, read the description and the first error lines, spot the mod name in the stack trace, then check for missing dependencies or version mismatches before you start removing mods one by one.

Where to find the crash files

Every crash report gets saved as a text file inside the crash-reports folder, which sits inside your .minecraft folder. Each file is named with a date and time, so the newest one at the top (or bottom, depending on how your file browser sorts) is the one you want.

If the game doesn’t fully crash but just freezes, closes silently, or won’t launch at all, check logs/latest.log instead, also inside .minecraft. This file gets overwritten every time you launch, so open it right after the problem happens, not the next day.

On most setups you can get to .minecraft through your launcher’s options, or by typing %appdata% into Windows Explorer and looking for the .minecraft folder there. If you’re using a modpack through a launcher like CurseForge or Prism, the instance has its own separate .minecraft-style folder, not the default one, so make sure you’re opening the right instance’s files.

The parts of the report that actually matter

Open the crash report in any text editor. It looks long and scary, but you only need three sections.

• The description line, near the top, under something like “Description:”. It gives a short category of what went wrong, such as a rendering error, a world loading error, or a mod loading error. It won’t name the mod, but it tells you what kind of problem you’re dealing with.
• The first lines of the actual error, right below the description. This is usually a line starting with something like java.lang.NullPointerException or java.lang.NoClassDefFoundError followed by a short message. Read this line even if the rest looks like gibberish, because it often names a method or class that hints at the source.
• The stack trace, the long list of lines starting with “at”. Scroll through it looking for anything that isn’t plain net.minecraft or net.minecraftforge/net.fabricmc. Mod code usually shows up as a package name that matches the mod’s internal ID, like com.someauthor.somemod. That’s your suspect.

Not every crash points straight at one mod. Sometimes the trace shows a vanilla class the whole way down, which usually means the problem is a conflict between two mods rather than one broken file, or it’s an issue with the base game itself.

Missing dependency messages at startup

If the game won’t even get past the loading screen, the crash report (or latest.log) often contains a very readable message instead of a stack trace. It will say something like a mod requires another mod that isn’t installed, or that it needs a specific version of the mod loader. These messages are usually written in plain English and will literally name the missing dependency.

To fix this:

1. Read the message carefully and note the exact mod name or library it’s asking for.
2. Download that dependency and drop it into your mods folder.
3. Relaunch and see if the message changes to ask for something else. It’s common to fix one dependency and immediately hit the next one.

Common dependencies include libraries that several mods share, like an API mod or a core library. If you installed a mod and skipped its “requires” note on the download page, this is almost always the cause.

Version mismatches

A huge number of crashes come down to three things not lining up: the Minecraft version, the mod loader version (Forge or Fabric, for example), and the version of the mod itself. A mod built for one Minecraft version will often crash instantly, or fail to load at all, if you drop it into a different version’s mods folder.

Check this by comparing:

• The Minecraft version shown in your launcher profile.
• The mod loader version you have installed.
• The version number in the mod’s file name or on its download page.

If any of these don’t match, that’s very likely your answer, no stack trace reading required. This is worth checking first, actually, before you even open the crash report, since it’s the single most common cause of crashes right after installing something.

Testing by halving your mod list

Sometimes the report is vague, the stack trace is all vanilla code, or you’ve got so many mods that the trace doesn’t clearly point anywhere. When that happens, stop reading and start testing instead.

1. Close the game and open your mods folder.
2. Move half of your mods out into a different folder, outside mods, so the game can’t see them.
3. Launch and see if the crash still happens.
4. If it crashes, the problem is in the half still installed. If it doesn’t crash, the problem is in the half you removed.
5. Take the half that contains the problem, split it in half again, and repeat.

This is slow but it always works, and it’s the method people fall back on when reading the report alone doesn’t give a clear answer. Keep a list of what you moved out at each step so you don’t lose track, and put mods back one at a time once you’ve narrowed it down to a small group, so you confirm the exact one responsible rather than just a suspect group.

Once you find the mod, check its page for a note about which Minecraft and loader version it supports, or for an updated file. Most of the time the fix is just downloading the matching version rather than anything more complicated.

Questions people ask

Why does my crash report not mention any mod names at all?

Some crashes happen deep in vanilla code or in the mod loader itself, so the stack trace never touches mod code directly. In these cases you usually need to test by removing mods in groups rather than reading the trace.

What's the difference between the crash-reports folder and latest.log?

The crash-reports folder holds a saved file for every full crash, while logs/latest.log is a running log of your most recent session that gets overwritten each time you launch, useful for freezes or silent closes that don't produce a crash report.

Can two perfectly fine mods still cause a crash together?

Yes, this happens often when two mods try to modify the same part of the game in conflicting ways. Neither mod is broken on its own, but running both together causes the crash, which is why halving your mod list is sometimes the only way to find it.

Does the order I install mods in affect crashes?

Load order rarely matters on its own, but installing a mod without its required dependency or on the wrong game version will crash regardless of order, so check those two things before worrying about install order.

Browse all Minecraft mods on CrashMods