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

Quiting Minecraft without any warnings

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.11
    • None
    • Java 8 update 111 (64 bit);
      Windows 8.1;
      Minecraft Launcher 1.6.70
    • Unconfirmed

      Today I wanted to play new version of Minecraft. I just loaded a new "1.11" version and clicked "Play". All went good while it was loading. I changed some setting (pic. 1) and wanted to start game. I click Create world twice and waited for loading(pic. 2). And after few second it loaded BUT after loading nearly chunks it crashed(pic. 3). Console even didn`t say that it was a crash!(pic 4)
      If I try to run 1.10.2 version, I get the same story : pic. 5

      WHAT SHOULD I DO?!

      UPdate: when I checked flag "Executable", I could run world but after a few seconds it gave me an error :
      //
      [17:45:52] [Server thread/INFO]: Saving and pausing game...
      [17:45:52] [Server thread/INFO]: Saving chunks for level 'New World--'/Overworld
      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffb2e5ecfc3, pid=11260, tid=8480
        #
      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+0x6cfc3][17:45:52] [Server thread/INFO]: Saving chunks for level 'New World--'/Nether
        [17:45:52] [Server thread/INFO]: Saving chunks for level 'New World--'/The End

      #

      1. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
        #
      2. An error report file with more information is saved as:
      3. C:\Users\Пользователь\AppData\Roaming\.minecraft\hs_err_pid11260.log
        #
      4. If you would like to submit a bug report, please visit:
      5. http://bugreport.sun.com/bugreport/crash.jsp
      6. The crash happened outside the Java Virtual Machine in native code.
      7. See problematic frame for where to report the bug.
        #
        [17:46:01] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3833ms behind, skipping 76 tick(s)
        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
        //

        1. Снимок1.PNG
          99 kB
          Sergey
        2. Снимок2.PNG
          43 kB
          Sergey
        3. Снимок3.PNG
          112 kB
          Sergey
        4. Снимок4.PNG
          64 kB
          Sergey
        5. Снимок5.PNG
          50 kB
          Sergey

            Unassigned Unassigned
            TaN_4iK Sergey
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: