#Minecraft not booting from Modrinth (Solved)

1 messages · Page 1 of 1 (latest)

paper prairie
#

repost of the original message

new to modrinth, I click "Play" and it boots the instance for a few seconds then stops instantly, and produces an error file I cannot attach here. Minecraft boots on the version by itself.

Log from Modrinth + text file hs_err_pid1392 attached🥹

[22Jan2024 22:50:03.731] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher running: args [--username, {MINECRAFT_USERNAME}, --version, 1.20.1, --gameDir, C:\Users{COMPUTER_USERNAME}\AppData\Roaming\com.modrinth.theseus\profiles\server_pack_1.0.0, --assetsDir, C:\Users{COMPUTER_USERNAME}\AppData\Roaming\com.modrinth.theseus\meta\assets, --assetIndex, 5, --uuid, {MINECRAFT_UUID}, --accessToken, ????????, --clientId, c4502edb-87c6-40cb-b595-64a280cf8906, --xuid, 0, --userType, msa, --versionType, release, --width, 854, --height, 480, --launchTarget, forgeclient, --fml.forgeVersion, 47.2.17, --fml.mcVersion, 1.20.1, --fml.forgeGroup, net.minecraftforge, --fml.mcpVersion, 20230612.114412]
[22Jan2024 22:50:03.736] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher 10.0.9+10.0.9+main.dcd20f30 starting: java version 17.0.9 by Azul Systems, Inc.; OS Windows 11 arch amd64 version 10.0
[22Jan2024 22:50:04.778] [main/INFO] [net.minecraftforge.fml.loading.ImmediateWindowHandler/]: Loading ImmediateWindowProvider fmlearlywindow
[22Jan2024 22:50:04.839] [main/INFO] [EARLYDISPLAY/]: Trying GL version 4.6

# 
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc6be26280, pid=1392, tid=17248
#
# JRE version: OpenJDK Runtime Environment Zulu17.46+19-CA (17.0.9+8) (build 17.0.9+8-LTS)
# Java VM: OpenJDK 64-Bit Server VM Zulu17.46+19-CA (17.0.9+8-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C  [atio6axx.dll+0x196280]
#
# 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:
#   http://www.azul.com/support/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
#

For the future: please never share hls_pid files because they contain your access token which can be used to access your account and play on your behalf. I deleted your original message

#

As for the error, try updating your AMD drivers. If that doesn't help, check that you don't have AMD Adrenalin installed, and if you do, try closing or uninstalling it

silver abyss
silver abyss