Post Reply
NVIDIA Pixel Clock Patcher
07-20-2020, 11:58 PM
Post: #781
RE: NVIDIA Pixel Clock Patcher
(07-20-2020 07:09 PM)Shockpaddles Wrote:  First off, Thank you ToastyX for all your hard work on these patchers. Currently using the X-Star 27" 1440p overclocked to 110Hz but looks like its days are numbered if cant get past v446.14. Its been a great ride but thought this day would come sooner or later. Have used this app for a very long time so how can i support you Mr ToastyX as i have had years worth of usage from CRU and the Pixel patcher.
You can still use the monitor with the NVIDIA control panel and this: https://www.monitortests.com/forum/Threa...-inf-files

I have a Patreon and PayPal.
Find all posts by this user
Quote this message in a reply
07-21-2020, 10:08 AM
Post: #782
RE: NVIDIA Pixel Clock Patcher
Thank you, donated and inf file works great! get some more life out of this Korean monitor yet!
Find all posts by this user
Quote this message in a reply
07-22-2020, 05:06 PM (Last edited: 07-23-2020, 08:39 AM by fluffi444)
Post: #783
RE: NVIDIA Pixel Clock Patcher
If there is someone who's interest in export/import of custom resolutions made via Nvidia Control Panel:

There are two things to de done after you've done your resolutions:
Save: C:\ProgramData\NVIDIA\UnsupportedResolutions.dat
and
Export/Save: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000\CustomDisplay

Export 0000 and delete the not needed stuff.

To import these settings just copy UnsupportedResolutions.dat back to its place and import former saved *.reg file.
Reboot -> done.

I attached a reg file to clear custom resolution and to have an idea how this should look like.

This works with latest driver 451.67.

I kown there is a backup tool called NvCRBT. But this works not 100% with latest driver. The available resolutions are not shown in NVCP - Even if they are working if called via external tool as PowerStrip (yes - I'm still using it :-))

EDIT
It's more or less obvious what happens here (imho):
The *.reg file stores the custom resolutions actually.
In the UnsupportedResolutions.dat there is the selection in NVCP stored.


Attached File(s)
.reg  CLEAR_custom_resolutions.reg (Size: 61.13 KB / Downloads: 21)
Find all posts by this user
Quote this message in a reply
07-24-2020, 12:44 PM (Last edited: 07-24-2020, 07:04 PM by nvtester)
Post: #784
RE: NVIDIA Pixel Clock Patcher
When patching the latest Nvidia driver(451.67) with NVIDIA Pixel Clock Patcher(1.4.11), the AIDA64 Display->GPGPU menu crashed the program, when clicked the "GPGPU" menu. There is no crashes in AIDA64 "GPGPU" menu, when the driver is not patched with NVIDIA Pixel Clock Patcher(1.4.11). Test scenario:

AIDA64 Extreme ver. 6.25.5458 beta
NVIDIA Pixel Clock Patcher ver. 1.4.11
Windows 10 x64 ver. 2004, OS Build: 10.0.19041.388
GPU: MSI GTX 1650 GAMING X 4G(MS-V380)
Find all posts by this user
Quote this message in a reply
07-25-2020, 07:58 AM
Post: #785
RE: NVIDIA Pixel Clock Patcher
(07-24-2020 12:44 PM)nvtester Wrote:  When patching the latest Nvidia driver(451.67) with NVIDIA Pixel Clock Patcher(1.4.11), the AIDA64 Display->GPGPU menu crashed the program, when clicked the "GPGPU" menu. There is no crashes in AIDA64 "GPGPU" menu, when the driver is not patched with NVIDIA Pixel Clock Patcher(1.4.11). Test scenario:

AIDA64 Extreme ver. 6.25.5458 beta
NVIDIA Pixel Clock Patcher ver. 1.4.11
Windows 10 x64 ver. 2004, OS Build: 10.0.19041.388
GPU: MSI GTX 1650 GAMING X 4G(MS-V380)

Please read all posts starting #767 and try Driver 446.14 (which is now known as the last working driver if patching is mandatory).
Find all posts by this user
Quote this message in a reply
07-27-2020, 06:41 AM (Last edited: 07-27-2020, 06:43 AM by ELK)
Post: #786
RE: NVIDIA Pixel Clock Patcher
I am using a dummy plug. It plugs into display port and is seen as a DVI single link. I am able to make and use the resolution 3840x2160@90hz with standard timings IF I make the resolution in the nvidia control panel. The problem is that my video game does not see nvidia's custom resolution which normally would not be a problem because I would just make them in CRU. Any resolution I make exceeding DVI single link's 165mhz limit will NOT show up if created in CRU. This applies to detailed resolution 4k@75hz. CES extension block 4k@75hz. DisplayID as only extension block 4k@90hz.

4k@30hz is actually in the dummy plug's edid, but it does not show up as it exceeds dvi single link 165mhz.

Why do CRU resolutions exceeding dvi single link 165mhz not show up when I can create 1000mhz+ resolutions in nvidia control panel using this patcher?
Find all posts by this user
Quote this message in a reply
07-28-2020, 01:23 AM
Post: #787
RE: NVIDIA Pixel Clock Patcher
(07-27-2020 06:41 AM)ELK Wrote:  Why do CRU resolutions exceeding dvi single link 165mhz not show up when I can create 1000mhz+ resolutions in nvidia control panel using this patcher?
NVIDIA's driver applies certain limits to EDID overrides but not the NVIDIA control panel.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 6 Guest(s)