-
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**
- Thread starter Boomstick777
- Start date
"Runs fine on my PC"....... Insert meme.
Can't believe how no one actually tests anything. Actually I can.
Got a new bug list running that's at about 5+ already. New one to add for latest drivers - RTX HDR now does not work! Either via Nvidia app or forcing via Nvidia Inspector.
And to all those who said the last lot of drivers were "fine", look at the ******* list of so called fixes in the latest release. And many of them aren't even fixed.....
Can't believe how no one actually tests anything. Actually I can.
Got a new bug list running that's at about 5+ already. New one to add for latest drivers - RTX HDR now does not work! Either via Nvidia app or forcing via Nvidia Inspector.
And to all those who said the last lot of drivers were "fine", look at the ******* list of so called fixes in the latest release. And many of them aren't even fixed.....
- [Fortnite] random crashes during gameplay [5171520]
- [The First Berserker: Khazan] DXGI_ERROR_DEVICE_REMOVED Crash [5195216]
- [Star Wars Outlaws] Application will freeze after leaving the game idle for 5+ minutes [5191099]
- Game stability issues when playing games with DLSS Frame Generation + GSYNC [5144337]
- [Monster Hunter Wilds] Crash after accepting quest with DLSS-FG Enabled [5087795]
- [InZOI] Game crashes with error “GPU crashed or D3D Device Removed” [5154864]
- [Overwatch 2] Stutter when using VSYNC [5171856]
- [Hellblade 2 Senua’s Saga] Increased aliasing when using TSR [5125662]
- [Hellblade 2 Senua’s Saga] Crashing when using Smooth Motion [5209772]
- [The Last of Us Part 1] Crash when using Smooth Motion [5208799]
- Dithering/banding in some games on RTX 50-series GPUs [5121715]
- [Control] Flickering corruption in multiple areas [5118876]
- Stutter when using VSYNC [5202703][5202474]
- VSYNC in NVCP + frame generation causes issues in DLSS 4 games [5124816]
- [UNCHARTED: Legacy of Thieves Collection] Artifacts on screen when collecting treasures [5158954]
- Stability issues when using Windows 11 24H2 [5160948]
- Bugcheck w/ PAGE_FAULT_IN_NONPAGED_AREA (50) when playing games with DLSS 4 multi-frame generation [5144337]
- [RTX 50 series] GPUs crashes with black screen/underflow [5160845]
- [RTX 50 series] Random Black Screen issues [5090505]
- General system stability issues [4921925]
- [RTX 50 series] System hard hang with 572.16 driver loaded [5107271]
- Compute Shader related tests are failing due to “error” [4894179]
- [HWBU][DT GB202/203][LG 27GN950 Specific]: Display blacked out when applying 120Hz refresh rate [5044229]
- PC display will not wake after extended sleep time [5131052]
- Two DP output of the RTX5090 will blue screen when trying to watch protected videos [5167145]
- Black screen issue when testing 3D mark with driver 572.02 and 572.16 [5095825]
- Primary Blank display showing blank after hot plug the display in daisy chain [4978206]
- Display shows blank screen on setting RR 165/200Hz when daisy chain is enabled. [5049227]
- Second display showing blank when we apply higher RR for second display when displays connected in daisy chain [4956573]
- Primary monitor (AOROUS FO32U2P) goes blank when we HPD/power cycle second display in Daisy chain. [5075448]
- GeForce RTX 50 series GPUs crashes with black screen when playing graphically demanding games [5098914]
- RTX 50 series displays blank screens on LG 5k2k 45GX950A-B when running in DisplayPort 2.1 mode w/ HDR [5192671]
- Black screen on installing drivers and booting into Windows [5153642]
- DP2.1 – UHBR10/13.5 link rates are unstable on LGE 27GX790A-B [5080789]
- Multiple users reporting black screen issue when disable the “FCH Spread Spectrum” settings [5204493]
- [RTX 50 series] Slightly higher DPC latency may be observed on some system configuration [5168553]
- [RTX 50 series] Varjo Aero VR headset may fail to establish connection [5117518]
- Changing state of “Display GPU Activity Icon in Notification Area” does not take effect until PC is rebooted [4995658]
- [RTX 50 series] Display may show black screen when selecting DLDSR resolution [5144768]
- [Octanebench] Performance regression [3523803]
- [DaVinci Resolve] UI overlay in Fusion page is not displayed correctly
A lot of those fixes are for the 5000 series. As a 4090 owner, I can't test those issues or may not even have those issues because it's specific to that architecture.
Things like vsync issues, blank screens, page fault issues, screens not waking up, or stability issues, etc, I just haven't come across them personally for my specific setup. The problem with these issues is you may only have to change out a monitor, and you might trigger one. At least for the games I play and the software I use, for the time being they are great for me.
With so many hardware and software variations out there, all you can do is install them and see what happens. You may be fine, or you may not be.
Things like vsync issues, blank screens, page fault issues, screens not waking up, or stability issues, etc, I just haven't come across them personally for my specific setup. The problem with these issues is you may only have to change out a monitor, and you might trigger one. At least for the games I play and the software I use, for the time being they are great for me.
With so many hardware and software variations out there, all you can do is install them and see what happens. You may be fine, or you may not be.
Last edited:
Vsync and Gsync issues is pretty big! Imagine getting stuttering and people go... ITS YOUR OVERCLOCK, ITS YOUR SYSTEM IT'S NOT STABLE...
Only to find it's another **** Nvidia issue
Still staying on Cuda's though!
What are these obscure drivers you keep harping on about Neil? What issues do they have compared to .83 and the newest ones? Might give them a go, nothing to lose except further sanity....
Put .83 drivers back on (had to DDU again). Now RTX HDR only works in 2 games where it worked in about 6 games I was using it for before with the same drivers. What the actual **** is going on?
EDIT - I reinstalled the same driver again over the top just using default express installation and now RTX HDR is working as normal again for all games. Come on, we shouldn't have to dance around like this....
EDIT - I reinstalled the same driver again over the top just using default express installation and now RTX HDR is working as normal again for all games. Come on, we shouldn't have to dance around like this....
Last edited:
CUDA Toolkit 12.1 Downloads
Get the latest feature updates to NVIDIA's proprietary compute stack.
developer.nvidia.com
These ones matey!
But you'll need NVslimmer to install ONLY the driver and not the cuda tool kit
So had a quick play after I installed the new drivers. Managed second best score in Steelnomad with a 5700x3d 9734 points.
However, even when dialled back for real gaming settings had afew crashes in Cyberpunk. So I’ve ended up about 20mhz less than previously for stability. Could be something to do with path tracing etc not sure.
However, even when dialled back for real gaming settings had afew crashes in Cyberpunk. So I’ve ended up about 20mhz less than previously for stability. Could be something to do with path tracing etc not sure.
It hasn't been working for me for a while now, so I moved back to Windows auto HDR and it works just fine for me really (after going through calibration first), without costing me any FPS unlike RTX HDR.
Working fine here
I am still sticking to 566.36, seems decent with my 4080.
Then again those with 5000 series of cards, choice it seems to be selecting the least impacting problem(s), when deciding to choose drivers.
The intern charged with Nvidia's driver creation seriously needs help, hopefully AI can offer that soon, when they can sort out the black screen issues.
Perhaps the answer could be........ 42.
Then again those with 5000 series of cards, choice it seems to be selecting the least impacting problem(s), when deciding to choose drivers.
The intern charged with Nvidia's driver creation seriously needs help, hopefully AI can offer that soon, when they can sort out the black screen issues.
Perhaps the answer could be........ 42.
Last edited:
(Not sure if should post here or in 50 series thread so done both for now as may be relevant for all NV cards....)
Right, had some proper time today to do some semi-scientific testing of this Nvidia drivers **** show and the problem with Gsync/ Vsync and Frame gen/ multi frame gen. Below are my own notes which I thought I'd share in here in case they're useful for anyone else.
NOTE: this is on a 5080 and I think this chronic issue is mostly 50 series specific (especially as it involves multi frame gen) but I'd be interested to know if x2 frame gen is also having these issues on 40 series - if you use the latest DLSSG DLLs.
NOTE: This is testing with the latest drivers 576.02. They have definitely NOT fixed the issue which the release notes purport to have done. The exact same behaviour occurs on 572.83 and earlier too.
ALSO NOTE: Please don't just say "all runs fine on my PC". I would bet a huge amount of money that if you actually deep dive into it, it will have these issues.....
-------------
FRAME GEN NOTES
APRIL 2025
'DLSS4' FG (x2) and MFG (x3 or x4) do not work properly with ANY DLSSG DLL files of v3.10.X and above when using the long term gold standard of Gsync on, Vsync on globally in NVCP, Vsync off in game, Reflex on in game if it has it. 'DLSS3' FG (DLSSG DLL v3.8.1 and below) still works fine with this gold standard, but obviously x2 FG is all you can get with this.
With 'DLSS4' FG (DLL files of v3.10.X and above) and Vsync ON in NVCP, THE BAD SYMPTOMS ARE:
x2 FG will NOT run with GPU at full usage so you lose ~20% performance, and MFG x3 or x4 mode will often just not work, at all! It's ALL to do with VSYNC settings....
....If Vsync is set to OFF or FAST in the NVCP/ NV App game profile then 'DLSS4' x2 FG works totally as it should with max GPU usage AND x3 and x4 mode also fully work! - BUT - with 'driver level' Vsync off *some* games are prone to the old school problem of screen sync 'tearing', which is ******* horrible, EVEN if you have GSYNC on AND keep FPS below monitor refresh rate with an FPS cap (eg in RTSS). *Some* games work fine this way with zero tearing and can keep fps at eg ~117fps cap on a 120Hz screen (remember in-game Reflex does NOT WORK with global/ driver level Vsync off, so you MUST use an FPS cap!)
Assuming 120Hz screen, *Some* games benefit from a lower cap of ~110fps which can 'almost' totally mitigate the tearing, but it seems to be game dependent/ random.
Until Nvidia properly fix this issue (driver and/ or new DLSSG DLLs) - if you can be bothered - the best FG settings need to be done on a per-game basis. A few different examples....
Cyberpunk 2077
- Vsync on globally in NVCP or forced on in App profile
- Use DLSSG v3.8.1 (latest 'DLSS3' standard x2 only DLL)
- Reflex on in game
Half Life 2 RTX
- Vsync OFF or FAST in App profile
- Use latest DLSS4 DLSSG Dlls
- Frame cap of 117fps (zero tearing)
Stalker 2
- Vsync on globally in NVCP or forced on in App profile
- Use DLSSG v3.8.1 (latest 'DLSS3' standard x2 only DLL)
- Reflex on in game
Indy and the Great Circle
(DLSS3 DLLs will not work with this game - crashes on load)
- Vsync OFF or FAST in App profile
- Use latest DLSS4 DLSSG Dlls
- Frame cap of 117fps (zero tearing)
Right, had some proper time today to do some semi-scientific testing of this Nvidia drivers **** show and the problem with Gsync/ Vsync and Frame gen/ multi frame gen. Below are my own notes which I thought I'd share in here in case they're useful for anyone else.
NOTE: this is on a 5080 and I think this chronic issue is mostly 50 series specific (especially as it involves multi frame gen) but I'd be interested to know if x2 frame gen is also having these issues on 40 series - if you use the latest DLSSG DLLs.
NOTE: This is testing with the latest drivers 576.02. They have definitely NOT fixed the issue which the release notes purport to have done. The exact same behaviour occurs on 572.83 and earlier too.
ALSO NOTE: Please don't just say "all runs fine on my PC". I would bet a huge amount of money that if you actually deep dive into it, it will have these issues.....
-------------
FRAME GEN NOTES
APRIL 2025
'DLSS4' FG (x2) and MFG (x3 or x4) do not work properly with ANY DLSSG DLL files of v3.10.X and above when using the long term gold standard of Gsync on, Vsync on globally in NVCP, Vsync off in game, Reflex on in game if it has it. 'DLSS3' FG (DLSSG DLL v3.8.1 and below) still works fine with this gold standard, but obviously x2 FG is all you can get with this.
With 'DLSS4' FG (DLL files of v3.10.X and above) and Vsync ON in NVCP, THE BAD SYMPTOMS ARE:
x2 FG will NOT run with GPU at full usage so you lose ~20% performance, and MFG x3 or x4 mode will often just not work, at all! It's ALL to do with VSYNC settings....
....If Vsync is set to OFF or FAST in the NVCP/ NV App game profile then 'DLSS4' x2 FG works totally as it should with max GPU usage AND x3 and x4 mode also fully work! - BUT - with 'driver level' Vsync off *some* games are prone to the old school problem of screen sync 'tearing', which is ******* horrible, EVEN if you have GSYNC on AND keep FPS below monitor refresh rate with an FPS cap (eg in RTSS). *Some* games work fine this way with zero tearing and can keep fps at eg ~117fps cap on a 120Hz screen (remember in-game Reflex does NOT WORK with global/ driver level Vsync off, so you MUST use an FPS cap!)
Assuming 120Hz screen, *Some* games benefit from a lower cap of ~110fps which can 'almost' totally mitigate the tearing, but it seems to be game dependent/ random.
Until Nvidia properly fix this issue (driver and/ or new DLSSG DLLs) - if you can be bothered - the best FG settings need to be done on a per-game basis. A few different examples....
Cyberpunk 2077
- Vsync on globally in NVCP or forced on in App profile
- Use DLSSG v3.8.1 (latest 'DLSS3' standard x2 only DLL)
- Reflex on in game
Half Life 2 RTX
- Vsync OFF or FAST in App profile
- Use latest DLSS4 DLSSG Dlls
- Frame cap of 117fps (zero tearing)
Stalker 2
- Vsync on globally in NVCP or forced on in App profile
- Use DLSSG v3.8.1 (latest 'DLSS3' standard x2 only DLL)
- Reflex on in game
Indy and the Great Circle
(DLSS3 DLLs will not work with this game - crashes on load)
- Vsync OFF or FAST in App profile
- Use latest DLSS4 DLSSG Dlls
- Frame cap of 117fps (zero tearing)
Last edited:
Rock solid drivers well for 40 seriesVsync and Gsync issues is pretty big! Imagine getting stuttering and people go... ITS YOUR OVERCLOCK, ITS YOUR SYSTEM IT'S NOT STABLE...
Only to find it's another **** Nvidia issue
Still staying on Cuda's though!
Last edited: