AMD/ATI Pixel Clock Patcher

[Transmaniacon]

(04-19-2016 11:11 PM)kilyan Wrote:  

(04-19-2016 11:07 PM)Transmaniacon Wrote:  

(04-19-2016 10:55 PM)kilyan Wrote:  

(04-19-2016 10:04 PM)Transmaniacon Wrote:  Hi there, I recently purchased a HP 25XW monitor, which is 1080P and 60Hz stock. This monitor can be overclocked to 75Hz according to the NCX review. I have an AMD R9 390X with Crimson 16.4.1 connected to the monitor via HDMI.

I went in and applied the patcher, it found all of them except the 640X480. I then went into CRU and added a profile for 75Hz. When I went into my monitor properties I didn't see anything higher than 60Hz. In the Crimson utility, there is an option to set a custom resolution, but the highest it will let me go is 68Hz with a pixel clock of 168.3MHz. Am I doing something wrong here? Should every monitor of the same model overclock the same? I would like to get this up to 75Hz, but so far I am having no luck. Any ideas?

use cru, not custom resolution than it will work.. i managed to reach 77hz on 1920x1080m but trying to figure out with the help of toasty, why my driver is reverting to 16.3 from 16.4.1 after using the patch. besides of that, it works. YOu need also to restart driver after setting the monitor frequence

Are you using the same monitor? I just did it with CRU and if I entered a 75Hz refresh rate, it wouldn't show up in the drop down for my monitor. But if I put in 68Hz, then I can choose that when in display settings. Not sure why I can't get over the hump, could my cable be limiting the refresh rate?

You put 68 with cru or crimson? try also to set no block option in the lower part of cru, and lcd standard or lcd reduced, if you have not tried yet

Got it!!! I set no block and used LCD Standard and am now running at 75Hz, thanks so much!

[kilyan]

(04-19-2016 11:23 PM)Transmaniacon Wrote:  

(04-19-2016 11:11 PM)kilyan Wrote:  

(04-19-2016 11:07 PM)Transmaniacon Wrote:  

(04-19-2016 10:55 PM)kilyan Wrote:  

(04-19-2016 10:04 PM)Transmaniacon Wrote:  Hi there, I recently purchased a HP 25XW monitor, which is 1080P and 60Hz stock. This monitor can be overclocked to 75Hz according to the NCX review. I have an AMD R9 390X with Crimson 16.4.1 connected to the monitor via HDMI.

I went in and applied the patcher, it found all of them except the 640X480. I then went into CRU and added a profile for 75Hz. When I went into my monitor properties I didn't see anything higher than 60Hz. In the Crimson utility, there is an option to set a custom resolution, but the highest it will let me go is 68Hz with a pixel clock of 168.3MHz. Am I doing something wrong here? Should every monitor of the same model overclock the same? I would like to get this up to 75Hz, but so far I am having no luck. Any ideas?

use cru, not custom resolution than it will work.. i managed to reach 77hz on 1920x1080m but trying to figure out with the help of toasty, why my driver is reverting to 16.3 from 16.4.1 after using the patch. besides of that, it works. YOu need also to restart driver after setting the monitor frequence

Are you using the same monitor? I just did it with CRU and if I entered a 75Hz refresh rate, it wouldn't show up in the drop down for my monitor. But if I put in 68Hz, then I can choose that when in display settings. Not sure why I can't get over the hump, could my cable be limiting the refresh rate?

You put 68 with cru or crimson? try also to set no block option in the lower part of cru, and lcd standard or lcd reduced, if you have not tried yet

Got it!!! I set no block and used LCD Standard and am now running at 75Hz, thanks so much!

glad my suggestions helped ^^

[ToastyX]

(04-19-2016 05:36 AM)kilyan Wrote:  

(04-19-2016 04:12 AM)ToastyX Wrote:  I need the exact size in bytes as shown in the file properties.

not patched=26.345.472 byte dimension and dimension on disc are the same

patched=dimension:26.349.632 byte
dimension on disc:26.353.664 byte

Those are the correct file sizes for 16.4.1. The driver is not reverting. I don't know why it's showing you the wrong version.

[ToastyX]

(04-19-2016 11:23 PM)Transmaniacon Wrote:  Got it!!! I set no block and used LCD Standard and am now running at 75Hz, thanks so much!

AMD's driver listens to the TMDS limit defined by the monitor in the default extension block. To override this, you need to use a custom extension block and add an HDMI support data block, or import the hdmi.dat file as described in the CRU thread. You shouldn't need the patch with HDMI if you do this. Disabling the extension block causes it to be treated as single-link DVI, which requires the patch.

[kilyan]

(04-20-2016 02:23 PM)ToastyX Wrote:  

(04-19-2016 05:36 AM)kilyan Wrote:  

(04-19-2016 04:12 AM)ToastyX Wrote:  I need the exact size in bytes as shown in the file properties.

not patched=26.345.472 byte dimension and dimension on disc are the same

patched=dimension:26.349.632 byte
dimension on disc:26.353.664 byte

Those are the correct file sizes for 16.4.1. The driver is not reverting. I don't know why it's showing you the wrong version.

The problem is both visual and physical. That is to say it requests to update to 16.4.1

[Transmaniacon]

(04-20-2016 02:28 PM)ToastyX Wrote:  

(04-19-2016 11:23 PM)Transmaniacon Wrote:  Got it!!! I set no block and used LCD Standard and am now running at 75Hz, thanks so much!

AMD's driver listens to the TMDS limit defined by the monitor in the default extension block. To override this, you need to use a custom extension block and add an HDMI support data block, or import the hdmi.dat file as described in the CRU thread. You shouldn't need the patch with HDMI if you do this. Disabling the extension block causes it to be treated as single-link DVI, which requires the patch.

Is the way I set it up alright or should I should use the support data block instead? It has been running with no issue since I set it, but I don't want to do anything that isn't kosher for the monitor...

[ToastyX]

(04-20-2016 11:01 PM)Transmaniacon Wrote:  Is the way I set it up alright or should I should use the support data block instead? It has been running with no issue since I set it, but I don't want to do anything that isn't kosher for the monitor...

It doesn't matter. HDMI is backward-compatible with single-link DVI, so it won't hurt the monitor to run in DVI mode. The only difference is you won't need to patch the driver if use a custom extension block with HDMI support.

[ToastyX]

(04-20-2016 02:56 PM)kilyan Wrote:  The problem is both visual and physical. That is to say it requests to update to 16.4.1

That's weird. I don't know why that's happening to you because I'm not having that problem and the patcher doesn't modify anything else. Try using DDU to completely remove all traces of old drivers: http://www.wagnardmobile.com/?q=display-...aller-ddu-

[kilyan]

(04-21-2016 03:45 AM)ToastyX Wrote:  

(04-20-2016 02:56 PM)kilyan Wrote:  The problem is both visual and physical. That is to say it requests to update to 16.4.1

That's weird. I don't know why that's happening to you because I'm not having that problem and the patcher doesn't modify anything else. Try using DDU to completely remove all traces of old drivers: http://www.wagnardmobile.com/?q=display-...aller-ddu-

I solved the reversion. I thought was the patcher's fault,, but it's not. I saved some registry tweaks I add after each driver change. and there the version of the driver was 16.3. I changed it to 16..4.1, and now doesn't revert anymore when adding those registry tweaks.

[h1tbox]

Hey ToastyX,
first of all thanks for developing all this stuff for everybody to use!
I have a little problem myself, I was using a Benq XL2411z V3 with the VT1502 tweak for a good year now. A week ago my graphic card died and I got an Asus R9 280x as a replacement.
Now everytime I try to apply the Pixel clock patcher, the patcher finds every limit except for the 640x480 but you mentioned earlier to disregard that.
But after patching and rebooting I only get vertical stripes (mine were green but similar to Example).
Tried updating my drivers or using a standard resolution before patching. Any ideas?
If I then switch to my onboard card, restore the backup from your programm, everything works just fine.