Custom Resolution Utility (CRU)

[SirHawk]

Currently I can do completely messed up 64Hz, over 65Hz is not even listed. My 290X and GTX 660 (the latter I got rid of this monday) were able to push up to 83Hz on the very same monitor, only after exceeding 80Hz it started to get blurry, it got stronger with higher refresh rate. On DVI-DVI cable on 290X it was just plain checkerboard of noise after going above 63Hz.

Steps taken, written in an online notepad: https://shrib.com/#v18Yj1UMzOoEibjkfnpn

The RX580 does have a DVI port, I'd need to get a DVI-DVI cable first though and sadly - there's none in PC shops in my city at the moment :v.

[ToastyX]

(05-10-2019 01:05 AM)SirHawk Wrote:  Currently I can do completely messed up 64Hz, over 65Hz is not even listed. My 290X and GTX 660 (the latter I got rid of this monday) were able to push up to 83Hz on the very same monitor, only after exceeding 80Hz it started to get blurry, it got stronger with higher refresh rate. On DVI-DVI cable on 290X it was just plain checkerboard of noise after going above 63Hz.

Well something strange is going on because anything up to 165 MHz pixel clock should be listed even without the patch. Run reset-all.exe and reboot, then export a file from CRU and post it here.

[SirHawk]

There you go.

[ToastyX]

(05-10-2019 09:25 PM)SirHawk Wrote:  There you go.

I don't see anything strange about the EDID. It's a simple basic EDID. I don't see any reason why anything over 65 Hz wouldn't be listed. It's possible the patch isn't having an effect with HDMI-DVI, which is why I asked you to try plain DVI, but even without the patch, "LCD native" should let you go up to 66 Hz, "LCD standard" should let you go up to 71 Hz, and "LCD reduced" should let you go up to 77 Hz. I have not seen any issues with AMD's driver that would prevent those resolutions from working.

In the display properties ("Edit..." button at the top), what is the default maximum pixel clock? CRU doesn't include the range limits by default so it shouldn't even matter, but if you change it, make sure to check "Include if slot available" and make sure it's showing in the detailed resolution list.

The only other thing I can think of is maybe you were using different timing parameters before. Some monitors have gaps in the refresh rates that they will display, but the driver should still list them. 83 Hz reminds me of the NEC EA231WMi, which only worked at 83 Hz with these specific timing parameters:

[SirHawk]

By default it's 210MHz and as I previously said, everything worked perfectly on my two previous cards. I've also tried again increasing the frequency, this time by trying step by step with each preconfigured timing. Apparently, I can do 70Hz fine on reduced blinking timings, 71Hz gives random white noise on the screen, 72Hz does not apply at all. Curiously, 70Hz reduced is 164.96MHz of pixel clock so it'd seem the 165MHz pixel clock limit on DVI SL (as a reminder, it's HDMI-DVI-D Single Link cable) is currently not taken off. Which used to be taken care off properly previously.

Also, none other timing allows to give any overclock at all, not even default frequency. And as an extra: on 290X the white noise existed on 80Hz too, but after reverting to a 60Hz then going back to 80Hz the noise and all other artifacts were gone. This did not happen with GTX660, just selected 80Hz and forever forgot about frequency choosing window.

EDIT: Yup, I'm right. I just added 80Hz resolution on CVT reduced timings and pixel clock manually reduced to 164MHz. Anything works as long as it's below 165MHz pixel clock.

[ToastyX]

(05-12-2019 01:09 PM)SirHawk Wrote:  EDIT: Yup, I'm right. I just added 80Hz resolution on CVT reduced timings and pixel clock manually reduced to 164MHz. Anything works as long as it's below 165MHz pixel clock.

I recommend getting a DVI cable then. There's probably some new limit that affects HDMI-DVI that I will have to look into, but plain DVI should be fine with the patch.

The white noise is an HDCP issue with AMD's drivers, but that should only happen if the horizontal blanking is too low.

The checkerboard noise on the 290X with DVI sounds like the video acceleration memory clock issue. That shouldn't happen with the RX 580.

[SirHawk]

But it does happen. I'll order a new DVI-DVI Dual Link cable but given my experience with one on 290X (couldn't go higher than 64Hz) I don't expect miracles.

EDIT: As expected, DVI-D DL -> DVI-D DL did not improve things, it still won't go beyond 165MHz. But it does work correctly, in contrast to how it behaved on 290X.

[ToastyX]

(05-12-2019 09:19 PM)SirHawk Wrote:  But it does happen. I'll order a new DVI-DVI Dual Link cable but given my experience with one on 290X (couldn't go higher than 64Hz) I don't expect miracles.

EDIT: As expected, DVI-D DL -> DVI-D DL did not improve things, it still won't go beyond 165MHz. But it does work correctly, in contrast to how it behaved on 290X.

I'm getting less clear about what's happening. What do you mean when you say it won't go beyond 165 MHz? Is the refresh rate not listed? Is it listed but the monitor won't display it correctly? You need to be clear about this because those are two different problems. If it's not displayed correctly, is it blurry or are you seeing random noise? Those are also two different problems. You've mentioned all of those happening at different points, so I'm not sure what's happening when.

When you said 72 Hz does not apply at all, what exactly did you mean? Is it not listed? Does the monitor not display it correctly? "LCD reduced" at 70 Hz is 162.49 MHz (not 164.96 MHz), and "LCD reduced" at 72 Hz is still under 165 MHz, so that doesn't explain anything.

What does the random noise look like? At first, I thought you were talking about this: https://imgur.com/a/njclU, which is an HDCP issue with AMD's driver when the horizontal blanking is too low, but now I realize you might be talking about something else. Does the noise completely obscure the screen like that, or are you still able to see the screen but with some noise?

When you said no other timing overclocks at all, what exactly did you mean? Did you mean the maximum pixel clock in the range limits? I only mentioned that because AMD's driver might block higher refresh rates from being listed if it's listening to that, but the default 210 MHz is sufficient, so don't worry about that.

When you said over 65 Hz is not even listed, what timing parameters were you talking about? As I said, even without the patch, "LCD native" should allow up to 66 Hz, "LCD standard" should allow up to 71 Hz, and "LCD reduced" should allow up to 76 Hz (I said 77 Hz originally but I forgot about the 56 horizontal blanking limit without the patch). By the way, I'm assuming 1920x1080 since that's the native resolution of the monitor.

Just to be clear, with the driver patched:

LCD standard: Does 71 Hz get listed? Does 72 Hz get listed? Does 80 Hz get listed? What does the monitor show at those refresh rates?

LCD native: Does 66 Hz get listed? Does 67 Hz get listed? Does 80 Hz get listed? What does the monitor show at those refresh rates?

LCD reduced: Everything up to 71 Hz should be the same as LCD standard. Does 72 Hz get listed? Does 80 Hz get listed? What does the monitor show at these refresh rates?

Manual: Did you try the 83 Hz timing parameters I posted? It's basically "LCD native" but with the vertical back porch set to 11. Try that at 80 Hz. Does it get listed? What does the monitor show?

Try that for both HDMI-DVI and plain DVI.

[SirHawk]

Don't mind anything written before the edit from Post #4102, those were mostly lucky shots on trials and errors. And sorry or being unspecific.

Everything is listed as long as the calculated Pixel Clock (or manually set) equals or is below 165MHz and works after selecting no matter what timings are set, they can be literally random. Screen then is either perfectly clear (if proper timings are set, like the timings from the screenshot you've given previously) or with noises. In example, I currently run 70Hz with timings set as in the screenshot from post #4011 but I had to lower pixel clock to 165MHz to actually be listed (and working without any random noise). If I am to exceed this 165MHz, the custom resolution is not listed at all. I put the setting I used on previous cards vs what I use now as well as an image from the nosies I mentioned.

Concerning the noise - it's just some pixels going white and blinking, as in the screenshot shows. Depending on how wrong timings are, they appear in different quantity on whole screen or contrasting edges. They're like a badly tuned TV.

Cable does not matter right now, it's the same issue on both DVI-D DL and HDMI-DVI-D. I'm not sure if I can explain that properly, but I will try:

- On 290X with dual DVI-D Dual Link cable exceeding 66Hz refresh rate resulted in screen being torn, red, green and blue pixels were visible all over the screen, you could see pieces of the image that should be displayed distorted as well. It was also a bit zoomed in.

- On both GTX660 and 290X using a HDMI/DisplayPort->DVI-D Single Link cable I could list every custom resolution that was below 88Hz with unmodified LCD Native timings. But after exceeding 80Hz the image became more and more blurry, trying to select 85Hz resulted in "Out of range" monit on the monitor.

[ToastyX]

(05-13-2019 08:28 PM)SirHawk Wrote:  In example, I currently run 70Hz with timings set as in the screenshot from post #4011 but I had to lower pixel clock to 165MHz to be listed (and working without any random noise).

Those timing parameters at 165 MHz would be 68 Hz, not 70 Hz.

(05-13-2019 08:28 PM)SirHawk Wrote:  If I am to exceed this 165MHz, the custom resolution is not even listed at all.

Is this with HDMI-DVI or plain DVI? With HDMI-DVI, that would mean the patch is not working. With plain DVI, that should not happen because the driver should list anything up to 330 MHz even without the patch. The only difference is without the patch, anything beyond 165 MHz will send a dual-link signal, while with the patch, anything up to 230 MHz will send a single-link signal.

(05-13-2019 08:28 PM)SirHawk Wrote:  Concerning the noise - it's just some pixels going white and blinking, as in the screenshot shows. Depending on how wrong timings are, they appear in different quantity on whole screen or contrasting edges. They're like a badly tuned TV.

That would mean the monitor can't handle the timing parameters, but I've never seen that vary between different video cards, so I'm not sure what's going on.

(05-13-2019 08:28 PM)SirHawk Wrote:  - On 290X with dual DVI-D Dual Link cable exceeding 66Hz refresh rate resulted in screen being torn, red, green and blue pixels were visible all over the screen, you could see pieces of the image that should be displayed distorted as well. It was also a bit zoomed in.

That would make sense with the "LCD native" timing parameters if the driver wasn't patched because it would send a dual-link signal, while the monitor expects a single-link signal. That should not happen if the driver is patched. HDMI/DisplayPort-DVI would not have this issue since it's always single-link.