Minecraft Forums

Every time I load Minecraft the launcher starts up fine. Then when I click play and the game begins to load. Once it hits the Mojang title screen the game stops and reverts back to the launcher. I've checked the Development Console and it tells me Java has detected a fatal error bye the runtime enviroment.

[04:34:44 INFO]: Client> # A fatal error has been detected by the Java Runtime Environment:
[04:34:44 INFO]: Client> #
[04:34:44 INFO]: Client> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x4cef3ed8, pid=174996, tid=175052
[04:34:44 INFO]: Client> #
[04:34:44 INFO]: Client> # JRE version: 6.0_45-b06
[04:34:44 INFO]: Client> # Java VM: Java HotSpot(TM) Client VM (20.45-b01 mixed mode windows-x86 )
[04:34:44 INFO]: Client> # Problematic frame:
[04:34:44 INFO]: Client> # C [ig4dev32.dll+0x3ed8]
[04:34:44 INFO]: Client> #
[04:34:44 INFO]: Client> # An error report file with more information is saved as:
[04:34:44 INFO]: Client> # C:\Users\Utah\AppData\Roaming\.minecraft\hs_err_pid174996.log
[04:34:44 INFO]: Client> #
[04:34:44 INFO]: Client> # If you would like to submit a bug report, please visit:
[04:34:44 INFO]: Client> # http://java.sun.com/webapps/bugreport/crash.jsp
[04:34:44 INFO]: Client> # The crash happened outside the Java Virtual Machine in native code.
[04:34:44 INFO]: Client> # See problematic frame for where to report the bug.
[04:34:44 INFO]: Client> #
[04:34:44 INFO]: Client> AL lib: (EE) alc_cleanup: 1 device not closed
[04:34:44 ERROR]: Game ended with bad state (exit code 1)
[04:34:44 INFO]: Ignoring visibility rule and showing launcher due to a game crash
[04:34:44 INFO]: Deleting C:\Users\Utah\AppData\Roaming\.minecraft\versions\1.7.10\1.7.10-natives-50715559905798
[04:34:44 WARN]: Couldn't delete C:\Users\Utah\AppData\Roaming\.minecraft\versions\1.7.10\1.7.10-natives-50715559905798 - scheduling for deletion upon exit

C [ig4dev32.dll+0x3ed8]

You have an Intel Series 4 graphics chip set that can't run any MC version newer than 1.7.2

See http://hopper.minecraft.net/help/references/intel-4-series-chipsets/

Note that the workaround posted there is hit or miss at best, and I would be reluctant to trust a driver of unknown provenance.