NVIDIA Pixel Clock Patcher

[fordmustang68gt]

(06-29-2013 03:51 PM)ToastyX Wrote:  Are you using CRU or are you using the NVIDIA control panel to add the refresh rates?

I used CRU and put in on the top line 2560 X 1440 120 hz. I then selected copy and OK and rebooted as per the instruction on the video from Overlord. However I have never been able to load Modern Warfare, Warfighter at that refresh. With the Beta drivers, I am at 60 hz in order to load. The previous driver approved driver, I was at 88 hz. I put in the 88 hz using Nvidia control panel and verify with Windows to make sure they are both the same refresh rate. I also have installed the EVGA Precision, but I have been avoiding using that in order not to complicate things.

[Ninjawithagun]

(06-28-2013 10:24 AM)ToastyX Wrote:  

(06-27-2013 12:54 AM)Ninjawithagun Wrote:  Yup, I used the full SLI patch. But, when I restart my computer for the patch to take effect the NVidia drivers are no longer recognized and the NVidia control panel is gone.

That's because test mode is not enabled. The patch definitely works with Windows 8.

(06-27-2013 12:54 AM)Ninjawithagun Wrote:  Also, something else I wanted to point out is that the Test Mode patch does not work in Windows 8 Pro. Not sure why, but I get a message that states "Test Mode Failed".

The test mode program should work in Windows 8. It's the same as typing "bcdedit /set testsigning on" in an elevated command prompt. If typing it in manually doesn't work, then you have an unusual boot configuration.

If you're dual booting, the boot store might be on a another partition. You'll have to run Disk Management and assign the partition to a drive letter, then run a command prompt as administrator and specify the boot store manually: bcdedit /store X:\Boot\BCD /set testsigning on

Also, make sure secure boot is not enabled in the BIOS because that will prevent test mode from working in Windows 8.

Thanks ToastyX!! That did the trick. I went into my UEFI BIOS and disabled Secure Boot and everything works perfectly now. You da' man!

[Faiyez]

Edit: nevermind

[ToastyX]

Do you have a QNIX monitor? It doesn't need the SL-DVI/HDMI limits patched, so try it anyway.

[Faiyez]

(07-02-2013 01:53 AM)ToastyX Wrote:  Do you have a QNIX monitor? It doesn't need the SL-DVI/HDMI limits patched, so try it anyway.

I am stupid and I apologize for that.

I forgot to uncheck "include extension block" in CRU.

Your patcher works like a charm with 326.01 drivers.

[fordmustang68gt]

Well, I found out something that I guess I should have understood about using CRU when setting up my Overlord monitor. After searching around on the web, as I was having issues keeping my monitor at 120 hz and accessing Modern Warfare-Warfighter through Origins, I found a link stating around using CRU. It indicated that when bring up CRU, use the drop down menu and delete any former monitors/modifications other than your current setting for the Overlord monitor. Well DUH, I did that, restarted the computer and WHAM, things work GREAT! I guess as shown on the overclocking vidio on Overlord.......the DUH word fits here. Hats off to Toasty for his great work and a big DUH to me for not fully understand all I needed to do to make this montor work to it full potential. Anyway, to anyone else overlooking this step, please learn from my experience.

[ToastyX]

That's weird. The other entries shouldn't affect anything. The only ones that matter are the active ones.

[darckhart]

so, i just tried patcher v1.1.5 after installing the new 326.01 drivers for my titan and got this weird looking response. (ran it again so i could get the screen cap.) and since i'm using a DL-DVI on this catleap, i can't really check the ones where it says not found.

http://i.imgur.com/hL3F4Xv.png

[sephr]

The patcher needs updated for 326.19 on x64, SLI

[Faiyez]

(07-19-2013 04:35 AM)sephr Wrote:  The patcher needs updated for 326.19 on x64, SLI

The new beta driver is broken. Doesn't even recognize my Qnix. Rolled back to 326.01