Game not responding after a few seconds of being launched (Forge 1.21 - 51.0.18)

[yoonxino]

I downloaded forge for 1.21 because I wanted to play the new update with a few mods. When I load up the game on the forge installation, the game seems to launch fine, but then freezes and goes into that "not responding" state a few seconds after sitting on the menu. It stays on not responding forever, and I have to close the game myself. The normal vanilla game without forge loads and works perfectly fine, though.

The exit code I receive is either 1 or -805306369, depending on how I close the game. When I force close with task manager, I get exit code 1. When I close using the not responding menu (close the program or wait for it to respond), I get exit code -805306369.

I tried taking all of the mods out to see if they were the problem, but the same issue still persists even with 0 mods in the mods folder. The pastebin linked is the log from when I launched the game with forge after taking all of the mods out of the mods folder.
(Nothing ever shows up in the crash-reports folder, but I do have this from the logs): https://pastebin.com/9bL8awvE
I had to delete some of the bottom of the log to be able to upload it onto pastebin, but anything deleted was identical to the lines there at the bottom.

Some things I have tried include: Allocating more ram, updating display drivers, updating java version (currently have Java 21, tried switching to java 17 but that did not work either), removing or changing settings on programs that may conflict with minecraft (followed this list https://minecrafthopper.net/help/known-incompatible-software/). None have worked so far.

I'm aware of course that this is a beta version of forge, but I just wanted to see if there was something I could do to fix this, or if I will just need to wait for a more stable, non beta version to be released.

 

[Ugdhar]

Just to make sure, did you update your video drivers from the AMD website? That's where you want to get your graphics updates from if not.

 

That error in the logs just looks very weird to me

Quote

[25Jun2024 00:33:45.370] [Render thread/INFO] [com.mojang.blaze3d.platform.GlDebug/]: OpenGL debug message: id=1009, source=API, type=ERROR, severity=HIGH, message='No detailed debug message due to a non-debug context'

 

[yoonxino]

1 hour ago, Ugdhar said:

Just to make sure, did you update your video drivers from the AMD website? That's where you want to get your graphics updates from if not.

 

That error in the logs just looks very weird to me

 

Yes, I downloaded the driver off of the official website and downloaded AMD Software: Adrenalin Edition in the process. It's showing me that my driver is up to date. I could try uninstalling and reinstalling it to see if there was anything I missed during the installation process, maybe?

Edit: Update, I downloaded the AMD stuff again following the exact instructions in the FAQ, and I am still getting the same issue.

Edited Tuesday at 11:49 PM by yoonxino

[yoonxino]

Did some digging on that specific error and found a reddit post. Someone replied that they fixed it by closing Overwolf, so I went into task manager and closed Overwolf before loading up the game. This seems to have fixed it! I guess the error has something to do with Overwolf then.