mojira.dev

Ted Taylor

Assigned

No issues.

Reported

MC-32606 JVM Crash in ig#icd64.dll (Broken Intel graphics card driver) Invalid

Comments

Wow. Just wow.

I thought this was a Mojang Inc official bug tracking system. Any good company would want to actually help their customers. And perhaps they would want to know what, exactly, is causing the crash and perhaps work around it, so that they could gain even more customers.

But since you asked...
Why not 1.5.2 ? I guess I could ; that is the version that I purchased. With my money. To Mojang.
Why not the snapshots? They tend to crash for other reasons not related to the Intel HD Graphics card.

Besides, they would like to be able to interact with others via multiplayer, and there are not many servers running the snapshots (if any).

I would appreciate it if a forum moderator would lock this thread. It is serving no purpose.

Kumasasa,

I understand the position you are in, but in reality, it takes TWO parties in order to declare an incompatibility.

Minecraft 1.6.x is triggering the condition that causes the display drivers to fail. These are the two parties. "Minecraft 1.6.x" is comprised of code written directly by Mojang, and third-party libraries chosen by Mojang and included in the distribution (eg ljwgl ). I have to come back to the fact that the latest snapshot (iirc, 13w39c) , on the exact same hardware and video does NOT trigger the display drivers to fail. If there was a fault in the video drivers exclusively, it should continue to fail and fail and fail regardless of what the Mojang code was doing.

The minimum acceptable outcome to me would be all four of:
a) confirmation from Mojang that there is a problem in MC 1.6.x with this particular configuration.
b) confirmation from Mojang that a specific line of program code in MC 1.6.x (or data being used by MC 1.6.x) is triggering the condition ... ie, when running the program in debug mode, if a Mojang engineer changes that line or data, the condition is no longer triggered)
c) confirmation from Mojang that said line of program code or data no longer exists in the latest snapshot (iirc, 13w39c).
d) confirmation from Mojang that said line of program code or data will not be re-introduced into the next versions of Minecraft official releases.

A bonus would be to have an approximate date of the next versions of MC official releases ... a date that I can tell my kids that they have to wait for before they can once again play what is (and hopefully will still be) one of their favourite games.

FYI, I did report the issue to Intel here: https://communities.intel.com/thread/45162 THAT is a whole other set of disappointment.

Still not able to run MC,
Ted.

Hmmmm. Marking this issue as "resolved" would seem to imply that Minecraft is playable, which it certainly is not.

Disappointed, (and with even more disappointed kids),
Ted.

In fiddling with the configuration, I found more detail. To get there, I swapped out the hard disk drive, installed Windows 7 x64 (retail) on it, and just the Intel Chip Drivers, Intel HD Graphics, Java 1.7.0u25, and Minecraft 1.6.

I also changed my launcher settings to keep the launcher window open.

The issue still occurs (play game in full screen mode, press ALT+TAB to return to the desktop, bang the video drivers fail) ; BUT, I see some information in the 'Development Console' window:

Client> #
Client> # A fatal error has been detected by the Java Runtime Environment:
Client> #
Client> # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000000c1c1c82, pid=2768, tid=2780
Client> #
Client> # JRE version: 7.0_25-b17
Client> # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode windows-amd64 compressed oops)
Client> # Problematic frame:
Client> # C [ig75icd64.dll+0x1c82]
Client> #
Client> # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
Client> #
Client> # An error report file with more information is saved as:
Client> # C:\Users\Ted\AppData\Roaming\.minecraft\hs_err_pid2768.log

The full text of the Development Console, plus the quoted hs_err_pid2768.log, are now attached.

Is there any further assistance available from Mojang ?

Ted.

Is there anything else I can do or provide, to help?
Ted.

OK, see attached crash report. I had to force it.

To be completely clean, I :
a) completely deleted my %AppData%\.minecraft folder
b) Ran MineCraft in full screen mode (MC had to re-download, as expected)
c) Pressed ALT+TAB to access the desktop. Graphics driver crashed.
d) Rebooted to reset the stage.
e) Checked for the %AppData%\.minecraft\crash-reports folder (none existed).
f) Ran MineCraft in full screen mode,
g) Pressed F3 + C for 10+ seconds.
h) The manually-triggered crash report was generated and attached!

Please let me know my next step. 🙂

Ted.

Attachments added as requested.

Actually, this cannot be a duplicate of MC-297 because I do not get either of the errors or crashes that are indicated in that ticket. Everything launches. Granted, the issue I am describing may be related to the issue.

Also, I cannot update the graphics drivers because
a) I have tried the latest version of Dell-supplied drivers v9.18.10.3165
b) I have tried the latest version Intel-supplied drivers v9.18.10,3257
c) I have tried the latest BETA version of Intel-supplied drivers v10.18.10.3282 (these are for Win8.1 but seems to work otherwise on my Win8.0). These drivers were released on September 18, 2013 - barely 7 days ago. They are not out of date. This is the link : https://communities.intel.com/docs/DOC-21232 .

The attached two print-screens are the bottom of the Snooper Settings page, as requested, from 1.5.2 (after downloading the mentioned Minecraft.exe which appears to be an old launcher) as well as the same page from 1.6.4, using the production launcher. I have also attached the a print-screen post-crash. All I did was play for 30 seconds on 1.6.4

You say " I suspect the new changes may be what's causing this ". I would presume that those same changes are also present in snapshot 13w38c. I can play that version without any crash. Curious.

Please "un-resolve" this issue, as it certainly is not resolved. I would like to work with you to find out how to fix the issue. Perhaps the solution is "wait until 1.7 is released". That would be a shame for the kids.

Ted.

PS: Attachments coming, once I figure out how to use this website. 🙂