Latest NVIDIA GeForce Graphics Drivers for Windows 10
-
Thank you Gramps. First post updated.
You. Are late. You. Get spankies!
-
-
-
Thanks for the heads up Gramps
-
-
Dont be too greedy , wait a few days , if no bugs occur , install...............
-
While in cd C:\Program Files\NVIDIA Corporation\NVSMI give
to get your Nvidia cards information:
Code:
==============NVSMI LOG==============
Timestamp : Sat Jul 20 18:55:07 2019
Driver Version : 431.36
CUDA Version : 10.1
Attached GPUs : 1
GPU 00000000:01:00.0
Product Name : GeForce RTX 2080 Ti
Product Brand : GeForce
Display Mode : Enabled
Display Active : Enabled
Persistence Mode : N/A
Accounting Mode : Disabled
Accounting Mode Buffer Size : 4000
Driver Model
Current : WDDM
Pending : WDDM
Serial Number : N/A
GPU UUID : GPU-3a6b6c85-12ff-99bc-b3b3-107e5759985e
Minor Number : N/A
VBIOS Version : 90.02.17.40.11
MultiGPU Board : No
Board ID : 0x100
GPU Part Number : N/A
Inforom Version
Image Version : G001.0000.02.04
OEM Object : 1.1
ECC Object : N/A
Power Management Object : N/A
GPU Operation Mode
Current : N/A
Pending : N/A
GPU Virtualization Mode
Virtualization mode : None
IBMNPU
Relaxed Ordering Mode : N/A
PCI
Bus : 0x01
Device : 0x00
Domain : 0x0000
Device Id : 0x1E0710DE
Bus Id : 00000000:01:00.0
Sub System Id : 0x451319DA
GPU Link Info
PCIe Generation
Max : 3
Current : 1
Link Width
Max : 16x
Current : 16x
Bridge Chip
Type : N/A
Firmware : N/A
Replays Since Reset : 0
Replay Number Rollovers : 0
Tx Throughput : 1000 KB/s
Rx Throughput : 0 KB/s
Fan Speed : 52 %
Performance State : P8
Clocks Throttle Reasons
Idle : Active
Applications Clocks Setting : Not Active
SW Power Cap : Not Active
HW Slowdown : Not Active
HW Thermal Slowdown : Not Active
HW Power Brake Slowdown : Not Active
Sync Boost : Not Active
SW Thermal Slowdown : Not Active
Display Clock Setting : Not Active
FB Memory Usage
Total : 11264 MiB
Used : 1300 MiB
Free : 9964 MiB
BAR1 Memory Usage
Total : 256 MiB
Used : 229 MiB
Free : 27 MiB
Compute Mode : Default
Utilization
Gpu : 3 %
Memory : 8 %
Encoder : 0 %
Decoder : 0 %
Encoder Stats
Active Sessions : 0
Average FPS : 0
Average Latency : 0
FBC Stats
Active Sessions : 0
Average FPS : 0
Average Latency : 0
Ecc Mode
Current : N/A
Pending : N/A
ECC Errors
Volatile
SRAM Correctable : N/A
SRAM Uncorrectable : N/A
DRAM Correctable : N/A
DRAM Uncorrectable : N/A
Aggregate
SRAM Correctable : N/A
SRAM Uncorrectable : N/A
DRAM Correctable : N/A
DRAM Uncorrectable : N/A
Retired Pages
Single Bit ECC : N/A
Double Bit ECC : N/A
Pending Page Blacklist : N/A
Temperature
GPU Current Temp : 36 C
GPU Shutdown Temp : 94 C
GPU Slowdown Temp : 91 C
GPU Max Operating Temp : 89 C
Memory Current Temp : N/A
Memory Max Operating Temp : N/A
Power Readings
Power Management : Supported
Power Draw : 30.00 W
Power Limit : 336.00 W
Default Power Limit : 300.00 W
Enforced Power Limit : 336.00 W
Min Power Limit : 100.00 W
Max Power Limit : 336.00 W
Clocks
Graphics : 300 MHz
SM : 300 MHz
Memory : 405 MHz
Video : 540 MHz
Applications Clocks
Graphics : N/A
Memory : N/A
Default Applications Clocks
Graphics : N/A
Memory : N/A
Max Clocks
Graphics : 2250 MHz
SM : 2250 MHz
Memory : 7200 MHz
Video : 1950 MHz
Max Customer Boost Clocks
Graphics : N/A
Clock Policy
Auto Boost : N/A
Auto Boost Default : N/A
Processes
Process ID : 1300
Type : C+G
Name : C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 1660
Type : C+G
Name : Insufficient Permissions
Used GPU Memory : Not available in WDDM driver model
Process ID : 2844
Type : C+G
Name : C:\Windows\SystemApps\InputApp_cw5n1h2txyewy\WindowsInternal.ComposableShell.Experiences.TextInput.InputApp.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 4940
Type : C+G
Name : C:\Program Files\WindowsApps\Microsoft.WindowsAlarms_10.1903.1006.0_x64__8wekyb3d8bbwe\Time.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 5056
Type : C+G
Name : C:\Users\cliff\AppData\Local\Microsoft\Edge SxS\Application\msedge.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 6796
Type : C+G
Name : C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_16005.11629.20316.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 7308
Type : C+G
Name : C:\Windows\explorer.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 8684
Type : C+G
Name : Insufficient Permissions
Used GPU Memory : Not available in WDDM driver model
Process ID : 8920
Type : C+G
Name : C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 9004
Type : C+G
Name : C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\StartMenuExperienceHost.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 9720
Type : C+G
Name : C:\Windows\ImmersiveControlPanel\SystemSettings.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 10592
Type : C+G
Name : C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1831.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 10596
Type : C+G
Name : C:\Program Files\WindowsApps\Microsoft.MicrosoftStickyNotes_3.6.76.0_x64__8wekyb3d8bbwe\Microsoft.Notes.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 11492
Type : C+G
Name : C:\Program Files\WindowsApps\Microsoft.BingWeather_4.31.11905.0_x64__8wekyb3d8bbwe\Microsoft.Msn.Weather.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 14132
Type : C+G
Name : C:\Program Files\WindowsApps\Microsoft.SkypeApp_14.48.51.0_x64__kzf8qxf38zg5c\SkypeApp.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 15048
Type : C+G
Name : C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_16005.11629.20316.0_x64__8wekyb3d8bbwe\HxCalendarAppImm.exe
Used GPU Memory : Not available in WDDM driver model
Process ID : 15160
Type : C+G
Name : C:\Program Files\WindowsApps\Microsoft.WindowsStore_11905.1001.4.0_x64__8wekyb3d8bbwe\WinStore.App.exe
Used GPU Memory : Not available in WDDM driver model
More commands are found in the PDF in C:\Program Files\NVIDIA Corporation\NVSMI
You don't have to 'Force Constant Voltage' to achieve maximum power state.
Use Windows Ultimate Performance or in my case Pro Lasso Bitsum High Performance plan.
Also by using 'optimal' power settings in the NVCP global settings, then setting each game to 'Prefer Max Performance' you will see your GPU clock and voltage drop to low number when not in use.
- - - Updated - - -
Dont be too greedy , wait a few days , if no bugs occur , install...............
+1
430.86 is still my favorite driver, before that it was 399.24 (doesn't work on Turing) - they are both almost identical in terms of stability and performance.
-
Thanks @Gramps. Got to call upon DDU again in order to streamline the whole thing.
-
You don't have to 'Force Constant Voltage' to achieve maximum power state.
Use Windows Ultimate Performance or in my case Pro Lasso Bitsum High Performance plan.
Also by using 'optimal' power settings in the NVCP global settings, then setting each game to 'Prefer Max Performance' you will see your GPU clock and voltage drop to low number when not in use.
.
"Use Windows Ultimate Performance or in my case Pro Lasso Bitsum High Performance plan." has nothing to do with the GPU.
'Prefer Max Performance' doesn't do what you think it does.
Forcing the constant voltage is what you what if you are benchmarking .
-
Any notes of whether the cursor corruption has been fixed in the new drivers?
-
-
Any notes of whether the cursor corruption has been fixed in the new drivers?
That is a good thing that you have raised the question. I was having issues with my cursor and didn't even know that it was caused by the previous driver. In my mind it was caused by LogiOptions' from Logitech's latest update which I had just installed a couple or three days back. More to the point, right now I am not having any issues considering that I have installed the latest Nvidia graphics driver just yesterday and everything seems to be working fine so far...LOL
-
That is a good thing that you have raised the question. I was having issues with my cursor and didn't even know that it was caused by the previous driver. In my mind it was caused by LogiOptions' from Logitech's latest update which I had just installed a couple or three days back. More to the point, right now I am not having any issues considering that I have installed the latest Nvidia graphics driver just yesterday and everything seems to be working fine so far...LOL
There's many reports of cursor corruption in 431.36 and few threads in various forums. Sometimes it happens exiting games but other times just occurs randomly which I have experienced. I'm afraid we're not out of the woods yet as the cursor corruption is still an open issue in the latest drivers. Under Open Issues: http://us.download.nvidia.com/Window...ease-notes.pdf