-
Bug
-
Resolution: Duplicate
-
None
-
Minecraft 1.9
-
Windows 10, Lastest Java Version
-
Unconfirmed
When ever I load a 1.9 world up it immediately crashes. Issue was fix by using Mark Barrow's Strategy: "Instead of using the minecraft icon on my desktop, i go to my files. Windows (c: ). Click program files (x86). Click minecraft folder. click game. drag the java launcher out. Click that. MINECRAFT WORKS!" Thank You so much Mark Barrow!
What I expected to happen was...:
The world to load in.
What actually happened was...:
Upon starting up the world the game will crash.
Steps to Reproduce:
1. Start or create a new world in version 1.9
2. Wait 1-5 seconds
3. As a result the game will crash
Game Output I got after crash:
Completely ignored arguments: [--nativeLauncherVersion, 301]
[16:44:43] [Client thread/INFO]: Setting user: ThatGuyBen14
[16:44:43] [Client thread/INFO]: (Session ID is token:6e451cc0100c470eb15d8437aa7a607d:0a4560845d2d4175b31c15a2bba11b49)
[16:44:44] [Client thread/INFO]: LWJGL Version: 2.9.4
[16:44:44] [Client thread/INFO]: Reloading ResourceManager: Default
[16:44:45] [Sound Library Loader/INFO]: Starting up SoundSystem...
[16:44:45] [Thread-5/INFO]: Initializing LWJGL OpenAL
[16:44:45] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[16:44:45] [Thread-5/INFO]: OpenAL initialized.
[16:44:45] [Sound Library Loader/INFO]: Sound engine started
[16:44:46] [Client thread/INFO]: Created: 1024x512 textures-atlas
[16:44:53] [Server thread/INFO]: Starting integrated minecraft server version 1.9
[16:44:53] [Server thread/INFO]: Generating keypair
[16:44:54] [Server thread/INFO]: Preparing start region for level 0
[16:44:55] [Server thread/INFO]: Preparing spawn area: 8%
[16:44:56] [Server thread/INFO]: Preparing spawn area: 16%
[16:44:57] [Server thread/INFO]: Preparing spawn area: 26%
[16:44:58] [Server thread/INFO]: Preparing spawn area: 35%
[16:44:59] [Server thread/INFO]: Preparing spawn area: 45%
[16:45:00] [Server thread/INFO]: Preparing spawn area: 57%
[16:45:01] [Server thread/INFO]: Preparing spawn area: 67%
[16:45:02] [Server thread/INFO]: Preparing spawn area: 79%
[16:45:03] [Server thread/INFO]: Preparing spawn area: 90%
[16:45:04] [Server thread/INFO]: Changing view distance to 12, from 10
[16:45:04] [Server thread/INFO]: ThatGuyBen14[local:E:b45eb04f] logged in with entity id 250 at (160.5, 76.0, 287.5)
[16:45:04] [Server thread/INFO]: ThatGuyBen14 joined the game
[16:45:09] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5032ms behind, skipping 100 tick(s)
#
- A fatal error has been detected by the Java Runtime Environment:
# - EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffcb7f96b37, pid=12532, tid=3544
# - 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 [ig8icd64.dll+0x16b37]
# - 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\Ben\AppData\Roaming\.minecraft\hs_err_pid12532.log
# - If you would like to submit a bug report, please visit:
- http://bugreport.sun.com/bugreport/crash.jsp
- 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
- duplicates
-
- Resolved
[MC-98652] 1.9 worlds will immediately crash after starting the world up *FIXED*
The issue has to do with the drivers because the Java Virtual Machine is crashing while using them. This issue is entirely outside of the game client. There have been several proposed work-arounds (including the one you proposed). Please note as well, just because your drivers are 100% up to date does not mean that the most recent drivers are perfect. There have been several cases of new driver releases that break various things.
It's a combination of the Java version and the intel drivers.
Mojang is looking at a way to get around this, but you have to understand that it's not caused by their software.
My graphics card is 100% up to date and it still crashes. My graphics card works with all other versions of minecraft except 1.9 so I an't updating till you fix this SHIT!
Hi All,
As you know I too was having this issue on a brand new computer.. So being as Tech support isnt helping us thank goodness for some of us with Tech Savvyness. On the minecraft main page (minecraft.net) it does give you a chance to go back.. however I just updated my java player and voila I am able to play on 1.9 .. So try that if not try the older version. It's actually my kiddos that play but I thought this would be helpful to all.
Craft On!
db
Cube the third. I have a BRAND NEW PURCHASED LAST WEEK HP laptop with the Intel I7 processor with driver version 20.XXXX. Another mod said the drivers need to be downgraded to version 15.xxxx. The I7 processor doesnt support version 15.xxx so therefore cannot be downgraded. There is nothing "BROKEN" about my driver i dont know why I keep seeing this excuse. This game is simply not playable on new computers and thats not right.
Yea that's the only thing that works. The game itself is glitchy but at least it's playable
You are wrong. Not only do I have a brand new computer purchased less than a week ago but I've manually updated all the drivers. Stop blaming the computers and look at the game itself. The previous version worked fine
All of these reports are duplicates of MC-32606. Caused by broken/outdated intel graphics drivers. See that report for details.
Yeah, I noticed that too. Funny thing is, the crash log is the same! There is currently no solution to this bug even if it looks like there is. Can't believe Mojang broke Minecraft just before release! Seems crazy!