Crashing on latest 572.** nvidia drivers

[TheBerch]

So, I know crashing is fairly common with this game for a number of reasons. I have a 4080, and tried running the 572.** drivers. I literally tried them all. No matter which one I would use, since the last update to Shadows, when the game would load to 93% when starting the game, my pc would hard crash (literally restarted automatically, no bluescreen) with the nvdia driver being the culprit according to the minidump files.

Since rolling back to the tried and true driver 566.36 I havent had any issues.

Has anyone else experience hard crashes with the game since the latest update, or the 572.** drivers? Kinda bummed that I have to roll back to 566.36 as I am no longer able to use dlss4 unless I manually inject it.

[Etny2k]

I never crashed. Almost 80 hours in. Do you have a 13th or 14th gen intel cpu? You might need to rma it.

[ilmedved]

Just bought the game, got overheats on my laptop with crashes every 20-30 mins. While in KCD2 got zero crashes in 108h with max graphics.

[Slavyk_FR]

Originally posted by TheBerch:

So, I know crashing is fairly common with this game for a number of reasons. I have a 4080, and tried running the 572.** drivers. I literally tried them all. No matter which one I would use, since the last update to Shadows, when the game would load to 93% when starting the game, my pc would hard crash (literally restarted automatically, no bluescreen) with the nvdia driver being the culprit according to the minidump files.

Since rolling back to the tried and true driver 566.36 I havent had any issues.

Has anyone else experience hard crashes with the game since the latest update, or the 572.** drivers? Kinda bummed that I have to roll back to 566.36 as I am no longer able to use dlss4 unless I manually inject it.

There is a know issue with that and 40xx gpus. I have the same problem with Star Wars Outlaws and the 572.x drivers.
Just disable the framegen and you won't get those crash anymore.

[Etny2k]

Originally posted by Slavyk_FR:

Originally posted by TheBerch:

So, I know crashing is fairly common with this game for a number of reasons. I have a 4080, and tried running the 572.** drivers. I literally tried them all. No matter which one I would use, since the last update to Shadows, when the game would load to 93% when starting the game, my pc would hard crash (literally restarted automatically, no bluescreen) with the nvdia driver being the culprit according to the minidump files.

Since rolling back to the tried and true driver 566.36 I havent had any issues.

Has anyone else experience hard crashes with the game since the latest update, or the 572.** drivers? Kinda bummed that I have to roll back to 566.36 as I am no longer able to use dlss4 unless I manually inject it.

There is a know issue with that and 40xx gpus. I have the same problem with Star Wars Outlaws and the 572.x drivers.
Just disable the framegen and you won't get those crash anymore.

I have a 4080 super, latest driver and can run in game frame gen just fine.

[Slavyk_FR]

Well you're a lucky one then. If I enable framegen the computer crash and reboot after 40-45mn of running the game.
The problem has been aknowledged and Ubi is working with nVidia on it.

[Slavyk_FR]

A lot of people are in the same situation as you OP...
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/557942/572xx-system-rebooting-crashes-when-frame-generati/

[OAXIOM]

man am i glad to see this post. The game just randomly crashes to desktop and i thought it was just me. Ive just been dealing with it for now lol the game saves right where i left off so not terrible just frustrating.
Not using Framegen
Ive just turned off GSync as per solution in the Nvidia forum, lets see how that goes.

[TheBerch]

Originally posted by Etny2k:

I never crashed. Almost 80 hours in. Do you have a 13th or 14th gen intel cpu? You might need to rma it.

I have a 9800x3d, so no, not a 13th or 14th gen, but that wouldnt have mattered anyway. As I said, I looked at the dump files, and each crash is due to the nvidia drivers. Rolled back to 566.36 and zero issues.

[TheBerch]

Originally posted by Etny2k:

Originally posted by Slavyk_FR:

There is a know issue with that and 40xx gpus. I have the same problem with Star Wars Outlaws and the 572.x drivers.
Just disable the framegen and you won't get those crash anymore.

I have a 4080 super, latest driver and can run in game frame gen just fine.

I was going to say the same thing. Before the latest update to the game, i had zero issues with the 572.** drivers, also running framegen. Not a HUGE deal, but still annoying none the less. Between this game and MH Wilds, these optimizations are driving me nuts.

[TheBerch]

Originally posted by Slavyk_FR:

A lot of people are in the same situation as you OP...
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/557942/572xx-system-rebooting-crashes-when-frame-generati/

Yeah, I was reading through them all. I may try swapping out my DP cable to my HDMI 2.1 cable. Worth a shot. Otherwise I will just be sticking with 566.36 for a very long time, and just manually injecting dlss4

[Etny2k]

Originally posted by TheBerch:

Originally posted by Etny2k:

I never crashed. Almost 80 hours in. Do you have a 13th or 14th gen intel cpu? You might need to rma it.

I have a 9800x3d, so no, not a 13th or 14th gen, but that wouldnt have mattered anyway. As I said, I looked at the dump files, and each crash is due to the nvidia drivers. Rolled back to 566.36 and zero issues.

A faulty cpu can cause driver crashes. I am not saying that is it just pointing it out.

[TheBerch]

Originally posted by Etny2k:

Originally posted by TheBerch:

I have a 9800x3d, so no, not a 13th or 14th gen, but that wouldnt have mattered anyway. As I said, I looked at the dump files, and each crash is due to the nvidia drivers. Rolled back to 566.36 and zero issues.

A faulty cpu can cause driver crashes. I am not saying that is it just pointing it out.

It wont cause nvidia driver crashes which is what the dump reports were all showing. A bad cpu can cause CRASHES, but not driver related crashes, thats software and not hardware related.

[aRg]

I had to roll back to 566.36 on my 4080, the latest drivers was giving me BSOD, stutter etc. First I was convinced is was a component failure in my PC but , RAM check and stress tests worked fine.

[Ubi-Vinci]

Thank you for your feedback, aRg.

We will keep an eye on the situation with the latest Nvidia drivers and monitor crash complaints from Nvidia users.

[TheBerch]

Originally posted by aRg:

I had to roll back to 566.36 on my 4080, the latest drivers was giving me BSOD, stutter etc. First I was convinced is was a component failure in my PC but , RAM check and stress tests worked fine.

Yup, its been a problem on both nvidia sides and shadows im sure. But rolling back to 566.36 has been the go to for anyone on a 40 series or older gpu. 50 series are kind of SOL and have to use the newer 572 drivers.