Threaded Mode | Linear Mode

Nielzx · 04-14-2015, 02:25 PM

(04-14-2015 08:22 AM)ToastyX Wrote: Try this: https://www.monitortests.com/nvlddmkm-patcher-1.3.2.zip

The SL-DVI/HDMI limit only affects single-link DVI ports and HDMI ports in DVI mode. You shouldn't need the patch with HDMI if you add or import HDMI support in the extension block, but some monitors may behave differently with an HDMI signal.

Hi Toastyx,

I tried the one you mentioned but didn't work. Before the update of 350.12, I patched the 1.3.1 and I was able to overclock my monitor up to 80hz without any issues or bandwagons. However, after updating to 350.12 and applying the 1.3.2 patch, I am still stuck with 66hz. I still can't get pass 67hz sadly.

***ToastyX*** · 04-14-2015, 04:44 PM

(04-14-2015 02:25 PM)Nielzx Wrote: I tried the one you mentioned but didn't work. Before the update of 350.12, I patched the 1.3.1 and I was able to overclock my monitor up to 80hz without any issues or bandwagons. However, after updating to 350.12 and applying the 1.3.2 patch, I am still stuck with 66hz. I still can't get pass 67hz sadly.

I don't see why it wouldn't work. What video card do you have? Are you using HDMI or DVI? What happens at 67 Hz?

Nielzx · (Last edited: 04-14-2015, 06:40 PM by Nielzx)

(04-14-2015 04:44 PM)ToastyX Wrote:
(04-14-2015 02:25 PM)Nielzx Wrote: I tried the one you mentioned but didn't work. Before the update of 350.12, I patched the 1.3.1 and I was able to overclock my monitor up to 80hz without any issues or bandwagons. However, after updating to 350.12 and applying the 1.3.2 patch, I am still stuck with 66hz. I still can't get pass 67hz sadly.
I don't see why it wouldn't work. What video card do you have? Are you using HDMI or DVI? What happens at 67 Hz?

Oh wow my bad. I forgot one important step for it to work. I haven't rebooted it yet after patching. Sorry my bad.
It works now. Thank you so much Smile

***ToastyX*** · 04-14-2015, 07:09 PM

(04-14-2015 05:04 PM)Nielzx Wrote: Oh wow my bad. I forgot one important step for it to work. I haven't rebooted it yet after patching. Sorry my bad.
It works now. Thank you so much

The old patch would have worked. You needed the single-link limit on DL-DVI, not the SL-DVI/HDMI limit. The GTX 970 doesn't have single-link DVI ports, and the SL-DVI/HDMI limit wouldn't affect dual-link DVI ports.

niceuser · 04-24-2015, 02:41 PM

I've got a qnix oced to 110hz at 1440p with the nvidia configuration tool and it works great. However when I enable DSR I lose the ability to create custom resolutions. Is there any way to run the monitor at downsampled higher resolutions with higher refresh rates?

***ToastyX*** · 04-24-2015, 04:45 PM

(04-24-2015 02:41 PM)niceuser Wrote: I've got a qnix oced to 110hz at 1440p with the nvidia configuration tool and it works great. However when I enable DSR I lose the ability to create custom resolutions. Is there any way to run the monitor at downsampled higher resolutions with higher refresh rates?

DSR uses the native resolution. Use CRU to define custom refresh rates at the native resolution: https://www.monitortests.com/forum/Threa...tility-CRU

iDRED · 04-26-2015, 04:51 PM

Hello, Sorry if this has been answered before but I am reading conflicting information.

Do you need to run this to use CRU for a GTX 970?

The reason I ask is I couldn't get my 100HZ refresh rate to show on CRU until I ran the pixel clock patch for my GTX 970. I actually got it to show 75HZ, but for some reason would not show 100HZ until I ran this patch.

I read where ToastyX said it is not needed for a single GTX 970. But in my case I needed to use it.

Thanks, I am worried if I damaged the drivers or something by using this patch with my GTX 970.

***ToastyX*** · 04-28-2015, 10:10 PM

(04-26-2015 04:51 PM)iDRED Wrote: Do you need to run this to use CRU for a GTX 970?

The reason I ask is I couldn't get my 100HZ refresh rate to show on CRU until I ran the pixel clock patch for my GTX 970. I actually got it to show 75HZ, but for some reason would not show 100HZ until I ran this patch.

That depends on the limit. The patch is needed for the 330 MHz dual-link DVI limit when using CRU but not when using the NVIDIA control panel. The 165 MHz single-link limit on dual-link DVI ports affects both, but that's mostly useful for 1080p monitors.

HDMI does not need the patch if HDMI support is defined in the extension block. Otherwise, HDMI will act like single-link DVI, which requires the patch for the 165 MHz limit when using CRU.

stoo · 05-03-2015, 12:20 AM

I have been having some strange frame capping issues with my 2x970s at 2160p60 - Asus PB287Q via DP. After much messing around I was finally testing custom refreshes using CRU and found that I can get normal operation at up to 45Hz - 397MHz pixel clock. Anything above 400 and the frame rate is capped with performance issues near the cap. Single GPU mode is fine.

Would you say that my problem is due to the SLI bridge (I have 3 of them - all 3yrs+ old, all affected) or a driver issue?

***ToastyX*** · 05-03-2015, 04:47 PM

(05-03-2015 12:20 AM)stoo Wrote: I have been having some strange frame capping issues with my 2x970s at 2160p60 - Asus PB287Q via DP. After much messing around I was finally testing custom refreshes using CRU and found that I can get normal operation at up to 45Hz - 397MHz pixel clock. Anything above 400 and the frame rate is capped with performance issues near the cap. Single GPU mode is fine.

Would you say that my problem is due to the SLI bridge (I have 3 of them - all 3yrs+ old, all affected) or a driver issue?

SLI has a 400 MHz pixel clock limit with older cards, but the GTX 970 shouldn't be affected. Have you tried it with and without the full patch? I don't think it's an issue with the bridge.