Well I can't exactly describe it. I got a new computer, a Latitude D630 but when I downloaded MC and logged in before pressing play it did the normal thing and pulled up the usual Mojang sign but it escaped itself and it went back to the page.

It said this:

Completely ignored arguments: [--nativeLauncherVersion, 307]
[16:44:26] [Client thread/INFO]: Setting user: TheMagesticOreo
[16:44:29] [Client thread/INFO]: LWJGL Version: 2.9.4
[16:44:30] [Client thread/INFO]: Reloading ResourceManager: Default
[16:44:32] [Sound Library Loader/INFO]: Starting up SoundSystem...
[16:44:32] [Thread-5/INFO]: Initializing LWJGL OpenAL
[16:44:32] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[16:44:35] [Client thread/INFO]: Created: 1024x512 textures-atlas
[16:44:35] [Thread-5/INFO]: OpenAL initialized.
[16:44:35] [Sound Library Loader/INFO]: Sound engine started
#

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

2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005b8255ec, pid=2544, tid=1340
   #

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 [ig4dev64.dll+0x55ec]
   #

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\owner\AppData\Roaming\.minecraft\hs_err_pid2544.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