Bug Description

Minecraft version: 1.21.5
Fabric loader: 0.16.13
Sodium version: 0.6.13+mc1.21.5
Java version: 21.0.2
Operating system: Windows 11
GPU: AMD Ryzen 3 5425U with integrated Radeon Vega 6
Driver version: Latest official AMD driver from amd.com, clean installed via DDU (April 2025)

💥 What happens:
When attempting to join a multiplayer server, the game loads up to “Loading terrain...” then freezes and exits silently with exit code -1073741819. No crash report is generated. Only the latest.log updates, but contains no actual error or stack trace.

✅ What I’ve tested:

• Fabric + all other mods + Sodium = still crashes
• All other mods removed = still crashes
• DDU used to wipe previous drivers → installed latest AMD GPU drivers fresh
• Minecraft 1.21.4 with previous Sodium version = worked fine
• Minecraft 1.21.5 without Sodium = works fine
• Minecraft 1.21.5 with Lithium, Starlight, FerriteCore = works fine
• Crash happens only with Sodium 0.6.13+mc1.21.5, during world rendering
• Main menu loads fine — crash only occurs during world load

📎 Additional info:

• No crash reports are generated in .minecraft/crash-reports/
• Crash seems to occur as soon as chunk rendering begins
• Exit code: -1073741819 (access violation / native crash)
• Vega 6 is integrated graphics (Ryzen 3 5425U), and this might affect similar APUs

Reproduction Steps

1. Install Minecraft 1.21.5 with the latest Fabric loader
2. Add Sodium 0.6.13+mc1.21.5 and Fabric API to the mods folder
3. Launch the game
4. Click “Multiplayer” and connect to any server
5. Wait for the game to reach “Loading terrain...”
6. Game freezes and exits with exit code -1073741819
7. No crash report is generated

Log File

latest.log

Crash Report

crash-2025-04-12_23.36.05-client.txt

Can you please upload the hs_err_pid*****.log file from your .minecraft folder? You are likely experiencing a JVM crash, which produces a different kind of crash report. Without this file, we cannot diagnose where the crash is happening or for what reason.

If you have multiple hs_err_pid*****.log files, then delete all of them, restart the game, and reproduce the crash so that you can know you're getting the latest crash report file.

where can i find this file

Inside your .minecraft directory

It won't be in the crash reports folder like regular crash reports

I checked my .minecraft folder and found no recent hs_err_pid logs. the most recent one is from december 2023. I deleted the old ones, reproduced the crash multiple times, and no new log file is generated.

I’ve already updated my AMD drivers using DDU, confirmed this only happens with Sodium 0.6.13, and that it didn’t occur on 1.21.4.

What’s actually happening (as I understand it):
When Minecraft + Sodium tries to load into a world, Sodium starts initializing world rendering. At this point, it seems to trigger a GPU-level failure on my machine (Ryzen 3 5425U with Vega 6 graphics). The AMD driver crashes so hard that the Java Virtual Machine is instantly terminated, without any hs_err_pid file being generated. This results in exit code -1073741819, which is a native Windows access violation error (0xC0000005).

In other words, this isn’t a regular Java exception or mod conflict — it’s a native crash caused by something in Sodium’s rendering pipeline hitting a bad code path on Vega 6 GPUs.

My theory:
It seems that Sodium 0.6.13 introduced a rendering change (optimization, pipeline tweak, OpenGL call, etc.) that’s incompatible with Vega 6’s driver, causing the driver to crash and the JVM to be killed. Since this is a native-level failure, there’s no Java crash report or diagnostic trail — just an instant exit.

I understand this may be difficult to reproduce without access to a Vega 6 system, but I’m happy to test debug builds or try diagnostic steps if that helps.

Let me know if I can provide anything else.

There were no changes in Sodium 0.6.13 that affected the rendering or shader code. It does not make sense why it would be causing this regression.

Minecraft 1.21.5 is known to be extremely unstable and problematic on some computers. You may be seeing issues related to this, and it is unlikely something we can fix. Without the JVM crash file (hs_err_pid*****.log), we cannot really do anything to help you, since there is no useful debugging information.

Please, try using Prism Launcher to reproduce your crash. We know that it should work correctly and that it will provide more useful debugging information. When the crash occurs, the hs_err_pid*****.log file should be placed in the minecraft folder, which can be navigated to like so:

Note that the exact appearance of Prism Launcher and your File Explorer will differ, since these screenshots are not taken on a Windows computer.

well, i downloaded the prism launcher and tried it again with all my mods that i use (sodium included) and it is running absolutely fine. i dont get why it works here but not in the normal launcher

Did you edit your JVM arguments? Try to reset them in the stock launcher

i once allocated it more ram yes, could this have something to do with it?

Probably not unless you made a typo. Just reset the args and try again

I reset the JVM arguments to the default in the vanilla launcher, as suggested.

With Sodium enabled, the game still crashes during “Loading terrain...” with exit code -1073741819.
As before, no hs_err_pid file is generated.

However, when I remove only Sodium, the game works perfectly fine — even with the same JVM arguments and mod setup.

This strongly suggests that Sodium combined with the vanilla launcher’s launch method is triggering something on my system (Vega 6 iGPU, AMD Ryzen 3 5425U) that crashes the JVM before any log can be produced.

Probably this: https://report.bugs.mojang.com/servicedesk/customer/portal/2/MC-296043
There is a mod that fixes this: https://github.com/Enchanted-Games/uniform-fix
Might make sense to include this fix in Sodium.

Confirmation by user on discord that this fix mod worked for them

thank you Gerrygames i will kiss your left buttcheek. it works. tysm

This has been fixed in Minecraft 1.21.8. We strongly suggest that players either update to the latest version, or install the mod mentioned above that addresses the problem.