Monitor Tests Forum

Full Version: AMD/ATI Pixel Clock Patcher
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Thank you very much. I should have tested that as well. Sorry.
Sorry for my double post.

Still can't get it working. Resolutions and refreshrates are available but only get a screwed-up image on my screen. i already get artifacts at 68Hz.

i switched gpu from 7950 to 290x and it was working fine with my tahiti up to 120Hz. Any ideas?
(06-29-2015 03:03 PM)Screemer Wrote: [ -> ]Sorry for my double post.

Still can't get it working. Resolutions and refreshrates are available but only get a screwed-up image on my screen. i already get artifacts at 68Hz.

i switched gpu from 7950 to 290x and it was working fine with my tahiti up to 120Hz. Any ideas?

I'm not sure what you mean by screwed-up image. If the entire screen is garbled, keep in mind this issue:
(09-07-2012 09:07 PM)ToastyX Wrote: [ -> ]
  • AMD/ATI cards have a design limitation unrelated to the patch that causes video acceleration to scramble the screen if the vertical blanking/total is below standard with the video card's memory overclocked or with multiple monitors connected. Skype is known to trigger this problem. Either don't overclock the video card's memory, or use the "LCD standard" vertical blanking/total in CRU.

If that's not the issue, then I wonder if it's related to the problem montymintypie reported on the previous page, but I don't see how that could happen unless the video card is sending a single-link signal, which would be a new problem that I haven't heard of before. Does choosing "Custom extension block" make a difference?
(07-02-2015 05:07 AM)ToastyX Wrote: [ -> ]If that's not the issue, then I wonder if it's related to the problem montymintypie reported on the previous page, but I don't see how that could happen unless the video card is sending a single-link signal, which would be a new problem that I haven't heard of before. Does choosing "Custom extension block" make a difference?
this seems to be the case. will try 14.9 again and will report back. same monitor, similar setup, similar problem.

is there anyway we can control if it's a single- oder duallink-connection?
Hi Toasty, this might be a little premature, but anyway: do you know if we'll still need this patcher (and CRU) if upgrading to Windows 10 next month, and if so if it will work?

I'm referring specifically to overclock the Tempest/Catleap/etc. monitors to approx. 120Hz.

Thanks.
(07-03-2015 07:55 AM)Black Octagon Wrote: [ -> ]Hi Toasty, this might be a little premature, but anyway: do you know if we'll still need this patcher (and CRU) if upgrading to Windows 10 next month, and if so if it will work?
I already tested Windows 10. Everything still works the same way. Nothing is different with Windows 10.
(07-02-2015 10:57 PM)Screemer Wrote: [ -> ]this seems to be the case. will try 14.9 again and will report back. same monitor, similar setup, similar problem.

is there anyway we can control if it's a single- oder duallink-connection?
That's handled by the driver. The only thing that would make it send a single-link signal is if HDMI support is defined in the extension block. Did you try setting "Custom extension block" in CRU? You don't have to have anything in it. The QNIX doesn't actually have an extension block, but it reports having one, so that may be confusing the driver. Also, try 68 Hz without the patch just to make sure it's not an issue with the patch. You can test up to 80 Hz without the patch. If that doesn't work properly, then it's probably a driver bug.
(07-05-2015 04:29 AM)ToastyX Wrote: [ -> ]
(07-03-2015 07:55 AM)Black Octagon Wrote: [ -> ]Hi Toasty, this might be a little premature, but anyway: do you know if we'll still need this patcher (and CRU) if upgrading to Windows 10 next month, and if so if it will work?
I already tested Windows 10. Everything still works the same way. Nothing is different with Windows 10.

Great, thanks!
Hi Toastyx got it working again on my 290 with 15.4beta. Using the other dvi-port and it worked with no artifacts out of the box. Seems to be a problem with the other dvi-port.

Now i am trying to overclock with a active dp->dvi-adaptor from accell. It's the following one. Other are using it with a native 144Hz-Monitor and it's working up to 120Hz with 1440p.

but the highest refreshrate is 81Hz with standard timings and 82Hz with reduced lcd timings. same behavior as without the pixelclock patch. i tried the different extensionblocks as well with no avail. do you have any idea about that?

[Image: http://abload.de/img/refresh79s8x.png]

€dit: ahh. i saw that i forgot to open the dropdown for the refreshrates when i made the screenshot. the 81Hz is the highest available rr.
Is your 290X overclocked? Some users have reported trouble with overclocking their monitors with the 290 / 290X if they have a GPU core or memory overclock.
Reference URL's