Flywheel Crashing On Multiplayer Server AMD 9070 XT

[Phil-D-D]

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd4cfe9207, pid=3628, tid=29116

JRE version: OpenJDK Runtime Environment Microsoft-8035246 (17.0.8+7) (build 17.0.8+7-LTS)

Java VM: OpenJDK 64-Bit Server VM Microsoft-8035246 (17.0.8+7-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)

Problematic frame:

C [atio6axx.dll+0x849207]

No core dump will be written. Minidumps are not enabled by default on client versions of Windows

If you would like to submit a bug report, please visit:

https://aka.ms/minecraftjavacrashes

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

hs_err_pid3628.log

[DeliciousBread481]

I have the same issue

hs_err_pid8136.log

[NEFirefox]

so do the 6900xt 1.21.1 NeoForged it will always crash when your VDCard Driver's version is above 24.5.1 Here is the hs_err report including create 6.0.3 ver

[sandtechnology]

It's unclear for which side issue (AMD OpenGL code side or FlyWheel side), but here is a workaround working for a 7900XTX machine:

1. Open your minecraft config folder (which located at upper folder for mods folder), the location should like .minecraft\config or .minecraft\versions\<your profile folder>\config.
2. Find and open flywheel-client.toml file with notepad or other text editor.
3. Find the following line, replace"DEFAULT" to "flywheel:instancing": backend = "DEFAULT"
4. After replacing, it should look like this: backend = "flywheel:instancing"
5. Save the file, Start the game to test if this workaround fix it.

Above steps basically force flywheel to use fallback backend instancing instead of indirect, so just bring fps impact for this workaround.

EDIT: It seems this issue is missing basic reproduce steps, the crash will just happen after join the singleplayer world or multiplayer world with create mod installed, and will crash in just a few seconds, there are another issue in AMD GPU driver repo may related to this crash: https://github.com/GPUOpen-Drivers/AMD-Gfx-Drivers/issues/37

[NEFirefox]

It's unclear for which side issue (AMD OpenGL code side or FlyWheel side), but here is a workaround working for a 7900XTX machine:

1. Open your minecraft config folder (which located at upper folder for mods folder), the location should like .minecraft\config or .minecraft\versions<your profile folder>\config.
2. Find and open flywheel-client.toml file with notepad or other text editor.
3. Find the following line, replace"DEFAULT" to "flywheel:instancing": backend = "DEFAULT"
4. After replacing, it should look like this: backend = "flywheel:instancing"
5. Save the file, Start the game to test if this workaround fix it.

Above steps basically force flywheel to use fallback backend instancing instead of indirect, so just bring fps impact for this workaround.

EDIT: It seems this issue is missing basic reproduce steps, the crash will just happen after join the singleplayer world or multiplayer world with create mod installed, and will crash in just a few seconds, there are another issue in AMD GPU driver repo may related to this crash: GPUOpen-Drivers/AMD-Gfx-Drivers#37

for me, it was just happen when the game start loading ANYTHING about create machines i'll try dis

[petrenko17]

This crash can be fixed by changing the flywheel backend from inderect to instancing trough in game command. This is a temporary solution.

[BersisSe]

I have a Amd APU with the igpu Radeon 860M and it has the same issue : https://mclo.gs/XbUwElZ Switching flywheel to the instancing makes the cogwheels and blazeburners invisible. but the off setting works fine