Minecraft is too easy fatal error has been detected

Question

Hallo zusammen
Ich spiele die Mincraftmod "Minecraft is too easy" seit einiger Zeit. Bis heute Nacht problemlos. Jetzt startet es nicht mehr und gibt mir einen report.
Ich wäre um jede Hilfe oder Info sehr dankbar.

2014-07-28 23:27:53 [CLIENT] [INFO] Setting user: frizzilina
2014-07-28 23:27:53 [CLIENT] [INFO] (Session ID is token:ce29fcf8826743229ec39bd2df7406d6:bffd5fd45348457885d64566a27dd3c4)
2014-07-28 23:27:55 [CLIENT] [INFO] LWJGL Version: 2.9.0
2014-07-28 23:27:56 [CLIENT] [INFO] Reloading ResourceManager: Default, MITE Resource Pack 1.6.4.zip
SoundsMITE: Loading sounds... [ok]

Starting up SoundSystem...
Initializing LWJGL OpenAL
(The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
OpenAL initialized.

2014-07-28 23:28:08 [SERVER] [INFO] Starting integrated minecraft server version 1.6.4
2014-07-28 23:28:08 [SERVER] [INFO] Generating keypair
2014-07-28 23:28:10 [SERVER] [INFO] Preparing start region for level 0
2014-07-28 23:28:11 [SERVER] [INFO] Preparing spawn area: 34%
2014-07-28 23:28:12 [SERVER] [INFO] Preparing spawn area: 89%
2014-07-28 23:28:12 [SERVER] [INFO] frizzilina passed integrity check
loading single player
2014-07-28 23:28:12 [SERVER] [INFO] frizzilina[/127.0.0.1:0] logged in with entity id 132 at (130.3421165787264, 63.0, 318.5591663952593)
2014-07-28 23:28:12 [SERVER] [INFO] frizzilina joined the game
Setting up custom skins
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=1817ms, packet id=1)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=24ms, packet id=13)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=12ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=27ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=14ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=13ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=13ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=9ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=9ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=11ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=9ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=10ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=12ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=12ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=9ms, packet id=56)
2014-07-28 23:28:15 [MITE-CLIENT] [INFO] [Client] Long time processing packet (delay=9ms, packet id=56)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x69b701f0, pid=3372, tid=5664
#
# JRE version: Java(TM) SE Runtime Environment (7.0_65-b20) (build 1.7.0_65-b20)
# Java VM: Java HotSpot(TM) Client VM (24.65-b04 mixed mode windows-x86 )
# Problematic frame:
# C [atioglxx.dll+0x9901f0]
#
# 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\hallo\AppData\Roaming\.minecraft\hs_err_pid3372.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

Answer 1

Hallo,

leider fehlen die Angaben zu deinem System, aber ich versuche mal so auf die Schnelle zu helfen. Anscheinend hast du eine ATI-Grafikkarte, die ein Verarbeitungsproblem mit der virtuellen Maschine von Java 7.65 hatte. Folgende Schritte sollten durchgeführt werden:

Lade dir die aktuell richtige Java Software v7.65 runter (Java 32 oder 64-Bit, je nach System). Dies machst du ebenfalls mit deinem ATI-AMD Grafikkartentreiber. Erst wenn beide aktualisierten Treiber-Versionen vorliegen, deinstallierst du zuerst Java 7.65 und anschließend die ATI-Grafikkartensoftware und startest den Rechner neu. Wenn Windows beim Neustart neue Hardware findet und nach dem Treiber suchen möchte, einfach alles abbrechen. Jetzt den ATI-Treiber manuell neu installieren und das System neu starten lassen. Anschließend die neue Java Version installieren und ebenfalls einen Neustart ausführen. Nun kannst du Testen, ob Minecraft wieder läuft. Sollte es weiterhin Probleme geben, kann man diese Schritte ebenfalls mit Minecraft durchführen.

Gruß Micha

Answer 2

Wenn der Rechner bis zum Absturz fehlerfrei lief, glaub ich weniger an ein Treiberproblem als an ein thermisches Problem oder sogar einen Hardwaredefekt. Das deutet zumindest darauf hin:

A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x69b701f0, pid=3372, tid=5664
#
# JRE version: Java(TM) SE Runtime Environment (7.0_65-b20) (build 1.7.0_65-b20)
# Java VM: Java HotSpot(TM) Client VM (24.65-b04 mixed mode windows-x86 )
# Problematic frame:
# C [atioglxx.dll+0x9901f0]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows

Also, den Rechner abkühlen lassen, dann mal die Festplatte überprüfen, zB mit HD Tune, dann das Spiel nochmal probieren. Dann kann man immer noch den Treiber neu installieren.