Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
22388 Discussions

Elden Ring: Nightreign – White Screen Crash Caused by Driver, Not GPU

Alex487
Beginner
2,474 Views
Dear Intel Support,

I’m writing to report a critical issue with Elden Ring: Nightreign on systems using Intel Iris Xe graphics. The game crashes instantly on launch with a white screen and never reaches the main menu.

To troubleshoot, I have:

Installed the latest driver (32.0.101.6874).

Tried older drivers (e.g. 27.x.x — which launches the game but shows a red tint, making it unplayable).

Repaired Easy Anti-Cheat.

Verified game files and system integrity.

Tried compatibility mode, clean boot, and other standard fixes.


Most importantly, when I disable the Intel GPU and run the game with the Microsoft Basic Display Adapter, the game successfully launches (though at ~5 FPS). This confirms the GPU is not the bottleneck, but rather the driver is causing the crash.

Please don’t tell me that Nightreign is a new game my system doesn’t meet the requirements for — guess what? That was the same case with Elden Ring, and even heavier titles like Black Myth: Wukong, God of War: Ragnarok, and The Last of Us — all of which run on this system.

If the GPU were truly the issue, the game would at least launch to the main menu. But here, it crashes immediately. For reference, here’s a YouTube video showing the crash behavior:
https://youtu.be/Su3KDYc9AS4?si=nVTsVRvcVqnoIcf0

Please escalate this to your driver team — the problem is clearly software-side. Many users are affected and waiting for a fix.

Regards,
Lokanath Sahoo
Labels (1)
15 Replies
SalesDW
Novice
2,420 Views

Up

People talking about the subject has cooled down a lot here, and I'm pretty hopeless that they'll actually do something, but we can't give up lol, I really want to stress out in Nightreign

0 Kudos
Rudra2
Novice
2,417 Views

Already made two posts , waiting for their response , if they don't take a step , we cannot do much , i guess 

0 Kudos
Mcrbgamer
Beginner
2,355 Views
Up
Day1
0 Kudos
Retlr
Beginner
2,195 Views
Unfortunately the newest driver update released on 6/9 does NOT fix this issue like I was hoping it would
0 Kudos
ArchieD_Intel
Moderator
2,160 Views

Hi Alex487,

 

Thank you for reaching out to the Intel Community Forum. To assist us in investigating the issue, please provide the following details:

 

  • Have you tried using the OEM driver for testing?
  • When did the issue start? Was it after a specific driver update or game patch?
  • Have you used DDU to completely remove all residual drivers and installed a new one?
  • Which gaming platform did you use to download the game?

 

Additionally, to gain a comprehensive understanding of your system, please use the System Support Utility (SSU). This tool will generate a text file compiling all your system information. You can follow the instructions at this link and send the text file here. Help Guide for the Intel® System Support Utility.

 

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

 

Hi @SalesDW@Rudra2 , @Mcrbgamer and @Retlr please create a different thread so we can focus on your own concern. Thank you.

 

Best regards,

 

Archie D.

Intel Customer Support Technician

 

0 Kudos
Rudra2
Novice
2,113 Views

@ArchieD_Intel  ,  I am sorry , but you don't understand the fact , that  every user is facing same issue related to intel iris Xe , while trying to run elden ring Night reign , i understand you are trying to do your job and make sure its not user error but trust me ,but its not , i have tried all latest drivers , and everything points towards drivers issue 

 

After debugging the game Through x64 debug :- 

1. **Crash Location**:  
   - Module: igd12um64xel.dll (v32.0.101.6795)  
   - Offset: 0x00000000000BEB40  
   - Exception: 0xC0000005 (ACCESS_VIOLATION)  

2. **Call Stack**:  
   - Fault occurs during DirectX 12/Vulkan command execution.  
   - ntdll!RtlGetReturnAddressHijackTarget detects stack corruption.  

3. **Registers at Crash**:  
   - RAX: 0x00000000 (NULL)  
   - RIP: igd12um64xel.dll + BEB40  
   - LastStatus: C0000034 (OBJECT_NAME_NOT_FOUND)  

  • Faulting module: igd12um64xel.dll (Intel’s official GPU driver).

  • Crash offset: 0xBEB40 (a specific function in Intel’s code).

  • No game/mod code was executing when it crashed.

🔹 Conclusion: The game sent a normal GPU command, and Intel’s driver failed to handle it.

This is all i found with help of ai and x64 debug , i cannot say everything is correct but this is what i could gather 

All i am trying to is help , since its been more than a week and no progress

SalesDW
Novice
2,088 Views
Good job bro, I tried to do that but I didn't understand anything and gave up lol. I understand that these guys have support rules, but **bleep**, more than 20 people sending the same problem, in the same game, with the same video card (intel iris xe) and they still come asking as if the problem was unique to the user like what? Don't these guys read their own support?
0 Kudos
Rudra2
Novice
2,086 Views

@SalesDW  , thats the problem , i believe that they havent reported the problem to their driver team , since new driver came yesterday and it still isnt fixed , if they dont report it , we just have to keep doing this

SalesDW
Novice
1,857 Views

Yes, at least now that we have this debug, we can send it in the post responses so they know what the exact error is, another progress in our fight lol.

DxCode
Novice
1,337 Views

I'm also curious. I've been debugging using Windows Event Viewer, and the error here also occurs in the igd12um64xel.dll file.

I think debugging at this level is sufficient to see that "there's indeed a problem with the GPU driver, not the GPU itself." At another time, I'll try to debug further to see the specific issue.

 

debug output using windows event viewer:

=================================================================================

Faulting application name: nightreign.exe, version: 1.1.2.0, time stamp: 0x683ee31e
Faulting module name: igd12um64xel.dll, version: 32.0.101.6129, time stamp: 0x6712b200
Exception code: 0xc0000005
Fault offset: 0x00000000000b6bb0
Faulting process id: 0x29C8
Faulting application start time: 0x1DBDAD187DFCDC8
Faulting application path: E:\steam\steamapps\common\ELDEN RING NIGHTREIGN\Game\nightreign.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_f93b33e201f14a12\igd12um64xel.dll
Report Id: e024d9d4-98f1-427d-8119-71ff95615644
Faulting package full name:
Faulting package-relative application ID:

=================================================================================

brief explanation:

  • Exception code: 0xc0000005 (This is an ACCESS_VIOLATION. It means that the Intel driver is trying to access memory that it shouldn't.)
  • Fault offset: 0x00000000000b6bb0 (This is the specific address within the igd12um64xel.dll file where the crash occurs.)

  • Faulting application path: E:\steam\steamapps\common\ELDEN RING NIGHTREIGN\Game\nightreign.exe (Location of the game executable file.)
  • Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_f93b33e201f14a12\igd12um64xel.dll (Full location of Intel driver file causing crash.)

 

0 Kudos
Mcrbgamer
Beginner
1,901 Views
Up day 2
0 Kudos
asamiya
Beginner
1,816 Views

Up

0 Kudos
Mcrbgamer
Beginner
1,702 Views
Up day 3
0 Kudos
Mcrbgamer
Beginner
1,622 Views
Up day 4
0 Kudos
ArchieD_Intel
Moderator
1,325 Views

Hi Alex487,

 

I have checked this and I would like to inform everyone that the Intel Iris Xe Graphics does not meet the minimum specifications established by the game developer. While some users may have been able to run previous versions or similar games, this particular version appears to use updated rendering features that are either not supported or unstable on this hardware. We recommend contacting the game developer directly, as they are in the best position to determine if support or a workaround can be provided.


I will be closing this inquiry. If you need further assistance, please submit a new question, as this thread will no longer be monitored.

 

Best regards,

 

Archie D.

Intel Customer Support Technician


0 Kudos
Reply