I play Forza Horizon 5 on PC (Microsoft store version) never had a single bug but since the last update i cant play more than 30/40 minutes and them the game freeze and close without any error code or something like that. I already tried a lot of fixes but no luck… Disable all avast shields, unplug my razer mouse and keyboard and close razer app, run the game as admin, uninstall and reinstall the game, uninstall FRAPS, update nvidia drivers, update Windows 10, reset Microsoft store, reset xbox app, checked forza horizon 5 files trought the xbox app, turned vsync on in game and limite my fps to 144 cause is my screen hz and use my corsair headphones with usb cable insted of wireless mode. I already tried a lot of things as you can see and no luck. I hope for a fix as fast as possible cause i would like to play the game i PAID!
RAM: 32Gb
CPU: Ryzen 7 3800x
GPU: Rtx 2070s
OS: Windows 10
SSD M2: western digital
I had this happen a year ago and fixed it by swapping my motherboard, however, now it’s back. I have no idea what could have caused the crash. There’s no CPU overload, memory leak, overheating, nothing. I cannot find anything relevant in the Event Viewer.
Forza support wasn’t very helpful, repeating themselves even after I said that none of the possible solutions they presented worked. I’ve been told to report the issue to the Microsoft Feedback Hub, but I haven’t received a reply to this day. Reports with the same issue already posted on the app are also ignored.
The sad thing is that this doesn’t only happen to FH5 but also to FH4. I honestly don’t know what to do.
I have the same error expect only 3-5 min in. I have a 3060 and same specs as you otherwise. I can’t afford to upgrade my motherboard so that is not the issue
Go back to 561.09 Nvidia update that’ll fix the crashes
4 Likes
+1. Seems to happen during multiplayer events the most. Did start happening after updating my Nvidia drivers, so suggestion above might work as a workaround. But, you know, I play other games, so not really a realistic option.
Reverting back to 561.09 did indeed fix the issue.
2 Likes
Yeah I got frustrated at did the rollback. Seems to have worked.
2 Likes