Hey, I'm trying to make a mod in 1.19.2, I followed the install instructions, when trying to run the "runClient" command it starts up as usual, however it always crashes with the following error

[18:43:28] [Render thread/INFO] [minecraft/Minecraft]: Setting user: Dev
[18:43:29] [Render thread/INFO] [minecraft/Minecraft]: Backend library: LWJGL version 3.3.1 build 7
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff49b92b60, pid=15380, tid=23724
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C  [atio6axx.dll+0x192b60]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Programing\Fiver\1192_zombie_jerkey\mdk\run\hs_err_pid15380.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[error occurred during error reporting (), id 0xc0000005, EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff4b97da79]

Does anyone know why this happens and how to fix it?

Quote

# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff49b92b60, pid=15380, tid=23724 # # JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8) # Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64) # Problematic frame: # C [atio6axx.dll+0x192b60]

Crash in your graphics driver.

See this thread for a possible fix: https://forums.minecraftforge.net/topic/117925-forge-1192-43147-crashing-on-startup-with-exit-code-1/#comment-519007

Otherwise contact amd.

4 minutes ago, Robin Roloff said:

Hey, I'm trying to make a mod in 1.19.2, I followed the install instructions, when trying to run the "runClient" command it starts up as usual, however it always crashes with the following error

[18:43:28] [Render thread/INFO] [minecraft/Minecraft]: Setting user: Dev
[18:43:29] [Render thread/INFO] [minecraft/Minecraft]: Backend library: LWJGL version 3.3.1 build 7
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff49b92b60, pid=15380, tid=23724
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C  [atio6axx.dll+0x192b60]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Programing\Fiver\1192_zombie_jerkey\mdk\run\hs_err_pid15380.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[error occurred during error reporting (), id 0xc0000005, EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff4b97da79]

Does anyone know why this happens and how to fix it?

This is a consistent problem with the latest versions of AMD drivers. I was on the more experimental 22Q, but I believe most of the up to date drivers have this issue.

I suggest downgrading to 20.4.2 as that seems to have consistently fixed the problem for anyone dealing with this. I reported the issue to AMD and can only hope it gets fixed. Seems to be an issue with glfwCreateWindow for some reason.

27 minutes ago, Sunku said:

This is a consistent problem with the latest versions of AMD drivers. I was on the more experimental 22Q, but I believe most of the up to date drivers have this issue.

I suggest downgrading to 20.4.2 as that seems to have consistently fixed the problem for anyone dealing with this. I reported the issue to AMD and can only hope it gets fixed. Seems to be an issue with glfwCreateWindow for some reason.

this helped alot, thank you!