• Icon: Bug Bug
    • Resolution: Invalid
    • None
    • Minecraft 1.11.2
    • None
    • OS: Windows 7 Home Premium ;Java 8 Update 121
    • Unconfirmed

      Minecraft Game Output:

      18:36:39 launcher main info Preparing to launch minecraft client for 1.11.2
      18:36:47 launcher main info Checking installations.
      18:36:47 launcher main info Minecraft client 1.11.2 is ready to start.
      18:36:47 launcher main info Starting!
      18:36:47 launcher main info Using default game log configuration client-1.7.xml (outputs XML)
      18:36:53 bes Client thread info Setting user: AlvaroLopez
      18:36:56 bes Client thread info LWJGL Version: 2.9.4
      18:36:57 launcher main info Process closed with exit code 1
      18:36:57 launcher main info
      #

      1. A fatal error has been detected by the Java Runtime Environment:
        #
      2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006895f5bf, pid=1056, tid=6548
        #
      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 [aticfx64.dll+0x2f5bf]
        #
      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\Elvira\AppData\Roaming\.minecraft\hs_err_pid1056.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.
        #
        Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

            Unassigned Unassigned
            Alvaro Lopez Elvira Martin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: