Mod conflicts

Not Enough Crashes InitErrorScreen Rendering Crash

What it looks like in the log

fudge.notenoughcrashes.gui.InitError

How to fix it

  1. Open your Minecraft profile's mods folder and delete or disable the Not Enough Crashes (notenoughcrashes) .jar file.
  2. Launch Minecraft again to test if removing the mod resolves the OpenGL conflict directly.
  3. If the game still crashes during startup, open the latest file in your crash-reports folder to read the real underlying mod error that Not Enough Crashes was masking.
LoadersFabric, Quilt, Forge
SeverityStops the game
CategoryMod conflicts

Check your own logDownload notenoughcrashes on 9Minecraft

Related errors

Mod conflictsAE2 Crash Viewing Unnamed Cable Tooltip When Channels Are DisabledUpdate Applied Energistics 2 to the latest `rv3` release for Minecraft 1.7.10, which updates recipes automaticMod conflictsCrash on Second Launch: "this.uniformCache" is null (Sodium & DashLoader)Open your Minecraft instance's mods folder and look for the DashLoader .jar file (e.g., dashloader-x.x.x.jar).Mod conflictsInvisible Blocks and Console Spam: Sodium ColorProvider.getColors NullPointerExceptionUpdate LittleTiles (and CreativeCore) to the latest version available for your Minecraft version, as newer relMod conflictsIris Shaders: Unknown Error Loading Distant Horizons CompatibilityUpdate Distant Horizons to the latest available release for your Minecraft version (specifically version 3.3.1Mod conflictsOptiFine is not compatible with this mod setOptiFine patches the same code many performance mods patchMod conflictsSodium Crash: BufferUnderflowException in MultiDrawBatchCheck your crash report for 'cullleaves' in the stacktrace; if you have the Cull Leaves mod installed, remove