Posted May 4, 20232 yr Got this crash with Java Version 8 Update 371 (build 1.8.0_317-b11) and forge 43.2.10. I've tried other Forge versions and they too have crashed with the same report: # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffddf16280, pid=14020, tid=1356 # # JRE version: OpenJDK Runtime Environment Microsoft-32931 (17.0.3+7) (build 17.0.3+7-LTS) # Java VM: OpenJDK 64-Bit Server VM Microsoft-32931 (17.0.3+7-LTS, mixed mode, 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: # https://github.com/microsoft/openjdk/issues # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # I don't believe this is an error with Java itself as Fabric mod loader still works.
May 4, 20232 yr https://forums.minecraftforge.net/topic/123416-exit-code-1/?do=findComment&comment=536369 If nothing on that post (or those linked to it) works contact AMD. Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
May 4, 20232 yr AMD Drivers on Windows are known to be really bad... Try clean installing all your drivers by removing them with Display Driver Uninstaller and then download fresh drivers. That's what worked for me the last time I had something like this happen. New year, new me. Nothing's going to get me down!
May 5, 20232 yr Author 10 hours ago, TheOneWithBlueEyes said: AMD Drivers on Windows are known to be really bad... Try clean installing all your drivers by removing them with Display Driver Uninstaller and then download fresh drivers. That's what worked for me the last time I had something like this happen. Thank you so much
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.