AMD/ATI Pixel Clock Patcher

[Mush256]

Thank you so much, I'm gonna try this and tell you the error codes when I get back home tomorrow.

[Mush256]

(07-16-2022 02:36 AM)ToastyX Wrote:  

(07-16-2022 01:18 AM)Mush256 Wrote:  Hello, I have a pretty big problem. I am using a MSI Armor RX 570 8GB and atikmdag-patcher 1.4.13 (also tried 1.4.12 and 1.4.9) doesn't seem to work on the latest Dev Channel Windows 11 insider build. (25158 to be specific, + using 22.1.2 drivers, because newer ones don't work with some of my gzdoom stuff.)
It always shows 2 errors:
CryptUIWizDigitalSign failed: 0x12
CryptUIWizDigitalSign failed:0x80070020
and then this:
Failed to sign new driver file.

It shows two errors because if normal signing fails, it tries to fall back to test signing, which is also failing. The second error code is a sharing violation, which means the signing function can't access a file because it is being used by another process. I just realized it's not reporting the correct error code for the first one. Try this and let me know what the error codes are: https://www.monitortests.com/atikmdag-patcher-test.zip

Now it shows 0x80000003 on the first one.

[ToastyX]

(07-17-2022 02:55 PM)Mush256 Wrote:  Now it shows 0x80000003 on the first one.

That means path not found, which doesn't make sense. While the first error message is still on the screen, does this file exist: C:\Windows\System32\drivers\atikmdag.sys.new

[Mush256]

(07-17-2022 03:19 PM)ToastyX Wrote:  

(07-17-2022 02:55 PM)Mush256 Wrote:  Now it shows 0x80000003 on the first one.

That means path not found, which doesn't make sense. While the first error message is still on the screen, does this file exist: C:\Windows\System32\drivers\atikmdag.sys.new

yes, it does exist

[Mangix]

while this is a windows tool, have you looked into the open source amdgpu driver on linux? I'm currently overclocking by flashing the EDID. The highest I've gotten on my QX2710 monitor is 84.40Hz (pixel clock 339.999). I see there's code for > 340Mhz pixel clock but I can't really make sense of it.

[pyrorob]

(07-17-2022 03:28 PM)Mush256 Wrote:  

(07-17-2022 03:19 PM)ToastyX Wrote:  

(07-17-2022 02:55 PM)Mush256 Wrote:  Now it shows 0x80000003 on the first one.

That means path not found, which doesn't make sense. While the first error message is still on the screen, does this file exist: C:\Windows\System32\drivers\atikmdag.sys.new

yes, it does exist

i am having the exact same error as this guy, but on win 11 25163 +amd 22.6.1
including the .new file in drivers.

[ToastyX]

(07-26-2022 12:14 AM)pyrorob Wrote:  i am having the exact same error as this guy, but on win 11 25163 +amd 22.6.1
including the .new file in drivers.

I don't know if there's a bug in the newer Windows builds or if they're blocking my method of signing. It doesn't tell me what path it's not finding.

Microsoft has gone out of their way to prevent ordinary users from developing and signing drivers, so if this is an intentional change, then it won't be an easy fix.

The second error seems to be a bug in Windows triggered by the first method failing. The second method would require Windows to be in test mode. I will have to add an option to bypass the first method.

[ToastyX]

(07-23-2022 11:29 PM)Mangix Wrote:  while this is a windows tool, have you looked into the open source amdgpu driver on linux? I'm currently overclocking by flashing the EDID. The highest I've gotten on my QX2710 monitor is 84.40Hz (pixel clock 339.999). I see there's code for > 340Mhz pixel clock but I can't really make sense of it.

I wanted to deal with Linux eventually, but not at this time.

[Mashiro]

I am having issues with the digital signature of the drivers, is it normal when I go to GPU-Z and under Digital Signature it will show as "Unknown"? it should WQHL or Beta right? With that, I cannot launch Apex Legends with the applied patch. But with other EasyAntiCheat games, it works. The workaround I did was to remove the patch when I'm gonna launch Apex, then use the patch again after. No need to restart so that I can still have the benefit of the patch.

EDIT: Just read previous replies, it seems like there are issues with signing because of Windows 10. I'm on 21H2 Build 19044.1865 if it helps.

[ToastyX]

(07-30-2022 08:26 PM)Mashiro Wrote:  I am having issues with the digital signature of the drivers, is it normal when I go to GPU-Z and under Digital Signature it will show as "Unknown"? it should WQHL or Beta right? With that, I cannot launch Apex Legends with the applied patch. But with other EasyAntiCheat games, it works. The workaround I did was to remove the patch when I'm gonna launch Apex, then use the patch again after. No need to restart so that I can still have the benefit of the patch.

EDIT: Just read previous replies, it seems like there are issues with signing because of Windows 10. I'm on 21H2 Build 19044.1865 if it helps.

Their issue is with the dev build of Windows 11 not being able to sign the driver, which is not the same as your issue. I can't WHQL sign. Only Microsoft can. If unpatching without restarting works around the problem, then it's not a signing issue because the patched driver is still loaded until you restart the driver or reboot. Do you get an error message when launching Apex Legends with the patch applied?