I go onto my Minecraft and download 1.10 - it loads fine and quickly. Then I click onto a realm and it lets me in for 3-30 seconds then kicks me out and crashes the game.

What I expected to happen was...:
I could play on realms like usual and the new update wouldn't cause any trouble.

What actually happened was...:
I abruptly crashed my game and I can`t play with the update.

Steps to Reproduce:
1. Load up Minecraft 1.10 using Windows 8
2. Join any Realm
3. Wait and see if you are kicked out of the game.

It Came Up With This On My Launcher (the part "game output") :

Completely ignored arguments: [--nativeLauncherVersion, 301]
[20:10:26] [Client thread/INFO]: Setting user: Summerpanda04
[20:10:29] [Client thread/WARN]: Skipping bad option: lastServer:
[20:10:29] [Client thread/INFO]: LWJGL Version: 2.9.4
[20:10:29] [Client thread/INFO]: Reloading ResourceManager: Default
[20:10:31] [Sound Library Loader/INFO]: Starting up SoundSystem...
[20:10:31] [Thread-5/INFO]: Initializing LWJGL OpenAL
[20:10:31] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[20:10:31] [Thread-5/INFO]: OpenAL initialized.
[20:10:31] [Sound Library Loader/INFO]: Sound engine started
[20:10:33] [Client thread/INFO]: Created: 1024x512 textures-atlas
[20:10:39] [Client thread/INFO]: Realms library version == 1.9.0
[20:10:40] MCO Compatability 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=0x0000000019c1a9b5, pid=6976, tid=6960
   #
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+0x6a9b5]
   #
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\Leah\AppData\Roaming\.minecraft\hs_err_pid6976.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

And the attachment is the error report file mentioned in the text above.

Thankyou for taking the time to read this and I hope the information I have given has helped you figure out why this bug keeps on happening.