Modpack guide

Minecraft crash helper mods compared

Crash helper mods do different jobs. Crash Assistant shows the logs and fixes known problems; Not Enough Crashes lists the mods in the crash and keeps the game open; Neruina stops ticking crashes from breaking a world; the Modkeel Companion names the one mod that most likely caused the crash, turns it off in one click and copies worlds before mods change.

Checked October 4, 2026, from each mod's Modrinth page and files; tested in a real game October 12 and 15, 2026; criteria added October 17, 2026. Written by Modkeel, which makes the Companion; corrections are welcome on GitHub.

The same crash, five crash mods

Descriptions only go so far, so on October 12, 2026 we crashed Minecraft 26.2 (Fabric) the same way with each of these mods installed, in a real game client. The crash comes from a small test mod, Crash Test Mod, that throws an error in the game's own code eight seconds after a world opens: the most common kind of mod crash, where one mod breaks and the game closes. Each run started from a clean game folder with Fabric API, the test mod and the crash mod, and we recorded what the player saw during the crash and on the next start.

The same mod crash on Minecraft 26.2 Fabric with each crash mod. No crash mod: the game closes and says nothing. Modkeel Companion: on the next start names Crash Test Mod and offers to turn it off; the game had closed. Crash Assistant: its own window after the game closes, with logs to share; names no mod and offers no fix for this crash. Not Enough Crashes: crash screen in the game naming Crash Test Mod and one innocent mod; the game stays open. CrashPatch: crash screen in the game naming Minecraft as the cause; the game stays open. Neruina: nothing; the game closes.
Tested in the Modkeel lab: reuse the image with a link to this page.

Without a crash mod the window went black and closed, and the next start showed the title screen with no word about what happened. Not Enough Crashes kept the game open and showed a crash screen naming two mods as potential causes: Crash Test Mod, the right one, and Fabric Lifecycle Events, part of Fabric API that only passed the error along. It offered the crash log to send to the mod's author. CrashPatch (which needs Not Enough Crashes and replaces its screen) also kept the game open, but named Minecraft itself as the likely cause. Crash Assistant opened its own window once the game had closed, with the crash report, the log and the mod list ready to upload and a message for your launcher's Discord; its main window named no mod, and this crash is not one of the known problems it has a fix for. Neruina did nothing, as expected: it guards ticking entities and blocks, not crashes in other code. The Modkeel Companion let the game close, then on the next start said the world was safe, named Crash Test Mod and offered one button to turn it off.

One crash of one kind, on one version: a known driver or mod conflict would favour Crash Assistant's fixes, and a crash in a ticking entity favours Neruina (the next test). We make the Companion; the screens below are what each mod showed, unedited apart from the strip.

Modkeel Companion on the next start after the crash: your world is safe, it was probably Crash Test Mod, button Disable Crash Test Mod Not Enough Crashes crash screen: potential causes Crash Test Mod and Fabric Lifecycle Events, buttons Back to Title Screen and Show crash log CrashPatch crash screen: your game crashed, this could have been caused by Minecraft Crash Assistant window after the game closed: available log files with Open and Upload buttons, and Upload all logs and copy a message for support

A ticking entity crash, five crash mods

The second kind of crash is the one Neruina is built for: a mod's code fails while a mob ticks, the crash report says "Ticking entity", and in a saved world the same mob can crash the game again every time it loads. On October 15, 2026 we ran it the same way: Crash Test Mod summons a burning pig, and the pig's first fire damage runs into an error in the test mod's code.

A ticking entity crash on Minecraft 26.2 Fabric with each crash mod. No crash mod: the game closes and says nothing. Neruina: a chat message names the pig, which it suspends, and the game stays open; it does not name the mod. Modkeel Companion: on the next start names Crash Test Mod and offers to turn it off; the game had closed. Crash Assistant: its own window after the game closes, with logs to share. Not Enough Crashes: crash screen naming Crash Test Mod and one innocent mod, then the game closes. CrashPatch: crash screen naming Minecraft, then the game closes.
Tested in the Modkeel lab: reuse the image with a link to this page.

Neruina did its job: the game kept running, the pig froze in place still burning, and a chat message said it had caught a ticking entity, a pig at those coordinates, suspended it, with buttons to learn more and copy the crash. It named the pig, not the mod whose code failed, and the mod stays installed, so the next mob that runs that code can fail too. Not Enough Crashes and CrashPatch showed their crash screens (Not Enough Crashes named Crash Test Mod and Fabric Entity Events, which only passed the error along; CrashPatch again named Minecraft), but this crash happened in the world's own server inside the game, and it came back on every frame until they gave up ("the game has crashed an excessive amount of times") and the game closed. Crash Assistant opened the same window as before, with the logs to share and no mod named. The Modkeel Companion did what it did for the first crash: the game closed, and the next start said the world was safe, named Crash Test Mod and offered to turn it off.

Neruina keeps you playing; the Companion names the mod to remove. They do different jobs and work together.

Neruina chat message in the game: caught ticking entity Pig at its coordinates, it has been suspended, with What Is This and Copy Crash buttons; the burning pig stands still Modkeel Companion on the next start after the ticking entity crash: your world is safe, it may have been Crash Test Mod, button Disable Crash Test Mod Not Enough Crashes crash screen: potential causes Crash Test Mod and Fabric Entity Events, before the game closed CrashPatch crash screen: this could have been caused by Minecraft, before the game closed

At a glance

Modkeel CompanionCrash AssistantNot Enough CrashesNeruina
Names the mod that most likely caused ityes, with how sure and whyfor known problemslists mods involvedthe entity, block or item
Turns a mod off in one clickyesmods the pack author listednono
Goes back to the mods that last workedyesshows what changednono
Copies worlds before mods changeyesnonono
Keeps the game open after a crashnonooftenticking crashes
Fixes for known problemswarns before they hityes, large listnono
Uploads logsopt-in, anonymouson click, to mclo.gson clickissue on click
Patches the game (mixins)noyesyesyes
LoadersFabric, NeoForge, ForgeFabric, Quilt, Forge, NeoForgeFabric, Quilt, NeoForge, ForgeFabric, Forge, NeoForge
Minecraft1.20.1 to 26.x1.6.4 to 26.31.16.5 to 26.31.18 to 26.2
LicenseMITown (KostromDan MML)MITMIT

What makes a crash tool right about the mod

Players asking which crash tool to trust want the same five things, and the two tests above show how far each mod gets on them.

  1. The culprit from the crash itself, with the evidence. The stack trace and the log say whose code failed; the mod list alone does not. In both tests the Companion named Crash Test Mod and gave the reason in plain words ("its code is in the error"; for a broken mixin, "its mixin failed to apply"). Not Enough Crashes named it too, next to a Fabric API module that only passed the error along. CrashPatch named Minecraft, and Crash Assistant named no mod for either crash.
  2. How sure it is, and when it cannot tell. A tool that always names a mod is wrong whenever the crash does not point at one. The Companion grades each answer ("It was", "It was probably", "It may have been": the first test got "probably", the ticking one "may have been"), and when nothing points at one mod it says "It is not clear which mod it was" and offers to go back to the mods that last worked instead of guessing.
  3. The exact file, not only the mod. A mod can crash in one build and not the next. The Companion matches each jar by its fingerprint against the Modkeel lab ("this exact file crashed on Minecraft 26.2 in the Modkeel lab"), says when a file name points at another Minecraft version, and when another mod expects a different version of it.
  4. Crashes before the game opens. Crash Assistant is strongest here: it loads very early and its window is a separate program, so it also shows up when startup fails. The Companion reads a startup crash on the next start; on NeoForge and Forge it also starts before the loader reads the mods and turns off a jar that would close the game before any mod runs (two mods that cannot be used together, a Forge mod made for another version). A crash that repeats on every launch before mods load leaves it no chance: paste latest.log into the crash reader, which gives the same reading from outside the game.
  5. The crash stays on your PC. The Companion reads crashes on your computer; nothing is uploaded to find the mod, and sharing an anonymous report is a box you tick, with every field shown first. Crash Assistant and Not Enough Crashes also keep logs local until you click Upload; Crash Assistant sends them to mclo.gs, which removes tokens, IP addresses and user names.

Crash Assistant

By KostromDan; the most downloaded of the group (about 20 million downloads on Modrinth alone). After the game closes, a separate window shows every relevant log and checks it against a long list of known problems, such as graphics drivers, duplicate mods and broken mixins; for many of them it explains the fix, and some have an Auto-Fix button. It shows which mods changed since the last launch that worked. Logs are uploaded to mclo.gs only when you click Upload. Pack authors can list mods it should offer to remove. It runs on more loaders and Minecraft versions than any other mod here. Crash Assistant on Modrinth.

Not Enough Crashes

By natanfudge, MIT. When the game crashes, it goes back to the title screen instead of closing, so you can keep playing without a restart, and it lists the mods involved in the crash with links to their issue trackers. It does not say which of them is the likely cause or turn any off. Not Enough Crashes on Modrinth.

Neruina

By Bawnorton, MIT. Neruina solves a different problem: a ticking entity, block or item that crashes the game every time the world loads. It suspends the thing that fails, so the world still opens, and lets you teleport to it, try again, remove it or report it. It does not diagnose other crashes. Neruina on Modrinth.

CrashPatch

By Wyvest and mariethepolarfox (Polyfrost). Like Not Enough Crashes it catches crashes and returns to the game, except during loading, looks up known fixes, and can open or upload the crash log. Recent Minecraft versions are Fabric only, and it has no 1.20.1 release. CrashPatch on Modrinth.

Modkeel Companion

Made by Modkeel, MIT. On the next start after a crash, the Modkeel Companion says which mod most likely caused it, how sure it is and why (for example "its mixin failed to apply" or "this exact file crashed on Minecraft 26.2 in the Modkeel lab"), and one button turns that mod off, or goes back to the set of mods that last worked; every change can be undone. Before a world loads with a different set of mods, it copies the world. It has no mixins, so it cannot be what breaks a pack, and it sends nothing unless the player ticks "Help other players". It does not keep the game open after a crash, and it covers fewer versions than Crash Assistant.

Which one to pick

Name the mod, keep the world

The Modkeel Companion is a free, open source mod for Fabric, NeoForge and Forge. It copies each world before it loads with different mods; if the game then crashes, the next start names the mod that most likely caused it and turns it off in one click.

Get the Modkeel Companion

Crashed already? Paste the crash report to see which mod caused it.

Questions

Is there a mod that tells you which mod crashed Minecraft?

Yes, several, in different ways. The Modkeel Companion names the one mod that most likely caused the crash, says how sure it is and why, and turns it off in one click. Not Enough Crashes lists the mods involved in the crash. Crash Assistant shows the logs, recognises known problems and offers fixes for them.

Which crash mod backs up my world?

Of the mods compared here, only the Modkeel Companion copies worlds: before a world loads with a different set of mods. Neruina protects worlds in another way: it suspends the entity, block or item whose ticking crashes, so the world can still be opened.

Which crash mod lets me keep playing after a crash?

Not Enough Crashes and CrashPatch send you back to the title screen after many crashes instead of closing the game, though in our test a ticking entity crash still closed it. Neruina keeps the game running through ticking entity and block crashes by suspending what failed. The Modkeel Companion and Crash Assistant act after the game has closed: on the next start or in a separate window.

Which crash tool is right about which mod crashed Minecraft?

One that names the culprit from the stack trace and the log, shows its evidence and says when it cannot tell. In the Modkeel lab's two tests on Minecraft 26.2, the Modkeel Companion named the right mod with the reason and how sure it was; Not Enough Crashes named it next to a Fabric API module that only passed the error along; CrashPatch named Minecraft; Crash Assistant named no mod. For crashes during startup, Crash Assistant's separate window catches the most.

Can I use more than one crash mod?

They do different jobs, so combining them can make sense; for example Neruina against ticking crashes and the Modkeel Companion for world copies and naming the mod. Test the combination in your pack before shipping it.

Related

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