• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New Nvidia drivers

K

KickAssCop

[H]F Junkie
2FA
Joined
Mar 19, 2003
Messages
9,659
Seems a few things are happening with me since I uploaded to new Nvidia drivers.

On native resolution, frame rates are choppier than before. I especially noticed this in Black Ops 6 while playing MP in Nuketown where I was getting frame drops under 100 when throwing nades etc.

Second on Stalker 2 VRR flicker is back in the menu. Still checking the game to see if this persists and trying out new DLSS modes but the menu flicker under compiling shaders is there now which was fine before. I didn’t change anything else in my computer except NV drivers.

Thoughts? Experiencing similar issues?
 
I've always had bad VRR flicker with Stalker 2, the new driver didn't seem to change that one way or the other for me. They did mention in the changelog that they "fixed" some VRR flicker instances...maybe it made it worse in your case?

1738310522930.png
 
Yeah I didn't have any VRR flicker before. And I am using same settings - maxed out with TAA.
Probably need to roll back to previous drivers as these ones seem a bit shit.
 
Ok this driver is completely bugged. Second time my computer didn’t wake up correctly. I am rolling back. What a shit show as always with new card launch drivers.
 
Was getting DCOM errors and what not. Reverted back and life is normal again.
 
I had to clean install 572.16. My PC went black screen during the install from the hotfix driver, forced me to hard reset the PC. The driver looked to be installed, but hardlocked the PC when I tried to play the updated Hogwarts.

DDU'd in safe mode, reinstalled 572.16, and now everything is working fine - I'd try that.
 
https://www.nvidia.com/en-us/geforc...rce-grd-57216-feedback-thread-released-13025/

Reading the dumps on the GeForce community shows that the driver is causing issues with the video card's memory (misaligned instruction pointer, null memory pointer, etc.). Somebody's cat jumped onto their keyboard while they were away and they didn't fix the errors before pushing the driver out.
arestavo said:
I had to clean install 572.16. My PC went black screen during the install from the hotfix driver, forced me to hard reset the PC. The driver looked to be installed, but hardlocked the PC when I tried to play the updated Hogwarts.

DDU'd in safe mode, reinstalled 572.16, and now everything is working fine - I'd try that.
Click to expand...
Some people are saying this didn't work for them.
 
I am going to wait for the next iteration. It’s not like I have a 5090 in my putter.
 
I installed the new drivers on two of my PC's. The lappy took it without issue, my Plex box........ the driver doesn't see the gpu. Have to revert that one and probably hold off on installing on other boxes.

On retrospect, the lappy got the studio driver, but I wouldn't think that would make that much of a difference.
 
Last edited:
Any driver after 351.XX should work just fine with the nvidia app update, unless they artificially limit it. All you would need to do for the transformer is take the 310.2.1.0 DLSS dll and overwrite whatever was included with your driver. I'd give clearer instructions, but I'm at work.
 
Last edited:
When I first installed the driver, it did give me a black screen for some reason and I had to hard boot. Killed my remote connection, too. After that it's seemed fine, though.
 
Armenius said:
https://www.nvidia.com/en-us/geforc...rce-grd-57216-feedback-thread-released-13025/

Reading the dumps on the GeForce community shows that the driver is causing issues with the video card's memory (misaligned instruction pointer, null memory pointer, etc.). Somebody's cat jumped onto their keyboard while they were away and they didn't fix the errors before pushing the driver out.

Some people are saying this didn't work for them.
Click to expand...
I'm shocked!

(no, I'm not shocked - the PC ecosystem is massively varied, and there's also a massive skill gap there that contributes as well)
 
I'm finding that I can no longer alt-tab when running a full screen app using these drivers. Doing so causes just a black screen and I am unable to switch to any other application or access my windows desktop. The only fix is to power down my machine. Running the 571.96 drivers I did not have this issue.
 
May or not be relevant, but, I had a problem with NV drivers this week, too. Not the 50 series version, but 566.36. I swapped a 4090 for a 3090Ti in a system that had been updated a few months ago from the 3090Ti to the 4090. I ended up getting hard locks in F@H and massive issues in Division 2 leading to a CTD. Reinstalled drivers, no joy. I removed and DDU'd the drivers, reinstalled and all was fine.

Sounds to me like there are some challenges with updating the latest drivers and we need to follow best practice of removing old and DDU'ing the system before updating.
 
Hitman World Of Assassination won't launch at all on the epic store. The screen goes black and locks up. Reverting to previous drivers fixes the problem.
 
I’m very happy with the new driver on 3090. A nice boost with DLSS quality in Diablo 4.
 
Every game just says "Unsupported" for DLSS Override in the app, is that normal? I tried reinstalling the driver but no luck. They seem to be working fine otherwise.
 
I couldn't take this anymore. Reverted back to December drivers. Everytime I was coming back to my PC one thing or the other was causing an error. Fuck these drivers. That is all. Plus I wanted my VRR back.
 
Is the new driver worth installing? I don't want to go through the BS with the 5090 release drivers again.
Anyone who can check will be appreciated.
 
I got a BSOD when playing BF2042 last night, mini dump indicated it was a problem with the driver or the card. I ran DDU in safe mode and reinstalled the 572.42 and everything seems fine, I managed several rounds with no issue, I also ran Furmark as well.
 
arestavo said:
I had to clean install 572.16. My PC went black screen during the install from the hotfix driver, forced me to hard reset the PC. The driver looked to be installed, but hardlocked the PC when I tried to play the updated Hogwarts.

DDU'd in safe mode, reinstalled 572.16, and now everything is working fine - I'd try that.
Click to expand...
Had to clean install the latest driver as installing them over 572.16 caused a black screen on installation via the Nvidia app again. I even tried re-installing via the app again after a hard reboot (waited 5 minutes after the black screen) and no dice.

Whatever Nvidia is doing with the new drivers with 50 series compatibility, it fucks with my 4090 FE and Samsung S90C via HDMI (direct, not going via a receiver).
 
They work fine for me now, but I did have to do a clean install (and DDU when I changed GPUs).
 
I've been having some serious driver issues with the 572 drivers and my 4080 + 750 Ti.

It started with 572.16, where my main monitor (out of 6 monitors total) would not want to wake up after turning off. This wasn't too big of a deal, because the monitor is on a Displayport switch. Using it to switch the input back and forth has the same effect as unplugging and re-plugging the displayport cable, which would always cause the monitor to turn back on. It was an easy workaround, and with 6 monitors I'm used to little quirks popping up so I didn't worry about it too much.

But when I updated to 572.47, it was a complete disaster. Ironically this driver supposedly had some kind of fix for this issue, but this is when the real problems began for me. Sometimes when I booted up my computer, my monitors would remain black and the computer would basically freeze at the point where I was supposed to get the login prompt (it would always make it through BIOS/UEFI initialization fine). Sometimes it would allow me to login, but some of the monitors (the ones attached to the 4080 usually) would go black at random, both during games and even while browsing the web.

Event log showed that it was the Nvidia driver that was repeatedly crashing. Event ID 153, "Reset TDR occurred on GPUID:100". It would usually do this 3 or 4 times. Occasionally it would come out of it, but usually after that 3rd or 4th time it would cause a 0x00000116 BSOD (VIDEO_TDR_FAILURE).

I tried removing the GTX 750 Ti in case the rumors of them dropping support for older cards were true and possibly the cause, but it didn't change anything.

Reverting to 566.36 from December fixed everything.
 
GotNoRice said:
I've been having some serious driver issues with the 572 drivers and my 4080 + 750 Ti.

It started with 572.16, where my main monitor (out of 6 monitors total) would not want to wake up after turning off. This wasn't too big of a deal, because the monitor is on a Displayport switch. Using it to switch the input back and forth has the same effect as unplugging and re-plugging the displayport cable, which would always cause the monitor to turn back on. It was an easy workaround, and with 6 monitors I'm used to little quirks popping up so I didn't worry about it too much.

But when I updated to 572.47, it was a complete disaster. Ironically this driver supposedly had some kind of fix for this issue, but this is when the real problems began for me. Sometimes when I booted up my computer, my monitors would remain black and the computer would basically freeze at the point where I was supposed to get the login prompt (it would always make it through BIOS/UEFI initialization fine). Sometimes it would allow me to login, but some of the monitors (the ones attached to the 4080 usually) would go black at random, both during games and even while browsing the web.

Event log showed that it was the Nvidia driver that was repeatedly crashing. Event ID 153, "Reset TDR occurred on GPUID:100". It would usually do this 3 or 4 times. Occasionally it would come out of it, but usually after that 3rd or 4th time it would cause a 0x00000116 BSOD (VIDEO_TDR_FAILURE).

I tried removing the GTX 750 Ti in case the rumors of them dropping support for older cards were true and possibly the cause, but it didn't change anything.

Reverting to 566.36 from December fixed everything.
Click to expand...
yap its known that the latest drivers are pretty poo poo for a lot of people. There is supposed to be a new update this week? Probably for Monster Hunter release.
 
I had two black screens playing Atomic Heart and Solasta 2 Demo I have a 4080 but the last set 572.47 I didn't have anything yesterday. Some people on reddit claim it's not fixed yet for 5000 series card and 4000 series cards. What happens with the black screens the GPU fans spin 100 percent and music from the game plays in the background but there isn't any video on the monitor just a black screen and you have to do a hard reset with the power button. Nvidia just says there is a issue with the monitor going to sleep. The 572.60 drivers might fix the issue though.
 
I will now try drivers when someone comes out and says that they aren't utter crap...
 
After some testing, this driver is bunk. Application lock ups, white screens, and black screens. Going to have to revert back to an older version.
 
KickAssCop said:
I will now try drivers when someone comes out and says that they aren't utter crap...
Click to expand...
So far for me they are good, tonight I'll do some gaming and I'll know more.

I ran 3D Mark Time Spy and it was fine.
 
Last edited:
This is the first 50 series compatible driver that DIDN'T black screen my gaming PC and eventually cause the keyboard to go unresponsive during installation via the Nvidia App. No issues loading up and playing KCD II either. 4090 FE Windows 11 24H2 Samsung S90C TV as a monitor.
 
DogsofJune said:
I installed the new drivers on two of my PC's. The lappy took it without issue, my Plex box........ the driver doesn't see the gpu. Have to revert that one and probably hold off on installing on other boxes.

On retrospect, the lappy got the studio driver, but I wouldn't think that would make that much of a difference.
Click to expand...
Revisiting this. The lappy has a bluescreen while booting up for the first time of the day. Has a dxkernel something or rather that I traced down in the minidump as being due to the Nvidia driver.
The lappy has an apu so at first I thought it was to blame, but it's actually the 4060 driver.

Sad thing is, even rolling back to an earlier driver still bluescreens. Using windows generic nvidia results in blueness as well.


I may wipe clean and reinstall OS and all.
 
Last edited:
techie81 said:
After some testing, this driver is bunk. Application lock ups, white screens, and black screens. Going to have to revert back to an older version.
Click to expand...
I had the weirdest issue where not only once, but twice my desktop locked up and I was unable to stop and restart explorer.exe like I have in the past on the very rare occasions this has happened. It was caused by copying and pasting a file to my desktop. It happened twice after two restarts, and I rolled back to the previous driver and haven't had the issue since. Very strange.
 
The last three drivers will make Shadow of the Tomb Raider crash if using ray tracing on ultra. Nvidia have known about this for a while but no mention of when it will be fixed.
 
You must log in or register to reply here.
Back
Top