NVIDIA Pixel Clock Patcher

[ToastyX]

(06-21-2016 11:14 PM)Riadon Wrote:  The issue definitely has something to do with a 330 MHz pixel clock, as I am able to boot at 86 Hz with tightened timings with a pixel clock of 329.5640, but the second I go to 87 Hz and cross 330, I can't boot. I am able to boot at 81 Hz at normal timings with a pixel clock of 326.2939 MHz, but I can't boot at 82 Hz at normal timings with a pixel clock of 330.3222 MHz. The full patcher found limits in my drivers, and successfully patched them, but clearly there is another limit in place that is introduced in Pascal.

This is something you need to report to NVIDIA because you shouldn't need to patch the driver to go beyond 330 MHz pixel clock when using the NVIDIA control panel to add custom resolutions. The patch already covers the basic limits. If the GTX 1070/1080 cards have a new limit, then I won't be able to find it without having one of those cards myself, and even then, I might not be able to find a way around it if it's like the 400 MHz Fermi check where the limit is not hard-coded in the driver. It took several weeks and literally thousands of driver restarts to find a way around that limit, and I don't have the time to do something like that right now.

[Riadon]

(06-23-2016 03:51 AM)ToastyX Wrote:  

(06-21-2016 11:14 PM)Riadon Wrote:  The issue definitely has something to do with a 330 MHz pixel clock, as I am able to boot at 86 Hz with tightened timings with a pixel clock of 329.5640, but the second I go to 87 Hz and cross 330, I can't boot. I am able to boot at 81 Hz at normal timings with a pixel clock of 326.2939 MHz, but I can't boot at 82 Hz at normal timings with a pixel clock of 330.3222 MHz. The full patcher found limits in my drivers, and successfully patched them, but clearly there is another limit in place that is introduced in Pascal.

This is something you need to report to NVIDIA because you shouldn't need to patch the driver to go beyond 330 MHz pixel clock when using the NVIDIA control panel to add custom resolutions. The patch already covers the basic limits. If the GTX 1070/1080 cards have a new limit, then I won't be able to find it without having one of those cards myself, and even then, I might not be able to find a way around it if it's like the 400 MHz Fermi check where the limit is not hard-coded in the driver. It took several weeks and literally thousands of driver restarts to find a way around that limit, and I don't have the time to do something like that right now.

I made a thread on the GeForce forum yesterday, but haven't really had any bites. How could I contact NVIDIA in a way that I will actually get a response and have a chance of the problem being looked into?

[GD7G]

I wish everyone luck on this one. My guess it's probably intentional and they want to push high end users to their Gsync panels. I worked on me as I was already on the fence on upgrading, picked up a very expensive PG279Q 165hz monitor. Bastards! I do love the monitor though.

[Mkilbride]

Oh crap, no.

I bought a 1080 due in a few days.

But now I'm hearing I'm not going to be able to hit my 120HZ OC on my monitor with it? That's basically a downgrade! Argh.


_______

This is featured on Guru3D now

http://www.overclock.net/t/1604243/guru3...mhz-issues

Hopefully this will get a lot more press!

[Mkilbride]

Got my 1080. I managed to hit my previous 115HZ OC, however I do think I'm seeing the green lines easier than I did before. I dunno, time will tell.

I have -not- tried to Restart yet though. Definitely seeing the green lines appear more frequently, and it doesn't feel as smooth as it used to.

OK, can confirm. It fucks up, I had to do a restart and didn't change resolution.

What happened was...I was greeted by 4 small screens. I had to change back to 60HZ to get rid of the fuck up.


________

Yeah, the green lines appear frequently and in everything - they did not before. This is frustrating as hell.

I know you don't own a Pascal chip so you can't do anything...but ugh.


NVIDIA HAS RESPONDED:

Quote:Some gamers using our latest Pascal based GPUs connected to high refresh rate monitor have reported that the highest refresh rates or resolutions are not available when connected using DVI. This behavior is due to limited bandwidth available on the DVI cables. NVIDIA recommends that these high performance monitors be connected using DP instead of DVI. DP natively has much higher performance and will support the full capabilities of modern monitors.

In addition, NVIDIA is updating our driver to attempt to run at higher clocks on older DVI cables and enable all monitor modes. However, this high clock behavior is beyond the cable specification and depending on cable and monitor quality, may be unstable or non-functional.

Sounds like a load of horse-shit, but yeah.

[Gonzales]

LG W1943SE (VGA)
GTX 750ti (tried 368.39 and then 362.00)
After patch i still have "bad" pixels with 75 hz. Nvidia panel - "auto" settings.
With CTV settings (screenshot) i have good pixels, but shifted to the left screen (photo). I cant move screen right using monitor or nvidia settings.
Please help

[Mkilbride]

http://www.lg.com/eg_en/tvs/lg-W1943SE

This monitor?

Your monitor is not one of the Korean ones bud. You can't do this.

[ToastyX]

(07-03-2016 11:01 AM)Gonzales Wrote:  LG W1943SE (VGA)
GTX 750ti (tried 368.39 and then 362.00)
After patch i still have "bad" pixels with 75 hz. Nvidia panel - "auto" settings.
With CTV settings (screenshot) i have good pixels, but shifted to the left screen (photo). I cant move screen right using monitor or nvidia settings.
Please help

The patch is for DVI and HDMI. It does nothing for VGA, and you don't need the patch anyway for pixel clocks less than 165 MHz. This is purely a monitor limitation. You'll have to figure out what timing parameters the monitor can handle at 75 Hz. Manually adjusting the horizontal front porch or total pixels might help.

VGA can have problems with positioning because the monitor has to figure out where the picture is when doing the analog to digital conversion, so the monitor might not be able to display 75 Hz correctly at all since it's only designed to support 60 Hz at the native resolution.

[tester68]

So to clarify, the pixel patcher does not help in this case with Pascal?

[tester68]

FYI with the new 368.81 the pixel clock issue/corruption problem is gone.

You can resume the normal use of Pixel patcher/CRU with Pascal cards over DL-DVI