Logging onto multiplayer on 1.9 closes game and opens launcher

Put the summary of the bug you're having here

What I expected to happen was...:
I would be able to log onto multiplayer without problems.

What actually happened was...:
My MC 1.9 closed and opened the launcher instantly when it logged on.

Steps to Reproduce:
1. Enter Minecraft 1.9 - No pre-releases!
2. Go to either Multiplayer or Minecraft Realms if you have any servers or Realms.
3. Log in to what ever it was and wait for a crash.

This is what all the text was for the launcher log...

Completely ignored arguments: [--nativeLauncherVersion, 301]
[20:56:11] [Client thread/INFO]: Setting user: Reapeageddon
[20:56:11] [Client thread/INFO]: (Session ID is <censored>)
[20:56:13] [Client thread/INFO]: LWJGL Version: 2.9.4
[20:56:13] [Client thread/INFO]: Reloading ResourceManager: Default
[20:56:14] [Sound Library Loader/INFO]: Starting up SoundSystem...
[20:56:14] [Thread-5/INFO]: Initializing LWJGL OpenAL
[20:56:14] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[20:56:15] [Thread-5/INFO]: OpenAL initialized.
[20:56:15] [Sound Library Loader/INFO]: Sound engine started
[20:56:16] [Client thread/INFO]: Created: 1024x512 textures-atlas
[20:56:21] [Client thread/INFO]: Realms library version == 1.8.4
[20:56:21] [MCO Availability Checker #1/INFO]: Realms is available for this user
#

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

2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffe0972e33c, pid=452, tid=8244
   #

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 [ig75icd64.dll+0x55e33c]
   #

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\JP\AppData\Roaming\.minecraft\hs_err_pid452.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

If you know a way to fix this, tell me on my account if possible.