I created a new world as soon as I found out that 1.9 had been released, and spawned next to a village. I started playing arround with the new combat mechanics and the spectral arrows... I got killed a couple of times, but oh well... Anyways, When I got killed the third time, I looked up to the village and everything glitched out. Red panels and weird streaks filled my screen, but when I looked away, It got fixed. I'll attach screenshots.
I have no idea if this was Minecraft or my computer, but I'll post it just in case it's Minecraft's. I was facing positive x when the glitch happened. Dunno if that matters.
Linked issues
Attachments
Comments 2
I deleted the world sadly, but when I created a new one, the same thing happened. But this time every world crashes when I open it.
Completely ignored arguments: [--nativeLauncherVersion, 301]
[12:24:02] [Client thread/INFO]: Setting user: Rojos
[12:24:02] [Client thread/INFO]: (Session ID is <censored>)
[12:24:03] [Client thread/INFO]: LWJGL Version: 2.9.4
[12:24:03] [Client thread/INFO]: Reloading ResourceManager: Default, faithful32pack.zip
[12:24:04] [Sound Library Loader/INFO]: Starting up SoundSystem...
[12:24:04] [Thread-5/INFO]: Initializing LWJGL OpenAL
[12:24:04] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[12:24:04] [Thread-5/INFO]: OpenAL initialized.
[12:24:04] [Sound Library Loader/INFO]: Sound engine started
[12:24:05] [Client thread/INFO]: Created: 2048x1024 textures-atlas
[12:24:18] [Server thread/INFO]: Starting integrated minecraft server version 1.9
[12:24:18] [Server thread/INFO]: Generating keypair
[12:24:19] [Server thread/INFO]: Preparing start region for level 0
[12:24:20] [Server thread/INFO]: Preparing spawn area: 10%
[12:24:21] [Server thread/INFO]: Preparing spawn area: 22%
[12:24:22] [Server thread/INFO]: Preparing spawn area: 34%
[12:24:23] [Server thread/INFO]: Preparing spawn area: 46%
[12:24:24] [Server thread/INFO]: Preparing spawn area: 58%
[12:24:25] [Server thread/INFO]: Preparing spawn area: 70%
[12:24:26] [Server thread/INFO]: Preparing spawn area: 84%
[12:24:27] [Server thread/INFO]: Changing view distance to 2, from 10
[12:24:27] [Server thread/INFO]: Rojos[local:E:37e218e7] logged in with entity id 217 at (194.5, 86.0, 126.5)
[12:24:27] [Server thread/INFO]: Rojos joined the game
#
A fatal error has been detected by the Java Runtime Environment:
#EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff8b059deac, pid=5016, tid=7636
#JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
Problematic frame:
C [ig75icd64.dll+0x55deac]
#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\Santiago\AppData\Roaming\.minecraft\hs_err_pid5016.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) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Thank you for your report.
However, your ticket has been resolved as awaiting response.
We currently do not have enough information to troubleshoot your issue.
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report (
[minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/finding-minecraft-data-folder]) here.Your report will be reopened or properly resolved as soon as we receive this information.