Threaded Mode | Linear Mode

***ToastyX*** · 10-16-2016, 06:48 PM

(10-15-2016 03:58 AM)DrPhilGood Wrote: I've just tried it and it seems fine. No flickering @ 80hz without the patch on 373.06.

What about when adding 96 Hz using the NVIDIA control panel without the patch?

DrPhilGood · 10-20-2016, 01:03 AM

(10-16-2016 06:48 PM)ToastyX Wrote: What about when adding 96 Hz using the NVIDIA control panel without the patch?

That worked! I had no idea you overclock through NV control panel without patching.

Thanks once again Toasty!

DrPhilGood · 10-22-2016, 04:46 AM

Just an FYI:

The flickering returns after restarting the PC. Fortunately, all I have to do is go into NVIDIA control panel, change it to 60hz, and then back to 96hz and it's gone.
It takes 5-10 seconds so it's not a big deal - just thought I'd let you know Toasty.

Cardnyl · 10-28-2016, 07:06 PM

I'm running a single GTX 680 with a monitor that supports 144hz by default, 150-165hz through OSD overclock. Monitor is connected using a displayport cable provided by the vendor. Monitor only has DP and HDMI for connectivity - no Dual-link DVI. Right now I seem to be limited to 120hz within NVIDIA control panel regardless of the resolution chosen.

I'm trying to determine if this is a software issue that can be fixed using this software, a limitation of the 680's displayport or something else entirely. Any help is appreciated.

***ToastyX*** · 10-28-2016, 07:42 PM

(10-28-2016 07:06 PM)Cardnyl Wrote: I'm running a single GTX 680 with a monitor that supports 144hz by default, 150-165hz through OSD overclock. Monitor is connected using a displayport cable provided by the vendor. Monitor only has DP and HDMI for connectivity - no Dual-link DVI. Right now I seem to be limited to 120hz within NVIDIA control panel regardless of the resolution chosen.

I'm trying to determine if this is a software issue that can be fixed using this software, a limitation of the 680's displayport or something else entirely. Any help is appreciated.

The patch does nothing for DisplayPort limits. You need a 900-series or newer card to get 2560x1440 @ 144 Hz.

Cardnyl · 10-29-2016, 05:16 PM

(10-28-2016 07:42 PM)ToastyX Wrote:
(10-28-2016 07:06 PM)Cardnyl Wrote: I'm running a single GTX 680 with a monitor that supports 144hz by default, 150-165hz through OSD overclock. Monitor is connected using a displayport cable provided by the vendor. Monitor only has DP and HDMI for connectivity - no Dual-link DVI. Right now I seem to be limited to 120hz within NVIDIA control panel regardless of the resolution chosen.

I'm trying to determine if this is a software issue that can be fixed using this software, a limitation of the 680's displayport or something else entirely. Any help is appreciated.
The patch does nothing for DisplayPort limits. You need a 900-series or newer card to get 2560x1440 @ 144 Hz.

Toasty thanks for taking time out to reply. As of right now my 680 will push 2560x1440 @ 120hz over displayport. While I was waiting on a reply I went ahead and tried both the NVIDIA control panel and CRU to side step the issue by running the panel at 1920x1080 to see if the higher refresh rates would become available. I assumed that since 1920x1080 @ 144hz was ~166hz on the pixel clock and 2560x1440 @ 120hz was ~183 that the screen would handle this just fine.

The NVIDIA control panel doesn't expose anything beyond 120hz regardless of the resolution used. CRU mainly results in the monitor saying its not getting a signal. Any chance you know (or can point me to) the limitation on the spec sheet that is stopping this from working? I'm dreading having to replace my old 680 given that it plays all of my current stuff at more than acceptable settings.

***ToastyX*** · 10-29-2016, 08:15 PM

(10-29-2016 05:16 PM)Cardnyl Wrote: Toasty thanks for taking time out to reply. As of right now my 680 will push 2560x1440 @ 120hz over displayport. While I was waiting on a reply I went ahead and tried both the NVIDIA control panel and CRU to side step the issue by running the panel at 1920x1080 to see if the higher refresh rates would become available. I assumed that since 1920x1080 @ 144hz was ~166hz on the pixel clock and 2560x1440 @ 120hz was ~183 that the screen would handle this just fine.

The NVIDIA control panel doesn't expose anything beyond 120hz regardless of the resolution used. CRU mainly results in the monitor saying its not getting a signal.

G-SYNC monitors don't have scalers, so you can't send lower resolutions to the monitor.

(10-29-2016 05:16 PM)Cardnyl Wrote: Any chance you know (or can point me to) the limitation on the spec sheet that is stopping this from working? I'm dreading having to replace my old 680 given that it plays all of my current stuff at more than acceptable settings.

It's not listed in the specs, but the pixel clock limit is 540 MHz. You can try adding 2560x1440 @ 144 Hz as a detailed resolution with the "LCD reduced" timing option in CRU. That will keep the pixel clock under 540 MHz, but the monitor might not be able to handle timing parameters that low.

Cardnyl · 10-30-2016, 12:12 AM

(10-29-2016 08:15 PM)ToastyX Wrote: G-SYNC monitors don't have scalers, so you can't send lower resolutions to the monitor.

Didn't know that but thank you for the info that certainly explains why it didnt work.

(10-29-2016 08:15 PM)ToastyX Wrote: It's not listed in the specs, but the pixel clock limit is 540 MHz. You can try adding 2560x1440 @ 144 Hz as a detailed resolution with the "LCD reduced" timing option in CRU. That will keep the pixel clock under 540 MHz, but the monitor might not be able to handle timing parameters that low.

The 540 Mhz on the pixel clock was the peice of information I was missing. When I made the last post and mentioned 166hz and 183hz I was reading off the wrong values in CRU - those values were the ones above the interlaced checkbox.

I fired up CRU again but was only able to get the panel to work with LCD Standard for the timings. I could push the equipment to 121hz with LCD Standard (501.91 Mhz Pixel clock) - anything beyond that and the panel would go into power saving mode from the video cutting out.

I tried LCD Reduced and LCD Native in 2Mhz steps from 122-130Hz and saw the same results above. I guess ~500 Mhz is the limit for my equipment. Looks like I will need to nut up and buy another video card if I want to go any faster. Again appreciate all the insight and help!

***ToastyX*** · 10-30-2016, 07:20 PM

(10-30-2016 12:12 AM)Cardnyl Wrote: I fired up CRU again but was only able to get the panel to work with LCD Standard for the timings. I could push the equipment to 121hz with LCD Standard (501.91 Mhz Pixel clock) - anything beyond that and the panel would go into power saving mode from the video cutting out.

I tried LCD Reduced and LCD Native in 2Mhz steps from 122-130Hz and saw the same results above. I guess ~500 Mhz is the limit for my equipment. Looks like I will need to nut up and buy another video card if I want to go any faster. Again appreciate all the insight and help!

G-SYNC monitors don't support in-between refresh rates. Try 144 Hz directly with the "LCD reduced" timing option. This is what the ASUS PG278Q uses to keep the pixel clock under 540 MHz.

apav · (Last edited: 10-31-2016, 03:52 AM by apav)

Hi guys,

So today I started having a bunch of random crashes where my computer freezes and restarts. There haven't been any changes to my hardware and I've been using 373.06 for a few weeks now. Up until this point I haven't had any issues and I'm still not sure if the pixel patcher is the cause, but the memory dumps point to nvlddmkm_patched.sys as the cause.

http://imgur.com/YAxVhmJ
http://imgur.com/PnapCAL

I reinstalled 373.06, and updated to 375.70, both times the issue still persists. Any ideas as to what this could be?