TerdyTheTerd

Rename the installer not the universal, forge changed this in more recent versions.

If you are using the most recent forge for 1.12.2, try downloading and renaming the Installer to modpack.jar, not the universal, otherwise use the 2847 universal. The most recent versions do not include any changes to forge itself, only changes to the license and build script.

I am assuming that is referring to the Java version. Downgrade to Java 8 or 9.

Unlikely it did nothing. Please provide either logs or a screenshot, preferably a log.

Forge changed in newer versions, but then they decided to push some updates to 1.12.2 that had these new changes in them. Most guides are still not updated to reflect this, many users have been having this issue recently.

Whoops I may have been looking at a different post, I thought this was placed under Bug Reports -> Launcher Issues. Platform pagoda is the correct spot, or allowed spot I should say. You are using the latest forge, so try renaming the installer instead of the universal.

Please change the formatting, black text is hardly readable with this background color. If you have discord join the Technic discord, they have bots to help you get the logs and will auto analyze them for common issues. Several useful pinned/sticky threads in the Technic Launcher forums section. Quick and Dirty: Launcher Options -> Open Logs -> open most recent file -> select and copy the contents -> go to pastebin or hastebin and copy the log contents -> share the created pastebin link here.

Please fix the formatting so it's readable. Also post in the correct section, I'm sure a moderator will be shortly to lock this out with no helpful information. If you don't where that is either read the rules or struggle on your own.

https://gaming.stackexchange.com/questions/96496/is-there-a-list-of-error-codes-for-minecraft/#:~:text=Pixel format not accelerated https://minecrafthopper.net/help/pixel-format-not-accelerated/ Should be enough info for you, did you even view the crash report? Come back if nothing there works for you. Also note Pixelmon support is not offered here, so unless this occurs on other packs as well (which it should in this case) you will need to go elsewhere for support.

Rename the installer to modpack not the universal, or downgrade to version 2487

If other packs work fine and it's just the 1.12.2 pack you are having issues, I suggest trying to get support from the 1.12.2 pack instead of here. https://www.technicpack.net/modpack/the-1122-pack.1406454/help There's too many possible causes, and unless this also occurs on other packs then I don't have the time to troubleshoot someone else's pack.

Just occurred to me, we never tried disabling the Stencil Buffer: Always worth a shot

What does the technic log file show?

Any info I can find related to that specific error code (EXCEPTION_ACCESS_VIOLATION (0xc0000005) with that problematic frame (jvm.dll) all point to bad memory, assuming that everything else is up to date (video drivers, bios drivers, java versions, windows updates etc.). If you have been experiencing any other issues recently with your pc, then that just strengthens the plausibility of bad RAM, especially if you've encountered frequent BSOD recently. Unless somebody else has any insight there isn't much else I can do from these forums (and frankly I don't have time for a one on one discord call, that's some enterprise level support right there, which these forums are not). Below are a few resources you may find useful or helpful: fastthread.io is an online tool for analyzing HotSpot error logs (that hs_err_pid file that was mentioned in that screenshot, its location is also shown). You can try uploading the log to that and see if it gives you anything useful. Two stackexchange threads with the same error code and problematic frame. There are many others but with different frames: - https://gaming.stackexchange.com/questions/362675/exception-access-violation-in-vanilla-minecraft - https://gaming.stackexchange.com/questions/166949/minecraft-exception-access-violation List of useful errors found in Minecraft and some solutions to them, scroll to the very bottom for this error - https://gaming.stackexchange.com/questions/96496/is-there-a-list-of-error-codes-for-minecraft Hope you find a solution or someone else is able to better help you, if you do make sure you update this thread in case it might help someone else.

Have you ran a memory test/and or tried to reseat your RAM? Additionally can you link your pack? It seams that Enchanted Oasis is a fairly popular pack, with many rip offs on the platform. If this is the official pack then you will need to reach out to pack author for support.

It's very normal for java process to show more memory usage than what might have been specified solely as the -Xmx (what you set in the launcher). This is due to various things, which you can read more about here. Your case does not seem too off, I just did a test on my pack and windows was showing about a ~60-70% increase over what Minecraft was reporting (depending on the min-max usage before/after GC). Knowing that the 1.12.2 pack is fairly heavy to run, it doesn't really surprise me that windows is showing ~100% increase. Try running another pack and see what it does.

Without checking I am just going to assume that you used the latest forge version and renamed the universal file. Forge made changes to newer versions, which includes the latest versions for 1.12.2, where you have to instead download the installer and rename that to modpack.jar. Lots of users have been having this issue recently as forge seems to have "snuck" these changes into the latest 1.12.2 builds, previously they were only for 1.13+, hence why any guide you may have followed did not include this newer info. If that's not the case then I will take a closer look.

Well that's a JVM error and not related to minecraft/technic. Have your tried uninstalling and reinstalling Java? If not, try it. This could always be an issue with bad RAM, but unless you've ran into other issues with your pc then you likely don't have bad RAM. It never hurts though to run a memory test with something like MemTest86. Perhaps an obscure solution, as this usually only corrects issues when an entire stick of RAM goes bad, but if nothing else provides results might look into reseating your RAM modules, but we can save that for last.

Well that should make this more interesting. Can you grab a log file after this occurs and upload to a pasting service, we'll see if there's anything useful in there. I wanted to clarify, did you mean all the modpacks you have installed and have played (or at least tested), or do you literally mean "my modpacks" as in this is occurring on your custom modpack?

Without checking I am just going to assume that you used the latest forge version and renamed the universal file. Forge made changes to newer versions, which includes the latest versions for 1.12.2, where you have to instead download the installer and rename that to modpack.jar. Lots of users have been having this issue recently as forge seems to have "snuck" these changes into the latest 1.12.2 builds, previously they were only for 1.13+, hence why any guide you may have followed did not include this newer info. If that's not the case then I will take a closer look.

That too, but I like giving people the benefit of the doubt. Looks like I missed the part where they mentioned removing/installing java, so it is looking more sus

Likely still a setting buried somewhere. To check if its a firewall issue open up Command Prompt and type "ping authserver.mojang.com". This should give you something like this: If you don't get a response it's likely the firewall, if you do get a response then it's likely java, try uninstalling and reinstalling java as it may be a corrupt certificate. This of course is assuming you are using a valid account.

Does this also occur with vanilla minecraft? I would think this is a graphic driver issue, but since the 1060 is relatively new I would assume it has recent enough drivers. Try checking if there are newer drivers you can install for your GPU. I've seen other games with similar behavior when running an unstable overclock on the gpu, but I can't say I've ever heard of minecraft having these issues...

Without checking I am just going to assume that you used the latest forge version and renamed the universal file. Forge made changes to newer versions, which includes the latest versions for 1.12.2, where you have to instead download the installer and rename that to modpack.jar. Lots of users have been having this issue recently as forge seems to have "snuck" these changes into the latest 1.12.2 builds, previously they were only for 1.13+, hence why any guide you may have followed did not include this newer info. If that's not the case then I will take a closer look.

Does this occur with other packs? Pixelmon support is not offered on these forums. If this happens with other packs it could just be that the window got moved "off screen". Try Shift + right clicking the icon on the taskbar, select "Move", press any arrow key and then move the mouse around.