AMD GPU Driver Timeout and F1 24 Game Crash

I should also say that this is when I play on a screen. 
Separately I also had crashes in VR with practice programs in career mode as already noted in a separate thread. Because of those crashes in VR I transitioned back to the screen where I have the issues mentioned in my above post.

Not sure if this is correct - but I tried

---

@TheAfrican308 wrote:

I am on PC with the following specs: Ryzen 5800x CPU, AMD 7900XTX GPU, on an SSD. I play on a wheel and have a Fanatec CSL DD with a Formula V2.5 rim. 
After the patch 1.3 update I now have AMD driver timeouts with the game crashing to desktop after a few minutes. This has occurred in races, as well as in the driver career menus. It has rendered the game unplayable for me as I can only be in the game for ~10 minutes before a crash now. 

I am not sure if this is an AMD or a F1 24 game issue. Although I did have a few random crashes prior to the patch 1.3, it is now a consistent problem. I have verified the game on Steam, re-installed AMD drivers, multiple PC restarts over several days. I did also do the Silent Crash workaround posted in the forum. All without success. 

---

No timeouts. 5600X, RX6800, NVMe, Fanatec CSL-E, F V2.5 same 24.5.1 driver. Not a driver issue.

@2euoxqb272hq @TheAfrican308 

Try these steps, thanks.

• Make sure your display is connected to your GPU and not the motherboard video output
• Run System File Checker to help ensure the integrity of your Windows System files: http://support.microsoft.com/kb/929833
• Perform a clean boot before starting: http://support.microsoft.com/kb/929135 or http://help.ea.com/en/article/how-to-clean-boot-your-pc/

I think I have found a fix.

I usually run the wheel and pedals into my PC separately. This week I remembered that F1 22 crashed when a wheel and pedals were separated with Fanatec specifically.

I tried plugging my pedals into my wheel instead and have not had any crashes since.

All the Best! 

same here

Can I just ask if you are running the latest Fanatec Driver and have updated firmware?

Because I can't believe what has been fixed previously is managing to become unfixed unless there is another factor at play. The other variable is code reversion via process failure.