Minecraft crash reports (found in .minecraft/crash-reports/) contain a full stack trace of the error that terminated the game. Reading the 'Description' and 'Caused by' lines tells you the specific cause — a mod conflict, resource pack issue, outdated Java, or hardware driver problem.
How to read a crash report
Open the crash report in a text editor. The Description line summarizes the crash type. Scroll to Caused by — that line identifies the specific exception. Mod-related crashes usually show a mod's package name (e.g., com.example.modname). Vanilla crashes show java.lang.* exceptions.
Common crash causes
1. Mod conflict — two mods modifying the same game system. 2. Missing mod dependency — a mod requires another mod that is not installed. 3. Outdated Java — Minecraft 1.17+ requires Java 17. 4. Corrupted world save. 5. GPU driver crash (hs_err_pid log alongside the crash report).
How to fix step by step
- 1Open .minecraft/crash-reports/ and find the most recent crash report file
- 2Read the Description and Caused by fields to identify the cause
- 3If mod-related: disable mods one by one (bisect method) to find the conflict
- 4If Java-related: update to Java 17 (for 1.17+) or Java 8 (for 1.16 and below)
- 5If GPU-related (hs_err_pid log present): update your GPU driver
How CRASH-REPORT differs from related codes
- Error EXIT-CODE-1: The Java Virtual Machine running Minecraft crashed and exited with code 1, indicating a fatal error. This is typically a Java or mod compatibility issue. (user-side)
- Error JAVA-HEAP-SPACE: Minecraft ran out of allocated Java heap memory. The JVM cannot allocate more objects because all configured RAM is used. This causes an immediate crash. (usually client-side)
- Error OUT-OF-MEMORY: Minecraft's Java process ran out of allocated memory (heap space). The game crashed because it could not allocate more RAM. (user-side)