1.9 worlds will immediately crash after starting the world up *FIXED*

Incomplete without a crash report from ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/finding-minecraft-data-folder]). Please attach it so that we can diagnose your issue.

For technical support please use the Mojang Support Center.

I'm having the exact same problem. So is my dad. I've attached my crash report.

It's confirmed. I was just going to report this as a bug. I even got a screenshot of my java pathways. here is my crash http://pastebin.com/0bFVZ0k9
here is my java path http://imgur.com/lV2xGrT
this is the actual file http://pastebin.com/pvuyf9cT
and this is it's name without the quotes "hs_err_pid3932"
here is where the crash is stored : C:\Users\jjred\AppData\Roaming\.minecraft\hs_err_pid3932.log
it's not a regular crash it's a java error. what the heck did mojang do to break minecraft this far for 1.9?

Here is my crash log too ...
Completely ignored arguments: [--nativeLauncherVersion, 301]
[18:03:37] [Client thread/INFO]: Setting user: DareBear08
[18:03:37] [Client thread/INFO]: (Session ID is token:7ee3a7b8ed7941c482b1f101ffe7cb76:eb7799a3e5284d92a8029b8d304e7146)
[18:03:37] [Client thread/INFO]: LWJGL Version: 2.9.4
[18:03:38] [Client thread/INFO]: Reloading ResourceManager: Default
[18:03:38] [Sound Library Loader/INFO]: Starting up SoundSystem...
[18:03:38] [Thread-5/INFO]: Initializing LWJGL OpenAL
[18:03:38] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[18:03:38] [Thread-5/INFO]: OpenAL initialized.
[18:03:38] [Sound Library Loader/INFO]: Sound engine started
[18:03:39] [Client thread/INFO]: Created: 1024x512 textures-atlas
[18:03:43] [Server thread/INFO]: Starting integrated minecraft server version 1.9
[18:03:43] [Server thread/INFO]: Generating keypair
[18:03:43] [Server thread/INFO]: Preparing start region for level 0
[18:03:44] [Server thread/INFO]: Preparing spawn area: 67%
[18:03:44] [Server thread/INFO]: Changing view distance to 12, from 10
[18:03:45] [Server thread/INFO]: DareBear08[local:E:cd5e9785] logged in with entity id 1135 at (275.40143734126246, 69.0, 264.7114420164296)
[18:03:45] [Server thread/INFO]: DareBear08 joined the game
[18:03:45] [Server thread/INFO]: Saving and pausing game...
[18:03:45] [Server thread/INFO]: Saving chunks for level 'MOO!'/Overworld
[18:03:45] [Server thread/INFO]: Saving chunks for level 'MOO!'/Nether
[18:03:45] [Server thread/INFO]: Saving chunks for level 'MOO!'/The End
#

1. A fatal error has been detected by the Java Runtime Environment:
   #

2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff91fd06637, pid=6128, tid=4640
   #

3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)

5. Problematic frame:

6. C [ig9icd64.dll+0x16637]
   #

7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
   #

8. An error report file with more information is saved as:

9. C:\Users\Kids\AppData\Roaming\.minecraft\hs_err_pid6128.log
   #

10. If you would like to submit a bug report, please visit:

11. http://bugreport.sun.com/bugreport/crash.jsp

12. The crash happened outside the Java Virtual Machine in native code.

13. 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

I have the same problem this is MY game output
Completely ignored arguments: [--nativeLauncherVersion, 301]
[20:32:04] [Client thread/INFO]: Setting user: pixiephoebe2004
[20:32:04] [Client thread/INFO]: (Session ID is token:95954f1f064e4880a7579a25d2e87372:df0c24149e114a91ad52522b43941099)
[20:32:05] [Client thread/INFO]: LWJGL Version: 2.9.4
[20:32:06] [Client thread/INFO]: Reloading ResourceManager: Default
[20:32:07] [Sound Library Loader/INFO]: Starting up SoundSystem...
[20:32:07] [Thread-5/INFO]: Initializing LWJGL OpenAL
[20:32:07] [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
[20:32:07] [Thread-5/ERROR]: Error in class 'LibraryLWJGLOpenAL'
[20:32:07] [Thread-5/ERROR]: Unable to initialize OpenAL. Probable cause: OpenAL not supported.
[20:32:07] [Thread-5/WARN]: ERROR MESSAGE:
[20:32:07] [Thread-5/INFO]: Could not locate OpenAL library.
[20:32:07] [Thread-5/WARN]: STACK TRACE:
[20:32:07] [Thread-5/INFO]: org.lwjgl.openal.AL.create(AL.java:156)
[20:32:07] [Thread-5/INFO]: org.lwjgl.openal.AL.create(AL.java:102)
[20:32:07] [Thread-5/INFO]: org.lwjgl.openal.AL.create(AL.java:206)
[20:32:07] [Thread-5/INFO]: paulscode.sound.libraries.LibraryLWJGLOpenAL.init(LibraryLWJGLOpenAL.java:164)
[20:32:07] [Thread-5/INFO]: paulscode.sound.SoundSystem.CommandNewLibrary(SoundSystem.java:1576)
[20:32:07] [Thread-5/INFO]: paulscode.sound.SoundSystem.CommandQueue(SoundSystem.java:2572)
[20:32:07] [Thread-5/INFO]: paulscode.sound.CommandThread.run(CommandThread.java:121)
[20:32:07] [Sound Library Loader/WARN]: ERROR MESSAGE:
[20:32:07] [Sound Library Loader/INFO]: Could not locate OpenAL library.
[20:32:07] [Sound Library Loader/INFO]: Starting up SoundSystem...
[20:32:07] [Thread-7/INFO]: Switching to No Sound
[20:32:07] [Thread-7/INFO]: (Silent Mode)
[20:32:08] [Sound Library Loader/INFO]: Sound engine started
[20:32:08] [Client thread/INFO]: Created: 1024x512 textures-atlas
[20:32:13] [Client thread/ERROR]: Can't ping Minecraftparty.com: Internal Exception: java.io.IOException: An existing connection was forcibly closed by the remote host
[20:32:15] [Client thread/INFO]: Connecting to play.minecats.com, 25565
[20:32:16] [Client thread/INFO]: [CHAT] Already connecting to this server!
[20:32:49] [Client thread/ERROR]: Can't ping Minecraftparty.com: Internal Exception: java.io.IOException: An existing connection was forcibly closed by the remote host
[20:32:53] [Client thread/INFO]: Connecting to play.minecats.com, 25565
[20:32:54] [Client thread/INFO]: [CHAT] Hello, pixiephoebe2004. Welcome to MineCats!
[20:32:54] [Client thread/INFO]: [CHAT] [EchoPet] The Pet Selector has been added to your inventory.
[20:32:54] [Client thread/INFO]: [CHAT] [EchoPet] You need to be a Champion to use the Pets.
[20:32:54] [Client thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_25]
at g.a(SourceFile:46) [1.9.jar:?]
at bcf.av(SourceFile:954) [1.9.jar:?]
at bcf.a(SourceFile:392) [1.9.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [1.9.jar:?]
Caused by: java.lang.NullPointerException
at fo.a(SourceFile:74) ~[1.9.jar:?]
at bks.a(SourceFile:462) ~[1.9.jar:?]
at fo.a(SourceFile:68) ~[1.9.jar:?]
at fo.a(SourceFile:15) ~[1.9.jar:?]
at fh$1.run(SourceFile:13) ~[1.9.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_25]
at g.a(SourceFile:45) ~[1.9.jar:?]
... 3 more
[20:32:54] [Client thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_25]
at g.a(SourceFile:46) [1.9.jar:?]
at bcf.av(SourceFile:954) [1.9.jar:?]
at bcf.a(SourceFile:392) [1.9.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [1.9.jar:?]
Caused by: java.lang.NullPointerException
at fo.a(SourceFile:74) ~[1.9.jar:?]
at bks.a(SourceFile:462) ~[1.9.jar:?]
at fo.a(SourceFile:68) ~[1.9.jar:?]
at fo.a(SourceFile:15) ~[1.9.jar:?]
at fh$1.run(SourceFile:13) ~[1.9.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_25]
at g.a(SourceFile:45) ~[1.9.jar:?]
... 3 more
[20:32:54] [Client thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_25]
at g.a(SourceFile:46) [1.9.jar:?]
at bcf.av(SourceFile:954) [1.9.jar:?]
at bcf.a(SourceFile:392) [1.9.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [1.9.jar:?]
Caused by: java.lang.NullPointerException
at fo.a(SourceFile:74) ~[1.9.jar:?]
at bks.a(SourceFile:462) ~[1.9.jar:?]
at fo.a(SourceFile:68) ~[1.9.jar:?]
at fo.a(SourceFile:15) ~[1.9.jar:?]
at fh$1.run(SourceFile:13) ~[1.9.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_25]
at g.a(SourceFile:45) ~[1.9.jar:?]
... 3 more
[20:32:54] [Client thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_25]
at g.a(SourceFile:46) [1.9.jar:?]
at bcf.av(SourceFile:954) [1.9.jar:?]
at bcf.a(SourceFile:392) [1.9.jar:?]
at net.minecraft.client.main.Main.main(SourceFile:124) [1.9.jar:?]
Caused by: java.lang.NullPointerException
at fo.a(SourceFile:74) ~[1.9.jar:?]
at bks.a(SourceFile:462) ~[1.9.jar:?]
at fo.a(SourceFile:68) ~[1.9.jar:?]
at fo.a(SourceFile:15) ~[1.9.jar:?]
at fh$1.run(SourceFile:13) ~[1.9.jar:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_25]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_25]
at g.a(SourceFile:45) ~[1.9.jar:?]
... 3 more
#

1. A fatal error has been detected by the Java Runtime Environment:
   #

2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffbbbcb6b37, pid=7744, tid=7188
   #

3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)

5. Problematic frame:

6. C [ig8icd64.dll+0x16b37]
   #

7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
   #

8. An error report file with more information is saved as:

9. C:\Users\phoeb\AppData\Roaming\.minecraft\hs_err_pid7744.log
   #

10. If you would like to submit a bug report, please visit:

11. http://bugreport.sun.com/bugreport/crash.jsp

12. The crash happened outside the Java Virtual Machine in native code.

13. 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

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

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!

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.

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.

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!