Uploaded image for project: 'Minecraft Launcher'
  1. Minecraft Launcher
  2. MCL-4249

Launcher does not start with error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Resolution: Duplicate
    • Affects Version/s: 1.6.48
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
      Windows 7
    • Confirmation Status:
      Unconfirmed

      Description

      Clicked Play, the loader starts, I get the Mojang logo then the error page is returned.

      It is reproduced every time.

      16:05:07] [Client thread/INFO]: (Session ID is token:76ff303d9b2948ff828093cee308d69d:8c3188c8f62f4311bae0c1a6a7c6ace2)
      [16:05:09] [Client thread/INFO]: LWJGL Version: 2.9.4
      [16:05:10] [Client thread/INFO]: Reloading ResourceManager: Default
      [16:05:11] [Sound Library Loader/INFO]: Starting up SoundSystem...
      [16:05:12] [Thread-6/INFO]: Initializing LWJGL OpenAL
      [16:05:12] [Thread-6/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
      [16:05:12] [Thread-6/INFO]: OpenAL initialized.
      [16:05:12] [Sound Library Loader/INFO]: Sound engine started
      [16:05:14] [Client thread/INFO]: Created: 512x512 textures-atlas
      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x27553e88, pid=5112, tid=5120
        #
      3. JRE version: Java(TM) SE Runtime Environment (8.0_66-b18) (build 1.8.0_66-b18)
      4. Java VM: Java HotSpot(TM) Client VM (25.66-b18 mixed mode windows-x86 )
      5. Problematic frame:
      6. C [ig4dev32.dll+0x3e88]
        #
      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\Dell Lattitude\AppData\Roaming\.minecraft\hs_err_pid5112.log
        #
      10. If you would like to submit a bug report, please visit:
      11. http://bugreport.java.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) Client VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              Olibear123 Andrew Atkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: