I've had this issue (see attached image) for some time but used to resolve it by switching over to the 32bit JRE, however the performance there was very poor and Minecraft couldn't allocate enough RAM to run smoothly.
I've tried adding the Nvidia program profiles for both java.exe and javaw.exe (for the 64bit JRE) and forcing them to "NVIDIA GPU", but still got the same error.
From the Windows Event log:
Faulting application name: javaw.exe, version: 7.0.600.19, time stamp: 0x536a919d
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000007fef94c0004
Faulting process id: 0x1c84
Faulting application start time: 0x01cf82318d0b95f0
Faulting application path: C:\Program Files\Java\jre7\bin\javaw.exe
Faulting module path: unknown
Report Id: ce740048-ee24-11e3-baa2-005056c00008The game works fine when I force the Nvidia program profile for "minecraft.exe" to "Integrated graphics" - but very slow.
Linked issues
Attachments
Comments 7
Interesting, my issues have been resolved by installing an unofficial OpenJDK 7 update 60 build 30 amd64 from https://github.com/alexkasko/openjdk-unofficial-builds (see attached image, max fps set 50, render distance set to 16). Nvidia optimus is working fine with OpenJDK and the performance is very good.
This leads me to believe there is a strange bug in Oracle JRE 7u60 amd64.
There appears to be some kind of problem between Nvidia Optimus and Oracle Java. This user found the same workaround.
Sorry, but I wouldn’t call this a straight up duplicate as I analyzed the referenced issue and found that the vm platform is completely different:
vm_info: Java HotSpot(TM) 64-Bit Server VM (24.45-b08) for linux-amd64 JRE (1.7.0_45-b18), built on Oct 8 2013 05:44:25 by "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)
You can even see it was not compiled officially by Oracle, but by Red Hat using gcc – probably including some of their own vendor specific patches/tweaks. I seriously doubt that the build section of vm_info is the same on Oracle JRE 7u60 amd64 Windows build as well:
C:\Program Files (x86)\Java\jre7\bin>java -version
java version "1.7.0_55"
Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
Java HotSpot(TM) Client VM (build 24.55-b03, mixed mode, sharing)C:\Users\petar\openjdk_1.7.0_u60_64\bin>java -version
openjdk version "1.7.0-u60-unofficial"
OpenJDK Runtime Environment (build 1.7.0-u60-unofficial-b30)
OpenJDK 64-Bit Server VM (build 24.60-b09, mixed mode)The workaround is indeed very similar, where he uses an official OpenJDK and I’m using an unofficial/unsupported build, but I’m afraid the issue itself is pretty much tied to the underlying Java/OS/Nvidia integration issues. Therefore, please consider unmarking this issue as a mere duplicate.
The bug is in code that's outside of Mojang's control, and it doesn't matter whether it's in Nvidia's or Oracle's – there's nothing for Mojang to do about it. Does it particularly matter to you whether this issue is marked as a duplicate of that one, or whether it's marked Invalid on its own?
I'd honestly preferer for it to be filed (or at least tagged) as something like "known issues outside of Mojang's control", but from the choices you've given me "duplicate" seems more appropriate.
BTW: A list of known issues ala https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Known_issues would be nice to have.
A list of known issues and solutions or workarounds is available at the Mojang Support Center. If this issue proves to be a common problem, and enough information is gathered to help people with it, an article would be posted there. However, it would be preferable if the problem was fixed, rather than just telling people to work around it.
OpenJDK 7 update 60 build 30