-
Bug
-
Resolution: Duplicate
-
None
-
2.1.5963-2.1.5969 (Stable), 1.6.93 (legacy), 2.1.7660 (Windows Beta)
-
Windows 10 64 bit
Java version 8 update 238
-
Unconfirmed
Minecraft use to run fine and all of a sudden it stopped working and constantly pops up with a crash report. I changed the version of the launcher to be able to get this message because I couldn't open the crash report on the latest version.
Completely ignored arguments: [--nativeLauncherVersion, 601, --nativeLauncherVersion, 601]
[13:48:08] [Client thread/INFO]: Setting user: Creeper_Josie
[13:48:13] [Client thread/INFO]: LWJGL Version: 3.2.2 build 10
#
- A fatal error has been detected by the Java Runtime Environment:
# - EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006313b665, pid=9024, tid=10604
# - JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
- Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops)
- Problematic frame:
- C [atio6axx.dll+0xffb665]
# - Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
# - An error report file with more information is saved as:
- C:\Users\Josie\AppData\Roaming\.minecraft\hs_err_pid9024.log
# - If you would like to submit a bug report, please visit:
- http://bugreport.java.com/bugreport/crash.jsp
- The crash happened outside the Java Virtual Machine in native code.
- See problematic frame for where to report the bug.
#
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
- duplicates
-
MC-105853 JRE Fatal Error - atio6axx.dll+0x1f80ea0
- Resolved