Fixing Crashes - 04Slash/Breaking-Down-Minecraft-Forge-Crash-Reports GitHub Wiki

Here will will go over the steps I take when faced with a crash. I will be using this crash report as a reference

  1. First thing’s first, I just take a quick look at the entire crash log, looking at the information pointed out above and the mods section down below. The goal here is to find anything obvious or a few lines that all point towards a single mod. This can be within the stack trace above, or the mods section below.
  2. If nothing is immediately obvious then I will start looking for information that might give a result on google. This would be the bit of information that mentioned Dim 23 is already taken, or the stack trace below it.
  3. If there is no obvious information there then I may pick out a line that might give a result. For example, if it’s an issue with a specific part of the world and net.minecraft.world.gen.ChunkProviderServer.loadChunk shows up in the stack trace then it might be useful to search for this line to see what happens in other crashes with this line in the stack trace. This won’t always give solid answers to your issue, but could give an idea.
  4. If none of the information that was pointed out here is present in a crash report, and there doesn’t seem to be an answer to what may be causing the crashes then I usually look at the latest.log next since that can sometimes provide more information or give a better idea as to what was happening at the time of the crash. What information should I be looking at in the latest.log?
  5. If all else fails, there one solution that should always work assuming the issue isn’t with Minecraft or Forge itself. That solution is doing a binary search. A binary search would mean to disable half the mods. If the issue persists, then disable half the remaining until you can single out a mod. If the issue does not persist after disabling the first half, then disable all the enabled mods and enable half the remaining. With bigger modpacks it may be better to just remove the mods and place them in a separate folder, or folders, so you have a better idea over what mods are not causing issues.

After finding which mod is causing issues the very first thing you should always do is check for updates for the problematic mod and ensure that the mod is crashing on it’s own, with no other mods present (apart from any dependencies). If there are no updates or the update didn’t fix it then check for updates with Forge. Note that in latest versions of minecraft (currently 1.16) Forge may make breaking changes between versions. If the mod lists a compatible forge version then it may be best to use that, and slowly update from there if needed by other mods. If it’s still crashing then check the github for the mod which can usually be found under the Issues or Source link on the curseforge page. Check the first page or two to see if anyone else is having this issue. If there is no one else reporting it then make an issue report with as much information as you can provide. There may be a template you need to fill out. ALWAYS fill this out or your report will just be ignored.

If there is no issue template on the on the Github then at least supply the following information:

  • What Forge version you’re using
  • What mod version you’re using
  • Steps to reproduce the crash
  • A crash report (if there is one)
  • The latest.log file (if there’s no crash report)

NEVER list forge or mod versions as “latest”. This isn’t a version and could even change between when you post the report and when the dev sees the issue.

You can share crash reports and logs with Pastebin, Ubuntu Pastebin, and gist.github. Pastebin has a character limit which Ubuntu Pastebin and gist.github don’t have. gist.gitgub requires an account to use.

⚠️ **GitHub.com Fallback** ⚠️