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

1.9 worlds will immediately crash after starting the world up *FIXED*

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • Minecraft 1.9
    • Windows 10, Lastest Java Version
    • Unconfirmed

      When ever I load a 1.9 world up it immediately crashes. Issue was fix by using Mark Barrow's Strategy: "Instead of using the minecraft icon on my desktop, i go to my files. Windows (c: ). Click program files (x86). Click minecraft folder. click game. drag the java launcher out. Click that. MINECRAFT WORKS!" Thank You so much Mark Barrow!

      What I expected to happen was...:
      The world to load in.

      What actually happened was...:
      Upon starting up the world the game will crash.

      Steps to Reproduce:
      1. Start or create a new world in version 1.9
      2. Wait 1-5 seconds
      3. As a result the game will crash

      Game Output I got after crash:

      Completely ignored arguments: [--nativeLauncherVersion, 301]
      [16:44:43] [Client thread/INFO]: Setting user: ThatGuyBen14
      [16:44:43] [Client thread/INFO]: (Session ID is token:6e451cc0100c470eb15d8437aa7a607d:0a4560845d2d4175b31c15a2bba11b49)
      [16:44:44] [Client thread/INFO]: LWJGL Version: 2.9.4
      [16:44:44] [Client thread/INFO]: Reloading ResourceManager: Default
      [16:44:45] [Sound Library Loader/INFO]: Starting up SoundSystem...
      [16:44:45] [Thread-5/INFO]: Initializing LWJGL OpenAL
      [16:44:45] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
      [16:44:45] [Thread-5/INFO]: OpenAL initialized.
      [16:44:45] [Sound Library Loader/INFO]: Sound engine started
      [16:44:46] [Client thread/INFO]: Created: 1024x512 textures-atlas
      [16:44:53] [Server thread/INFO]: Starting integrated minecraft server version 1.9
      [16:44:53] [Server thread/INFO]: Generating keypair
      [16:44:54] [Server thread/INFO]: Preparing start region for level 0
      [16:44:55] [Server thread/INFO]: Preparing spawn area: 8%
      [16:44:56] [Server thread/INFO]: Preparing spawn area: 16%
      [16:44:57] [Server thread/INFO]: Preparing spawn area: 26%
      [16:44:58] [Server thread/INFO]: Preparing spawn area: 35%
      [16:44:59] [Server thread/INFO]: Preparing spawn area: 45%
      [16:45:00] [Server thread/INFO]: Preparing spawn area: 57%
      [16:45:01] [Server thread/INFO]: Preparing spawn area: 67%
      [16:45:02] [Server thread/INFO]: Preparing spawn area: 79%
      [16:45:03] [Server thread/INFO]: Preparing spawn area: 90%
      [16:45:04] [Server thread/INFO]: Changing view distance to 12, from 10
      [16:45:04] [Server thread/INFO]: ThatGuyBen14[local:E:b45eb04f] logged in with entity id 250 at (160.5, 76.0, 287.5)
      [16:45:04] [Server thread/INFO]: ThatGuyBen14 joined the game
      [16:45:09] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5032ms behind, skipping 100 tick(s)
      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffcb7f96b37, pid=12532, tid=3544
        #
      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 [ig8icd64.dll+0x16b37]
        #
      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\Ben\AppData\Roaming\.minecraft\hs_err_pid12532.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

            Unassigned Unassigned
            ThatGuyBen14 Benjamin Hart
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: