Threaded Mode | Linear Mode

***ToastyX*** · 12-16-2021, 09:32 PM

(12-15-2021 07:06 PM)zamar19 Wrote: Having Gigabyte RX 460 rev.1.0 GPU, I tried to apply the Patcher 1.4.12 as admin to the latest AMD 21.12.1 driver on a Win 10 21H2 64-bit PC with all updates. It finds all the limits, but persistantly gives the error "Can't move driver file", even in PC Safe Mode when Win Defender is switched Off. If I restore the ATI WHQL driver supplied with Win 10 or install an older 2016 driver, the patcher gives another error "The driver file is too big". Cleaning GPU drivers with DDU and reinstalling any doesn't affect this error.

Those are both unusual problems. The "Failed to move driver file" error has never been reported before. Try removing this folder if it exists: C:\Windows\System32\drivers\atikmdag-patched

The current version of the patcher should work fine with older drivers. The "Driver file too large" error should not happen with older drivers because older drivers are not large enough to trigger the error. I can't think of anything that would cause this error if you're using the current patcher.

(12-15-2021 07:06 PM)zamar19 Wrote: Btw, I run the same Patcher on a clean installed Win 11 SSD on the same PC, and it patched the latest GPU driver from 2-nd attempt without any error. The 1st attempt went through OK, however when the driver get reinstalled the card was still blocked by Windows with Error 43, so the patch was apparently not fully applied despite no Patcher error.

If the patcher didn't report an error, then it applied successfully. The patch has to be applied every time the driver is updated. Windows Update has a nasty habit of updating the driver in the background even while you're installing a newer driver. Then when you reboot, it actually boots the older driver. It's best to disconnect from the Internet until after you've installed the new driver and rebooted.

zamar19 · (Last edited: 12-17-2021, 03:17 AM by zamar19)

(12-16-2021 09:32 PM)ToastyX Wrote: Try removing this folder if it exists: C:\Windows\System32\drivers\atikmdag-patched

Thanks, it patched without a glitch. Smile

But strange thing happen? I originally installed Crimson v16.11.5 2016 driver, which didn't require patching. Then I updated to the latest for Gigabyte RX 460 patched with your tool driver "Radeon-pro-software-21.q4-dec3" v. 30.0.14011.2006 dated 11/26/2021. However, GPU-Z still shows the same old Crimson driver was installed (see pic). Is it possible, AMD packed the old most stable driver for this card inside the latest driver? Still no GPU wakeup from sleep, and this bug was mentioned in the Crimson Release Notes.

I also suspect, the card BIOS is undervolted as it was used by a previous owner for mining, and it may cause failure to wakeup from sleep. But when trying to update to this (original?) BIOS, @bios tool says "The BIOS is the same" despite I know the installed BIOS is modded. What should I change with Polaris Bios Editor to have it recognized as new? As a guru, could you suggest if the same card would equally accept 512MB or 256MB BIOS? The installed BIOS is exported by @bios as 512MB, but GPU-Z exports it as 256MB - why? Sorry for the side questions, but Pixel Clock Patcher and GPU BIOS modding are logically linked.

***ToastyX*** · 12-17-2021, 04:50 AM

(12-17-2021 02:55 AM)zamar19 Wrote: Thanks, it patched without a glitch. But strange thing happen? I originally installed Crimson v16.11.5 2016 driver, which didn't require patching. Then I updated to the latest for Gigabyte RX 460 patched with your tool driver "Radeon-pro-software-21.q4-dec3" v. 30.0.14011.2006 dated 11/26/2021. However, GPU-Z still shows the same old Crimson driver was installed (see pic). Is it possible, AMD packed the old most stable driver for this card inside the latest driver?

No, the Pro driver is for Pro cards, so it didn't install the actual driver at all.

(12-17-2021 02:55 AM)zamar19 Wrote: I also suspect, the card BIOS is undervolted as it was used by a previous owner for mining, and it may cause failure to wakeup from sleep. But when trying to update to this (original?) BIOS, @bios tool says "The BIOS is the same" despite I know the installed BIOS is modded. What should I change with Polaris Bios Editor to have it recognized as new? As a guru, could you suggest if the same card would equally accept 512MB or 256MB BIOS? The installed BIOS is exported by @bios as 512MB, but GPU-Z exports it as 256MB - why?

That just means your card has 512 kB of EEPROM for the firmware, so smaller files should work if the firmware is compatible with your card. @BIOS might only be checking the signature instead of the whole image. Try using VBFlash: https://www.techpowerup.com/download/ati-atiflash/

Gennarino1234 · 12-17-2021, 05:38 PM

hi, I state that I have a Rx 480 Nitro +, I have installed the adrenalin 21.9.2 (the latest version supported according to the AMD / ATI Cloak Pixel 1.4.12
here my question ... but if I want I can install the latest update for the GPU, not that 21.10.2? or should I wait for an ati cloak pixel 1.4.13? thanks for everything and have a nice day.
Sorry if there is any mistake but I'm Italian

***ToastyX*** · 12-17-2021, 06:45 PM

(12-17-2021 05:38 PM)Gennarino1234 Wrote: hi, I state that I have a Rx 480 Nitro +, I have installed the adrenalin 21.9.2 (the latest version supported according to the AMD / ATI Cloak Pixel 1.4.12
here my question ... but if I want I can install the latest update for the GPU, not that 21.10.2? or should I wait for an ati cloak pixel 1.4.13? thanks for everything and have a nice day.
Sorry if there is any mistake but I'm Italian

You can use a newer driver if the patcher finds the limits you need.

Gennarino1234 · (Last edited: 12-17-2021, 08:26 PM by Gennarino1234)

(12-17-2021 06:45 PM)ToastyX Wrote:
(12-17-2021 05:38 PM)Gennarino1234 Wrote: hi, I state that I have a Rx 480 Nitro +, I have installed the adrenalin 21.9.2 (the latest version supported according to the AMD / ATI Cloak Pixel 1.4.12
here my question ... but if I want I can install the latest update for the GPU, not that 21.10.2? or should I wait for an ati cloak pixel 1.4.13? thanks for everything and have a nice day.
Sorry if there is any mistake but I'm Italian
You can use a newer driver if the patcher finds the limits you need.

do i need to update and re-install the cloacker? i dont want to delete all drivers and reinstall everything
thanks btw

how do i know if the patcher can find the limits i need?

zamar19 · (Last edited: 12-21-2021, 06:03 AM by zamar19)

(12-17-2021 08:24 PM)Gennarino1234 Wrote: do i need to update and re-install the cloacker?

Just run the patcher after the new driver is installed. Its window will show the limits found. It does work with latest GPU drivers.

Gennarino1234 · 12-18-2021, 01:21 AM

ok thx guys

matmanmining · 01-22-2022, 02:44 PM

Recently, as of 1/20/2022, a windows update had created an issue with driver signing for RX570 gpus that have been overclocked. Is it possible that a new atikmdag patcher will be released?

***ToastyX*** · 01-22-2022, 03:53 PM

(01-22-2022 02:44 PM)matmanmining Wrote: Recently, as of 1/20/2022, a windows update had created an issue with driver signing for RX570 gpus that have been overclocked. Is it possible that a new atikmdag patcher will be released?

Which update? What is the problem?