NVIDIA Pixel Clock Patcher

[broken pixel]

I use win8 64 bit and the pixel clock patcher worked for me. OC my ASUS VW266 1980x1200 @ 72Hz via HDMI cable. I know ToastyX programmed worked because Nvidia CP custom resolution would only allow me to OC to 64Hz before I applied his patch. I used both 310.70 and 310.90 drivers to test.

I will test more when I get home since I have an Overlord Tempest X270OC - Grade A waiting for me at my front door. Whoop!

[peanutlasko]

Would you be willing to look at the pixel limit on Macs? Not asking for a "for sure patch", just an opportunity to look at the driver and see what you can do.

I'd be happy to donate towards the effort if there is any even remote chance it's feasible.

[ToastyX]

No. Dealing with Macs is a hassle. AMD/ATI, NVIDIA, and Intel all have different drivers, and different generations of GPUs have separate drivers in OS X, and every version of OS X has different versions of these drivers with no way to download them separately. On top of that, most Macs don't have dual-link DVI ports, so you have to use active adapters, which have their own limitations. There's no way I can deal with all those combinations without having the hardware available to test them myself. There might be other software limitations as well.

[Absalom]

Can anyone confirm the patcher unlocks the pixel clock cap with GTX200 series under Win7 64?

Ran the patcher, everything patches successfully. However, when I add a 2560x1440x32 custom res via CRU or NVCP, any refresh rate over 81MHz is simply not applicable. NVCP is still giving me the dreaded "not supported by your display" message. Refreshes above 81 added via CRU are simply not showing up in the Windows Monitor Settings dropdown.

FYI: Using the 310.90 drivers and successfully booted in testmode.

For the heck of it, I tried signing the drivers with DSEO, but still no dice.

Any advice?

[ToastyX]

The patch has no effect on the 200 series GPUs. You can use 301.42 without the patch to get 100 Hz by reducing the vertical total to 1450 (or 97 Hz with CVT-RB). You'll have to use the NVIDIA control panel because CRU can't go past 330 MHz with 301.42.

[Absalom]

(01-19-2013 06:24 AM)ToastyX Wrote:  The patch has no effect on the 200 series GPUs. You can use 301.42 without the patch to get 100 Hz by reducing the vertical total to 1450 (or 97 Hz with CVT-RB). You'll have to use the NVIDIA control panel because CRU can't go past 330 MHz with 301.42.

Hmph. Well that figures.

Thanks for the info, ToastyX.

[Mkilbride]

Hey, NVIDIA released new drivers, 313.95, and this no longer works properly, all I get is a Black screen when I try to change to anything above 60. Then I have to reboot.

I've done everything as I always do it...so this odd. Got the monitor driver installed, test mode on, this patcher enabled...I had this problem before and it had turned out I had -not- re-installed the Monitor driver.

But I have this time, so I figure it must be driver related...

[sephr]

I'm having the same issue as Mkilbride with the 313.95/96 beta drivers.

[Sheepit]

313.95 working fine for me. Installed graphics driver & PhysX portions (none of the extras), ran the patcher, rebooted.
Running at 120hz on my Catleap just fine.

Edit: Using GTX 670's in SLi, and CRU for resolution changes.

[magnus333]

313.95 isn't working for me in 64 bit, same issue as above. The patcher says HDMI limit: not found, the others say patched.