Threaded Mode | Linear Mode

Lumonaut · 11-08-2015, 01:27 AM

(11-07-2015 10:27 PM)ToastyX Wrote:
(11-07-2015 10:02 PM)Lumonaut Wrote: Already disabled driver enforcement and installed that. Yes it's the QNIX QX2710. Already rebooted and that's the error that Nvidia's control panel gives me. It gave me that before I installed Toasty's patch as well but I thought that might fix it.
That sounds like a driver bug, or they added a new limit that I haven't heard about. I know some people had trouble adding any refresh rate with some of the earlier Windows 10 drivers, but that should have been fixed by now. I don't know why some people are still affected by that. Have you tried wiping the driver with DDU? http://www.wagnardmobile.com/DDU/

If that doesn't work, the CRU method should still work.

Weirdly enough, CRU (which I've used also) didn't work either. Gonna try wiping with DDU.

***ToastyX*** · 11-08-2015, 02:40 AM

(11-08-2015 01:27 AM)Lumonaut Wrote: Weirdly enough, CRU (which I've used also) didn't work either. Gonna try wiping with DDU.

Did you set a custom extension block?

Lumonaut · 11-08-2015, 02:49 AM

(11-08-2015 02:40 AM)ToastyX Wrote:
(11-08-2015 01:27 AM)Lumonaut Wrote: Weirdly enough, CRU (which I've used also) didn't work either. Gonna try wiping with DDU.
Did you set a custom extension block?

Yup I did. Also, after resetting all drivers, same thing. Follow the instructions and nada. I've overclocked this monitor on two separate AMD cards, a 980, and now this 980 Ti, so this whole thing is very strange to me as I've done it several times and several ways.

Sour · 11-08-2015, 01:47 PM

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.

***ToastyX*** · 11-08-2015, 02:48 PM

(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?

***ToastyX*** · 11-08-2015, 02:48 PM

(11-08-2015 02:49 AM)Lumonaut Wrote: Yup I did. Also, after resetting all drivers, same thing. Follow the instructions and nada. I've overclocked this monitor on two separate AMD cards, a 980, and now this 980 Ti, so this whole thing is very strange to me as I've done it several times and several ways.

Maybe they broke something in the latest driver. Try an older driver like 355.98.

niciuffo · 11-08-2015, 02:49 PM

I can confirm that the latest nVidia display driver (358.87) does not allow me to add a new custom resolution. The pop-up shows the usual message (Test failed. Your monitor doesn't support the custom resolution).
I have seen other people complain the same symptoms with this particular driver. Rolling back to the one before that (358.50), I can still add custom resolutions.
I hope this is a bug on nVidia's side, and not an artificial restriction of the driver.

Sour · 11-08-2015, 02:55 PM

(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.

***ToastyX*** · 11-08-2015, 03:09 PM

(11-08-2015 02:55 PM)Sour Wrote: 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).

You shouldn't need the patch to add higher refresh rates when using the NVIDIA control panel with 980 Ti cards. I don't understand why people are using the patch in cases where it isn't needed. This isn't a patch issue because it should work without the patch.

(11-08-2015 02:55 PM)Sour Wrote: 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.

I'm surprised the CRU method isn't working anymore. I haven't had a chance to try the latest driver yet because I'm using an AMD card at the moment. I will take a look when I get a chance in a couple of days. For now, use 358.50 or 355.98.

Sour · (Last edited: 11-08-2015, 03:32 PM by Sour)

(11-08-2015 03:09 PM)ToastyX Wrote:
(11-08-2015 02:55 PM)Sour Wrote: 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).
You shouldn't need the patch to add higher refresh rates when using the NVIDIA control panel with 980 Ti cards. I don't understand why people are using the patch in cases where it isn't needed. This isn't a patch issue because it should work without the patch.

(11-08-2015 02:55 PM)Sour Wrote: 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.
I'm surprised the CRU method isn't working anymore. I haven't had a chance to try the latest driver yet because I'm using an AMD card at the moment. I will take a look when I get a chance in a couple of days. For now, use 358.50 or 355.98.

Well I assume I had to patch it because it didn't work when it was unpatched. And because of this on the OP, "Catleap/Tempest/QNIX/X-Star users with SLI or 400/500-series GPUs: run nvlddmkm-patcher-full.exe instead." I'm just really used to having to patch when I was running crossfire.