System Name | Firelance. |
---|---|
Processor | Threadripper 3960X |
Motherboard | ROG Strix TRX40-E Gaming |
Cooling | IceGem 360 + 6x Arctic Cooling P12 |
Memory | 8x 16GB Patriot Viper DDR4-3200 CL16 |
Video Card(s) | MSI GeForce RTX 4060 Ti Ventus 2X OC |
Storage | 2TB WD SN850X (boot), 4TB Crucial P3 (data) |
Display(s) | Dell S3221QS(A) (32" 38x21 60Hz) + 2x AOC Q32E2N (32" 25x14 75Hz) |
Case | Enthoo Pro II Server Edition (Closed Panel) + 6 fans |
Power Supply | Fractal Design Ion+ 2 Platinum 760W |
Mouse | Logitech G604 |
Keyboard | Razer Pro Type Ultra |
Software | Windows 10 Professional x64 |
No you don't, there is nothing stopping you from going to https://github.com/keylase/nvidia-patch/blob/master/win/README.md and checking if that driver version is listed as patched.we have to download the entire driver to know whether or not there is a patch available
I guess this would be relatively trivial to implement, you just have to try fetch https://raw.githubusercontent.com/keylase/nvidia-patch/master/win/win10_x64/<major.minor>/nvencodeapi64.1337 (modifying URL for Windows version and bitness) and if it returns 404, there isn't a new version available (not sure if GH allows HEAD requests or not, which could be an optimisation). Given that NVCI is already fetching these patches and applying them, seems like it wouldn't be much work to go this extra step.
Does seem like it steps a bit outside the intention of the software though - it's called "NVCleanInstall", not "NVEncCleanInstall".
No you don't, there is nothing stopping you from going to https://github.com/keylase/nvidia-patch/blob/master/win/README.md and checking if that driver version is listed as patched.
Processor | Ryzen 7 5700X |
---|---|
Memory | 48 GB |
Video Card(s) | RTX 4080 |
Storage | 2x HDD RAID 1, 3x M.2 NVMe |
Display(s) | 30" 2560x1600 + 19" 1280x1024 |
Software | Windows 10 64-bit |