Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-104571

I can go into the minecraft launcher but when i try to start a single-or multiplayer minecraft crashes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.10.2
    • None
    • Unconfirmed

      i can get into the launche but when i try to start a single- or multiplayer game minecraft crashes and i get back to the laucher and in the game Output i can read that but i dont know what to do :
      Completely ignored arguments: [--nativeLauncherVersion, 301]
      [19:27:05] [Client thread/INFO]: Setting user: Learichard
      [19:27:07] [Client thread/INFO]: LWJGL Version: 2.9.4
      [19:27:07] [Client thread/INFO]: Reloading ResourceManager: Default
      [19:27:08] [Sound Library Loader/INFO
      ]: Starting up SoundSystem...
      [19:27:09] [Thread-5/INFO]: Initializing LWJGL OpenAL
      [19:27:09] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
      [19:27:09] [Thread-5/INFO]: OpenAL initialized.[19:27:09] [Sound Library Loader/INFO]: Sound engine started
      [19:27:11] [Client thread/INFO]: Created: 1024x512 textures-atlas
      [19:27:17] [Server thread/INFO]: Starting integrated minecraft server version 1.10.2
      [19:27:17] [Server thread/INFO]: Generating keypair
      [19:27:17] [Server thread/INFO]: Preparing start region for level 0
      [19:27:18] [Server thread/INFO]: Preparing spawn area: 22%
      [19:27:19] [Server thread/INFO]: Preparing spawn area: 74%
      [19:27:20] [Server thread/INFO]: Changing view distance to 12, from 10
      [19:27:23] [Server thread/INFO]: Learichard[local:E:26f77833] logged in with entity id 341 at (-174.93334397244107, 150.0, 348.5928212844818)
      [19:27:23] [Server thread/INFO]: Learichard hat das Spiel betreten
      [19:27:27] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2114ms behind, skipping 42 tick(s)
      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd4689d5d3, pid=6140, tid=8088
        #
      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 [ig7icd64.dll+0x6d5d3]
        #
      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\Lea Richard\AppData\Roaming\.minecraft\hs_err_pid6140.log
        Compiled method (c1) 27526 7016 2 bwn::a (11 bytes)
        total in heap [0x000000000314c190,0x000000000314cb10] = 2432
        relocation [0x000000000314c2b0,0x000000000314c340] = 144
        main code [0x000000000314c340,0x000000000314c640] = 768
        stub code [0x000000000314c640,0x000000000314c738] = 248
        oops [0x000000000314c738,0x000000000314c740] = 8
        metadata [0x000000000314c740,0x000000000314c780] = 64
        scopes data [0x000000000314c780,0x000000000314c9f8] = 632
        scopes pcs [0x000000000314c9f8,0x000000000314cae8] = 240
        dependencies [0x000000000314cae8,0x000000000314caf0] = 8
        nul chk table [0x000000000314caf0,0x000000000314cb10] = 32
        #
      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

            Unassigned Unassigned
            Learichard Lea Richard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: