Modpack Version
1.0.1
Crash Assistant Message (big green button)
All the Mons - 1.0.1 crashed without a crash report. The logs have been uploaded to gnomebot.dev:
Mod list changes on top of the modpack:
Added mods:
.index (resourcepack)
Maxi's-JM+CM_Pixel-U10.zip (resourcepack)
NewGlowingOres-§6[Border]§r.zip (resourcepack)
What happened?
The game crashes silently during the bootstrap/mixin phase, before the mod
loading screen ever appears. No crash report is generated. The early loading
window shows "Launching Minecraft" with CPU: -100.0%, which indicates the JVM
died at the native level.
After investigation across multiple crash sessions, the root cause was isolated
to Sodium 0.8.12-beta.2 conflicting with the AMD RX 9060 XT (RDNA 4 / Navi 44)
on Windows 11. Sodium applies the AMD_GAME_OPTIMIZATION_BROKEN workaround
at startup but the JVM still crashes silently shortly after, consistently at
the same point in every attempt (right after Datafixer Bootstrap completes).
Bisect result:
- With Sodium 0.8.12-beta.2 present → silent crash, no crash report, game
never reaches the title screen
- With Sodium removed → game loads past the bootstrap phase normally
Crash Assistant confirms (every session):
- Reached first tick of TitleScreen: false
- Joined world successfully: false
- stop() / close() / emergencySave() functions: all false
- No crash report generated
System:
- GPU: AMD Radeon RX 9060 XT (RDNA 4, Navi 44)
- Driver: Adrenalin 26.6.4 (OpenGL 4.6)
- CPU: AMD Ryzen 7 5700X
- RAM: 32 GB DDR4
- Java: Microsoft OpenJDK 21.0.7
- OS: Windows 11
- Launcher: Prism Launcher
- NeoForge: 21.1.234
The Crash Assistant message with all logs is pasted above. The modpack's bundled
version of Sodium (0.8.12-beta.2) appears to be incompatible with RDNA 4 GPUs
on Windows. A possible fix would be updating Sodium to a newer version or adding
an explicit workaround for the RX 9060 XT / Navi 44 architecture.
Crash Log or Disconnect Log
No response
Latest.Log
No response
Read this!
Modpack Version
1.0.1
Crash Assistant Message (big green button)
All the Mons - 1.0.1 crashed without a crash report. The logs have been uploaded to
gnomebot.dev:latest.log | debug.log | PrismLauncher-0.log head / tail (~47k lines) | crash_assistant_app.log | modlist.txt
Mod list changes on top of the modpack:
What happened?
The game crashes silently during the bootstrap/mixin phase, before the mod
loading screen ever appears. No crash report is generated. The early loading
window shows "Launching Minecraft" with CPU: -100.0%, which indicates the JVM
died at the native level.
After investigation across multiple crash sessions, the root cause was isolated
to Sodium 0.8.12-beta.2 conflicting with the AMD RX 9060 XT (RDNA 4 / Navi 44)
on Windows 11. Sodium applies the
AMD_GAME_OPTIMIZATION_BROKENworkaroundat startup but the JVM still crashes silently shortly after, consistently at
the same point in every attempt (right after Datafixer Bootstrap completes).
Bisect result:
never reaches the title screen
Crash Assistant confirms (every session):
System:
The Crash Assistant message with all logs is pasted above. The modpack's bundled
version of Sodium (0.8.12-beta.2) appears to be incompatible with RDNA 4 GPUs
on Windows. A possible fix would be updating Sodium to a newer version or adding
an explicit workaround for the RX 9060 XT / Navi 44 architecture.
Crash Log or Disconnect Log
No response
Latest.Log
No response
Read this!