NVIDIA Pixel Clock Patcher

[driedupfish]

Hi all, I have some questions:

1. For Nvidia, which version of the patch (nvlddmkm-patcher.exe or nvlddmkm-patcher-full.exe) should I use if I have an gtx 780. Sorry English is not my native language. I don't understand the wording on the front page for the full.exe. Should I be using the full.exe if I have an x-star, or is it only for SLI and 400/500 series cards?

2. Has anyone updated to the newest Nvidia driver yet? Should I reset back to the stock refresh rate before updating to the newest driver?

Thanks

[ToastyX]

(01-09-2014 05:55 PM)driedupfish Wrote:  1. For Nvidia, which version of the patch (nvlddmkm-patcher.exe or nvlddmkm-patcher-full.exe) should I use if I have an gtx 780. Sorry English is not my native language. I don't understand the wording on the front page for the full.exe. Should I be using the full.exe if I have an x-star, or is it only for SLI and 400/500 series cards?

You only need the regular patch. The full patch is for SLI or 400/500-series cards.

(01-09-2014 05:55 PM)driedupfish Wrote:  2. Has anyone updated to the newest Nvidia driver yet? Should I reset back to the stock refresh rate before updating to the newest driver?

I haven't tested the newest driver yet, but the patcher finds all the values, so it should work.

As long as 60 Hz is still available and you didn't delete it with CRU, you don't need to reset it to update the driver.

[noob]

sorry for my noobish question but can you explain me what benefits i can expect with patching all values found with this patch? I have nvidia gtx 770 and latest drivers but after patching I am getting every few seconds driver stop responding and recovered... error.I am using 120 hz in lightboost mode on my benq xl2411t without any issues but when i apply nvidia pixel clock patch i am getting this error constantly.

[ToastyX]

What are you using the patch for? The BenQ XL2411T shouldn't need it.

The patch is for getting around pixel clock limits when adding custom resolutions. The patch by itself shouldn't affect anything if you didn't add a custom resolution. It shouldn't cause the driver to stop responding every few seconds. I've only heard of that happening with SLI, which is resolved with the full patch. You shouldn't need the full patch with a single card.

[lawson67]

Hi toastyx first i would like to congratulate you on making such good software enabling people like me to overclock there monitors and then making yourself available to help people use it...
I have just bought this ...QNIX QX2710 LED Evolution ll [Matte] Perfect Pixel 27"...and i have done a lot of reading in an attempt to understand and be ready to overclock it safely when it arrives.

I would like to run by you what i think i must do to achieve a overclock from my new monitor from what i have read, and would like you point me in the right direction if i have not understood something correctly....
My system i have windows 8.1 running a i7-4770K and i have 2x Asus GTX 660 DIRECT cu OC running in SLI....ok from my understanding this is what i think i must do to overclock my monitor.

Firstly i MUST use the NVIDIA Pixel Clock Patcher because i am running in SLI and there is no exception to this rule if you are running SLI?
Secondly i can use the Custom Resolution Utility (CRU) to create custom resolutions and back up my original resolution and from this utility i can change my monitors refresh rate and save the new profile.....then reboot into windows and open up the NVIDIA control panel and pick the new Resolution which i have just made with CRU?...
Also i believe i don't need to use the test mode utility program any more?

Method 2 Patch the Drivers using "NVIDIA Pixel Clock Patcher"...this is a MUST due to the fact i am running SLI?....
Then purely use the NVIDIA control panel alone WITHOUT the use of (CRU) utility to create a custom resolution and simply up the refresh rate...test the new resolution with windows and if it tests ok job done....However also using this method from what i have read i will then need the catleap.zip file to add and the inf file inside it to add a new "Generic PnP Monitormonitor driver" to make games use the higher refresh rate?....i achieve this by browsing to the catleap.inf from device manager and add this as the "Generic PnP Monitormonitor driver"?

I would like to ask if you could confirm the methods above or correct me if i have something wrong and therefore misunderstood some of the process.....
Also if i am right which would be the best method to try?
And also do i need to disenable windows 8.1 digital driver signing?....i have read some people have had trouble doing this process under windows 8 due to its digital driver signing?
Also would it be advisable for me to downgrade my drivers to NVIDIA 331.93 as i am running 332.21 right now?

Thanks Toastyx in advance for any advice

[ToastyX]

Yes, you must use the full patch to get around the 400 MHz pixel clock limit for SLI unless you plan to only use 96 Hz. If you stay under that limit, the regular patch is still required for CRU but not the NVIDIA control panel.

CRU is more effective at making custom refresh rates available to games. You only need to add a detailed resolution and change the refresh rate. To reduce the pixel clock for a more stable signal, set the totals to 2652x1458.

If you use CRU with NVIDIA, you must either disable the extension block and uninstall GeForce Experience, or you can work around the GeForce Experience problem by enabling the extension block and importing this file: https://www.monitortests.com/blank-extension.dat

If you use the NVIDIA control panel, many games won't use the custom refresh rate unless you install the qnix.inf file in the device manager: https://www.monitortests.com/qnix.zip

You only need to disable driver signature enforcement if you need to install the qnix.inf file. You don't need to install that file if you're using CRU.

You don't need to downgrade the driver. The patch should work with 332.21.

[lawson67]

(01-12-2014 05:41 PM)ToastyX Wrote:  Yes, you must use the full patch to get around the 400 MHz pixel clock limit for SLI unless you plan to only use 96 Hz. If you stay under that limit, the regular patch is still required for CRU but not the NVIDIA control panel.

CRU is more effective at making custom refresh rates available to games. You only need to add a detailed resolution and change the refresh rate. To reduce the pixel clock for a more stable signal, set the totals to 2652x1458.

If you use CRU with NVIDIA, you must either disable the extension block and uninstall GeForce Experience, or you can work around the GeForce Experience problem by enabling the extension block and importing this file: https://www.monitortests.com/blank-extension.dat

If you use the NVIDIA control panel, many games won't use the custom refresh rate unless you install the qnix.inf file in the device manager: https://www.monitortests.com/qnix.zip

You only need to disable driver signature enforcement if you need to install the qnix.inf file. You don't need to install that file if you're using CRU.

You don't need to downgrade the driver. The patch should work with 332.21.

Thank you very much ToastyX for your reply explaining things in understandable layman's terms for me and explaining to me what must be the most up to date method, also thankyou so much for the extra files.

I think i shall go with the (CRU) method as i would like to push for 120hz if possible...so am i correct in believing that when i make my new custom detailed resolution file in (CRU) i set the totals to 2652x1458 in the "Active area" of (CRU) before i push ok to make the new detailed resolution?

Also after i pushed ok and made my detailed resolution i will of ticked the box for "Include extension block" and browsed and selected the "extension.dat" file which you kindly gave me, as this will enable me to still use GeForce Experience....which is something i like as it sets up my games graphics nicely i personally think.....anyhow if i am all correct with all of this i thank you once again for your time and help!.... and i am now very much looking forward the the arrival of my new monitor..

Btw i am not going to use the NVIDIA control panel method and so therefore i will not use the Qnix.zip driver file....however if anyone does goes this route and needs to turn off windows digital driver signing feature this program from this link http://files.ngohq.com/ngo/dseo/dseo13b.exe i am lead to believe works well at achieving this this in windows 8.1 even though it was made for earlier versions of windows.....

Once again thank you very much for your time and help ToastyX and i hope i have interpreted correctly all you have told me and my chosen method works

[ToastyX]

(01-12-2014 08:02 PM)lawson67 Wrote:  I think i shall go with the (CRU) method as i would like to push for 120hz if possible...so am i correct in believing that when i make my new custom detailed resolution file in (CRU) i set the totals to 2652x1458 in the Active area of (CRU) before i push ok to make the new detailed resolution?

Set the totals, not the active. Active should be 2560x1440.

[lawson67]

(01-12-2014 08:06 PM)ToastyX Wrote:  

(01-12-2014 08:02 PM)lawson67 Wrote:  I think i shall go with the (CRU) method as i would like to push for 120hz if possible...so am i correct in believing that when i make my new custom detailed resolution file in (CRU) i set the totals to 2652x1458 in the Active area of (CRU) before i push ok to make the new detailed resolution?

Set the totals, not the active. Active should be 2560x1440.

Yep brilliant ToastyX and thanks i found the totals in (CRU) detailed resolution underneath of the blanking values.....thanks very much for all your help mate and such great software....respect!

[cubadoo23]

Hi toasty just an update the 1.2.4 patcher wont patch any higher than 96hz ( my hazro 1440p clocks to 115hz on everything up to this driver) on the new 334.67 quadro driver (modified inf on a 680). Fantastic software tho thanks