07:58:34.368
launcher
main
Preparing to launch minecraft client for 1.16.4
07:58:35.178
launcher
main
Checking installations.
07:58:35.188
launcher
main
Minecraft client 1.16.4 is ready to start.
07:58:35.188
launcher
main
Starting!
07:58:35.321
launcher
main
Using default game log configuration client-1.12.xml (outputs XML)
07:58:39.894
com.mojang.authlib.yggdrasil.YggdrasilAuthenticationService
Render thread
Environment: authHost='https://authserver.mojang.com', accountsHost='https://api.mojang.com', sessionHost='https://sessionserver.mojang.com', servicesHost='https://api.minecraftservices.com', name='PROD'
07:58:40.303
djz
Render thread
Setting user: TheDiamondPro_MC
07:58:40.928
djz
Render thread
Backend library: LWJGL version 3.2.2 build 10
07:58:42.899
launcher
main

#

1. A fatal error has been detected by the Java Runtime Environment:
   #
2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000000000000, pid=33176, tid=29048
   #
3. JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops)
5. Problematic frame:
6. C 0x0000000000000000
   #
7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
   #
8. An error report file with more information is saved as:
9. C:\Users\Taylor\AppData\Roaming\.minecraft\hs_err_pid33176.log
   #
10. If you would like to submit a bug report, please visit:
11. http://bugreport.java.com/bugreport/crash.jsp
12. The crash happened outside the Java Virtual Machine in native code.
13. See problematic frame for where to report the bug.
    #
    07:58:42.899
    monitor
    Process Monitor
    Process crashed with exit code 1