server/data/known_crashes.json

[
  {
    "signature": "java.lang.OutOfMemoryError",
    "cause": "The game ran out of allocated RAM.",
    "fix": "Allocate more RAM in your launcher settings (e.g., increase -Xmx argument to at least 4G or 6G depending on modpack size)."
  },
  {
    "signature": "net.fabricmc.loader.impl.FormattedException: Mod resolution encountered an incompatible mod set",
    "cause": "You have incompatible or missing mod dependencies.",
    "fix": "Read the crash log closely to find which mod is missing or incompatible, and download the exact version required for your Minecraft version."
  },
  {
    "signature": "java.lang.NoSuchMethodError",
    "cause": "A mod is trying to use a method that does not exist, usually because it was built for a different version of Minecraft or an incompatible API.",
    "fix": "Ensure all mods are strictly for your exact Minecraft version. Remove recently added mods one by one to isolate the issue."
  },
  {
    "signature": "org.spongepowered.asm.mixin.throwables.MixinApplyError",
    "cause": "Two or more mods are trying to modify the same base game code (Mixin conflict), causing a collision.",
    "fix": "Identify the conflicting mods mentioned near the MixinApplyError in the log. You may need to remove one of them, or look for a compatibility patch/updated version."
  },
  {
    "signature": "java.lang.IllegalStateException: Lock is no longer valid",
    "cause": "A race condition deadlock caused by ModernFix's 'Fast Entity Loading' optimization. It is attempting to bypass the standard world-save lock while Starlight is simultaneously recalculating light maps for the same chunk entities. This makes the game think the world file has been corrupted or closed prematurely.",
    "fix": "Locate the 'modernfix-mixins.properties' file in your config folder. Find the line 'mixin.perf.fast_entity_loading=true' and change it to 'false'. This disables the specific buggy optimization without needing to delete the entire mod."
  },
  {
    "signature": "EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=... [nio.dll+0x3451]",
    "cause": "This is a Thread Scheduling conflict caused by Intel 12th/13th/14th Gen 'Hybrid Architecture' CPUs. Windows is attempting to park the Minecraft Render Thread on an 'E-Core' (Efficiency Core) instead of a 'P-Core' (Performance Core). This causes a memory access violation because the Java NIO library cannot handle the core-hopping during a heavy I/O tick.",
    "fix": "Add the following JVM argument to your launcher profile: '-XX:ThreadPriorityPolicy=1'. Additionally, ensure Windows 'Power Plan' is set to 'High Performance' to prevent the OS from offloading Java threads to background cores."
  }