• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

**THE NVIDIA DRIVERS THREAD**

Nvidia has issued a "high-severity" warning for owners of its GPUs.


 
Last edited:
Nvidia has issued a "high-severity" warning for owners of its GPUs.


Meanwhile a lot of people go back to older drivers for various reasons but they never pay any attention to actual security issues with that approach. I suppose it went way over the head of most people that these days everything in one's computer (and router etc.) can and will be abused by bad actors in some ways. And then we have millions of zombie routers out there doing ddos attacks all they time and plenty of other issues. Just reality of things these days, sadly.
 
Last edited:

Vulkan Developer Beta Driver Release Updates​


May 22nd, 2026 - Windows 596.60, Linux 595.44.09


  • Fixes:
    • Fix bug causing skipped barrier after host transfer under some conditions
    • Fix descriptor heap mapping bug involving indexed array with offset under some conditions
    • Fix crash with previous Beta drivers after loading a RenderDoc capture with the texture viewer open
    • Fix descriptor buffer embedded samplers from using the wrong binding
    • Improve descriptor heap stability and performance under some conditions
    • Fix image blits involving D24 formats with Vulkan SC on Blackwell

https://developer.nvidia.com/downloads/vulkan-beta-59660-windows

The first 596.60 branch, so can't be far off the 600.x drivers :eek:
 
Last edited:
4 weeks in now and not a single isssue since i replaced the 5090 power lead .what i have noticed is there is no nv errors in event viewer now..
 
Meanwhile a lot of people go back to older drivers for various reasons but they never pay any attention to actual security issues with that approach. I suppose it went way over the head of most people that these days everything in one's computer (and router etc.) can and will be abused by bad actors in some ways. And then we have millions of zombie routers out there doing ddos attacks all they time and plenty of other issues. Just reality of things these days, sadly.
The risk to the average regular person from most disclosed security vulnerabilities is extremely low. Generally they require the attacker to already have a level of access to your system that'd mean you're already boned anyway and the vulnerability is irrelevant. The most likely way for any of these particular vulnerabilities to be exploited would be via a supply chain attack, which circles back to the issue that there's already at least as much heinous stuff that an attacker could do in that situation without needing a vulnerability like this. The highest-rated vulnerability in this particular disclosure is Linux-only, which is doubly unlikely to ever see exploitation in the wild since the Nvidia driver is handled by your distro's packaging team and would require a bad actor to have infiltrated that, which yet again circles back to the issue that you'd have far bigger problems in such a scenario.

None of which is to say that such vulnerabilities shouldn't be patched and reported, but you're hardly playing with fire by rolling back to an older graphics driver. You're far more likely to be caught out by good old social engineering or a simple lapse in judgement/concentration than to ever see vulnerabilities like this exploted on your machine.
 
Last edited:
The risk to the average regular person from most disclosed security vulnerabilities is extremely low. (...)
Yes, that's why we have literally millions of zombie computers, routers, IOT devices etc. out there. :) The risk to THEM might be low, the risk to everyone else, when that hardware gets under control of bad actors, not so low. This is what most people completely miss. A common person is only annoyed with IT security improvements, never updates router's firmware, any of the PC firmware (unless forced or it's automated), never reads about drivers' vulnerabilities and generally has zero clue about those risks. To be clear, I am not theorising here; it's a known fact and also a part of my daily job to deal with it. There are plenty of high CVE vulnerabilities that have close to no influence on the owner of the home machine in theory. But MANY more that can turn one's computer into zombie in a very easy way, because software and firmware on it is horribly outdated. Bad actors always find a way and not all of those get high CVE scoring or headlines. And sadly, often enough vulnerable are components of other software - various DLLs included in it etc. And those usually do not get headlines with the main software's name (as nearly everything these days uses components of someone else, often badly outdated too). In such cases not much user can do, it requires vendor to patch the software and user wouldn't even know they have vulnerable components as many home scanners do not show that at all. That includes drivers.
Generally they require the attacker to already have a level of access to your system that'd mean you're already boned anyway and the vulnerability is irrelevant. The most likely way for any of these particular vulnerabilities to be exploited would be via a supply chain attack, which circles back to the issue that there's already at least as much heinous stuff that an attacker could do in that situation without needing a vulnerability like this. The highest-rated vulnerability in this particular disclosure is Linux-only, which is doubly unlikely to ever see exploitation in the wild since the Nvidia driver is handled by your distro's packaging team and would require a bad actor to have infiltrated that, which yet again circles back to the issue that you'd have far bigger problems in such a scenario.
I've not been talking about one specific driver. Plus, surprise - for every disclosed vulnerability there are plenty existing 0-days that haven't yet been found/disclosed by general public. And some exist only because of other factors existing on the machine, that one usually doesn't find on pro machines, which security researchers often miss because of this - as they often assume at least a basic level of patching has been done, which on home machine is often NOT the case.
None of which is to say that such vulnerabilities shouldn't be patched and reported, but you're hardly playing with fire by rolling back to an older graphics driver.
Unless in combination with other issues suddenly it's a problem and one simply have no way of telling on home machine - way too many variations to account for. There's a reason a saying "Patch your rubbish" (just less nicely said) exists for a long time now in IT. :D
You're far more likely to be caught out by good old social engineering or a simple lapse in judgement/concentration than to ever see vulnerabilities like this exploted on your machine.
You'd think so, but again - as I said at the start - a lot of cyber security issues affect not the ones compromised, but other people (zombie machines used to DDOS things or send spam/scam, data mining, lateral movement, etc.). We live in a most connected world in history of humanity, there are nearly no isolated individuals anymore, everything affects something else these days.

TLDR - patch your stuff people, even if it doesn't show any vulnerabilities on headlines, you can be sure it DOES contain some! :)
 
Last edited:
TLDR - patch your stuff people, even if it doesn't show any vulnerabilities on headlines, you can be sure it DOES contain some! :)

A lot of the worst security issues I've encountered lately are due to businesses leaving legacy hardware i.e. wireless access points sitting around idle but still active after being depreciated. Seems to be a common thing with businesses these days to have different teams coming in i.e. one installs the new replacement equipment and swaps everything over but doesn't remove the old hardware and then another team comes in later to remove the old stuff - sometimes with the removal being a low priority and being pushed back and the hardware going out of update service and becoming vulnerable or even exploited in the gap.
 
Last edited:

:rolleyes:
 
 

NVIDIA DLSS 5 Settings Appear in the Latest Drivers​

May 26, 2026 John Papadopoulos 1 Comment
NVIDIA has just released a new driver for its graphics cards, and from the looks of it, it adds initial support for DLSS 5. So, let’s take a closer look at it.

As Guru3D’s Warkratos discovered, the new GeForce Game Ready 610.47 adds three DLSS 5 settings. These are DLSS-NR, DLSS-NR Streamline, and DLSS-NR Presets.

DLSS 5 settings in the latest drivers

To find these strings, you’ll have to use the Nvidia Inspector Tool. And, in case you’re wondering, no. You cannot force DLSS 5 in any game right now. Even if you enable the preset via the tool, you won’t get any DLSS 5 effects in any game.

For those who did not know, DLSS 5 introduces a real-time neural rendering model that infuses pixels with photoreal lighting and materials. DLSS 5 aims to empower game developers to deliver a new level of photoreal computer graphics previously only achieved in Hollywood visual effects. Or at least that’s what NVIDIA claims.

DLSS 5 will take a game’s color and motion vectors for each frame as input. It will then use an AI model to infuse the scene with photoreal lighting and materials that are anchored to source 3D content and consistent from frame to frame. DLSS 5 will run in real time at up to 4K resolution for smooth, interactive gameplay.

From the looks of it, the green team is preparing its drivers for DLSS 5. As I said, this is initial support for it. In other words, for most of you, it’s a nothing-burger. Still, it shows that NVIDIA has not abandoned its plans for DLSS 5, despite the early harsh criticism surrounding it.

NVIDIA has stated that DLSS 5 will become available in Fall 2026. The first games that will support it are AION 2, Assassin’s Creed Shadows, Black State, CINDER CITY, Delta Force, Hogwarts Legacy, Justice, NARAKA: BLADEPOINT, NTE: Neverness to Everness, Phantom Blade Zero, Resident Evil Requiem, Sea of Remnants, Starfield, The Elder Scrolls IV: Oblivion Remastered, and Where Winds Meet.

It’s also worth noting that this new NVIDIA driver sunsets the NVIDIA Control Panel. As such, NVIDIA users will have to either use the NVIDIA App or the NVIDIA Inspector Tool.

Finally, the NVIDIA GeForce Game Ready 610.47 WHQL driver adds official support for 007 First Light. For our benchmarks, I used the previous driver (as I did not have access to this new driver). Despite that, the game ran incredibly well with it. So, realistically, I don’t expect any major performance improvements from this new driver.

Anyway, those interested can download this new NVIDIA driver from this link.

Stay tuned for more!
 
NVIDIA GeForce 610.47 WHQL Driver


Game Ready for 007 First Light
This new Game Ready Driver provides the best gaming experience for the latest new games supporting DLSS and RTX technologies including 007 First Light, LEGO® Batman™: Legacy of the Dark Knight, EA SPORTS™ F1® 25: 2026 Season Pack, and World of Tanks: HEAT.

What’s New in Release 610
> Support for CUDA 13.3
> Adds the latest performance improvements, bug fixes, and driver enhancements.

Fixed Gaming Bugs
> Like a Dragon: Infinite Wealth: Shadow/light flicker after driver update [5973185]
> Enshrouded: Missing terrain after driver update [5955501]
> Visual corruption may appear in certain games using Godot engine [5948805]
> Multimonitor gaming stability improvements when using V-SYNC [5343252]

Fixed General Bugs
> Adobe Lightroom Classic: Application stability issues [6090770]
> Autodesk Forma: Memory leak during camera orbit when OpenGL is used [5935127]
> Apple Studio Display XDR only displays 480p after driver update [5976295]
> Samsung The Frame: Using display's Game mode disables key functionality [5825631]

Open Issues
> "Prefer Maximum Performance” Power Management Mode may not be applied correctly [6007998]


NVIDIA Control Panel retirement
"After 20 years of dedicated service, the classic NVIDIA Control Panel is officially retiring for Game Ready and Studio Drivers. For NVIDIA RTX PRO users, the NVIDIA Control Panel will continue to be supported until we have migrated professional features to the NVIDIA app

Existing installs of the NVIDIA Control Panel will remain on users’ systems, unless they perform a clean installation, and users who still need the NVIDIA Control Panel can continue to download it from the Microsoft Store, but we won’t be adding features, fixes, or other changes."

Here's the full details in regards to above posts!

Download: https://www.guru3d.com/download/nvidia-geforce-61047-whql-driver-download/

Article: https://www.nvidia.com/en-us/geforce/news/007-first-light-geforce-game-ready-driver/
 
Last edited:
Are people using Studio or Gameready 610.47 drivers? The last drivers i thought id try studio for first time and ive had no bother.
 
Back
Top Bottom