AMD/ATI Pixel Clock Patcher

[lateforwork1000]

ok i tried it but it still did not work

[ToastyX]

(07-10-2022 11:10 PM)lateforwork1000 Wrote:  ok i tried it but it still did not work

Is the limit still 165 MHz or is it 297 MHz or 340 MHz?

[lateforwork1000]

it still have the 165 limit it will not move. i tried reinstalling the drivers with old drivers and new drivers then try using the reset-all.exe then try importing the .bin files. with the EDID box check, I'm still stuck at 165MHz.

[ToastyX]

(07-11-2022 03:32 AM)lateforwork1000 Wrote:  it still have the 165 limit it will not move. i tried reinstalling the drivers with old drivers and new drivers then try using the reset-all.exe then try importing the .bin files. with the EDID box check, I'm still stuck at 165MHz.

There must be something weird about the plug then. I wonder if the HDMI plug is writable. Maybe you can try writing a new EDID using this: https://www.monitortests.com/forum/Threa...yID-Writer

[lateforwork1000]

Okey i tried that I'm now able to go up to 340MHz

[lateforwork1000]

thanks!

[Mush256]

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.

[ToastyX]

(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

[Mush256]

The link doesn't work for me, it just returns me to page 1 of this thread.

[ToastyX]

(07-16-2022 12:39 PM)Mush256 Wrote:  The link doesn't work for me, it just returns me to page 1 of this thread.

Sorry about that. I've moved it here: https://www.monitortests.com/test/atikmd...r-test.zip