NVIDIA Pixel Clock Patcher

[MBarros91]

Hey fellow, I have a 9600GT XFX GPU with Dx11 support and, instead as common, it only supports Shader Model 4.0. Can you tell if I can "unlock" the Shader Model 5.0 support or the game requirement with this software/utility/patcher?

[ToastyX]

(03-27-2021 01:04 AM)MBarros91 Wrote:  Hey fellow, I have a 9600GT XFX GPU with Dx11 support and, instead as common, it only supports Shader Model 4.0. Can you tell if I can "unlock" the Shader Model 5.0 support or the game requirement with this software/utility/patcher?

No.

[crankz]

i get this after using the patch...

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)
gtx 960, dvi-i, tried different OS and Drivers still the same

anyone knows why

[crankz]

(03-27-2021 06:02 PM)crankz Wrote:  i get this after using the patch...

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)
gtx 960, dvi-i, tried different OS and Drivers still the same

anyone knows why

Guess i found the issue...

AMD/Nvidia Pixel Clock Patcher

We only support official graphic drivers, drivers patched with AMD/Nvidia Pixel Clock Patcher will not work as they are not signed with a proper digital certificate

Is there a way u can rework the program to avoid this ?

[ToastyX]

(03-27-2021 07:57 PM)crankz Wrote:  We only support official graphic drivers, drivers patched with AMD/Nvidia Pixel Clock Patcher will not work as they are not signed with a proper digital certificate

Is there a way u can rework the program to avoid this ?

No, it's impossible without forming a company and spending hundreds of dollars per year for an EV certificate. Kernel-mode code signing certificates are no longer available, so everything has to be signed by Microsoft now, which has strict requirements. Then every driver version would have to be submitted to Microsoft, and every driver version would require a new patcher. That's not something I can do right now. Maybe in the future if I start a company, but the patcher is slowly becoming obsolete with HDMI 2.x and DisplayPort taking over.

The problem is really on FACEIT's end, not mine. Their software takes over your computer and breaks software they don't like. That should be considered malware.

[odikzz2]

Applying Patch to a SL-DVI still can't go beyond 165mhz Changing cable to DL-DVI Not patch still cannot go beyond 165mhz

My monitor is Asus vp228NE

HELP ME!

[ToastyX]

(06-09-2021 01:25 AM)odikzz2 Wrote:  Applying Patch to a SL-DVI still can't go beyond 165mhz Changing cable to DL-DVI Not patch still cannot go beyond 165mhz

What happens when you go beyond 165 MHz?

[odikzz2]

It's just black screen and when i try to reduce both horizontal and vertical and manage to overclock to 77hz which has a pixel clock of 164.83 but STILL BLACK SCREEN it's a shame that my old aoc monitor can do 90hz for now i can only reach 75hz.

[ToastyX]

(06-14-2021 12:10 PM)odikzz2 Wrote:  It's just black screen and when i try to reduce both horizontal and vertical and manage to overclock to 77hz which has a pixel clock of 164.83 but STILL BLACK SCREEN it's a shame that my old aoc monitor can do 90hz for now i can only reach 75hz.

Then it's a monitor limitation. The patcher is for GPU driver limitations.

[Alex997]

Trying out NVIDIA driver 471.11 today, but Pixel Clock Patcher 1.4.13 cannot find 'SL-DVI/HDMI limit' (all others found).

Does this mean we need a new Pixel Patcher version?

Many thanks