warjort

Issue with the java virtual machine. Contact microsoft. Or try a different version of java: https://adoptium.net/ Sometimes an access violation can just be you running out of memory and java not handling it correctly.

That error code is a crash in native code. It means windows has detected the program has corrupted its memory. Usual causes are a bug in your graphics driver or java virtual machine. Make sure these are up-to-date or try a different version of java: https://adoptium.net/ You probably have a file beginning hs_err_pid in your minecraft folder from the time of the crash. If you do just post the first 20 lines so we can see the error. Or the launcher_log.txt will sometimes include this information.

Looks like one of your mod files is corrupted and not a valid jar file (probably because it didn't finish downloading it properly). The error message does not say which one. Try redownloading your mods until you find the one that fixes the problem. Or you can try to open each mod file with a program like winzip which should tell you if it is a valid zip/jar file.

There are 2 main reasons for getting this error: 1) You have a very old version of java that has expired trust certificates so java can't create https sessions. The solution is to upgrade java to a recent version. The original poster already has java 19 so that is not the issue here. 2) You have been using cracked minecraft that has modified your hosts file to redirect requests to minecraft's download site to some other dodgy website. When the forge installer tries to download minecraft you get the above error, which basically says "that's not the official download site". Pirated versions of minecraft are not supported in this forum.

No error in that file either. Read my footer for how to get the launcher_log.txt

install the latest preview release of optifine.

This is a crash in the java virtual machine. You need to report it to microsoft. Or try a different version of java: https://adoptium.net/

You are missing the architectury mod. You have a mod that is not a 1.19.3 mod.

Issue with create, probably a conflict with another mod? Check you have the latest version then contact mod author.

One of your mods is trying to send a network packet that is too big. The logs you have posted don't show the error. Try adding the following system property to your user_jvm_args.txt -Dforge.logging.mojang.level=debug To see if it will display an error in the server logs/debug.log that shows which mod. Otherwise, the only way to find it is to experiment with removing mods until the problem goes away. (Backup your world before removing mods).

One of your mods has broken networking code. Usually the only way to find it is to experiment with removing mods until the problem goes away. (Backup your world before removing mods). But if you post a link to your logs/debug.log it might have some clue. Like I said, usually not though.

Install the latest preview release of optifine.

Oculus issue: https://github.com/Asek3/Oculus/issues/257

You need to post a link to the logs/debug.log so we can see the error(s).

Oculus issue: https://github.com/Asek3/Oculus/issues/257

Looks like one of your mods wants curios installed or you have the wrong version?

Issue with valhelsia_core, others have said it conflicts with optifine.

Issue with valhelsia_core, others have said it conflicts with optifine.

There is no error in that log. If it is the full log, post the launcher_log.txt without restarting the launcher after the crash.

Use java 17, mixin doesn't support java 19

One of your mods is trying to reference client side only classes on the server. From the error I would guess it is either twighlight forest or voidscape? Check you have the latest versions then contact the mod authors.

Invalid/corrupted config file. It's in the config folder. If you don't have a backup, delete the file and it will be recreated with default values.

Nope. 🙂

It looks like you have a minecraft server already running on that network port. Or maybe some other operating system service is? If it's the latter, you can change the "server-port" number in server.properties

That crash does not show the real error. Post a link to your logs/debug.log