#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000000000000, pid=5300, tid=9612
#
# JRE version: OpenJDK Runtime Environment Microsoft-22300 (16.0.1+9) (build 16.0.1+9)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-22300 (16.0.1+9, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C 0x0000000000000000
#
# 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.
#
--------------- T H R E A D ---------------
Current thread (0x000001738bf61790): JavaThread "Render thread" [_thread_in_native, id=9612, stack(0x0000004677500000,0x0000004677600000)]
Stack: [0x0000004677500000,0x0000004677600000], sp=0x00000046775fc5e8, free space=1009k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.lwjgl.system.JNI.invokePPPP(IIJJJJ)J+0
j org.lwjgl.glfw.GLFW.nglfwCreateWindow(IIJJJ)J+14
j org.lwjgl.glfw.GLFW.glfwCreateWindow(IILjava/lang/CharSequence;JJ)J+37
j dpq.<init>(Ldpr;Ldpn;Ldpd;Ljava/lang/String;Ljava/lang/String;)V+286
j enw.a(Ldpd;Ljava/lang/String;Ljava/lang/String;)Ldpq;+15
j dvo.<init>(Leex;)V+712
j net.minecraft.client.main.Main.main([Ljava/lang/String;)V+1211
v ~StubRoutines::call_stub
siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), data execution prevention violation at address 0x0000000000000000
Note that the Native Frames in the crash reports seem to vary:
Related issues
is duplicated by
Attachments
Comments


Experiencing the same issue.

Same thing for me. The 16.5 version of the game was working perfectly yesterday, with all of my current mods having no issue. Then today, Mojang automatically updated my Minecraft Launcher, and now the game doesn't work at all with no mods changed. Uninstalled and reinstalled minecraft but nothing worked.
We do not have enough information to find the cause of this issue.
Please go to your [minecraft data folder|https://minecrafthopper.net/help/finding-minecraft-data-folder/]
(click the link to learn how), and then locate a file with a name like hs_err_pid_1234.log
. Please attach that file to this bug report.
This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki


No such file as hs_err_pid_1234.log, but found all the crash reports with hs_err_pid.
Says the same thing over and over again:
Problematic frame:
C 0x0000000000000000
[media]Thank you. I've removed sensitive information from the crash log and reuploaded it as
[media].

I updated many things since posting this. Now it is saying
GLFW error 65542: WGL: The driver does not appear to support OpenGL
I've been chatting with NVIDIA and getting nowhere.
I've set Minecraft to use NVIDIA instead of the INTEL.
In order for it to work at all, I have to disable the NVIDIA graphics card.

I give up. I've spent about 15 hours trying to fix this!
Guess I will no longer be playing Minecraft. How do I get my money back for a defective product?

Lorraine Chocholka, the GLFW error 65542 is MC-128302. Verify if you have all the necessary requirements, and please contact the community support.

So I kept checking lots of things.
If anyone else has the problem of driver not supporting OpenGL, I figured it out myself what was wrong.
My monitor cable was plugged into a docking station, and that was plugged into my laptop.
I moved the cable to my laptop instead, and, voila, the game now works.
Even though I can play WoW and other games that way, Minecraft can NOT work through a docking station apparently.

I have a similar problem, but on a different frame:
[media]

@@unknown, I have deleted your attached JVM crash report because these crash reports contain sensitive data. Feel free to create a new private issue, then we can link the issues.
However, your crash report contained atio6axx.dll+0xd28ffb
as native frame which we have already covered (see bottom of description of this issue), so there is probably no need for a new report.

@Lorraine Chocholka I had the same problem. I don't have my PC plugged into a docking station. I only have my PC plugged into a charging plug, an external drive, and my mouse