NVIDIA Pixel Clock Patcher

[Sour]

(11-08-2015 02:48 PM)ToastyX Wrote:  

(11-08-2015 01:47 PM)Sour Wrote:  Just made an account to say I'm having the same exact problem as Lumonaut. I had no problem with this monitor for over 2 years. Now that I clean installed the lasted Nvidia drivers, I can no longer change the framerate through NVCP (I am using SLI so I used the full-patch). The last drivers (before the hotfix) I was able to change the framerate through NVCP and somehow carry it over when I dirty installed the latest drivers in the hopes to fix the HORRIBLE framerate problems I was having with some games using GSync on my Acer Predator x34, but that didn't work, so I clean installed them using DDU.

What monitor are you talking about? What video cards do you have? What resolution are you trying to add?

Oh my, I neglected to say I was using the QNIX, my bad. I have 2 980 ti's in SLI and just wanted to change the refresh rate to 100 to match the refresh rate of my Acer Predator X34 (I use to have the QNIX set at 120 hz). But like I said, I now get the error Lumonaut receives when trying to change the refresh rate through NVCP. I can go back to the old drivers and change them no problem. But with the newest Nvidia drivers I get "Test failed. Custom resolution of 2560 x 1440 (32-bit) is not supported by your display." Can't change it with NVCP, PrecisionX, or even the old CRU I used when I was running 7950s in crossfire.