Completely ignored arguments: [--nativeLauncherVersion, 301]
[19:33:12] [Client thread/INFO]: Setting user: M1GHTYJOEL
[19:33:12] [Client thread/INFO]: (Session ID is <censored>)
[19:33:14] [Client thread/INFO]: LWJGL Version: 2.9.4
[19:33:15] [Client thread/INFO]: Reloading ResourceManager: Default
[19:33:32] [Sound Library Loader/INFO]: Starting up SoundSystem...
[19:33:33] [Thread-5/INFO]: Initializing LWJGL OpenAL
[19:33:33] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
AL lib: (EE) MMDevApiOpenPlayback: Device init failed: 0x80004005
AL lib: (EE) MMDevApiOpenPlayback: Device init failed: 0x80004005
[19:33:33] [Thread-5/ERROR]: Error in class 'LibraryLWJGLOpenAL'
[19:33:33] [Thread-5/ERROR]: Unable to initialize OpenAL. Probable cause: OpenAL not supported.
[19:33:33] [Thread-5/WARN]: ERROR MESSAGE:
[19:33:33] [Thread-5/INFO]: Could not locate OpenAL library.
[19:33:33] [Thread-5/WARN]: STACK TRACE:
[19:33:33] [Thread-5/INFO]: org.lwjgl.openal.AL.create(AL.java:156)
[19:33:33] [Thread-5/INFO]: org.lwjgl.openal.AL.create(AL.java:102)
[19:33:33] [Thread-5/INFO]: org.lwjgl.openal.AL.create(AL.java:206)
[19:33:33] [Thread-5/INFO]: paulscode.sound.libraries.LibraryLWJGLOpenAL.init(LibraryLWJGLOpenAL.java:164)
[19:33:33] [Thread-5/INFO]: paulscode.sound.SoundSystem.CommandNewLibrary(SoundSystem.java:1576)
[19:33:33] [Thread-5/INFO]: paulscode.sound.SoundSystem.CommandQueue(SoundSystem.java:2572)
[19:33:33] [Thread-5/INFO]: paulscode.sound.CommandThread.run(CommandThread.java:121)
[19:33:33] [Sound Library Loader/WARN]: ERROR MESSAGE:
[19:33:33] [Sound Library Loader/INFO]: Could not locate OpenAL library.
[19:33:33] [Sound Library Loader/INFO]: Starting up SoundSystem...
[19:33:33] [Thread-7/INFO]: Switching to No Sound
[19:33:33] [Thread-7/INFO]: (Silent Mode)
[19:33:34] [Sound Library Loader/INFO]: Sound engine started
[19:33:35] [Client thread/INFO]: Created: 1024x512 textures-atlas
[19:33:47] [Client thread/INFO]: Connecting to us.mineplex.com, 25565
[19:34:06] [Client thread/INFO]: Connecting to us.mineplex.com, 25565
[19:34:28] [Server thread/INFO]: Starting integrated minecraft server version 1.9
[19:34:28] [Server thread/INFO]: Generating keypair
[19:34:29] [Server thread/INFO]: Preparing start region for level 0
[19:34:30] [Server thread/INFO]: Preparing spawn area: 5%
[19:34:30] [pool-3-thread-1/ERROR]: Couldn't get trial availability
com.mojang.realmsclient.exception.RealmsServiceException: Could not connect to Realms: connect timed out
at com.mojang.realmsclient.client.RealmsClient.execute(RealmsClient.java:438) ~[realms-1.8.6.jar:1.8.6]
at com.mojang.realmsclient.client.RealmsClient.trialAvailable(RealmsClient.java:368) ~[realms-1.8.6.jar:1.8.6]
at com.mojang.realmsclient.gui.RealmsDataFetcher$TrialAvailabilityTask.getTrialAvailable(RealmsDataFetcher.java:263) [realms-1.8.6.jar:1.8.6]
at com.mojang.realmsclient.gui.RealmsDataFetcher$TrialAvailabilityTask.run(RealmsDataFetcher.java:254) [realms-1.8.6.jar:1.8.6]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_25]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_25]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_25]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_25]
[19:34:31] [Server thread/INFO]: Preparing spawn area: 10%
[19:34:32] [Server thread/INFO]: Preparing spawn area: 16%
[19:34:33] [Server thread/INFO]: Preparing spawn area: 22%
[19:34:34] [Server thread/INFO]: Preparing spawn area: 29%
[19:34:35] [Server thread/INFO]: Preparing spawn area: 35%
[19:34:36] [Server thread/INFO]: Preparing spawn area: 43%
[19:34:37] [Server thread/INFO]: Preparing spawn area: 52%
[19:34:38] [Server thread/INFO]: Preparing spawn area: 60%
[19:34:39] [Server thread/INFO]: Preparing spawn area: 68%
[19:34:40] [Server thread/INFO]: Preparing spawn area: 77%
[19:34:41] [Server thread/INFO]: Preparing spawn area: 86%
[19:34:42] [Server thread/INFO]: Preparing spawn area: 95%
[19:34:43] [Server thread/INFO]: M1GHTYJOEL[local:E:fce02658] logged in with entity id 131 at (-77.5, 92.0, 248.5)
[19:34:43] [Server thread/INFO]: M1GHTYJOEL joined the game
[19:34:43] [Server thread/INFO]: Changing view distance to 8, from 10
#
A fatal error has been detected by the Java Runtime Environment:
#EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffad369628c, pid=11572, tid=6824
#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+0x55628c]
#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\Luis\AppData\Roaming\.minecraft\hs_err_pid11572.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.
#
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Linked issues
Comments 4
This is the same thing that happens to me, I have reported it to Java, but it only happens to me in 1.9, in 1.8 I'm fine. It happens everytime. Right before I spawn into the world. Sometimes I can see my item bar, but most of the time just the blue sky.
Mitch, I think the crash is caused by a bad item ID or plugin. You should know that Mineplex is a modded server and is not compatible with 1.9. You should be playing it in versions compatible with it, which is 1.8 right now as there is no MCP for 1.9. (That MCP is half a year away.)
Duplicate of MC-32606. This issue is caused by broken or outdated Intel graphics drivers. Please see that report for details.
This should be handled by Java, though usually those crashes are rare. Can you try to recreate it again?