AMD/ATI Pixel Clock Patcher

[fragfeaster777]

Hi eucalyptux,

Actually for me, even increasing my Hz to 70 breaks everything (ie garbled output at reboot), whilst with previous drivers I went up to 110 without issues

Another big thumbs up to ToastX for his amazing work!!

[falkentyne]

(07-13-2015 07:41 PM)fragfeaster777 Wrote:  Hi eucalyptux,

Actually for me, even increasing my Hz to 70 breaks everything (ie garbled output at reboot), whilst with previous drivers I went up to 110 without issues

Another big thumbs up to ToastX for his amazing work!!

15.7 is the first driver with Radeon Fury support, right?
I know fury-X doesn't have DVI ports anymore but Fury (Air cooled) one does. Looks like AMD changed something.

I haven't updated to 15.7 but I am using displayport now.

[ToastyX]

(07-13-2015 02:21 PM)fragfeaster777 Wrote:  So maybe there is something going on with Catalyst 15.7, especially since Patcher couldnt find the DVI limit.

Please check the latest version of the patcher before reporting limits not being found. The current version should already be compatible with 15.7.

(07-13-2015 07:41 PM)fragfeaster777 Wrote:  Actually for me, even increasing my Hz to 70 breaks everything (ie garbled output at reboot), whilst with previous drivers I went up to 110 without issues

If your card has two DVI ports, try the other DVI port. Some people are reporting issues with one of the dual-link DVI ports on R9 290 cards, but I can't confirm that myself.

[Screemer]

(07-12-2015 12:04 AM)ToastyX Wrote:  

(07-06-2015 01:41 PM)Screemer Wrote:  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.

I haven't heard of anyone getting 2560x1440 @ 120 Hz with that adapter. It can only handle around 100 Hz with 18-bit color (6 bpc). 1920x1080 @ 144 Hz is still under 330 MHz, so that wouldn't affect 144 Hz monitors.

could be that i got something wrong here. maybe the guy i was refering to used it on at 144Hz@1080p.

(07-12-2015 12:04 AM)ToastyX Wrote:  

(07-06-2015 01:41 PM)Screemer Wrote:  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?

That's weird because the 330 MHz dual-link DVI limit shouldn't affect DisplayPort with an active adapter unless AMD changed something recently. Other people have used that adapter with AMD cards, so I don't know why you're seeing this limit. The limit should be 360 MHz with 24-bit color (8 bpc) and 480 MHz with 18-bit color (6 bpc). Is the limit actually 330 MHz, or is it something else like 327 MHz or 360 MHz?

i will take a look at it as soon as i find some time. thanks for the explanations.

[clipped.osprey]

Hey yo ToastyX!

Thanks for the tool, man! I busted myself so hard trying to fix it, but thanks to you, my rig is working well now.

[jacques strap]

Sorry if this has been asked already but will the AMD Pixel Clock Patcher and CRU work with Windows10?

[Black Octagon]

(07-31-2015 01:07 AM)jacques strap Wrote:  Sorry if this has been asked already but will the AMD Pixel Clock Patcher and CRU work with Windows10?

Toasty said yes a few weeks back but I made the upgrade today and can double check later. Still installing updates and tweaking my actual OS

[Black Octagon]

Just tried it - works seamlessly just as before. Note that I used the latest version 1.3.4 of the patcher and version 1.2.1 of CRU. Thanks Toasty!

[ToastyX]

I just upgraded to Windows 10 myself. Everything works the same as before.

[Black Octagon]

Toasty, there is one thing that doesn't work the same anymore in Windows 10. I can no longer right-click YouTube videos to 'disable hardware acceleration' for Flash videos. As a result, I'm getting instant full-screen corruption when surfing in 120Hz and accessing videos (or even basic things like Skype). Hoping you know another way to disable hardware acceleration, as that's what I always did in the past to get around this. In the meantime, I'm surfing at 96Hz. Thanks a lot.

EDIT: Never mind I think I fixed it. I went into Control Panel --> Internet Options --> Advanced --> Accelerated graphics and checked the "Use software rendering instead of GPU rendering" box. Seems to have fixed everyting up