When i try to play on a server in minecraft 1.9 it always takes me back to the launcher on a page called game output.

please provide the game output

Mine is doing it as well - Windows 10 pro on a Surface 4pro i7. Worked fine before the update to 1.9 that it just did when I logged in (been offline for 2 weeks). I see my MC realm and people are on it playing, mine gets to "downloading terrain" and then exits game and goes to game output tab on launcher window with the below info:

Completely ignored arguments: [--nativeLauncherVersion, 301]
[10:17:44] [Client thread/INFO]: Setting user: Amdrocks
[10:17:44] [Client thread/INFO]: (Session ID is <censored>)
[10:17:45] [Client thread/INFO]: LWJGL Version: 2.9.4
[10:17:46] [Client thread/INFO]: Reloading ResourceManager: Default
[10:17:46] [Sound Library Loader/INFO]: Starting up SoundSystem...
[10:17:46] [Thread-5/INFO]: Initializing LWJGL OpenAL
[10:17:46] [Thread-5/INFO]: (The LWJGL binding of OpenAL.  For more information, see http://www.lwjgl.org)
[10:17:46] [Thread-5/INFO]: OpenAL initialized.
[10:17:47] [Sound Library Loader/INFO]: Sound engine started
[10:17:47] [Client thread/INFO]: Created: 1024x512 textures-atlas
[10:17:55] [Client thread/INFO]: Realms library version == 1.8.6
[10:17:56] [MCO Compatability Checker #1/INFO]: Realms is available for this user
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fff235e6557, pid=3192, tid=6684
#
# 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  [ig9icd64.dll+0x16557]
#
# 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\Jeremy\AppData\Roaming\.minecraft\hs_err_pid3192.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

broken/outdated intel drivers, follow the instructions provided at MC-32606 to fix your issue

Thank you FVbico - I only did the 2gb memory allocate and VBOs - ON (vsync was already on) and that cleared it up!