NVIDIA Pixel Clock Patcher

[AlphaRadke]

New TMDS limit for 451.67 released yesterday

[apav]

(06-28-2020 01:56 PM)ToastyX Wrote:  I can't do anything about that. The patcher doesn't mess with DLLs, so it has to be a bug in the DLL.

Hi ToastyX,

I can't believe I'm just asking this after using your tools for nearly seven years now, but is the Pixel Clock Patcher necessary for my custom resolution? I'm also having the issue where on Nvidia drivers starting with 451 and newer, patching the drivers causes certain games to crash at startup while using the original drivers doesn't. Just to test it, I tried making the same custom resolution I use in CRU (110hz with 432.78 MHz pixel clock) in the Nvidia Control Panel without patching my drivers first, and it worked. My games don't crash on startup either. But will I encounter any issues if I use this custom resolution without patching it?

Thank you.

[ToastyX]

(07-11-2020 02:02 PM)apav Wrote:  I can't believe I'm just asking this after using your tools for nearly seven years now, but is the Pixel Clock Patcher necessary for my custom resolution? I'm also having the issue where on Nvidia drivers starting with 451 and newer, patching the drivers causes certain games to crash at startup while using the original drivers doesn't. Just to test it, I tried making the same custom resolution I use in CRU (110hz with 432.78 MHz pixel clock) in the Nvidia Control Panel without patching my drivers first, and it worked. My games don't crash on startup either. But will I encounter any issues if I use this custom resolution without patching it?

In your case, you don't need the patch when using the NVIDIA control panel, but you should install this to make sure games recognize the higher refresh rate: https://www.monitortests.com/forum/Threa...-inf-files

[apav]

(07-11-2020 03:04 PM)ToastyX Wrote:  

(07-11-2020 02:02 PM)apav Wrote:  I can't believe I'm just asking this after using your tools for nearly seven years now, but is the Pixel Clock Patcher necessary for my custom resolution? I'm also having the issue where on Nvidia drivers starting with 451 and newer, patching the drivers causes certain games to crash at startup while using the original drivers doesn't. Just to test it, I tried making the same custom resolution I use in CRU (110hz with 432.78 MHz pixel clock) in the Nvidia Control Panel without patching my drivers first, and it worked. My games don't crash on startup either. But will I encounter any issues if I use this custom resolution without patching it?

In your case, you don't need the patch when using the NVIDIA control panel, but you should install this to make sure games recognize the higher refresh rate: https://www.monitortests.com/forum/Threa...-inf-files

Thanks so much, I'll do this! Why don't I need patch when using the Nvidia Control Panel in my case? I thought the patch was necessary to get past the 330 MHz limit with dual link DVI for any custom resolution.

[ToastyX]

(07-11-2020 03:34 PM)apav Wrote:  Thanks so much, I'll do this! Why don't I need patch when using the Nvidia Control Panel in my case? I thought the patch was necessary to get past the 330 MHz limit with dual link DVI for any custom resolution.

They got rid of pixel clock limits for the NVIDIA control panel many years ago, but the limits still apply to EDID overrides. The only limit that also affects the NVIDIA control panel is the SL-DVI limit on DL-DVI ports.

[ToastyX]

(07-11-2020 01:37 AM)AlphaRadke Wrote:  New TMDS limit for 451.67 released yesterday

Try this: https://www.monitortests.com/download/nv...1.4.11.zip

[MedGR45]

Been using this tool for years and it worked flawlessly, but unfortunately it doesn't anymore.
This is with the patch enabled, it disables/removes cuda support which is needed by almost all games/apps that released in the past decade:

So running any compute or 3D app will crash it and throw a cuda error in the event viewer directly.
And this is without the patch:

Running both the latest Windows 10 build and driver.

[ToastyX]

(07-12-2020 12:11 AM)MedGR45 Wrote:  Been using this tool for years and it worked flawlessly, but unfortunately it doesn't anymore.
This is with the patch enabled, it disables/removes cuda support which is needed by almost all games/apps that released in the past decade:

I can't do anything about that. I'm not touching anything related to cuda, so it probably happens with any change to the driver.

[fluffi444]

My two cents:

Patcher 1.4.11 changes the new TMDS limt an custom resolution are now working. 1.4.10 does not (for 451.67).

But I have the same strange issue with CUDA/PhysX

Driver 451.67 after pached with nvlddmkm-patcher-1.4.11:
   

Driver 451.67 after restored the backup with nvlddmkm-patcher-1.4.11:
   

Going back to 451.48 and patched 1.4.11 (!) -> CUDA/PhysX missing
   

And for further testing - And this is strange!
451.67 "patched" with 1.4.10 (!) - TMDS missing - But here also CUDA/PhysX missing:
   

451.48 and patched with 1.4.10 everything is working.
EDIT
NOT CORRECT. Sorry. Also here CUDA/PhysX is missing! I guess I overlocked this in the past...
Will try to find out when and with which driver this happens!

[fluffi444]

OK - Tried driver 446.14 with patcher 1.4.11 and CUDA/PhysX are OK:
   

So it looks like its NOT the patcher but the driver starting 451.48+.
Maybe NVIDIA itself changed something related to patching in generel and CUDA/PhysX. If this is only an cosmetic issue or the support is removed actually is out of my knowledge. Can't test this currently. But as @MedGR45 reported it removed the support... Maybe he can test if patched 446.14 works for him....