AMD/ATI Pixel Clock Patcher

[ToastyX]

I will come up with a more future-proof method of finding the DVI/HDMI limit for newer drivers.

[Nick0602]

(06-06-2015 08:47 PM)ToastyX Wrote:  I will come up with a more future-proof method of finding the DVI/HDMI limit for newer drivers.

Much appreciated!
Thanks a lot for your efforts!

[ToastyX]

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

The new method works all the way back to 11.9, so hopefully that will work for a while.

[MojoW]

(06-07-2015 03:22 AM)ToastyX Wrote:  Try this: https://www.monitortests.com/atikmdag-patcher-1.3.4.zip

The new method works all the way back to 11.9, so hopefully that will work for a while.

Thank you sir.
It works as it should again.

Will CRU be updated for this too?
As the newly added Res/Hz does not show up in windows or CCC.

[ToastyX]

(06-07-2015 09:03 AM)MojoW Wrote:  Thank you sir.
It works as it should again.

Will CRU be updated for this too?
As the newly added Res/Hz does not show up in windows or CCC.

CRU is not driver-specific. It shouldn't need to be updated. Are you sure it's not a pixel clock limit?

What monitor do you have? Are you using DVI or HDMI? What resolutions are you trying to add?

[Nick0602]

(06-07-2015 09:36 AM)ToastyX Wrote:  CRU is not driver-specific. It shouldn't need to be updated. Are you sure it's not a pixel clock limit?

What monitor do you have? Are you using DVI or HDMI? What resolutions are you trying to add?

1.3.4 works fine here with a QNIX QX2710 at 100Hz via DVI-DL:
http://i.imgur.com/Rd6jKQO.png

Thanks a lot again^^

[MojoW]

(06-07-2015 09:36 AM)ToastyX Wrote:  

(06-07-2015 09:03 AM)MojoW Wrote:  Thank you sir.
It works as it should again.

Will CRU be updated for this too?
As the newly added Res/Hz does not show up in windows or CCC.

CRU is not driver-specific. It shouldn't need to be updated. Are you sure it's not a pixel clock limit?

What monitor do you have? Are you using DVI or HDMI? What resolutions are you trying to add?

Yeah it was because of the limit.
I was confused as the last time that the patcher didn't work, CRU would still add the Hz but just gave me a black screen on reboot.(Because of the pixel clock limit)
But all is good now and i'm sorry for the confusion ToastyX.
Keep up the great work and thank you again!

[montymintypie]

Just posting this here for any future Googlers:

Qnix 27" 1440p defaulted to 30Hz and cannot break 70Hz.

Upgraded my drivers from 14.something to the new Omega drivers. Have successfully done a 120Hz overclock previously on my Qnix. 60Hz 1440p disappeared! Tried the Pixel Clock Patcher + CRU to add 60Hz, good as gold. Tried to go to 90, digital rain, complete garbage. At 70Hz I was getting artifacts I would only previously get at 150Hz.

Solution? Roll back to 14.9 Catalyst. Not sure why it exploded with Omega, but there we go...

Thanks for the great utility! Happy on 96Hz right now

[Screemer]

I have the same problem the other users had before. CCC or Settings don't show the resolutions/frequencies i added with cru. I am on the 15.4.1 beta. My Monitor is a qnix dp2710 connected by dl-dvi.

I already tried patching and undoing it multiple times and i restarted after patching. Didn't work for me.

Am i doing something wrong?
[Image: http://abload.de/img/resolutionso5uug.jpg]

[ToastyX]

(06-27-2015 12:45 PM)Screemer Wrote:  I have the same problem the other users had before. CCC or Settings don't show the resolutions/frequencies i added with cru. I am on the 15.4.1 beta. My Monitor is a qnix dp2710 connected by dl-dvi.

I already tried patching and undoing it multiple times and i restarted after patching. Didn't work for me.

Am i doing something wrong?

You need to update CRU because of this issue:

(09-07-2012 09:06 PM)ToastyX Wrote:  Changes in 1.1.1:

• Fixed monitors with invalid signal type information not working with AMD/ATI GPUs