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.
Hello all,

I've been messing with the AMD Pixel Clock Patch & Custom Resolution Utility a bit for the last week and I've encountered some issues.
I immediately started by applying the patch and this seemed to be a success. It found all patches and applied all of them.
Then I started with CRU and added some custom resolution settings. My goal was overclocking my monitors hertz from it's default 60 to whatever high I can get. I have an Eyefinity setup of 3x1 with an additional screen as my "secondary" screen, so too said. My Eyefinity monitors are 3 x Asus VK248H and my additional "secondary" screen is an Samsung Smart TV.

What I've accomplished so far are:
3 Asus monitors from 60 to 70Hz by adding a custom resolution with LCD Standard and setting the amount of Hz to 70.
Samsung TV on 70Hz with LCD Standard also.

Whenever I try to get the Asus monitors on anything higher then 70Hz my monitors say "Input not supported". I've tried reducing the blanking, etc.. as much as possible which did succeed for quite a bit. I got the blanking as low as 100 from an 160 until tearing began to occur. This reduced the pixel clock from about an 163 to 155/157. However this only seemed to help to increase the refresh rate by just a little bit. Say till 72Hz or so. It looks like whenever I hit the 165 with the Pixel Clock my monitors seem to get the error. Now this could be coincidence, as my monitors might just be too cheap to handle anything more than 70Hz but it made me wonder if it isn't still being limited by the 165 Pixel Clock even after the patch.

Further more, I can get my Eyefinity setup to operate at 70Hz but everytime I reboot my PC it will boot in Extended Mode instead of Eyefinity mode.

Two of my Asus monitors are connected through a DVI-D Dual Link and one through HDMI-HDMI-to-DP active adapter. My TV is connected through HDMI. Though my TV doesn't have any trouble exceeding the 70Hz and I've gotten as far as 80Hz with no trouble at all. I haven't tried getting it higher so far.
They are all connected to my Asus HD7950-DC2T-3GD5-V2 which is Crossfired with another Asus HD7950-DC2T-3GD5-V2.

I would really love this to work and get me even further. Help would be much appreciated Smile
(09-12-2014 11:34 AM)HAXTC Wrote: [ -> ]Whenever I try to get the Asus monitors on anything higher then 70Hz my monitors say "Input not supported". I've tried reducing the blanking, etc.. as much as possible which did succeed for quite a bit. I got the blanking as low as 100 from an 160 until tearing began to occur. This reduced the pixel clock from about an 163 to 155/157. However this only seemed to help to increase the refresh rate by just a little bit. Say till 72Hz or so. It looks like whenever I hit the 165 with the Pixel Clock my monitors seem to get the error. Now this could be coincidence, as my monitors might just be too cheap to handle anything more than 70Hz but it made me wonder if it isn't still being limited by the 165 Pixel Clock even after the patch.
If 165.00 works but 165.01 doesn't, then it's a driver limitation. Otherwise, it's a monitor limitation.

(09-12-2014 11:34 AM)HAXTC Wrote: [ -> ]Two of my Asus monitors are connected through a DVI-D Dual Link and one through HDMI-HDMI-to-DP active adapter.
Active adapters also have their own limitations.
Hello everyone! Smile First of all thanks to Toasty for creating the awesome CRU and Pixel Clock Patcher! A friend recently introduced me to the idea of monitor overclocking and while I thought it was only feasible for 3D monitors with Lightboost and dismissed 70-75hz as being better I quickly noticed I was wrong, hitting 70hz for the first time I was in disbelief at how smooth window dragging and the Windows animations suddenly were. Now I want more but I have a problem going anywhere over 70hz so I decided to ask here for help.

I'm using a Club3D 7970 Royal Queen along with a LG 23ET83 IPS Monitor, connected with a HDMI to DVI cable, the HDMI end being on the monitor and Catalyst 14.6 Beta 1 with Windows 7 64bit. I did not use the Pixel Clock patcher yet but only CRU for now. If I add a custom resolution with 70hz and reboot I can select 70hz fine and it works perfect, now adding anything over 70hz, even 71hz doesn't even register in Windows. I tried adding 70, 71 and 75 with CRU and when I go to the Hz dropdown menu on Generic PnP Monitor everything above 70hz isn't listed even though CRU still has them listed as inserted. I used LCD Standard as my preset when adding 70hz, 71hz and 75hz.

I assume this means I have to use the Pixel Clock Patcher? If yes, reading around a bit here this means the following for me correct?

- I lose Flash hardware acceleration (I have that disabled anyway as it annoys me that my GPU clock gets stuck at 501mhz whenever a Youtube tab is open while not even playing)
- I can't use the Raptr Gaming Evolved App anymore (also a non-issue since I don't use it)

Now some questions I have beyond that:

- Will I also lose DXVA video acceleration in Media Player Classic for non-HDCP videos that aren't .wmvs?
- Can I still use AMD VCE hardware accelerated recording in MSI Afterburner?

Also some interesting thing I noticed, my monitor had a Detailed Resolution out of the box in CRU listed as 1920x1080@60hz with the polarity +/+ while my custom resolution for 1920x1080@70hz that works defaulted to +/-, does that mean anything?

Thanks for any help in advance, I know I asked alot here and I can imagine Toasty gets lots of questions each day so I appreciate any helping hand Smile

EDIT: A small update, I decided to update my drivers to the newest leaked Catalyst Beta and obviously had to redo the whole CRU process, however this time I picked LCD Reduced for 71 and 75hz and 75hz now shows up and seems to work fine! Big Grin Although my monitors OSD seems to display something strange now, the input signal is shown as: 1080p/1400x1050 75hz HDMI1
The actual displayed resolution still seems to be 1920x1080 though from what I can depict on screen and Windows itself says so aswell o.o Should I maybe open a separate thread?

EDIT 2: Seems like 75hz is a no-go for me, it works fine but causes my idle GPU clock to rise to 500mhz and my idle memory clock to 1375mhz o.o along with a temperature rise to 50°C so I will stick to 70hz for now I guess Sad

EDIT 3: Upon further reading seems like this is normal and happens when the blanking? is too low so I won't mess with it further by myself since I have no idea what I'm doing with CRU other than changing the refresh rate Tongue
(09-16-2014 01:47 PM)Skyy Wrote: [ -> ]- I can't use the Raptr Gaming Evolved App anymore (also a non-issue since I don't use it)

Now some questions I have beyond that:

- Can I still use AMD VCE hardware accelerated recording in MSI Afterburner?

I've been using AMD Gaming Evolved app and recording videos with it (new AMD VCE feature on Raptr) for a while now. I have applied pixel-patcher and CRU OC'd my monitor to 112Hz (from 60hz, my monitor is very overclockable - Qnix QX2710)
(09-17-2014 12:33 AM)InStars Wrote: [ -> ]
(09-16-2014 01:47 PM)Skyy Wrote: [ -> ]- I can't use the Raptr Gaming Evolved App anymore (also a non-issue since I don't use it)

Now some questions I have beyond that:

- Can I still use AMD VCE hardware accelerated recording in MSI Afterburner?

I've been using AMD Gaming Evolved app and recording videos with it (new AMD VCE feature on Raptr) for a while now. I have applied pixel-patcher and CRU OC'd my monitor to 112Hz (from 60hz, my monitor is very overclockable - Qnix QX2710)

Hmm interesting, I might have misunderstood something then, thanks! Smile I guess I'm going to try the patch since I can always just un-patch again later.
Woohoo, the 14.9 drivers have finally fixed my flickering issue (although I did find a workaround by increasing my gpu voltage with the beta drivers). No issues between 14.9 and the 1.2.7 patcher in case anyone was wondering.
Thanks for the continuing support Toasty!
(09-30-2014 04:56 AM)DrPhilGood Wrote: [ -> ]Woohoo, the 14.9 drivers have finally fixed my flickering issue (although I did find a workaround by increasing my gpu voltage with the beta drivers). No issues between 14.9 and the 1.2.7 patcher in case anyone was wondering.
Thanks for the continuing support Toasty!

This is great news, man! Also, interesting fix for your issue. Glad you're not getting it anymore Smile

I hope others report the same as far as compatibility
Toastyx do you think it will be possible to release a version of the AMD/ATI Pixel Clock Patcher that restores DXVA functionality?

I feel tied to using Catalyst 14.4 with Pixel Clock patch 1.2.4 because I really need DXVA support. I spent the last couple months using 14.7 with 1.2.6/7 and all the hardware video processing issues have been a total nightmare.

Examples: Disabling hardware acceleration in Chrome was necessary to make youtube videos work. Turning off hardware acceleration in MPC-HC was necessary to get decent playback. Flash videos have all kinds of weird playback issues with DXVA disabled. If you bitstream audio to a Home Theater Receiver then using Klite codecs aren't an option.

Thanks for all your hard work on this pixel patch. I really appreciate how difficult it must be to edit a video driver with more lines of code than Windows NT.
Hello Toastyx,
I need help, since the 14.9 catalyst, my crossfire of 290 tri-x doesnt works correcly (lot of stuttering) at 119hz ! When i take of the patch, it s works perfectly at 60hz.
Do you have a idea ?
Thann ! Smile
It s when i m playing battlefield 4 Big Grin
Reference URL's