IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
116 stars 4 forks source link

Marvel's Spider-Man: Miles Morales driver crash in last mission (always) #262

Closed paulober closed 1 year ago

paulober commented 1 year ago

Checklist [README]

Game / Application [Required]

Marvel's Spider-Man: Miles Morales

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

Ryzen 7 5800X

Graphic Card [Required]

Intel Arc A770 (LE)

GPU Driver Version [Required]

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

10.0.22621.1344

Intel System Support Utility report

igcit_ssu.txt

Description and steps to reproduce [Required]

In the final mission of the game you can get to the roof of the building and the fight against the guards and face the sunset. This always results in an error message that the driver is not responding. But only in 1 out of 5 cases does the game actually close and display the error message, followed by a "Send Report" dialog. In the other 4 cases, it just gives up while playing the same sound over and over again without updating any frame. The crashes can also be recognized by the fact that it is not possible to get another window into the foreground. The only possibility is then Alt+14. (notice the game is running in Exclusive-Fullscreen mode in my case)

Final issue when the game crashed: 0x887A0006: DXGI_ERROR_DEVICE_HUNG Also the message in the dialog was (translated from German): A problem occured with the display driver. A reasobn for this could be outdated drivers, higher game settings as you GPU could handle, or an error in the game. Please try, updating you GPU driver or lowering the game settings. Current GPU and GPU driver: Intel(R) Arc(TM) A770 Graphics, 31.0.101.4146

Game graphic quality [Required]

Game resolution [Required]

3440x1440

Game VSync [Required]

On

Game display mode [Required]

Detailed game settings [Required]

Here are my graphics settings: (That's a registry file as the games saves the graphics settings per user in the registry so installing this .reg file will automaticly set all my settings) SpiderManMilesMoralesGraphicsSettings.reg.zip

I have all settings maxed and all raytracing effects enabled. Also XeSS is running in Quality mode without Dynamic Resolution Scaling.

Device / Platform name

Desktop

Crash dumps [Required, if applicable]

I think that's the Windows event logging manifest warning message which occured while the game crased the one time it shows the error message: SpiderManMileMoralesCrash.evtx.zip

Screenshot of Error message shown by the game Final issue when the game crashed: 0x887A0006: DXGI_ERROR_DEVICE_HUNG Also the message in the dialog was (translated from German): A problem occured with the display driver. A reasobn for this could be outdated drivers, higher game settings as you GPU could handle, or an error in the game. Please try, updating you GPU driver or lowering the game settings. Current GPU and GPU driver: Intel(R) Arc(TM) A770 Graphics, 31.0.101.4146

InsomniacGamesSomethingWentWrong

Last IntelGFXFwUpdateToolLog.log:

[IntelFWUpdateService]: IntelGfxFwUpdateTool Version:4.2.1 
Current Time Stamp is : 2023/3/10-15:33:7
[IntelFWUpdateService]: FwUpdateServiceThread started 
[IntelFWUpdateService]: initialize Oprom Update param started
[IntelFWUpdateService]: Skip Update Value: 1.
[IntelFWUpdateService]: Skip Update is set. Skipping the Oprom Update Flow!!!

[IntelFWUpdateService]: initialize Ifwi data Update param started
[IntelFWUpdateService]: Ifwidata Skip Update Value: 1.
[IntelFWUpdateService]: Ifwidata Skip Update is set. Skipping the Oprom Update Flow!!!

[IntelFWUpdateService]: for OPROM!!! Search Folder : dg?_*.rom

[IntelFWUpdateService]:Total OPROM File Count = 0
[IntelFWUpdateService]:Total OPROM Code File Count = 0
[IntelFWUpdateService]:Total OPROM Data File Count = 0

[IntelFWUpdateService]: for IFWI data bin!!! Search Folder : dg?_*.bin

[IntelFWUpdateService]:Total IFWI Data File Count = 0
[IntelFWUpdateService]: Exit FwUpdateServiceThread
Current Time Stamp is : 2023/3/10-15:33:17
[IntelFWUpdateService]: Exit Thread

igcit-dumps_71fcb2f7.7z.zip

And here is a screen-recording of the game crash (three times): Recording.mp4 OneDrive

Save game

No response

paulober commented 1 year ago

The same error causes Project 401 (the titanic recreation) demo based on Unreal Engine 5 to crash when trying to load the game. I have not made a screenshot of the error there yesterday. So i tried to reproduce and now i get following error: Screenshot 2023-03-11 173402 Again it seems like it as something to do with the GPU gets "removed" from the games renderer.... (just my uneducated guess) After changing the resolution it seemed to work for while. But now when ever i enter a special room it crashes a again (every time). Here is a screen-recording of the bug in this game showcaseing how diffrent settings affect when the crash happen and how a certain area always causes the engine to crash.

screen-recording (OneDrive)

Since the two games don't use the same engine there could be either a bug in both engines or in the Arc GPU driver (or sth else)...

Arturo-Intel commented 1 year ago

Hi @paulober !

Thank you for sharing this!

I will try and reproduce this issue here in the lab, I just have some troubles opening the igcit-dumps_71fcb2f7.7z.zip file image If you can share the pass or resend the zip file without it :)

Thank you for all the evidence you provide, this help us a lot!..

-- r2

IGCIT commented 1 year ago

@Arturo-Intel you can retrieve the password via internal api (this is temporary method and soon will be replaced) @Bryce-7995 has the instructions, can you please send them to Arturo?

Arturo-Intel commented 1 year ago

BTW is there a way to share the save file you are using @paulober ?

paulober commented 1 year ago

@Arturo-Intel

The Intel tool specifically says not to upload the password, so I thought that was sufficient. But anyway, here it is: 3357972699db835bcfcde01b7f08080e

And here is some additional information:

The ingame log from one of the crashes detected by the game engine: Marvel's Spider-Man Miles Morales.log (I think it should also contain some usefull information like:

(00010608) > [D3D] ERROR! Device removed detected (0x887A0006: DXGI_ERROR_DEVICE_HUNG)
...
(00010608) > [Crash] Unhandled exception at address 0x000000005e4c5b90 (code: 0xc0000005): "Access violation"

Here is the mini dump file the log is mentioning: Marvel's Spider-Man Miles Morales-v2.209.0.0 2023-03-10-20-58-19.mdmp.zip

And here are the game saves (i don't know which one is needed as they three where all created at the same time): Saves.zip

paulober commented 1 year ago

I will try and reproduce this issue here in the lab, [...]

Thank you for all the evidence you provide, this help us a lot!..

-- r2

Thank you for taking care of this problem.

Glad I can help...

Arturo-Intel commented 1 year ago

Yep, I can replicate the issue, I will share this to the team and start the process, just keep in mind that the fix may take from 3 up to 6 months to be included, so please keep your drivers up to date and do not close this post until a fix has been released.

Thanks again for helping us reporting it :)

Arturo-Intel commented 1 year ago

Hello @paulober

Can you try with the latest driver? 4255

I was unable to reproduce it :)

--r2

paulober commented 1 year ago

@Arturo-Intel Still the same issue with Driver version 101.4255 and Windows 11 22H2 Build 22621.1635.

2023-04-26 Screenshot 2023-04-26 180434

Here is the game log of the crash: Marvel's Spider-Man Miles Morales.log (If it helps i could provide the in the log mentioned memory dump (mdmp) if it only included the games memory and no steam creds.)

Arturo-Intel commented 1 year ago

Thank you for the info, still I am unable to reproduce the issue. I update to the driver 4314, w/o seeing the issue here.

Can you please try with 4314?

paulober commented 1 year ago

I think you mean 4369. It resolved my issue, the game now does not crash anymore at this state. Thought i see the same "Device Lost" exception with Vulkan and "Zelda Tears of the Kingdom" running in an Emulator. Any ideas where these device lost errors come from any why they were only fixed for Spider Man Miles Morales now and not fully? And why does Intel always want you to run DDU, NVIDIA and AMD doesn't and their driver doesn't have a problem with it...

Arturo-Intel commented 1 year ago

@paulober thanks for confirm the fix in your end. About the "device lost" exception in vulkan: there are several ways to do the same thing, in this case to enable a vulkan device. It is quite possible that the way that is was implemented on Miles Morales is different that it was on the Switch emulator. Please share this issue to the emulator developers, maybe they can come to us and we can look for a fix. About the DDU: It simple, with this software we can be sure there is non corrupted data of pass drivers in your end. Its a measure to discard any driver corruption/garbage left.

--r2

paulober commented 1 year ago

@Arturo-Intel Thanks for the explantation. I'll report to them.