Display problems with the 3060 Recurring Driver update.
Display problems with the 3060 Recurring Driver update.
I'm someone who's dealt with troubleshooting a lot. I've assembled several computers over the years. My time in IT was around six years, but I'm facing a problem that's really getting to me. It's tough because I think I understand what's wrong, yet fixing it outside of swapping out parts feels impossible. This is my wife's PC — it runs the Founders Edition 3070, has a 32GB DDR4 Corsair Vengeance RAM, a Ryzen 7 3700X processor. The motherboard is a TUF Gaming X570 Plus with Wi-Fi and BIOS version 3.001. The issue started after a GPU update from NVIDIA. Once the update was applied, display problems began.
I resolved it by booting into safe mode and deleting the graphics card drivers. When the system started up, it would automatically update the graphics card and then the problem returned. I found a working GPU driver update for this setup. Using the Display Driver Uninstaller, I removed the drivers in safe mode, unplugged the Ethernet cable, installed the GPU driver 472.84, and cleared registry entries that might interfere. I also avoided reinstalling GeForce Experience.
After some testing, the display error would only appear when the computer restarted and applied the update. The update log showed it was installed on the 21st, but the error screenshot from yesterday confirmed it was active for three days without issues. I tried everything to stop the update, but it kept happening. Now I'm hoping for a lasting fix.
Has anyone else faced this issue? Is there a way to prevent the update from causing problems, or is there a method to stop it from updating altogether? I'm feeling really uncertain about this situation. If the problem is tied to the Founders Edition 3070 and the motherboard, could switching to a different GPU or motherboard be a viable solution? I'm at my limit with this.
Have you explored adjusting the DOCP configuration for your RAM?
Your RAM might be causing this problem because the GPU driver update interfered with its communication, even though you haven't used DOCP. This could lead to instability or conflicts between the GPU and RAM.
This seems to point toward a GPU hardware issue instead of a driver problem you're encountering. It might be related to the driver, but it could also be unrelated. If you have another PC, test the card there and vice versa to see if the issue persists. Check the card's temperature settings—ensure updates aren't interfering with your commands. Run sfc /scannow via the admin command prompt after changing Windows Update preferences. Avoid only using regedit when running ddu; also, clear any remaining NVIDIA folders in the registry. Consider reseating the GPU, using a different HDMI/DP cable, testing other PCIe slots, or performing a fresh Windows installation.
Hi. It looks very frustrating. But also looks like a faulty/damaged card and not a driver issue as well. But hard to say. In this one case, I think it's worth it to do install it, after you have your correct driver version that works. Because Geforce experience now would hold on the update until you approve it, so I think your windows wont try to do that automatically. But then again, it really doesn't look like a driver issue to me. Sorry if I've missed it, but did you ever try reinstalling your OS or trying the card in some other PC? If per chance this is a software issue, you should be able to deteremain it that way. I see that you've used DDU, but DDU can be complicated and since you have doubt, I suggest to defintely try it on a fresh install of windows, and I mean fresh from 0 wiping out your current OS drive first. You can even try to keep the system offline for a while to test it out, but I suspect that this will fix your issue if it is software related. If not then it's what I would suspect in the first place, which is a faulty card.
//nvidia.custhelp.com/app/answers/detail/a_id/5233/~/nvidia-gpu-firmware-update-tool-for-displayid https://nvidia.custhelp.com/app/answers/...pdate-tool Now, regarding the next point. The motherboard BIOS is two years old. https://www.asus.com/motherboards-compon...-X570-PLUS This indicates several previously fixed problems remain on that setup. From the information provided, it seems the system may also be missing AMD Chipset drivers... https://www.amd.com/en/support/chipsets/...t-am4/x570
I thought my motherboard firmware was current...obviously I was mistaken. I've been attempting to install the latest updates, but it keeps claiming the file isn't a valid BIOS. I've experimented with other BIOS versions after the 3001 release, yet the issue persists. The motherboard still fails to recognize the updated firmware files. I'll retry, but first I tried using the GPU firmware utility and my screen went black while the system stayed active. After that, I restarted the computer and attempted the firmware update again. Still no success. I plan to try the firmware tool once more and also test the AMD chipset method to see if progress is possible. I'm puzzled as to why I can't update through the web interface, unlike others who seem able to do so with this board. At least I saw that option in a YouTube tutorial for the same model, but I don't have access to it.
Check if the motherboard matches your CPU model using CPU-z under the Motherboard section.
It was the wrong motherboard. I guess there is a distinction between the x570 plus and x570 plus (wi-fi). Updated firmware on the board, updated firmware on the card. Updated amd chipset drivers. Ran DDU again. Ran fine with windows display adapter. Ran fine with update 472.84. Try to update to newest driver. Same display error shows up. So I don't know man. I'm going to take a break and come back to it. Maybe put the gpu in another build and see if it's hardware related even though there is a very clear correlation between the error and updating past driver 472.84. Correlation may not equal causation but it sure feels like one is causing the other. I haven't tried every update after 472.84 but this has been an issue for awhile and has been an issue since before the latest update.
I've started using the computer with the 497.29 update. It seems to work with NVIDIA drivers, though not the newer ones in the 500 series. I'll keep testing to figure out exactly which update caused the problem. If it's a driver issue, I'll look into it further and see if changing to the latest version on another board helps.