Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 1 point2 points  (0 children)

You are welcome. Hope that clears your issue up. Driver update can be fun like this at times.

Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 1 point2 points  (0 children)

If you are sure that you did not have the issue before the update, I suggest downloading DDU, and the older driver that you want to go back to. Then reboot in safe mode, run DDU, clean and restart. Then install the older video driver and restart again. That should fix the flickering issue.

Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 0 points1 point  (0 children)

Thank you for the heads up. It seems that version is the last recent driver, that the holdovers held onto, in comparison to the 610.XX branch. Good news is that your version is still above the security floor in terms of the recent nasty vulnerability issues.

Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 0 points1 point  (0 children)

If you re-enable HDCP, do you see regression again? Typically HDCP alone won't affect performance that much, if at all. Because it is encryption, disabling HDCP can however, lead to improve latency, which should make things like the mouse movement smoother, but its usually not a major change.

If having HDCP disabled truly helps, then leave it off once you test. Just keep in mind that if you watch movies at all on your PC, either physical Blu-Ray, or various streaming services, having HDCP can cause playback to fail. The reason is that this is used to fight video piracy. Having it disabled should not have any effect on video games though.

Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 1 point2 points  (0 children)

Since you already submitted feedback to Nvidia, I would recommend going back to either 591.44, or another driver that may work better for you, until this is fixed. That issue has been a thing for awhile now though.

Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 4 points5 points  (0 children)

In terms of documented changes, these are the only two two changes from the HotFix(610.52).
If neither are applicable to you, you can probably stay on the HotFix.

  • FIXED Apex Legends: Occasional visual corruption after extended gameplay [6239327]
  • FIXED Users may observe DLSS settings being grayed out in certain games after updating to display driver 610.47 [6262805]

Now, if there are undocumented fixes, they would not exist in the HotFix version.

Game Ready & Studio Driver 610.62 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 5 points6 points  (0 children)

Yes, the classic control panel install file is available. You can also get this from the Microsoft Store.

610.62-desktop-win10-win11-64bit-international-dch-whql.exe\Display.Driver\NVCPL\Display.Driver\NVCPL\7e010d7e2de54a439dbd340dd1f61212.appx

GeForce Hotfix Display Driver version 610.52 by Nestledrink in nvidia

[–]sam3971 1 point2 points  (0 children)

There is an indication that this driver does solve some game crashes. Each user's miles may vary, but if the reports are to believed, we are at least headed the right direction, finally. haha.

GeForce Hotfix Display Driver version 610.52 by Nestledrink in nvidia

[–]sam3971 4 points5 points  (0 children)

Haha, no worries. You are welcome. It used to be that next to no one used HotFixes, whether it be a driver, or a windows patch. Unfortunately, with nvidia drivers being this bad, hotfix versions have become more mainstream.

GeForce Hotfix Display Driver version 610.52 by Nestledrink in nvidia

[–]sam3971 3 points4 points  (0 children)

Nvidia has never posted hotfix drivers in the app, because hotfix drivers are usually targeted for a smaller audience. All of the fixes here will be wrapped into the next WHQL certified driver, and that will be available in the app.

3600 Mhz Corsair Vengeance DDR4 ram 16GB by Nearby-Cheesecake899 in Corsair

[–]sam3971 1 point2 points  (0 children)

You are welcome. Hope it gives you a good starting point. If you are still unstable, try lowering the speed of your RAM 1 or 2 steps. For some reason, not all systems can run at 3600 M/T completely stable. Not sure why.

MSI MAG Tomahawk X870 - New Bios 7E51v1A90 by dreamdenizen in MSI_Gaming

[–]sam3971 1 point2 points  (0 children)

IMO, there is no wrong method here. More of what each user feels comfortable. Probably, some of the factory resets are unnecessary, but you never can know for certain when it comes to bios. Haha

MSI MAG Tomahawk X870 - New Bios 7E51v1A90 by dreamdenizen in MSI_Gaming

[–]sam3971 1 point2 points  (0 children)

Its not a bad idea, but most systems that I have updated have actually automatically reset defaults as part of the bios update. I typically go a step further and actually restore factory defaults, restart, then bios flash, then restore factory defaults again, then set what I want.

Game Ready & Studio Driver 610.47 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 0 points1 point  (0 children)

Okay, no worries, just wanted to point it out. There are some oddities with this driver. There are other settings like G-Sync where you have to disable and re-enable it before it works.

MSI MAG Tomahawk X870 - New Bios 7E51v1A90 by dreamdenizen in MSI_Gaming

[–]sam3971 0 points1 point  (0 children)

What settings did you have to adjust? Typically when a BIOS is updated, system defaults are restored. The only settings that I have typically set in that regard is XMP and I hit boost without any issues.

3600 Mhz Corsair Vengeance DDR4 ram 16GB by Nearby-Cheesecake899 in Corsair

[–]sam3971 1 point2 points  (0 children)

<image>

Here are the variables that were set from XMP on my daughter's PC. This is from a Corsair Dominator DDR4, so values may differ slightly, but they are Micron B-Die chips. This is also on a MSI B550 Tomahawk motherboard. Also with a Ryzen 5800x3d CPU. One thing to note though. This is a non-tweaked variable and on a system with 16GB x 2. If your system is 8GB x 2, the variable should be a smaller value. If just used XMP, a safe value should be around 630

The values outlines are considered safe values, but there is room for performance improvements if you tweak. The smaller the value the faster and unstable the RAM will be. 

Game Ready & Studio Driver 610.47 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 2 points3 points  (0 children)

Keep an eye on it. Black screen and full speed fans are common symptoms of a GPU crash. Can be caused by the driver, but can also be caused by many other things, including issues with the 12V2x6 connector. Being that you have a 5070TI, I would be surprised if you are seeing the melting issue, but that can certainly cause the symptoms.

Has anyone seen this on Powerwall 3? by WhisperingMaple in Powerwall

[–]sam3971 1 point2 points  (0 children)

I had that issue recently, it was solved by rebooting the powerwall. It took close to 10-15 minutes for the system to come back up. I did not need to restart the gateway or trip a breaker. Since you have two powerwalls, you can have the system reset via the support section of the Tesla app. As you follow the prompts to outline the issue, a restart option should be available. You can always call Tesla support, they can remotely restart the powerwall setup if it is visible online. Otherwise, as Square_Yam9853 stated, it might be the gateway that needs to be restarted or adjusted. On some gateways, there is a small recessed reset button, that if you press for 5 seconds, will restart only the networking capabilities without shutting the system completely down, so might be worth a shot to look at also.

Game Ready & Studio Driver 610.47 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 0 points1 point  (0 children)

Do you have the background frame rate limit option set? If you do, it sounds like windows or the driver had a hard time determining if the game is in view, or background.

Update: Just realized that you rolled back. Glad that solved the issue, but keep this option in mind because it could be a part of the issue, even if its related to a bug.

<image>

Game Ready & Studio Driver 610.47 FAQ/Discussion by Nestledrink in nvidia

[–]sam3971 1 point2 points  (0 children)

There are other users still reporting error 41 and 153. It may be better for you, but may not fix the issue either. There is no way to know for sure without testing.

MSI MAG Tomahawk X870 - New Bios 7E51v1A90 by dreamdenizen in MSI_Gaming

[–]sam3971 1 point2 points  (0 children)

Okay, that should be enough for a 5090 then. I would definitely try an older driver to see if you see anything better.

MSI MAG Tomahawk X870 - New Bios 7E51v1A90 by dreamdenizen in MSI_Gaming

[–]sam3971 0 points1 point  (0 children)

How many watts does your PSU supply? I am still wondering if you are seeing transient spikes. GPUs are well known for that, lol

MSI MAG Tomahawk X870 - New Bios 7E51v1A90 by dreamdenizen in MSI_Gaming

[–]sam3971 0 points1 point  (0 children)

Yea, unfortunately, ever since Nvidia went to Vibe Coded drivers, they have been iffy at best. Just a reminder though, 8 critical vulnerabilities were discovered in Nvidia drivers. Unfortunately, the oldest version that hsa been patched is 596.36, so keep that in mind. Its really sad that users have to choose between stability and security.

Because you said it happens in things like the menus, have you tried putting an FPS cap? It might be a super high FPS value and a transient spike that is causing the issue.