So, I have a problem with a "minidumps not enabled" crash. Here is the crash report from my latest attempt to play:
Completely ignored arguments: [--nativeLauncherVersion, 301]
[18:02:58] [Client thread/INFO]: Setting user: RiosXX3
[18:02:59] [Client thread/INFO]: LWJGL Version: 2.9.4
[18:02:59] [Client thread/INFO]: Reloading ResourceManager: Default
[18:03:00] [Sound Library Loader/INFO]: Starting up SoundSystem...
[18:03:00] [Thread-5/INFO]: Initializing LWJGL OpenAL
[18:03:00] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[18:03:01] [Thread-5/INFO]: OpenAL initialized.
[18:03:01] [Sound Library Loader/INFO]: Sound engine started
[18:03:02] [Client thread/INFO]: Created: 1024x512 textures-atlas
[18:03:27] [Client thread/INFO]: Connecting to server.superhostileonline.com, 25565
[18:03:30] [Client thread/INFO]: [CHAT] RiosXX3 joined the game
[18:03:31] [Client thread/INFO]: [CHAT] <milomill> i kinda close to spawn
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffd35d986c, pid=11116, tid=4780
#
# 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 [ig8icd64.dll+0x63986c]
#
# 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\versa\AppData\Roaming\.minecraft\hs_err_pid11116.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'm currently on windows 10, but I never had this problem until 1.9. I have the latest drivers, and I'm on the latest Java. Here's the thing though; I was able to fix these crashes by going to the options.txt and putting "fboEnable:false." The only problem with that is the fact that my screen now goes black whenever I look at glowing mobs. If anyone is aware of a way to fix both issues without triggering the other, please let me know.
So, I have a problem with a "minidumps not enabled" crash. Here is the crash report from my latest attempt to play:
Completely ignored arguments: [--nativeLauncherVersion, 301]
[18:02:58] [Client thread/INFO]: Setting user: RiosXX3
[18:02:59] [Client thread/INFO]: LWJGL Version: 2.9.4
[18:02:59] [Client thread/INFO]: Reloading ResourceManager: Default
[18:03:00] [Sound Library Loader/INFO]: Starting up SoundSystem...
[18:03:00] [Thread-5/INFO]: Initializing LWJGL OpenAL
[18:03:00] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[18:03:01] [Thread-5/INFO]: OpenAL initialized.
[18:03:01] [Sound Library Loader/INFO]: Sound engine started
[18:03:02] [Client thread/INFO]: Created: 1024x512 textures-atlas
[18:03:27] [Client thread/INFO]: Connecting to server.superhostileonline.com, 25565
[18:03:30] [Client thread/INFO]: [CHAT] RiosXX3 joined the game
[18:03:31] [Client thread/INFO]: [CHAT] <milomill> i kinda close to spawn
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007fffd35d986c, pid=11116, tid=4780
#
# 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 [ig8icd64.dll+0x63986c]
#
# 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\versa\AppData\Roaming\.minecraft\hs_err_pid11116.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'm currently on windows 10, but I never had this problem until 1.9. I have the latest drivers, and I'm on the latest Java. Here's the thing though; I was able to fix these crashes by going to the options.txt and putting "fboEnable:false." The only problem with that is the fact that my screen now goes black whenever I look at glowing mobs. If anyone is aware of a way to fix both issues without triggering the other, please let me know.
-
View User Profile
-
View Posts
-
Send Message
Moderatorsee point 2 here http://www.minecraftforum.net/forums/support/unmodified-minecraft-client/2627432-1-9-faqs-read-before-posting
turn on VBOs and v-sync
Thanks for your help