My cpu is 64 bit but i orignally played on minecraft on a 32 bit after finding out my cpu was actually 64 bit I updated and now minecraft won't run i would get as far as the Launcher screen then click play where i am then greeted with this
[16:59:59] [Client thread/INFO]: Setting user: Vizzard99
[16:59:59] [Client thread/INFO]: (Session ID is token:cfeaa61caae744a4923365c756e14128:0f4b38c6cdd34c37ae1a7d344e5682c1)
[17:00:04] [Client thread/INFO]: LWJGL Version: 2.9.1
[17:00:05] [Client thread/INFO]: Reloading ResourceManager: Default
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005af0a905, pid=6052, tid=7576
#
# JRE version: Java(TM) SE Runtime Environment (8.0_20-b26) (build 1.8.0_20-b26)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.20-b23 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig7icd64.dll+0x47a905]
#
# 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\Candy\AppData\Roaming\.minecraft\hs_err_pid6052.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.
#
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
It's entirely possible for a driver to have different bugs in the 32bit and 64bit versions and switching between 32bit and 64bit Java will switch between two different versions of the driver.
Generally speaking, for a recent OS (Win7 or never) I would expect that there would be fewer bugs in the 64bit version assuming this is the most commonly deployed and most tested version. For older OSes it might be the other way around. For example I know there's a 64bit version of Windows XP, but I would expect that it suffers from more bugs since that was a very uncommon deployment.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
[16:59:59] [Client thread/INFO]: Setting user: Vizzard99
[16:59:59] [Client thread/INFO]: (Session ID is token:cfeaa61caae744a4923365c756e14128:0f4b38c6cdd34c37ae1a7d344e5682c1)
[17:00:04] [Client thread/INFO]: LWJGL Version: 2.9.1
[17:00:05] [Client thread/INFO]: Reloading ResourceManager: Default
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000005af0a905, pid=6052, tid=7576
#
# JRE version: Java(TM) SE Runtime Environment (8.0_20-b26) (build 1.8.0_20-b26)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.20-b23 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [ig7icd64.dll+0x47a905]
#
# 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\Candy\AppData\Roaming\.minecraft\hs_err_pid6052.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.
#
Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release
Please help q.q.
-
View User Profile
-
View Posts
-
Send Message
ModeratorGenerally speaking, for a recent OS (Win7 or never) I would expect that there would be fewer bugs in the 64bit version assuming this is the most commonly deployed and most tested version. For older OSes it might be the other way around. For example I know there's a 64bit version of Windows XP, but I would expect that it suffers from more bugs since that was a very uncommon deployment.