Crash help

Minecraft froze or closed with no crash report: find the mod

When modded Minecraft freezes, closes to the desktop or stops on a black screen without a crash report, the cause is still written somewhere: in the game log, in a Java error file or in the launcher's log. If none of them names a mod, halving the mods folder finds it in a few starts.

Updated October 17, 2026. Fabric, NeoForge and Forge.

Why there is no crash report

The game writes a file to crash-reports only when it catches the error itself. It writes nothing when the Java process dies outright (a graphics driver fault, the system running out of memory), when the launcher kills it, or when it hangs: a frozen game is still running, so nothing has crashed yet. A dedicated server is the exception for hangs: when one tick takes longer than max-tick-time in server.properties (60 seconds by default), its watchdog stops the server and writes a report.

1. Read the end of latest.log

logs/latest.log in your instance folder holds everything from the last start, up to the moment the game stopped. Read it from the bottom up: the last lines before it ends are usually an error and the mod that raised it. On Forge and NeoForge, logs/debug.log has more detail for the same run. A crash report, when there is one, is a summary of one error; the log is the whole session, warnings included.

2. Look for an hs_err_pid file

When Java itself crashes, it writes hs_err_pid<number>.log into the game folder (the instance folder, or .minecraft). Its first lines name the library where it failed: a graphics driver file (such as nvoglv64.dll or atio6axx.dll) points at the driver or a rendering mod, not at the mod list in general. An OutOfMemoryError in it or in the log means the game ran out of the memory it was given: see out of memory.

3. Check the launcher's log

The launcher records the game's output and exit code even when the game left no file. Prism Launcher shows it on the instance's Minecraft Log page; the official launcher keeps launcher_log.txt in .minecraft. With no error above the exit code, the lines just before that exit are the last thing the game printed.

4. Nothing names a mod? Halve the mods folder

  1. Copy the world first, or test on a new one.
  2. Move half the JARs out of mods and start the game the same way as before.
  3. Still breaks: the cause is in the half that is in. Works: it is in the half you took out.
  4. Repeat with the guilty half. With 100 mods, about seven starts leave one.

Mind the dependencies: if a mod needs a library (Fabric API, Architectury, Cloth Config and the like), keep them on the same side. Taking a library out gives a "missing dependency" error that the loader names clearly; that is a different stop, not the one you are hunting.

Have a crash report after all?

Paste it into the crash report reader: it names the mod that most likely caused it, in the browser. The Modkeel Companion, a free mod for Fabric, NeoForge and Forge, does the same in game on the next start after a crash, and copies each world before it loads with different mods.

Get the Modkeel Companion

Questions

Can taking mods out damage my world?

Yes: blocks, items and entities from a removed mod are dropped when the world loads without it. Test the halves on a new world or on a copy of the save, never on the world you play.

Why did the crash go away when I split the mods?

Some crashes need two mods together. If neither half crashes on its own, the cause is a pair: keep one half in, add back the other half piece by piece until it crashes again.

Related

Still stuck? Write to Modkeel support with your Minecraft version, loader and the log.