Every Minecraft crash leaves a written explanation. Knowing where to find it and which lines matter turns hours of guessing into a few minutes.
Where the files are
Inside your instance or .minecraft folder:
crash-reports/holds a file for each game crash, named with the date and time.logs/latest.logis the log of the most recent launch, even when no crash report was made.logs/debug.log(Forge and NeoForge) has more detail.hs_err_pid*.logfiles in the game folder mean Java itself crashed. These usually point to graphics drivers or memory, not mods.
Reading a crash report
- Description tells you what the game was doing, such as “Initializing game” or “Ticking entity”.
- The first stack trace under it shows where the error happened. Look for package names; they often contain the mod ID, such as
com.simibubi.createormekanism. - Caused by lines explain the underlying error. The last
Caused byis often the root cause. - Forge, NeoForge and Fabric may add a Suspected Mods list.
- The mod list near the bottom shows every loaded mod and its version.
Reading latest.log
Read from the bottom up. Find the first line with ERROR, Exception or Caused by before the game stopped. Errors earlier in the log are often harmless warnings.
Use the error finder
Paste the log into the error finder. It matches known messages, such as missing dependencies or Java version errors, against our fixes.
Asking for help
Upload the full log to a log-sharing site such as mclo.gs and share the link. Screenshots cut off the lines helpers need.