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.
Well on my PC (2x r9 290X) the clock patcher crash the new 14.12 Driver.
Until 14.11.1 it worked fine but when I patch the values the driver dont find anymore my graphic cards
(12-09-2014 11:40 AM)sepei Wrote: [ -> ]Well on my PC (2x r9 290X) the clock patcher crash the new 14.12 Driver.
Until 14.11.1 it worked fine but when I patch the values the driver dont find anymore my graphic cards
That sounds more like a signing issue to me. Did the patcher give any errors?

I'm not seeing any issues with 14.12. There's nothing different about the way the limits are handled.
(12-09-2014 01:07 PM)ToastyX Wrote: [ -> ]
(12-09-2014 11:40 AM)sepei Wrote: [ -> ]Well on my PC (2x r9 290X) the clock patcher crash the new 14.12 Driver.
Until 14.11.1 it worked fine but when I patch the values the driver dont find anymore my graphic cards
That sounds more like a signing issue to me. Did the patcher give any errors?

I'm not seeing any issues with 14.12. There's nothing different about the way the limits are handled.

Hello, just got registered to give my five cents.
The patching itself went fine.
But as soon as I made a custom resultion (hz) in CRU and rebooted stuff got weird.
Started with lines across the screen, keep in mind that I have not applied the new hz. Mostly because it was not there. And when I reverted the patching the screen just shows lines and colors. Had to reinstall the driver, tried a couple of times and same result.
Hope its an easy fix, need my silky smooth monitor Rolleyes

Specs: r9 290 with qnix 2710.
(12-09-2014 02:10 PM)eXizoR Wrote: [ -> ]
(12-09-2014 01:07 PM)ToastyX Wrote: [ -> ]
(12-09-2014 11:40 AM)sepei Wrote: [ -> ]Well on my PC (2x r9 290X) the clock patcher crash the new 14.12 Driver.
Until 14.11.1 it worked fine but when I patch the values the driver dont find anymore my graphic cards
That sounds more like a signing issue to me. Did the patcher give any errors?

I'm not seeing any issues with 14.12. There's nothing different about the way the limits are handled.

Hello, just got registered to give my five cents.
The patching itself went fine.
But as soon as I made a custom resultion (hz) in CRU and rebooted stuff got weird.
Started with lines across the screen, keep in mind that I have not applied the new hz. Mostly because it was not there. And when I reverted the patching the screen just shows lines and colors. Had to reinstall the driver, tried a couple of times and same result.
Hope its an easy fix, need my silky smooth monitor Rolleyes

Specs: r9 290 with qnix 2710.

Yeh same, atikmdag patcher works fine, 'CRU' tho seems to have issues with the new omega drivers. I have a variant TEMPEST OC (emaxeon) with flashed default OC settings in the edid of the monitor itself up to 110hz. Which works after pixel clock patching, but now if i try and run the cru to add my usual extra 120hz setting it now gets a brief blackscreen and driver has stopped responding each time on windows boot and breaks all refresh rates to only 60 or below.
If i run cru's reset-all.exe it fixes the driver recovery on boot and the 110hz default monitor setting.

Granted my OS install is fairly bloated, but havent had any issue with the pixel patcher or cru until these drivers... probably something to do with how these drivers handle VSR downsampling now.?

R290 CF / emaxeon 2710
That's odd, CRU works fine on my 1440p Achieva with the new drivers, Windows 10 and a 7950.

This driver update is focused on the newest cards from AMD (namely the 260(X), 290(X) and the 285). That could explain why my older 7950 works, but your 290s don't.


Hey ToastyX, what card do you test the patcher/CRU with?
Just uninstalled Afterburner and RTSS, rebooted.

Uninstalled AMD catalysts using CCC, rebooted.

Ran DDU, rebooted into safemode and it ran it's uninstall, rebooted.

Ran AMD catalyst Omega install, rebooted.

Applied Pixel patcher 1.3, rebooted.

Ran CRU 1.1.2, set resolution for 120hz rebooted

rebooted into the non-driver signature enforcement mode and added the qnix driver, rebooted.

installed latest afterburner, rebooted.

installed latest RTSS, rebooted.


Everything works perfectly.


Relevant system specs: Win 8.1 64 bit, sabertooth x-79 mobo, i7 4930k, Three R9 290x's. QNIXQX2710.

Hope that helps.
Ok after faf'ing about with new ddu omega several times and finding out i was still using cru1.1 and not 1.12 managed to get everything working.
(12-10-2014 06:09 PM)DOXaus Wrote: [ -> ]Ok after faf'ing about with new ddu omega several times and finding out i was still using cru1.1 and not 1.12 managed to get everything working.

I could have been doing the same thing.
But after seeing the9quad's steps I installed multiple hz qnix drivers from the forum and that worked like a charm.
Thanks!
ToastyX do you have any Webmoney wallet ?
(12-10-2014 07:40 PM)MaestroMental Wrote: [ -> ]ToastyX do you have any Webmoney wallet ?
No, it's not available to U.S. residents or citizens.
Reference URL's