George T. Rat
Assigned
Reported
Comments
I had this same problem. I am running Windows 8.1. The launcher worked fine, but when I tried to enter a world, the game crashed before the world opened. I found this error message in the launcher:
[18:11:05 FATAL]: Fatal error launching game. Report this to http://bugs.mojang.com please!
java.io.FileNotFoundException: File 'C:\Users\PK\AppData\Roaming\.minecraft\assets\indexes\legacy.json' does not exist
at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:299) ~[launcher.jar:1.6.61]
at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1711) ~[launcher.jar:1.6.61]
at net.minecraft.launcher.Launcher.cleanupOrphanedAssets(Launcher.java:254) ~[launcher.jar:1.6.61]
at net.minecraft.launcher.Launcher.performCleanups(Launcher.java:496) ~[launcher.jar:1.6.61]
at net.minecraft.launcher.game.MinecraftGameRunner.launchGame(MinecraftGameRunner.java:231) ~[launcher.jar:1.6.61]
at com.mojang.launcher.game.runner.AbstractGameRunner.onDownloadJobFinished(AbstractGameRunner.java:186) [launcher.jar:1.6.61]
at com.mojang.launcher.updater.download.DownloadJob.popAndDownload(DownloadJob.java:122) [launcher.jar:1.6.61]
at com.mojang.launcher.updater.download.DownloadJob.access$000(DownloadJob.java:12) [launcher.jar:1.6.61]
at com.mojang.launcher.updater.download.DownloadJob$1.run(DownloadJob.java:86) [launcher.jar:1.6.61]
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:1.8.0_45]
at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:1.8.0_45]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_45]
[18:11:46 ERROR]: Game ended with bad state (exit code 255)
[18:11:46 INFO]: Ignoring visibility rule and showing launcher due to a game crash
[18:11:46 INFO]: Deleting C:\Users\PK\AppData\Roaming\.minecraft\versions\1.10\1.10-natives-378347114418185
[18:11:46 WARN]: Couldn't delete C:\Users\PK\AppData\Roaming\.minecraft\versions\1.10\1.10-natives-378347114418185 - scheduling for deletion upon exit
When I went into a different world, the world opened, but crashed soon afterwards. This time I found the following error message:
[18:28:39] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4749ms behind, skipping 94 tick(s)
#
A fatal error has been detected by the Java Runtime Environment:
#EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x58960b66, pid=5496, tid=5340
#JRE version: Java(TM) SE Runtime Environment (8.0_45-b15) (build 1.8.0_45-b15)
Java VM: Java HotSpot(TM) Client VM (25.45-b02 mixed mode windows-x86 )
Problematic frame:
C [ig75icd32.dll+0x60b66]
#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\PK\AppData\Roaming\.minecraft\hs_err_pid5496.log
#If you would like to submit a bug report, please visit:
The crash happened outside the Java Virtual Machine in native code.
See problematic frame for where to report the bug.
#
AL lib: (EE) alc_cleanup: 1 device not closed
Java HotSpot(TM) Client VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
I'm going to attach screenshots of these two messages, in case the formatting makes them difficult to read.
I'm not sure what this means, but If there are anymore details that would help find the problem, I would be happy to provide them.
I don't think this is a duplicate. Even when playing with older versions, it still doesn't work. My graphics driver is updated. Also, other people an a forum at http://www.minecraftforum.net/forums/support/unmodified-minecraft-client/2688875-minecraft-keeps-crashing also were having this problem, and they also found that the driver wasn't the problem. Both them and I found the only way to fix the problem was turn VBOs off, which is the opposite of what was recommended for MC 32606. Also, this problem seems to be specific to 1.10, considering the number of people I have seen who haven't had this problem until its release.