Major Crashes since 1.10 Release

Discussion in 'Miscellaneous' started by QuilliamPenn, Jun 8, 2016.

Thread Status:
Not open for further replies.
  1. At first i thought it was just 1.10, so i downgraded back to 1.9.4, but now I can't join any world or server without crashing within 30 seconds. I have never, EVER had this issue before, and it's quite annoying. I tried contacting Mojang but on their bug-report forum they asked me for a crash report, marked the issue as resolved and i haven't heard a word from them since.

    I'm just wondering if anyone else has had this problem. I'll copy the crash report below.

    # A fatal error has been detected by the Java Runtime Environment:
    #
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffddeca5cc0, pid=18788, tid=21384
    #
    # JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
    # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
    # Problematic frame:
    # C [ig7icd64.dll+0x155cc0]
    #
    # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
    #
    # An error report file with more information is saved as:
    # C:\Users\Quilliam\AppData\Roaming\.minecraft\hs_err_pid18788.log
    #
    # If you would like to submit a bug report, please visit:
    # http://bugreport.sun.com/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # 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

    I have no idea what this means.

    Help pls ;;
  2. Do you have the most recent Java version?
    Wither_Addict likes this.
  3. If it was because you were on 1.10 then you went back to 1.9, then there shouldn't be a problem, I would just try and uninstall then reinstall
  4. Yes I do, I've been doing more research and it may have something to do with memory allocation or something.

    (Edit) Tried increasing memory allocation from 1GB to 2GB, nothing changes. Still Crashing, Toggling VBO's and Vsync, nothing changes there either.

    I'll be sure to try that, don't know why i didn't think of it in the first place.
    Wither_Addict likes this.
  5. Could you get the Crash Log?

    That is just the one that shows in the launcher....

    # An error report file with more information is saved as:
    # C:\Users\Quilliam\AppData\Roaming\.minecraft\hs_err_pid18788.log

    This will show the error, as right now, All mojang sees is no information on the lag as well as everyone else that looks at it... its just the basic information...
    QuilliamPenn likes this.
  6. Like i said, I know little about all this. I'll post the crashlog. One moment.

    How do you make it into a spoiler (I've never done it before :eek:) Because it's a whole wall of text I don't want to flood the forum page.
  7. I've tried lol it's far too long to post in one sometimes.
  8. u dont got the most recent java version.

    # JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

    recent is 1.8.0_91 or so. id start there.
  9. Doing that now. Guess it wasn't updated. Thanks!

    I feel so foolish, i hope you all forgive me. I'm just really unlearned at this stuff.
    AyanamiKun likes this.
  10. Problem solved! It was a mixture of both Java, and my graphics drivers were apparently wayyy out of date. Updated them both, it's back to running fine! Thank you all!
    AyanamiKun and TomvanWijnen like this.
  11. I'm having the same issue but when I try yo update Java I get a "download failed" message...
    SirTah likes this.
  12. I'm having the issue as well. I started out on 1.9.4 on EMC, then went to 1.10 to try it on realms. Ever since then, minecraft has been crashing even when I put it back on 1.9.4. I've updated/deleted/re-downloaded both Java and minecraft multiple times and I updated graphics.
  13. I'll add a reply there.
  14. Continue discussion on issue here
Thread Status:
Not open for further replies.