(06-25-2020 10:11 PM)ToastyX Wrote: [ -> ] (06-25-2020 03:10 PM)Jochim Wrote: [ -> ]Not sure if this is the correct place to report, but I had issues with nVidia driver 451.48 released yesterday 24/04/2020. The monitors not working may just be an issue with my individual setup, but the patcher only detected the SL-DVI limit on DL-DVI. Even when patched my monitors wouldn't display anything. I reverted back to nVidia driver 441.66 and the monitors work as expect with the patcher finding limits on all fields.
Try this: https://www.monitortests.com/download/nv...-1.4.9.zip
Working perfectly for me. Thanks very much!
I don't know if this makes any sense, but patching the drivers on the latest version (451.48) on my Windows 10 2004 installation, with my GTX 1060, seems to break "nvcuda.dll" in some way that software which depends on that file crashes instantly when trying to use it, for example:
MPC-HC crashes as soon as the "NVIDIA CUVID" hardware decoder is selected
Davinci Resolve crashes when starting up
I can replicate this as many times as I want by patching and restoring the driver
.
(06-26-2020 08:45 PM)RaulDJ Wrote: [ -> ]I don't know if this makes any sense, but patching the drivers on the latest version (451.48) on my Windows 10 2004 installation, with my GTX 1060, seems to break "nvcuda.dll" in some way that software which depends on that file crashes instantly when trying to use it, for example:
MPC-HC crashes as soon as the "NVIDIA CUVID" hardware decoder is selected
Davinci Resolve crashes when starting up
I can replicate this as many times as I want by patching and restoring the driver .
Also experiencing this now. I just updated to 2004 and the nvcuda dll is faulting when I try to launch RTX voice. Didn't check whether it was starting on previous Windows version sorry.
(06-26-2020 08:45 PM)RaulDJ Wrote: [ -> ]I don't know if this makes any sense, but patching the drivers on the latest version (451.48) on my Windows 10 2004 installation, with my GTX 1060, seems to break "nvcuda.dll" in some way that software which depends on that file crashes instantly when trying to use it, for example:
MPC-HC crashes as soon as the "NVIDIA CUVID" hardware decoder is selected
Davinci Resolve crashes when starting up
I can replicate this as many times as I want by patching and restoring the driver .
same problem with 451.48 and 1.4.10 on 1909
I can't do anything about that. The patcher doesn't mess with DLLs, so it has to be a bug in the DLL.
(06-28-2020 01:56 PM)ToastyX Wrote: [ -> ]I can't do anything about that. The patcher doesn't mess with DLLs, so it has to be a bug in the DLL.
Oh well, thanks anyway. Hopefully it will get fixed by NVIDIA themselves sometime.
Use 446.14 ver driver. On my system (1080 + last win10) work correct!
Same issue as mentioned in the replies above. the cuda dll makes most games & apps unusable (crashes on launch) after using the patch on the 451.48 driver with W10 version 2004.
Hello ToastyX,
I have an QNIX 2710 (v1) and had an "Inno3D IChill GTX970 Herkulez2" GK before, and everything worked fine with PP and CRU for 4 Years. Then i bought a new card 2 month ago, "EVGA RTX 2060 KO". When I use the latest PP and CRU ı get artifacts even at 60 Hz even before adding new frequencies. With my old card I could go 110 without artefacts. Now if I add 110Hz with CRU and do a restart I get coloured vertical lines and must reset with F8 because u can't see anything. If I go back and revert everything and do add 110Hz from the NVidia control panel it works, ok... but,
Some games like Battlefield 3-5 don't see that correctly. E.g. if I have a native resolution of 2560x1440 on ur desktop the game then works 110Hz @ that resolution. If u want to play in 1080 resolution then u cant because there is no option to choose from in the game. (Battlefield wont see it)
So it was my only way to get these option via ur tools. But unfortunately they wont work anymore on my system. :/
By the way: Thnx 4 ur efforts and 4 these utilities. They helped a lot the years.
PS: NVDriver 451.48 and also the driver before the same. And ı also tried ur qnix.inf file shared here. Latest CRU 1.4.2 and Pixelpatcher 1.4.10 and before. No use. ı mean, they dont work.
(07-10-2020 05:23 AM)bmq Wrote: [ -> ]I have an QNIX 2710 (v1) and had an "Inno3D IChill GTX970 Herkulez2" GK before, and everything worked fine with PP and CRU for 4 Years. Then i bought a new card 2 month ago, "EVGA RTX 2060 KO". When I use the latest PP and CRU ı get artifacts even at 60 Hz even before adding new frequencies. With my old card I could go 110 without artefacts. Now if I add 110Hz with CRU and do a restart I get coloured vertical lines and must reset with F8 because u can't see anything. If I go back and revert everything and do add 110Hz from the NVidia control panel it works, ok... but,
It sounds like the DVI port is acting like a single-link port. Are there artifacts at 60 Hz without the patcher?