F1 23 Crashes to Desktop, No Errors.

---

@Rumaf wrote:

OK, thanks @sirupflex for the explanation, my bad english misunderstood the post. And thanks @SteveJackson for trying to help.

But as I said on my first post, all the drivers are updated, I triple or quaduple-checked that, also with software to scan drivers.

There is no way to know which was the cause of the crash? I don't want more blind tries because I will go over the 2 gaming hours that will forbid me to ask for a refund.

---

I just don’t understand why you don’t post a dxdiag because it happens all the time that people don’t see updates because of the way they check.

Also I never heard of any of my update suggestions causing issues.

The file itself (dxdiag) may highlight combinations of hardware or configurations that can be problematic. WER is also handy and although not always conclusive is helpful in the round.

I will agree Nvidia drivers are spaghetti. 80 of the issues are PCs containing their cards. Different issues, sure.

Hi @sirupflex , @SteveJackson 

I'm also facing the same issue, the game is rebooting my machine in 1-2 laps after an audio glitch, the screen freezes for 1 second and then reboots my machine.

You have mentioned to remove the hardware settings XML file, but I see 2 files in the below location namely 

1. hardware_settings_config.XML

2. hardware_settings_info.XML

Do I have to remove all files, any one? 
Location: C:\Users\Admin\Documents\My Games\F1 23\hardwaresettings

Please also find my DxDiag.txt file attached.. My main board is: Gigabyte Technology B550M DS3H

---

@gkimiraikkonen7 wrote:

Hi @sirupflex , @SteveJackson 

I'm also facing the same issue, the game is rebooting my machine in 1-2 laps after an audio glitch, the screen freezes for 1 second and then reboots my machine.

You have mentioned to remove the hardware settings XML file, but I see 2 files in the below location namely 

1. hardware_settings_config.XML

2. hardware_settings_info.XML

Do I have to remove all files, any one? 
Location: C:\Users\Admin\Documents\My Games\F1 23\hardwaresettings

Please also find my DxDiag.txt file attached.. My main board is: Gigabyte Technology B550M DS3H

---

Just hardware_settings_config.xml

---

@gkimiraikkonen7 wrote:

Hi @sirupflex , @SteveJackson 

I'm also facing the same issue, the game is rebooting my machine in 1-2 laps after an audio glitch, the screen freezes for 1 second and then reboots my machine.

You have mentioned to remove the hardware settings XML file, but I see 2 files in the below location namely 

1. hardware_settings_config.XML

2. hardware_settings_info.XML

Do I have to remove all files, any one? 
Location: C:\Users\Admin\Documents\My Games\F1 23\hardwaresettings

Please also find my DxDiag.txt file attached.. My main board is: Gigabyte Technology B550M DS3H

---

You will need updates, similar to most advice.

UEFI BIOS and mainboard drivers.

ill post pointers later.

F18c (I have the same AGESA, please load and save defaults first)

Audio driver 9373 (I use the same driver)

v5 chipset driver (I use these drivers, uninstall any older drivers first from Add/Remove Programs and reboot)

Toggle DLSS/TAA Anti-aliasing to see if that has a bearing. 

DDU and reinstall Nvidia driver (546.01 is latest) as a last resort.

Verify Steam / EA files, delete hardware_settings_config.xml before launching game.

Good luck!

Thanks @SteveJackson will do this..

Without removing/renaming the hardware config file I opened the game yesterday and was able to finish a 5 lap race. 

The last I had opened the game was like 2 months ago, I'm not sure if a recent update resolved this issue, or some corrupt cache memory got deleted.. Will be testing this game for a few weeks and will let you know if there are any updates

---

@gkimiraikkonen7 wrote:

Thanks @SteveJackson will do this..

Without removing/renaming the hardware config file I opened the game yesterday and was able to finish a 5 lap race. 

The last I had opened the game was like 2 months ago, I'm not sure if a recent update resolved this issue, or some corrupt cache memory got deleted.. Will be testing this game for a few weeks and will let you know if there are any updates

---

Deffo do the updates mate, your PC will run much better and even be more secure. There aren't many AMD security vulnerabilities but the update natches all of them.

Hi, just an update on the testing I've done till now...
1. Removing the hardware config file didn't do any changes to the crashing. The game crashes my PC even after removing this file.

2. Removing the entire 'F1 23' folder which consists the hardware config file also didn't solve the issue.

3. Removed Steam download cache files. Need to login to Steam again once I've done this. The game still crashes my PC. After doing this, the game crashes on the 6th lap, not on the usual 1-2 laps.

I've tried all of these in F1 World -> Grand Prix -> F2 2022 as I have an ongoing race weekend in it. I'm now starting to wonder if it is a bug with the F2 2022 module itself. Will again have to test all of these in other modules like F1 2023, F2 2023, Career, Braking Point, etc...

---

@gkimiraikkonen7 wrote:

Hi, just an update on the testing I've done till now...
1. Removing the hardware config file didn't do any changes to the crashing. The game crashes my PC even after removing this file.

2. Removing the entire 'F1 23' folder which consists the hardware config file also didn't solve the issue.

3. Removed Steam download cache files. Need to login to Steam again once I've done this. The game still crashes my PC. After doing this, the game crashes on the 6th lap, not on the usual 1-2 laps.

I've tried all of these in F1 World -> Grand Prix -> F2 2022 as I have an ongoing race weekend in it. I'm now starting to wonder if it is a bug with the F2 2022 module itself. Will again have to test all of these in other modules like F1 2023, F2 2023, Career, Braking Point, etc...

---

I don't recommend any of the steps you've tried.

Simply deleting the hardware_settings_config.xml is sufficient - it effectively uses a "File exists? Use it. File does not exist? Re-create it." methodology. Starts the game in 'safe' mode', effectively re-probing the hardware.

Deleting random folders is never recommended or messing with Steam settings is only advised if there is anything in the release notes. Update the client and read the update history if there's an issue. People always ready to blame Steam; it's not the answer this time just because there may have been issues in the past. Rather a knee-* response.