F1 23 Crashes to Desktop, No Errors.

F1 2023 also crashes on my pc after a lap or two, or just seeing a video of the breaking point story.

All drivers updated. I have dozens of games in steam and I didn't have an issue like this with any other game.

I bought the game this week, I'll only wait a day or two before asking for a refund of the game.

We shouldn't be the ones changing files or looking for workarounds, the game should work as other games do, period.

---

@Rumaf wrote:

F1 2023 also crashes on my pc after a lap or two, or just seeing a video of the breaking point story.

All drivers updated. I have dozens of games in steam and I didn't have an issue like this with any other game.

I bought the game this week, I'll only wait a day or two before asking for a refund of the game.

We shouldn't be the ones changing files or looking for workarounds, the game should work as other games do, period.

---

You should update your machine. The newer it is, the less it was finished before you bought it.

@SteveJackson :

It's really interesting. After I wrote here around an hour ago, I again deleted the hardware_settings XML file, started F1 23, F1 World Time Trials Monza ... and I was on the race track for full 30mins continuously and no crash occurred. That pattern also still exists. So far, since I bought the game 3 days ago, I tried this 6-7 times, i.e. after a crash deleting the hardware settings XML file, and each time when I did it, with no exception so far, I could then immediately be on the race track with no crash at all. Not a single crash. When I change any settings or, as it was this time, coming back to the game the next day, it crashes consistently on the first 1-2 laps. Not on the 4th or 5th lap, always on the first 1-2 laps. Once the crashes start, I can re-start the game (without deleting the XML file), go on the same race track, and it keeps crashing consistently in the first 1-2 laps. Until I delete again the hardware settings XML file, and so on.

So I guess we have two possibilities:

• Either it is a huge coincidence that it does not crash after having deleted the hardware settings XML file (each single time for all the 6-7 times I tried), while it always crashes within 1-2 laps when it reaches the "unstable state" (statistically pretty unlikely, but not entirely impossible)
• OR it is still somehow related to whatever happens with this file (which is kind of weird as well as a root cause, I admit)

One observation I'd like to add:

When I delete the hardware settings XML file, and start up F1 23 again, then the controller settings and drive assist settings are still here (thankfully). What I have to re-configure each time, however, is the video settings. My PC is connected to a native 4k projector via HDMI. F1 23, when restoring the hardware settings file, sets 1080p as the default resolution. Not sure if that's just a global default you always set or if F1 23 does not recognize the projector's resolution correctly. I have then to set the resolution manually to 2160p and vSync On (projector is fixed on 50Hz, no VRR, etc.), then it's fine and it's fine until again I have to delete the file.

---

@sirupflex wrote:

@SteveJackson :

It's really interesting. After I wrote here around an hour ago, I again deleted the hardware_settings XML file, started F1 23, F1 World Time Trials Monza ... and I was on the race track for full 30mins continuously and no crash occurred. That pattern also still exists. So far, since I bought the game 3 days ago, I tried this 6-7 times, i.e. after a crash deleting the hardware settings XML file, and each time when I did it, with no exception so far, I could then immediately be on the race track with no crash at all. Not a single crash. When I change any settings or, as it was this time, coming back to the game the next day, it crashes consistently on the first 1-2 laps. Not on the 4th or 5th lap, always on the first 1-2 laps. Once the crashes start, I can re-start the game (without deleting the XML file), go on the same race track, and it keeps crashing consistently in the first 1-2 laps. Until I delete again the hardware settings XML file, and so on.

So I guess we have two possibilities:

• Either it is a huge coincidence that it does not crash after having deleted the hardware settings XML file (each single time for all the 6-7 times I tried), while it always crashes within 1-2 laps when it reaches the "unstable state" (statistically pretty unlikely, but not entirely impossible)
• OR it is still somehow related to whatever happens with this file (which is kind of weird as well as a root cause, I admit)

One observation I'd like to add:

When I delete the hardware settings XML file, and start up F1 23 again, then the controller settings and drive assist settings are still here (thankfully). What I have to re-configure each time, however, is the video settings. My PC is connected to a native 4k projector via HDMI. F1 23, when restoring the hardware settings file, sets 1080p as the default resolution. Not sure if that's just a global default you always set or if F1 23 does not recognize the projector's resolution correctly. I have then to set the resolution manually to 2160p and vSync On (projector is fixed on 50Hz, no VRR, etc.), then it's fine and it's fine until again I have to delete the file.

---

I believe 1080 is the default resolution, yes.

In the dxdiag the default refresh for the projector is listed as 60Hz (p).Game maybe can't get the information from the graphics card about the connected display or chooses the Virtual Display and has no information?

---

@SteveJackson wrote:

 

You should update your machine. The newer it is, the less it was finished before you bought it.

---

How do you know that I should update my machine?

13600K in a Gaming X MOBO, 850W PSU, 7200 DDR5 RAM... that's not enough updated to play this game?

If not a solution I just want a message or a log that tells what's the cause of the crash.

I guess what Steve meant is that, because your PC has pretty recent components, there's always the risk that drivers, firmwares, etc. are not fully mature yet, so it would be important to ensure you have the latest version of drivers and firmwares. That would at least be my interpretation of the feedback.

---

@sirupflex wrote:

I guess what Steve meant is that, because your PC has pretty recent components, there's always the risk that drivers, firmwares, etc. are not fully mature yet, so it would be important to ensure you have the latest version of drivers and firmwares. That would at least be my interpretation of the feedback.

---

Exactly what I meant, because it is totally true.

The nvlddmkm issue is an incredibly well known, widely reported bug in every single NVIDIA driver version in the 53X driver set. The last known stable driver was 528.49. I would suggest using DDU in Safemode to completely remove all traces of the garbage driver, and then install the 528.49 drivers.

Thanks for the hint. The strange thing is that this issue only occurs in this very specific situation in F1 23. I didn't have a single crash (or appearance in the event log for this) in any of my other games that I currently play many, many more hours than F1 23. I will, however, keep that in mind as an option to go through if no other solution can be found.

PS: If I stay on nVidia 528.xx driver, then for any issue I report (no matter for which game / software) the immediate answer would be "update your outdated nVidia driver, before that we cannot help" 😉

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.