NVIDIA Pixel Clock Patcher

[mastermike]

Hi ToastyX,

I just wanted to say I really appreciate you making this tool - it is SO useful! I have 2x1440p @ 110hz and it works flawlessly!

Only recently have I encountered issues with it. The issue I am having is that certain games fail to launch (so far all the Borderlands series and now Halo the Master Chief Collection.)

I discovered the cause of the crashing by accident when I did a fresh driver install (used DDU to remove the old drivers), and all games launched successfully. Then I realized what was causing them to crash - it was the pixel clock patcher. I seriously cannot understand WHY that would cause the game to crash, but unfortunately it does. I verified this by: launching the game, immediate crash. Then I patched the old (default) clocks back, restarted the gpu drivers, and all games immediately stopped crashing.

Has anyone else encountered a similar issue or a fix?

[fluffi444]

(07-12-2020 03:53 PM)mastermike Wrote:  ....
Has anyone else encountered a similar issue or a fix?

Could you please try driver 446.14, patch it (use lastest 1.4.11) and see it this works?
Did you read all the last posts here from today? Maybe this goes to the same direction as @MedGR45 reported...

[bmq]

(07-10-2020 01:54 PM)ToastyX Wrote:  

(07-10-2020 05:23 AM)bmq Wrote:  I have an QNIX 2710 (v1) and had an "Inno3D IChill GTX970 Herkulez2" GK before, and everything worked fine with PP and CRU for 4 Years. Then i bought a new card 2 month ago, "EVGA RTX 2060 KO". When I use the latest PP and CRU ı get artifacts even at 60 Hz even before adding new frequencies. With my old card I could go 110 without artefacts. Now if I add 110Hz with CRU and do a restart I get coloured vertical lines and must reset with F8 because u can't see anything. If I go back and revert everything and do add 110Hz from the NVidia control panel it works, ok... but,

It sounds like the DVI port is acting like a single-link port. Are there artifacts at 60 Hz without the patcher?

There is no artifacts at all. Only if I use patcher and after CRU tool. :/

[tyabaryuu]

Hey, I wanted to notify that this pixel clock patcher is incompatible with RTX Voice. The instant I install the patch, RTX Voice crashes and will not work again until the patch is reverted.

Hope this information is useful to you!


Edit: Just figured out that the issue I'm experiencing is also related to the driver changes from 451.48 onward. CUDA and PhysX stop working as mentioned in previous posts, and in turn RTX Voice will no longer work either. I run Windows 10 Update 2004.

Edit 2: Downgraded to 446.14 and all systems nominal~

[fluffi444]

(07-13-2020 12:48 PM)tyabaryuu Wrote:  Hey, I wanted to notify that this pixel clock patcher is incompatible with RTX Voice. The instant I install the patch, RTX Voice crashes and will not work again until the patch is reverted.

Hope this information is useful to you!


Edit: Just figured out that the issue I'm experiencing is also related to the driver changes from 451.48 onward. CUDA and PhysX stop working as mentioned in previous posts, and in turn RTX Voice will no longer work either. I run Windows 10 Update 2004.

Edit 2: Downgraded to 446.14 and all systems nominal~

Thanks for your report. Looks like that we found the Problem. So 446.14 is working. Later drivers not.

Gesendet von meinem SM-G965F mit Tapatalk

[LELEKA_TURBO]

hi, have problem on 451.67 after patching. call of duty warzone crash on startup, after patch uninstall its ok.

here is log from windows

- EventData

ModernWarfare.exe
1.0.0.0
5f07519a
nvcuda.dll
27.21.14.5167
5f021f31
c0000409
00000000001f2c0c
44c
01d65a054936d23a
C:\Program Files (x86)\Call of Duty Modern Warfare\ModernWarfare.exe
C:\WINDOWS\system32\nvcuda.dll
02502514-8217-42f4-99ea-4854d08ddd39

[fluffi444]

(07-14-2020 05:51 PM)LELEKA_TURBO Wrote:  hi, have problem on 451.67 after patching. call of duty warzone crash on startup, after patch uninstall its ok.
.....

Are you kidding? We already talking about that last few days and the current solution/workaround is exactly above your post :-)

[MedGR45]

446.14 works fine here as well. Anything prior to the 451.x drivers works great; From the looks of it, it's a major change in the driver that's doing this issue given that Nvidia has added the new Hardware Accelerated GPU Scheduling support in Windows, and the addition of the WDDM 2.7 driver model. Hopefully there'll some thing to bypass this or a modded driver that doesn't remove/stop CUDA if it gets patched or any of its components gets altered. It's a long shot anyways...

[fluffi444]

(07-16-2020 09:45 PM)MedGR45 Wrote:  446.14 works fine here as well. Anything prior to the 451.x drivers works great; From the looks of it, it's a major change in the driver that's doing this issue given that Nvidia has added the new Hardware Accelerated GPU Scheduling support in Windows, and the addition of the WDDM 2.7 driver model. Hopefully there'll some thing to bypass this or a modded driver that doesn't remove/stop CUDA if it gets patched or any of its components gets altered. It's a long shot anyways...

Thanks for your report!
I guess we need master @ToastyX to have a look into this with hope he can help.
Hopefully there is a chance to solve this.

[Shockpaddles]

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.