NVIDIA Pixel Clock Patcher

[jarda]

Please update for compatibility in the new 368.22 whql

[jarda]

once again very please about the update, I do not want to play the damned 60 Hz ...... :>(

[ToastyX]

I will update it over the weekend.

[ToastyX]

Here it is: https://www.monitortests.com/nvlddmkm-patcher-1.3.7.zip

[jarda]

(05-28-2016 07:00 PM)ToastyX Wrote:  Here it is: https://www.monitortests.com/nvlddmkm-patcher-1.3.7.zip

thankYou very much...

[LocutusEstBorg]

I have a Quadro NVS 310 (GF119) which has 2x DisplayPort 1.2 ouputs. I am unable to run my PG278Q (2560x1440 @ 144 Hz) above 85 Hz. The EDID for the PG278Q uses a 538.3 MHz pixel clock for 144 Hz. According to this document (https://www.pny.com/File%20Library/Suppo...01_v02.pdf), the DisplayPort 1.2 port can do 540 MHz. It should not even require a patch.

I applied the full patch successfully but am still limited to 85 Hz. There are different drivers for Windows Server 2012 R2, Windows 8.1, and Windows 10, unlike the GeForce cards where Windows Server 2012 R2 and Windows 8.1 use the same driver and only Windows 10 uses a separate driver. I am currently using the Windows Server 2012 R2 driver.
Windows Server 2012 R2: http://www.nvidia.in/download/driverResu...2808/en-in
Windows 8.1: http://www.nvidia.in/download/driverResu...2718/en-in

[GD7G]

(05-28-2016 07:00 PM)ToastyX Wrote:  Here it is: https://www.monitortests.com/nvlddmkm-patcher-1.3.7.zip

I have a GTX 1080 and was able to oc to 96hz no problem, however until upon restarting my pc, I get a black screen. I have found my hard limit to be 80hz without getting the black screen upon wake. I used this pixel patch, drivers 368.25 and 368.39. I first tried CRU but it didn't create a new res choice in windows so I ended up making the custom resolution in NVCP. This is a qnix 2710 with d-dvi. My previous card was AMD and it OC'd the same monitor to 96hz no problem. Any ideas?

[ToastyX]

(06-14-2016 01:56 AM)GD7G Wrote:  I have a GTX 1080 and was able to oc to 96hz no problem, however until upon restarting my pc, I get a black screen. I have found my hard limit to be 80hz without getting the black screen upon wake. I used this pixel patch, drivers 368.25 and 368.39. I first tried CRU but it didn't create a new res choice in windows so I ended up making the custom resolution in NVCP. This is a qnix 2710 with d-dvi. My previous card was AMD and it OC'd the same monitor to 96hz no problem. Any ideas?

That sounds like a driver bug because you shouldn't need the patch to add higher refresh rates using the NVIDIA control panel unless they added a new limitation. I don't know what limitations the new GTX 1080/1070 cards have.

[Riadon]

(06-14-2016 01:56 AM)GD7G Wrote:  

(05-28-2016 07:00 PM)ToastyX Wrote:  Here it is: https://www.monitortests.com/nvlddmkm-patcher-1.3.7.zip

I have a GTX 1080 and was able to oc to 96hz no problem, however until upon restarting my pc, I get a black screen. I have found my hard limit to be 80hz without getting the black screen upon wake. I used this pixel patch, drivers 368.25 and 368.39. I first tried CRU but it didn't create a new res choice in windows so I ended up making the custom resolution in NVCP. This is a qnix 2710 with d-dvi. My previous card was AMD and it OC'd the same monitor to 96hz no problem. Any ideas?

I have the same problem, and the same monitor.

I have a GTX 1070 and I am locked to 80 Hz (maybe I could hit 81 Hz, but I haven't tried).

I can easily overclock to 120 Hz stable after I am loaded into windows, but if my refresh rate is any higher than 80 Hz when I load into Windows, I get eternal flashing colors on my QNIX in place of the welcome screen.

I get the same result without the patch, with the normal patch, and with the full patch. Without the QNIX monitor driver, and with.

I'm assuming I could set the monitor to 81 Hz, but the second I set it to 82 Hz (330.3222 pixel clock), I can't boot. This leads me to believe that there is a DL-DVI driver issue with Pascal when clocking above 330 MHz that isn't addressed with the patcher.

Also, my friend with the same monitor and a GTX 1080 has the exact same problem. However, for some reason, if he spams a random key on his keyboard or moves his mouse around a bit before the flashing screen appears, he is able to boot into windows. However, if he doesn't touch his mouse or keyboard, he gets the screen. This doesn't work for me, however. The only reason I could see that it works for him and not me is because he has an MSI motherboard and I have an ASUS, but that's just a shot in the dark.

I'm willing to do as much as is needed to help fix this problem if I am able

[Riadon]

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.