AMD/ATI Pixel Clock Patcher

[ToastyX]

Try this: https://www.monitortests.com/atikmdag-patcher-1.4.0.zip

[Garwinski]

(09-12-2016 03:00 PM)ToastyX Wrote:  Try this: https://www.monitortests.com/atikmdag-patcher-1.4.0.zip

Worked for me. Thanks! I have not yet tried any games but I will do this tonight and I'll report back/edit this post whether it works or not.

[malaquita]

(09-12-2016 03:00 PM)ToastyX Wrote:  Try this: https://www.monitortests.com/atikmdag-patcher-1.4.0.zip

And for me too. Qnix2710+AMD FURY

Enviado desde mi ASUS_Z00AD mediante Tapatalk

[kev007]

Quote:1.4.0: Updated for 16.9.1. Changed the way the driver is located and patched. Replaced 640x480 limit with low-resolution limit. Fixed VGA limit for 32-bit.

Thanks a million ToastyX! Let me buy you a beer!

35T01731SE476793P

[the9quad]

(09-12-2016 03:00 PM)ToastyX Wrote:  Try this: https://www.monitortests.com/atikmdag-patcher-1.4.0.zip

This version is broke for me, 1.3.6 still work though.
Anyway:
Driver:Catalyst 16.9.1 (sept 13th) 64 bit.
OS: Windows 10 Pro.
Video Cards: 2 R9 290x's in CFX.
Monitors: Qnix 2710 (1440p) single input over HDMI. Samsung (1080p) over HDMI.

Here is what happens, I install the driver and reboot everything works fine. Run the patcher, it finds all the values fine and patches them. Reboot, and my qnix no longer works, only the samsung, and I keep getting a display driver is not working message.

So I uninstall the driver, use DDU, install the driver and try again two more times, always the same result.

Finally, do it all again, but this time use the old 1.3.6 version of pixel patcher, and everything works fine.

Not sure what 1.4.0 does differently, but it definitely breaks something on my end.

[ToastyX]

(09-14-2016 05:29 PM)the9quad Wrote:  

(09-12-2016 03:00 PM)ToastyX Wrote:  Try this: https://www.monitortests.com/atikmdag-patcher-1.4.0.zip

This version is broke for me, 1.3.6 still work though.
Anyway:
Driver:Catalyst 16.9.1 (sept 13th) 64 bit.
OS: Windows 10 Pro.
Video Cards: 2 R9 290x's in CFX.
Monitors: Qnix 2710 (1440p) single input over HDMI. Samsung (1080p) over HDMI.

Here is what happens, I install the driver and reboot everything works fine. Run the patcher, it finds all the values fine and patches them. Reboot, and my qnix no longer works, only the samsung, and I keep getting a display driver is not working message.

So I uninstall the driver, use DDU, install the driver and try again two more times, always the same result.

Finally, do it all again, but this time use the old 1.3.6 version of pixel patcher, and everything works fine.

Not sure what 1.4.0 does differently, but it definitely breaks something on my end.

That's strange because that means the driver is installing two different ways depending on something on the system. Have you installed the Windows 10 anniversary update or are you still using 1511?

[the9quad]

(09-12-2016 03:00 PM)ToastyX Wrote:  That's strange because that means the driver is installing two different ways depending on something on the system. Have you installed the Windows 10 anniversary update or are you still using 1511?

I don't think I have installed the anniversary update.

[ToastyX]

I was able to reproduce the problem by modifying the driver .inf file to install the "old" way. This is strange because all the .dll files are in the right place, and 16.7.3 does not behave like this.

It seems they changed the way the .dll files are located:

• If the .sys file is in the old location, it looks for the .dll files in the old locations.
• If the .sys file is in the new location, it looks for the .dll files in the same directory as the .sys file and ignores the ones in the old locations.
  

The driver only seems to install the new way if you have the anniversary update installed. It seems I will have to make the patcher create links to all the .dll files even if they're in the old locations.

[ToastyX]

This should work: https://www.monitortests.com/atikmdag-patcher-1.4.1.zip

If you used the old 1.3.6 patcher, you'll have to run it three times to patch it the new way. The first time, it will just fix the low-resolution limit and leave everything else alone. The second time, it will restore from backup. The third time, it will patch the new way. You only need to reboot after the third time.

[Sampulla]

I am having a problem with newest version of patcher 1.4.1 and 16.9.1 WHQL driver. I am using Windows 10 anniversary with latest updates. When i try to patch it gives me error: Failed to create driver links. Using DDU and reinstalling drivers didnt help.