Intel Arc b580 newest driver update causes modded minecraft curseforge to crash

[Kairan]

As title suggests, the most recent driver update for the b580 graphics card caused my curseforge minecraft mod loader to crash on launch, crash message is attached below. I tried launching empty modpacks with nothing in them, and curseforge still crashes, so it is likely a compatibility issue with curseforge itself and the newest driver update. I tried using DDU to clean install the newest driver, which did not solve the issue. I also tried redownlaoding older drivers, which seems to fix the crash.

[Alkabcxz]

Hi, i am having the same problem how do i redownload older drivers

[Kairan]

You can use the intel driver support assistant to see your driver download history. If you select one of your past downloads I believe you can download previous drivers. 

[Mike_Intel]

Hello Kairan,

Thank you for posting in Intel community Forum.

For me to further check this, please help provide the following details:

1. When did you purchase your unit?
2. How did you update the driver?
3. Are you using an Intel brand Arc B580?
4. What do you mean by Modded Minecraft?

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

[Kairan]

I purchased my card around late December. The driver was updated through the official intel website; I clicked on a intel driver assistant notification which brought me to the website containing the new driver download. I have a sparkle titan b580 bought from newegg online. 

The modded minecraft I was referring in the post was a third party launcher called curseforge, which allows players to launch minecraft with modifications of their choosing that are listed on the launcher. There are other third party launchers that has the same function, such as fabric and modrinth. The issue I experienced might also exist with those launchers as well. 

[djmrFunnyMan]

Fyi curseforge is not a mod loader. It's a minecraft launcher. Same goes for modrinth. The mod loader you're using is called neoforge. You did get fabric right, it is a mod loader.

Anyways the issue is specific to the neoforge mod loader regardless of what launcher the game is started from so curseforge is entirely irrelevant here.

[w1_0]

Hi im having similar problems with my intel arc b580,

it just wont start modded minecraft over curseforge and only give me this error.

 

nevermind found a fix

[HadesDurin]

I have the same Problem trying to play Modded Minecraft using Curse Forge.

My PC is self build 

Fresh Microsoft Windows

Fresh latest Driver 32.0.101.6557 (B580)

I read down the Postings, that the Issue is due to longer Time initiating OpenGL (>10s).

I have no infuence on that part and dont know how to mess around with the debug menu.

Until a Driver update comes out to fix the issue its no minecraft for me

[Mike_Intel]

Hello Kairan,

Thank you for the update.

Please try to reinstall the latest driver using the DDU method.

Kindly check the links below for the steps and the link of the latest driver:

https://www.intel.com/content/www/us/en/support/articles/000091878/graphics.html

https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html

If you have questions, please let us know. Thank you.

Best regards,

Michael L.

Intel Customer Support Technician

[djmrFunnyMan]

@Mike_IntelHello. I would like to provide you with actually useful information about this issue.

The problem is: The most recent intel arc driver update introduced a regression that severely prolonged the time it takes for the OpenGL context to get initialized (its now ~12 seconds or longer)
The neoforge mod loader is configured in a way to time out if OpenGL context initialization takes longer than 10 seconds.

To be clear the extremely long OpenGL context initialization time does also happen with other mod loaders and even vanilla minecraft (possibly other OpenGL applications as well). It's just that only neoforge happens to have this timeout.

For now a pull request has been made to the neoforge github to increase the initialization timeout to 30 seconds: https://github.com/neoforged/FancyModLoader/pull/243

Users may work around this issue in 4 ways:
- Downgrade the intel arc driver to 32.0.101.6557_101.6262
- Disable early window in .minecraft/config/fml.toml (open with notepad) Change "earlyWindowControl" from true to false
- Use the fabric loader instead of neoforge
- Wait for the afformentioned pull request to get merged


So for Intel: The driver is not causing a crash per se, but OpenGL context initialization shouldn't take this long and this regression needs to be adressed. As a possible lead, one mod developer speculated someone at intel left debugging code in the driver which made it into release and severely slowed things down.

[Mike_Intel]

Hello Kairan,

I hope this message finds you well. 

Were you able to check the previous post?

Please let us know if you still need assistance.

@djmrFunnyMan

If you need assistance, please create a new thread for us to assist you on your own thread and gather the details of your systems.

Best regards,

Michael L.

Intel Customer Support Technician

[djmrFunnyMan]

I do not need assistance. I was providing you with information about the issue Kairan is having because I know exactly what's going on (no credit to me, JellySquid spent 2 hours on my PC debugging it herself)

So please read it.

[JohnM_Intel]

Hello Kairan,

I wanted to check if you had the chance to review the questions my colleague Michael posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter. 

Regards,

John Sergio M.

Intel Customer Support Technician

[Lufaces]

As a player who just replaced my RTX3060ti with B580, I can say that the problem still exists now, which made me a little bit disappointed. No matter what launcher you use, Forge will crash while the game is loading. 

Edit: The problem has been solved by the latest driver update. Great job!

[Mike_Intel]

Hello Kairan,

I hope you are having a good day.

I am sending another follow up if you tried our last recommendations. 

Since we have not heard back from you, I need to close this inquiry. 

If you need further assistance, please post a new question as this thread will no longer be monitored. 

Thank you and have a great day. 

@Luface

If you need assistance, please create a new thread for us to assist you on your own thread and gather the details of your systems.

Best regards,

Michael L.

Intel Customer Support Technician

[djmrFunnyMan]

The underlying issue appears to have been resolved in the latest (not WHQL certified) intel driver update. Though neoforged also deployed their own workaround where they increased the opengl initialization timeout.