AMD/ATI Pixel Clock Patcher

[timescroll]

(10-24-2017 02:06 AM)ToastyX Wrote:  

(10-24-2017 01:27 AM)timescroll Wrote:  Last BETA driver and 17.10.2. broke Freesync mod were I set a freesync range of 30-74 while using a 75 hz resolution. Newest atipatcher does not seem to work. Instead of having a reange of 30-75 i get no Freesync support message . Seems Freesync range on HDMI block needs to Match monitor Hz to work and in this config i get the blanking problem anyway. Something wrong with new port limits ? Tried also the new atipatcher you posted @ToastyX

I have no idea what you're talking about. The patcher has nothing to do with FreeSync. What port limits are you talking about?

TLDR 17.10.1 FS range 30-74 and monitor Hz @ 75 produces a working configuration of 30-75 in Radeon drivers . BETA and latest driver break this and it is not supported . Now only a range of 30-75 in the block produces a supported configuration and comes with with blanking in games . I posted here because wuch things usualy get fixed with atipatcher . Might be a C..R.U. issue EDIT : I use DVI-D ΤΟ HDMI 1.4 and HDMI TO HDMI monitors both stopped performing the trick

[musti1595]

Hello everyone
i need do something about it. while im playing games like skyrim, w3, csgo im getting this screen and need to restart everytime. Sometimes its occuring in 5 min and sometimes its occurin 3 hour. i tried uninstall with ddu and fresly install but it didnt work.
Windows 10
Asus Hd7870 direct cu 2
amd fx 8350 ep
16gb ram

[Sabbathi]

(10-29-2017 08:16 AM)musti1595 Wrote:  Hello everyone
i need do something about it. while im playing games like skyrim, w3, csgo im getting this screen and need to restart everytime. Sometimes its occuring in 5 min and sometimes its occurin 3 hour. i tried uninstall with ddu and fresly install but it didnt work.
Windows 10
Asus Hd7870 direct cu 2
amd fx 8350 ep
16gb ram

Hello!

This issue may signal a hardware error.

I do not have experience with 7870, but with a 7970 reference Sapphire card.

After 5 years of overclocked gaming, I started getting this error during gaming and during 3dmark benchmarks.

The issue was resolved by 1) baking the card; and 2) replacing the thermal paste on the core and thermal pads on RAM and VRM chips.

You could take the card for baking to a specialist or do it yourself using online guides.

[pZombie]

(07-07-2017 04:45 AM)ToastyX Wrote:  

(07-06-2017 07:41 AM)Xuper Wrote:  after I flashed Bios RX 480 , I went AMD patcher and I get Error :

CryptUIWizdigitalSign failed : 0x12
CryptUIWizdigitalSign failed : 0x800b0003
Failed to sign new driver file

Something is wrong with your Windows installation. Either something is missing or disabled. I don't know what specifically because I've never been able to reproduce this on any system. A normal Windows installation would not have this problem.

I got the same error, so i ran windows in safe mode and see if it works there.

Sure enough, it worked fine. Not sure why, but probably has something to do with different user accounts and me having installed it under another occasion in safe mode, but that is just guess work.
Also i am not sure if installing it in safe mode is a good idea at all. It might cause other issues i am not aware of.

Hope that helps tracking the issue further.

[ToastyX]

(11-03-2017 07:01 PM)pZombie Wrote:  I got the same error, so i ran windows in safe mode and see if it works there.

Sure enough, it worked fine. Not sure why, but probably has something to do with different user accounts and me having installed it under another occasion in safe mode, but that is just guess work.
Also i am not sure if installing it in safe mode is a good idea at all. It might cause other issues i am not aware of.

Are you sure it's the same error with the same error codes? There's a different error code (0x80090016) that can be fixed by renaming or deleting the folder under %AppData%\Microsoft\Crypto\RSA. That issue would be specific to the user account and only affects the driver signing process. Using the patcher in safe mode is fine and shouldn't cause any errors.

[pZombie]

(11-03-2017 08:25 PM)ToastyX Wrote:  

(11-03-2017 07:01 PM)pZombie Wrote:  I got the same error, so i ran windows in safe mode and see if it works there.

Sure enough, it worked fine. Not sure why, but probably has something to do with different user accounts and me having installed it under another occasion in safe mode, but that is just guess work.
Also i am not sure if installing it in safe mode is a good idea at all. It might cause other issues i am not aware of.

Are you sure it's the same error with the same error codes? There's a different error code (0x80090016) that can be fixed by renaming or deleting the folder under %AppData%\Microsoft\Crypto\RSA. That issue would be specific to the user account and only affects the driver signing process. Using the patcher in safe mode is fine and shouldn't cause any errors.

I got the "same" error with two different codes. Before and after deleting the RSA folder. But deleting the folder did not really help installing it.
Safe mode worked however.

CryptUIwizDigitalSign failed 0x12 before deleting
CryptUIwizDigitalSign failed 0x6 CertCreateSelfSignCertificate failed 0x8009000f after deleting


As i said, my guess is that it worked because i guess that safe mode uses a different user account under which i formerly installed the patch. But that's just a lot of guesses. Could be some entirely different reason.

[ToastyX]

(11-07-2017 06:36 PM)pZombie Wrote:  I got the "same" error with two different codes. Before and after deleting the RSA folder. But deleting the folder did not really help installing it.
Safe mode worked however.

CryptUIwizDigitalSign failed 0x12 before deleting
CryptUIwizDigitalSign failed 0x6 CertCreateSelfSignCertificate failed 0x8009000f after deleting


As i said, my guess is that it worked because i guess that safe mode uses a different user account under which i formerly installed the patch. But that's just a lot of guesses. Could be some entirely different reason.

Maybe it's a permissions issue, but UAC is supposed to take care of that. The patcher doesn't do anything user-specific, but the signing process might. Microsoft didn't document the ways CryptUIWizDigitalSign can fail, and the error codes don't give me enough information to figure this out. The patcher only tries CertCreateSelfSignCertificate if the normal signing process fails, so that means both methods are failing. That tell me there has to be some external factor involved, like a missing service or some sort of permissions issue or user restriction. I don't know what because I've never been able to reproduce this.

[brnfex]

Hello, it seems like this patcher somehow breaks MSI Afterburner (and maybe other tools as well?) when it is used on Crimson 17.10.x and 17.11.x along with the Fall Creators Update.

I did a clean install of:
- Windows 1709 (Fall Creators Update)
- Afterburner 4.4.0 Final
- Any of the Crimson 17.10.x and 17.11.x drivers
- AMD/ATI Pixel Clock Patcher (atikmdag-patcher-1.4.6 and 1.4.5)

If the driver is stock (unpatched) - Afterburner works like usual. If I patch it - Afterburner shows blank values, no sliders and empty string for Driver version, however the graphics cards are visible in the list. If I revert the patch, Afterburner is still broken, until I completely reinstall the driver.

I have reported the same issue to the Afterburner's forum. Can you please look into it?

[ToastyX]

(11-15-2017 08:21 PM)brnfex Wrote:  Hello, it seems like this patcher somehow breaks MSI Afterburner (and maybe other tools as well?) when it is used on Crimson 17.10.x and 17.11.x along with the Fall Creators Update.

I did a clean install of:
- Windows 1709 (Fall Creators Update)
- Afterburner 4.4.0 Final
- Any of the Crimson 17.10.x and 17.11.x drivers
- AMD/ATI Pixel Clock Patcher (atikmdag-patcher-1.4.6 and 1.4.5)

If the driver is stock (unpatched) - Afterburner works like usual. If I patch it - Afterburner shows blank values, no sliders and empty string for Driver version, however the graphics cards are visible in the list. If I revert the patch, Afterburner is still broken, until I completely reinstall the driver.

I have reported the same issue to the Afterburner's forum. Can you please look into it?

I'm not seeing this issue, and I don't see how Afterburner could still be broken after reverting the patch.

[pkirill]

Hello, I have a very strange issue, after I install the patch, my start button does not work (also alt-tab not working).

Also I`m having strange errors during reboot:
https://photos.app.goo.gl/VGajfraPmJIcwl8W2

A have the latest Windows and I`m having the same issues with AMD blockchain drivers and also with the latest 17.11.4-Nov27 drivers.

Anyone else seen this?

I only need to disable bios check in driver.