ZeroBarrier
Gawd
- Joined
- Mar 19, 2011
- Messages
- 727
Same, no issues so far for me at least.I been on 526.86 for awhile and everything run good for me.
Same, no issues so far for me at least.I been on 526.86 for awhile and everything run good for me.
They came out yesterday...I been on 526.86 for awhile and everything run good for me.
I update as soon as they release, have been since the RTX 2000 series cards and haven't yet run into an issue. I have gone from clean install to not clean install, back and forth depending though; but I don't know if that really matters.They came out yesterday...
as always, YMMV.
Yep you and millions of other people have no issues with these drivers.I update as soon as they release, have been since the RTX 2000 series cards and haven't yet run into an issue. I have gone from clean install to not clean install, back and forth depending though; but I don't know if that really matters.
Sounds like I may have dodged a bullet...again.Here's a weird word of warning for people using newer Nvidia drivers. In particular the 526.98 driver. These are known to cause issues with HDMI output and flickering with Gsync displays. The caveat is, once you install these, the issues stays even if you go back to older drivers. That's with using a full removal via DDU and everything. No idea what's going on/wrong, but I'd avoid those if you're using HDMI and a Gsync display.
This sounds highly unlikely, if it is a driver issue, it should be resolved by reverting. What is your source for this?Here's a weird word of warning for people using newer Nvidia drivers. In particular the 526.98 driver. These are known to cause issues with HDMI output and flickering with Gsync displays. The caveat is, once you install these, the issues stays even if you go back to older drivers. That's with using a full removal via DDU and everything. No idea what's going on/wrong, but I'd avoid those if you're using HDMI and a Gsync display.
This sounds highly unlikely, if it is a driver issue, it should be resolved by reverting. What is your source for this?
If even a fresh install of Windows still shows the issues, it is not possible to be caused by drivers, unless they actually damaged the card/port/display. Which will be big if to be the case of course, but that also would be highly unlikely. If anything would be able to damage through an update, it would be a firmware update.
Weird stuff, did you try a fresh install on a separate drive?I don't think it's doing "damage," but it's definitely a bug. It could potentially be one of the other components in the Nvidia software suite like the audio driver, Geforce Experience, or even the Control panel applet which is updated via MS store now. Could be a Windows update thing, but it seems to be happening to people on both Win10 and Win11. It has happened to me, and there are several other folks reporting the exact same thing over at Guru. Installing previous drivers that didn't do it now have the same issue.
Weird stuff, did you try a fresh install on a separate drive?
FYI 526.98 came out on November 16, so they were not patched "today."Those of you running NVIDIA driver version less than 526.98 should update your drivers this weekend. Some big vulnerabilities were patched today:
https://nvidia.custhelp.com/app/answers/detail/a_id/5415
The older 474 (Windows) and 470 (Linux) series drivers were also fixed too.