Intel integrated GPU drivers fail on Windows 10 (HD2000 and HD3000)

[Parker8283]

Log: http://paste.ee/r/oVh9z

I had to do some trickery to use the Intel provided graphics drivers on Win8+, which have OpenGL support. Normal Minecraft launcher works just fine.

[peterix]

The real issues is: the graphics drivers are choosing the wrong graphics card to use.

This is something that needs to be fixed. How? I'm not exactly sure.

[peterix]

Let's call it a bug and actually work on that :)

[peterix]

I assume you have dual graphics? Something like Nvidia Optimus?

Please describe what you needed to do to make it work.

[Parker8283]

wrong card? I've only got the one :P

I've got Intel integrated graphics (really old as well, but they work). I had this issue a while back, but it was because I was using the microsoft provided graphics drivers because the intel ones didn't support win8+ (this was after I updated to win10). I did some trickery to get win10 to accept the win7 intel drivers, and everything has worked just fine since then. MultiMC also worked for a while like this. I just started it today (updated to latest development release), and this started happening again.

[peterix]

Multiple issues then...

[peterix]

What happens if you rename the 'multimc.exe' to 'minecraft.exe'?

[Parker8283]

Same output

[peterix]

So, the graphics driver is completely broken. Maybe it got replaced?

[Parker8283]

The problem is, the mojang launcher still works just fine. Just checked Device Manager, and it's still using the Intel ones I installed.

[peterix]

That sounds impossible.

[Parker8283]

I'm as baffled as you are; running the vanilla launcher:

Also, as I stated, MultiMC was working fine until just today, when I updated to the latest development release. Let me grab the latest stable and test again.

[Parker8283]

uhh...wat? Ok, 0.4.7 stable isn't working anymore either...I'm seriously confused.

[Parker8283]

I know that MultiMC was working with the intel drivers, because I used MultiMC to test the new graphics drivers and see if minecraft would launch (and it did)

[peterix]

Did the OS update the drivers while you weren't looking?

Then again, why is it working using the mojang launcher... that makes absolutely no sense.

[Parker8283]

So, no.

[Parker8283]

The only thing I can think of is that either the mojang launcher is doing something weird with selecting drivers or something, or you're doing something that is somehow affecting driver selection...kinda hard to tell...

[peterix]

There is no such thing as 'driver selection'.

[peterix]

Anyway, there has to be some difference. Can you post the log from the vanilla launcher? Ideally also the json file from the version profile it is using.

[Parker8283]

Which is why I was even more confused, because I know that there IS only one driver for a device. The only think I could have thought of was it was finding the files for the other drivers on the system somewhere and using those, but that seems pretty far-fetched. At this point, I just sound like an idiot :P

Anyways, here's a gist with that stuff.

[peterix]

OK. I can't see anything too different in that. LWJGL version is the same. The only difference is in how it's launched.

So, I'll experiment with that. Dismantle the launcher part and get rid of some old cruft... I'll see how it goes :)

[Parker8283]

I bid you the best of luck, sir.

/me can't wait until I get my new computer.

[peterix]

Alright. If you switch to the 'dumblaunch' branch and update, you should get a much simplified launch method.

Does it work?

[Parker8283]

Nope, same result. Here's the new log, if it helps.

[peterix]

Right, one more time:
Close down everything, rename MultiMC.exe to Minecraft.exe and check (make sure you have file extensions enabled, so it doesn't end up being Minecraft.exe.exe). If that doesn't help, then I have no more ideas.

[peterix]

Actually, maybe...

Did you enable fullscreen mode in game?

[peterix]

The root cause has been found - it's actually the intel driver's fault. See the linked LWJGL issue.

I've posted about it on the intel driver bug report forum and it finally got some much needed attention.

[Parker8283]

"attention" being "sucks for using an old IG chipset, buy a new one" it seems...great...

[peterix]

Yeah.

You know, I'm going to work around all these issues. It's pretty much the next thing I'll do. It will be a horrible pile of weird things, but I can get all of this working.

Anyway, this is NOT a MultiMC bug.
MultiMC CANNOT choose the graphics drivers to use.
It can contort itself into funny shapes by impersonating the Mojang launcher and Java itself and convince the drivers to activate by faking a lot of things.

And that's what I'll do.

[peterix]

For the time being, do not use Windows 10 - 7, 8 and 8.1 are still perfectly fine, no matter what Microsoft says to get you on the new spyware platform.

Or get third party drivers that aren't from Intel or Microsoft.

Or switch to Linux - it has better intel graphics support than Windows.

[Parker8283]

I may or may not have mentioned this, but this is a temp computer that's not technically even mine; I fully intend on making Arch my main OS when I get my new permanent computer ;)

[peterix]

That's fine. It's aimed at anyone reading this. You aren't alone with this issue.

[Wasted31]

Hello there,
just a message to tell you I got the same problem, with Win10, included MC java version or JRE 8 and Intel HD Graphics 2000 chip :

• no pb with official Minecraft launcher
• on MultiMC : no instance sucessfully launch / all crashes are due to LWJGL pixel format not accelerated error

After reading your posts / FAQ, I tried to :

• rename MultiMC.exe in Minecraft.exe => not better
• test other versions of LWJGL using your Youtube tuto => not better
• update my driver version, which already was the last Intel one (but provided for Win7/8)

Nothing worked since I installed JRE 7u80, and chose it in MultiMC parameters !! Now instances launch !

So thanks for the post 👍 , and hope this kind of summary will help others !

[AverageComet250]

@peterix is this still supposed to be open still or is this just an issue everyone forget about and accidently didn't close

[kb-1000]

This is not really a MultiMC issue. However, it is still present, the Intel driver bug (or in Intel's eyes, probably feature) is still there.
I have a Java build that can resolve it without downgrading to 8u51 or Windows 7: https://ci.appveyor.com/project/kb1000/jdk8u/build/artifacts
It will probably soon be resolved by using Mojang's Java build by default.