I've been trying to fix this for roughly a year and a half now. (Granted, a good some of it has been procrastination.) I'm running a Windows 7 64-bit VAIO laptop. My attempts to fix up a nice tower are taking some time, but this laptop runs Minecraft well enough. Or did... After 1.6.4 I was unable to load any version of Minecraft. I figured I was just kinda SOL and went without it for the longest time. But after a little fiddling I figured out I can still play 1.6.4 and any previous version. Just not 1.7-1.8.3. And I'm not saying 1.6.4 isn't good enough, but I can't seem to load mods on it anymore and there are NO VANILLA SERVERS for 1.6.4...
[15:31:15] [Client thread/INFO]: Setting user: [][][][][][][][][][]
[15:31:15] [Client thread/INFO]: (Session ID is token:e6bd113bd3884c128e429aca237b7068:1c540adea16c423b89a748197071e3a3)
[15:31:18] [Client thread/INFO]: LWJGL Version: 2.9.4
[15:31:18] [Client thread/INFO]: Reloading ResourceManager: Default
[15:31:19] [Sound Library Loader/INFO]: Starting up SoundSystem...
[15:31:20] [Thread-5/INFO]: Initializing LWJGL OpenAL
[15:31:20] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[15:31:20] [Thread-5/INFO]: OpenAL initialized.
[15:31:20] [Sound Library Loader/INFO]: Sound engine started
[15:31:36] [Client thread/INFO]: Created: 512x512 textures-atlas
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005ac255ec, pid=5672, tid=2288
#
# 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 [ig4dev64.dll+0x55ec]
#
# 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\[][][][][][]\AppData\Roaming\.minecraft\hs_err_pid5672.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 blurred out personal data with [][]'s. And to anyone who could help explain what I need to do, my eternal gratitude. I've tried re-installing Minecraft, Java, Updatind drivers, Downloading the newest launcher which includes java. I've even gone as far to try to include Client Mods to see if it "messes up enough to make things work"...
I'd be more than happy to answer any questions, and I'll monitor this page for a while to answer quickly. I'm so ready to get this fixed and get back to playing...
P.S. I installed Ubuntu on a partition on the same computer to test something, AND MINECRAFT WORKED FINE ON THE UBUNTU SIDE. This furthers my idea that it is an issue with Window's settings. But in all honestly I prefer to keep to the Window's partition.
To add to this, when I mentioned that the Ubuntu version allowed it to run, that surely means that it's not because of my terrible graphics card, because I was able to run it on this same laptop, just not the Windows side of it. Right?
The problem is a bug in the windows intel driver. While the functionality is not required (yet), MC will use it if the driver claims support, and then the driver crashes.
While this makes since. This laptop is pretty old. That still doesn't explain how I can use the same exact computer with an Ubuntu operating system and be able to run 1.8.3 just as fluidly. Doesn't that mean that it isn't just outdated GPU?
I've been trying to fix this for roughly a year and a half now. (Granted, a good some of it has been procrastination.) I'm running a Windows 7 64-bit VAIO laptop. My attempts to fix up a nice tower are taking some time, but this laptop runs Minecraft well enough. Or did... After 1.6.4 I was unable to load any version of Minecraft. I figured I was just kinda SOL and went without it for the longest time. But after a little fiddling I figured out I can still play 1.6.4 and any previous version. Just not 1.7-1.8.3. And I'm not saying 1.6.4 isn't good enough, but I can't seem to load mods on it anymore and there are NO VANILLA SERVERS for 1.6.4...
I believe that recently someone made a page that could help: http://www.spigotmc.org/threads/minecraft-64bit-java-error-exception_access_violation-0xc0000005.32934/ , but I can't seem to make since enough of it to actually fix my issues. I tried to run 1.8.3 a few minutes ago to re-read the report it gives me. What I got is as follows:
------------------------------------------------------------------------------------------
[15:31:15] [Client thread/INFO]: Setting user: [][][][][][][][][][]
[15:31:15] [Client thread/INFO]: (Session ID is token:e6bd113bd3884c128e429aca237b7068:1c540adea16c423b89a748197071e3a3)
[15:31:18] [Client thread/INFO]: LWJGL Version: 2.9.4
[15:31:18] [Client thread/INFO]: Reloading ResourceManager: Default
[15:31:19] [Sound Library Loader/INFO]: Starting up SoundSystem...
[15:31:20] [Thread-5/INFO]: Initializing LWJGL OpenAL
[15:31:20] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[15:31:20] [Thread-5/INFO]: OpenAL initialized.
[15:31:20] [Sound Library Loader/INFO]: Sound engine started
[15:31:36] [Client thread/INFO]: Created: 512x512 textures-atlas
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005ac255ec, pid=5672, tid=2288
#
# 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 [ig4dev64.dll+0x55ec]
#
# 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\[][][][][][]\AppData\Roaming\.minecraft\hs_err_pid5672.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 blurred out personal data with [][]'s. And to anyone who could help explain what I need to do, my eternal gratitude. I've tried re-installing Minecraft, Java, Updatind drivers, Downloading the newest launcher which includes java. I've even gone as far to try to include Client Mods to see if it "messes up enough to make things work"...
I'd be more than happy to answer any questions, and I'll monitor this page for a while to answer quickly. I'm so ready to get this fixed and get back to playing...
P.S. I installed Ubuntu on a partition on the same computer to test something, AND MINECRAFT WORKED FINE ON THE UBUNTU SIDE. This furthers my idea that it is an issue with Window's settings. But in all honestly I prefer to keep to the Window's partition.
To add to this, when I mentioned that the Ubuntu version allowed it to run, that surely means that it's not because of my terrible graphics card, because I was able to run it on this same laptop, just not the Windows side of it. Right?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumYeah, you're crashing your graphics driver. Time for an upgrade, I would say.
See: http://hopper.minecraft.net/help/references/intel-4-series-chipsets/
The problem is a bug in the windows intel driver. While the functionality is not required (yet), MC will use it if the driver claims support, and then the driver crashes.
While this makes since. This laptop is pretty old. That still doesn't explain how I can use the same exact computer with an Ubuntu operating system and be able to run 1.8.3 just as fluidly. Doesn't that mean that it isn't just outdated GPU?
Windows driver != Linux driver
The GPU is so old that it is no longer supported by Intel which means that any existing bugs in the driver will never be fixed.
But wouldn't the Ubuntu side of the computer still use the same drivers?
Of course not. Linux is not windows.
I see... Thank you for helping me understand ^-^ You're the best.