search

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

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

Forza Horizon 5 crashes on launch #426

Open TheWonderfulTartiflette opened 1 year ago

TheWonderfulTartiflette commented 1 year ago

Checklist [README]

Game / Application [Required]

Forza Horizon 5

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

Intel Core i5-13600K

Graphic Card [Required]

Intel Arc A770 16GB LE

GPU Driver Version [Required]

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

Intel SSU 12.08.2023.txt

Description and steps to reproduce [Required]

Launch FH5

Game graphic quality [Required]

Game resolution [Required]

1920x1080

Game VSync [Required]

On

Game display mode [Required]

Detailed game settings [Required]

Everything to max, XeSS ultra quality

Device / Platform name

ASUS PRIME Z790-P WiFi D4

Crash dumps [Required, if applicable]

Event Viewer : https://1drv.ms/f/s!AmnzYyniwxuygaQJ3cYT3ArDs3R9Bw?e=phAcvE I tried the IGCIT crash dump tool, but it outputted an empty .7z even though I think I enabled the crash dump in IGCIT

Save game

No response

TheWonderfulTartiflette commented 1 year ago

Note: I've tried the obviouses reboot, reinstall etc

Karen-Intel commented 1 year ago

Hey @TheWonderfulTartiflette thank you! Downloading game already, will update soon!

Karen

Karen-Intel commented 1 year ago

Hi @TheWonderfulTartiflette I could not repro the crash on launch running the game on Steam I used the same settings you have and no issues at all, you can see it here Checking your SSU, I see your system BIOS is a bit outdated, there's a new version that was released just a couple months ago. Also, make sure to check your system game files and in case you keep on seeing the crash after the BIOS update and having checked your game files, please send the dump file that is created in this location: \SteamLibrary\steamapps\common\ForzaHorizon5 to analyze it further.

Thanks!

Karen

TheWonderfulTartiflette commented 1 year ago

Hi @TheWonderfulTartiflette I could not repro the crash on launch running the game on Steam I used the same settings you have and no issues at all, you can see it here Checking your SSU, I see your system BIOS is a bit outdated, there's a new version that was released just a couple months ago. Also, make sure to check your system game files and in case you keep on seeing the crash after the BIOS update and having checked your game files, please send the dump file that is created in this location: \SteamLibrary\steamapps\common\ForzaHorizon5 to analyze it further.

Thanks!

Karen

Thanks ! Indeed, surprisingly a BIOS update solved it, thanks a ton :)

TheWonderfulTartiflette commented 1 year ago

Actually no, this still happens, crash log (idk if it's different) : https://drive.google.com/file/d/1MaXQE3qx1B3tZ223EU-l7D45QvCsLqx5/view?usp=sharing

kestrelgone commented 1 year ago

I don't know if this is related, but FH5 consistently crashes to desktop for me unless I have Multi Sample Anti Alias (MSAA) turned off in the in-game graphics options. This is true of FH4 as well. I'm using the Arc A770M and it does not like that setting. It does make the game look worse, but turning it off might help.

TheWonderfulTartiflette commented 1 year ago

I don't know if this is related, but FH5 consistently crashes to desktop for me unless I have Multi Sample Anti Alias (MSAA) turned off in the in-game graphics options. This is true of FH4 as well. I'm using the Arc A770M and it does not like that setting. It does make the game look worse, but turning it off might help.

I was getting this issue already without MSAA but XeSS enabled So I tried to disable XeSS, nothing more happened But I enabled MSAA 8x, and I could play the game for like 5 seconds, and then it crashed. But here, it spitted an error : image (The instruction at [...] uses the memory address [...]. The memory state/status cannot be written)

Karen-Intel commented 1 year ago

Hey @TheWonderfulTartiflette unfortunately the log doesn't say much :( I've been playing the game for a while with an A380 and no crashes so far, these are the scenarios I have tested MSAA > 8x > No crash (I had been playing for around 10 minutes before starting the recording) XeSS > Performance or higher > No crash Here's another video for you Note: CapframeX says I am using UHD 770 but that is wrong. I was using my A380 with UHD 770 enabled too Question, I see you have installed a driver for your VR headset. Could you please uninstall it and see if it makes any difference? It is the only thing that calls my attention and that is different from your setup to mine. Thanks

TheWonderfulTartiflette commented 1 year ago

Hey @TheWonderfulTartiflette unfortunately the log doesn't say much :( I've been playing the game for a while with an A380 and no crashes so far, these are the scenarios I have tested MSAA > 8x > No crash (I had been playing for around 10 minutes before starting the recording) XeSS > Performance or higher > No crash Here's another video for you Note: CapframeX says I am using UHD 770 but that is wrong. I was using my A380 with UHD 770 enabled too Question, I see you have installed a driver for your VR headset. Could you please uninstall it and see if it makes any difference? It is the only thing that calls my attention and that is different from your setup to mine. Thanks

This works, but maybe just for now. I uninstalled Oculus, the game still didn't launch, so I rebooted, and now it launches, and I can play it, but it's not sure that I won't get the same error anytime soon. I'll reopen if I get the error again. Thanks a ton!

Karen-Intel commented 1 year ago

Hey @TheWonderfulTartiflette unfortunately the log doesn't say much :( I've been playing the game for a while with an A380 and no crashes so far, these are the scenarios I have tested MSAA > 8x > No crash (I had been playing for around 10 minutes before starting the recording) XeSS > Performance or higher > No crash Here's another video for you Note: CapframeX says I am using UHD 770 but that is wrong. I was using my A380 with UHD 770 enabled too Question, I see you have installed a driver for your VR headset. Could you please uninstall it and see if it makes any difference? It is the only thing that calls my attention and that is different from your setup to mine. Thanks

This works, but maybe just for now. I uninstalled Oculus, the game still didn't launch, so I rebooted, and now it launches, and I can play it, but it's not sure that I won't get the same error anytime soon. I'll reopen if I get the error again. Thanks a ton!

Sounds great! We're here to help, please help us close in the meantime :) Have a great week

Karen

TheWonderfulTartiflette commented 1 year ago

Okay so this still happens actually my bad, verifying the files doesn't do anything btw, "All the files have been validated"

TheWonderfulTartiflette commented 1 year ago

I tried to relaunch it again, just to see if anything improved even though I didn't change anything. The shaders were compiling, and at around 60% of shader compile, my Windows completely blue screened, here is a .dmp of it : https://drive.google.com/file/d/1MeVK2AJgedAvuZXsEEyPpvx0Wj20StTQ/view?usp=sharing

TheWonderfulTartiflette commented 1 year ago

And the one from event viewer, if that's useful : https://drive.google.com/file/d/1MfKVlk7Je6UTIJoipyC38YUohH0B9HXo/view?usp=sharing

kestrelgone commented 1 year ago

I was getting this issue already without MSAA but XeSS enabled So I tried to disable XeSS, nothing more happened

Interesting. I've been playing with XeSS on and haven't had any crashes with it. I'm not playing the Steam version though, I wonder if that could have anything to do with it.

TheWonderfulTartiflette commented 1 year ago

I noticed that it's a particular graphic setting that makes the game crash. I was playing at high, like normal, and I switched to max. The game crashed, and when I try to relaunch it, it freezes my whole Windows for 10 seconds (even Ctrl Alt Suppr doesn't work!), and spits an error, now different than the last one : image Even made my Windows taskbar glitch a bit with two icons superposed : image

BiZkViT96 commented 1 year ago

@TheWonderfulTartiflette After reading all of this, I think it's not a GPU driver problem.

I advise you to do two things:

Test your ram with MemTest86 https://www.memtest86.com/download.htm Test ONE RAM stick at a time. Keep in mind you need USB flash and test will take quite some time.

Run after all of it System File Checker tool https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

TheWonderfulTartiflette commented 1 year ago

@BiZkViT96 So I've just did it, and on both of my sticks, with a big green PASS at the end. Same for the SFC check. I'll try as soon as I can to launch FH5

Karen-Intel commented 11 months ago

Hi all! Doing some recent testing w/driver v/4826 and no crashes at all in FH5 on launch MSAA 8x XeSS disabled We haven't had any other reports related to launch so I'm thinking this issue has to do with local configuration. @TheWonderfulTartiflette please let us know when you have updated your driver with DDU and report back to us, ty

Karen

kestrelgone commented 11 months ago

Hi Karen,

I'm still getting crashes as long as MSAA is turned on. In my research in trying to solve the problem, it appears to be a pretty common problem with the Arc A770. I'm surprised it's not consistently reproducible for you. It's as predictable as a sunrise for me and my system was built by Intel.

Karen-Intel commented 11 months ago

Hey @kestrelgone! Yeah it seems to be pretty consistent for some but for us it is not :( We will dig deeper, no worries. Just send us your system specs and we will try to find similar configs in the lab, just like we have done with other users :)

Thanks!

Karen

kestrelgone commented 11 months ago

Sure thing. I'm using an Intel NUC 12 Enthusiast Mini desktop. It has an Intel Core i7-12700H processor and comes equipped with both the Arc A770M and Iris Xe GPUs. It's running Windows 10. I added 32 GB of RAM and two 2TB hard drives, but those are the only factory options.. The game is currently installed on the D: drive while the OS is on the C: drive. Here's a link for further info.

https://www.intel.com/content/www/us/en/products/docs/boards-kits/nuc/mini-pcs/nuc-12-enthusiast.html

Thanks, Karen!