How to Read a Crash Log
Learn what parts of a crash log actually matter and what can usually be ignored.
Beginner-friendly guides for crash logs, missing dependencies, mod conflicts, loader errors, corrupted game files, and safer troubleshooting before you start deleting mods.
Basic FixMyGame and crash-log help before you start changing files.
Specific crash messages and common modded-game errors.
Fix crashes mentioning mezz.jei.api.runtime.IJeiRuntime or missing JEI classes.
Fix Minecraft crashes caused by running the wrong Java version for your modpack.
What to do when a Fabric mod needs Fabric API before it can load.
Clean up SMAPI skipped-mod warnings caused by empty or invalid mod folders.
Find the right BepInEx log and understand missing dependency issues.
General troubleshooting concepts FixMyGame uses when reading logs.
What it means when a mod needs another mod installed before it can work.
How two mods can break each other and why removing one is sometimes the fix.
What FixMyGame can safely help with and why backups matter before changes.
Know when the issue is probably game files instead of your mods.
If your game crashed, recreate the issue first, then open the newest crash or error log created after the problem happened. Old logs can look healthy even when the newest session is broken.