Here is a log for an unmodded crash. It's been going on for some time now, even after new graphics card purchase, and a re-installation of Windows. Any help or ideas, please and thank you.
Completely ignored arguments: [--nativeLauncherVersion, 307]
[18:06:15] [Client thread/INFO]: Setting user: VoodooNinja
[18:06:16] [Client thread/WARN]: Skipping bad option: lastServer:
[18:06:16] [Client thread/INFO]: LWJGL Version: 2.9.4
[18:06:17] [Client thread/INFO]: Reloading ResourceManager: Default
[18:06:21] [Sound Library Loader/INFO]: Starting up SoundSystem...
[18:06:22] [Thread-5/INFO]: Initializing LWJGL OpenAL
[18:06:22] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[18:06:22] [Thread-5/INFO]: OpenAL initialized.
[18:06:22] [Sound Library Loader/INFO]: Sound engine started
[18:06:25] [Client thread/INFO]: Created: 1024x512 textures-atlas
[18:08:42] [Client thread/INFO]: Connecting to
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000002c563e0, pid=9704, tid=0x000000000000173c
#
# JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# v ~BufferBlob::C1 temporary CodeBuffer
#
# 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\VoodooNinja\AppData\Roaming\.minecraft\hs_err_pid9704.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
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
Another crash that just happened trying to reload;
Completely ignored arguments: [--nativeLauncherVersion, 307]
[18:18:26] [Client thread/INFO]: Setting user: VoodooNinja
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000002f259a4, pid=1076, tid=0x0000000000001d70
#
# JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J 1357 C1 java.util.jar.JarVerifier.beginEntry(Ljava/util/jar/JarEntry;Lsun/security/util/ManifestEntryVerifier;)V (233 bytes) @ 0x0000000002f259a4 [0x0000000002f24b80+0xe24]
#
# 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\VoodooNinja\AppData\Roaming\.minecraft\hs_err_pid1076.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Those are some weird Java errors I've never seen before. You have what looks like the most recent version of Java, so that shouldn't be it. When you installed Java, did it ask if you wanted old versions removed? You should do so if it asks that, so that any old versions don't interfere with the current version. If you have some utilities or programs that need the old version of Java, then you should see if they have been updated. Really just guessing there, those are really strange errors.
Maybe try reinstalling both the 32 and 64 bit versions of Java from here: https://www.java.com/en/download/manual.jsp grab the offline installer for both of them, install the 32 bit one first, and if it asks to uninstall any old versions, let it do that, then install the 64 bit version.
Thanks for the replies. Yes I removed the old versions. I did notice something though, Minecrafts launcher has an older version of Java in it's directory.
As long as you set the version of Java used in the launcher to the most recent one installed, it should use that and ignore the outdated one that comes with the launcher.
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
Well, I tried version 7, and even tried teh beta 112 version and still crashes. Just not sure what happened. Starting to wonder if it's a hardware thing on my system. I'm completely baffled.
The game only shows a portion of this type of crash, can you get the contents of this file on your computer, and use a code/spoiler tag in the post to show it. C:\Users\VoodooNinja\AppData\Roaming\.minecraft\hs_err_pid9704.log\
Keeping in mind that that is the error log generated by the first crash you showed. You may want to let it crash again, and get the contents from the newest error log it makes. The game-output window you get when it crashes will show you the location and number of the file.
Here is a log for an unmodded crash. It's been going on for some time now, even after new graphics card purchase, and a re-installation of Windows. Any help or ideas, please and thank you.
Completely ignored arguments: [--nativeLauncherVersion, 307]
[18:06:15] [Client thread/INFO]: Setting user: VoodooNinja
[18:06:16] [Client thread/WARN]: Skipping bad option: lastServer:
[18:06:16] [Client thread/INFO]: LWJGL Version: 2.9.4
[18:06:17] [Client thread/INFO]: Reloading ResourceManager: Default
[18:06:21] [Sound Library Loader/INFO]: Starting up SoundSystem...
[18:06:22] [Thread-5/INFO]: Initializing LWJGL OpenAL
[18:06:22] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[18:06:22] [Thread-5/INFO]: OpenAL initialized.
[18:06:22] [Sound Library Loader/INFO]: Sound engine started
[18:06:25] [Client thread/INFO]: Created: 1024x512 textures-atlas
[18:08:42] [Client thread/INFO]: Connecting to
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000002c563e0, pid=9704, tid=0x000000000000173c
#
# JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# v ~BufferBlob::C1 temporary CodeBuffer
#
# 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\VoodooNinja\AppData\Roaming\.minecraft\hs_err_pid9704.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
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
Another crash that just happened trying to reload;
Completely ignored arguments: [--nativeLauncherVersion, 307]
[18:18:26] [Client thread/INFO]: Setting user: VoodooNinja
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000002f259a4, pid=1076, tid=0x0000000000001d70
#
# JRE version: Java(TM) SE Runtime Environment (8.0_111-b14) (build 1.8.0_111-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.111-b14 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J 1357 C1 java.util.jar.JarVerifier.beginEntry(Ljava/util/jar/JarEntry;Lsun/security/util/ManifestEntryVerifier;)V (233 bytes) @ 0x0000000002f259a4 [0x0000000002f24b80+0xe24]
#
# 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\VoodooNinja\AppData\Roaming\.minecraft\hs_err_pid1076.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Maybe try using Java 7 and not the version of java minecraft has built in?
Those are some weird Java errors I've never seen before. You have what looks like the most recent version of Java, so that shouldn't be it. When you installed Java, did it ask if you wanted old versions removed? You should do so if it asks that, so that any old versions don't interfere with the current version. If you have some utilities or programs that need the old version of Java, then you should see if they have been updated. Really just guessing there, those are really strange errors.
Maybe try reinstalling both the 32 and 64 bit versions of Java from here: https://www.java.com/en/download/manual.jsp grab the offline installer for both of them, install the 32 bit one first, and if it asks to uninstall any old versions, let it do that, then install the 64 bit version.
D_B
To tell them how to live is to prevent them living.
Thanks for the replies. Yes I removed the old versions. I did notice something though, Minecrafts launcher has an older version of Java in it's directory.
Would that be causing problems?
I haven't tried Java 7 yet. I'll give it a whirl.
As long as you set the version of Java used in the launcher to the most recent one installed, it should use that and ignore the outdated one that comes with the launcher.
D_B
To tell them how to live is to prevent them living.
Well, I tried version 7, and even tried teh beta 112 version and still crashes. Just not sure what happened. Starting to wonder if it's a hardware thing on my system. I'm completely baffled.
The game only shows a portion of this type of crash, can you get the contents of this file on your computer, and use a code/spoiler tag in the post to show it. C:\Users\VoodooNinja\AppData\Roaming\.minecraft\hs_err_pid9704.log\
Keeping in mind that that is the error log generated by the first crash you showed. You may want to let it crash again, and get the contents from the newest error log it makes. The game-output window you get when it crashes will show you the location and number of the file.
Okay, I'll do this when I get home tonight and repost.