Monitor Tests Forum

(07-18-2020 03:14 PM)ToastyX Wrote: [ -> ]

(07-18-2020 03:05 PM)Nielzx Wrote: [ -> ]Hi there,

I'm kind of needing some help.
I'm trying to overclock a monitor with a native resolution of 2560x1440 running at 165Hz out of the box.
I have Vega 64 as GPU and I already did the AMD pixel patcher 1.4.8.

Unfortunately, the CRU won't let me overclock the refresh rate.
I'm overclocking this monitor for experience and knowledge.

After some investigation and tinkering, I found out that the CRU just won't simply let me go anything above 655.35MHz Pixel Clock rate.
The odd thing is that the monitor is rated 165Hz Refresh Rate but when I run CRU, it won't let me set a 165Hz refresh rate and it prevents me to go above 162Hz with a 2560x1440p resolution even though the monitor is rated 165Hz at the same resolution. Everything is by default.

Can anyone enlighten me on what's wrong?

I also did the same thing on my other monitors and CRU is limiting me to 655.35MHz pixel clock rate no matter what.

Any help is highly appreciated. Thank you for spending time reading this.

You need to use a DisplayID extension block to go beyond 655.35 MHz.

Thank you so much ToastyX, that helps a lot. I can finally exceed the limit.

will this tool increase the idle clocks for intel gpu?


i had an old laptop with amd radeon 7570M as the display gpu, i was able to oc from 60hz to 80hz stable but the clocks and power cons in idle has increased.

will this happen too if i oc a laptop with intel 630 and gtx1660ti using cru
im asking coz i cant check in details the intel gpu, im worried about battery life to be shrinked in half or 30%.

(07-18-2020 02:43 PM)ToastyX Wrote: [ -> ]I see 3840x2160 @ 50/60 Hz in the TV resolutions data block in the first extension block. It might also be in the second extension block, which is likely a DisplayID extension block, but it seems CRU can't read it. You should be able to just delete the second extension block.

Thank you for your reply. I have already tried deleting the whole set of TV resolutions and the HDMI support block (and restarted the driver/rebooted the machine), but Nvidia's driver still sees those phantom resolutions. By second extension block, do you mean the "Default extension block" in the following screenshot?

[attachment=526]

Edit: Removing the extra "Default extension block" did the trick and removed all the extra resolutions and allowed DSR to correctly scale from the native 2k resolution with the correct refresh rates, rather than the phantom 4k resolution at 60 Hz. However, there is a downside: removing that extension block also removes the 165 Hz resolution. I believe that must be the block Lenovo added to overclock the panel to 165 Hz. I might be able to bring 2k 165 Hz back using this guide (which is actually supposed to fix another problem with my monitor), though:

https://motherbear.home.blog/2019/12/10/...creen-fix/

Is it possible to add support for reading that block using CRU in the future?

(07-18-2020 06:59 PM)maftul Wrote: [ -> ]Edit: Removing the extra "Default extension block" did the trick and removed all the extra resolutions and allowed DSR to correctly scale from the native 2k resolution with the correct refresh rates, rather than the phantom 4k resolution at 60 Hz. However, there is a downside: removing that extension block also removes the 165 Hz resolution. I believe that must be the block Lenovo added to overclock the panel to 165 Hz. I might be able to bring 2k 165 Hz back using this guide (which is actually supposed to fix another problem with my monitor), though:

https://motherbear.home.blog/2019/12/10/...creen-fix/

Is it possible to add support for reading that block using CRU in the future?

CRU already has support for reading the extension block but for some reason NVIDIA's driver only returns the first extension block (AMD works fine). You can add a DisplayID extension block manually and add 165 Hz in there.

(07-18-2020 04:26 PM)4700mq Wrote: [ -> ]will this tool increase the idle clocks for intel gpu?


i had an old laptop with amd radeon 7570M as the display gpu, i was able to oc from 60hz to 80hz stable but the clocks and power cons in idle has increased.

will this happen too if i oc a laptop with intel 630 and gtx1660ti using cru
im asking coz i cant check in details the intel gpu, im worried about battery life to be shrinked in half or 30%.

The GPU might not clock down if the vertical blanking is too low. In most cases, using "LCD standard" timing will allow it to clock down.

(07-18-2020 07:25 PM)ToastyX Wrote: [ -> ]CRU already has support for reading the extension block but for some reason NVIDIA's driver only returns the first extension block (AMD works fine). You can add a DisplayID extension block manually and add 165 Hz in there.

I see, that is what I am going to do. I really appreciate the time and effort you are putting into CRU and also solving people's problems in the forum.

(07-18-2020 02:41 PM)ToastyX Wrote: [ -> ]

(07-18-2020 07:54 AM)Otzl Wrote: [ -> ]Hi everyone, how do I make DisplayID detailed resolutions active? I've created a custom 120Hz resolution with a large vertical total for my Viewsonic XG270, but this is only possible with DisplayID. I also have an AMD card, so I cannot use the Nvidia Control Panel like in this guide: forums.blurbusters.com/viewtopic.php?f=4&t=6478

What do you mean by make active?

Thank you for your reply.

I successfully created the resolution I need under DisplayID, with a large Vertical Front Porch Total of 1080, which isn't possible with CEA-861. Even if I remove the CEA-861 block, the DisplayID resolution I want doesn't show up in Windows. How do I use it? Hope this makes more sense. Thanks in advance.

(07-18-2020 08:58 PM)Otzl Wrote: [ -> ]I successfully created the resolution I need under DisplayID, with a large Vertical Front Porch Total of 1080, which isn't possible with CEA-861. Even if I remove the CEA-861 block, the DisplayID resolution I want doesn't show up in Windows. How do I use it? Hope this makes more sense. Thanks in advance.

It should show up unless the driver is ignoring it. If it's not a pixel clock limit, maybe it doesn't like a large vertical front porch. Try the back porch instead.

Hello there, everyone.

I own an LG 29WK600 (29" UWD 2560x1080 75Hz "HDR"), and am currently using it with an RTX2080S through DisplayPort (1.2 I believe, GPU-Z shows 5,4Gbps). Some time ago I was experimenting with nVidia custom resolution, typed in 3440x1440 just for the kicks and for my surprise it "worked", I mean, the image came right up, stuff on the screen were smaller, and no glitches that I could see. Typed in 3840x1600, and it also worked, same way described before, both at 75Hz. For some reason the image became a lot darker when using custom resolutions through nvidia panel, but at least I knew it might be possible.

After that, I decided to try CRU and see if I could create new resolutions properly, and I could, this time I went only for 3840x1600 75Hz, everything worked fine, the OSD from the monitor itself showed that resolution. However, from time to time the screen goes black for like 1 second, and than comes back. Happens at 3440x1440 75Hz as well, everything seems to work beautifully, and then out of the blue screen flashes black and comes back.

Naturally I tried lowering refresh rate, and both resolutions work flawlessly at 60Hz, no flashes at all, but since the monitor is rated 75Hz, I was hoping to actually be able to use those resolutions at the "desired" refresh rate.

What I would like to know, please, is if there is any possibility that the "flashing behavior" is something that can be solved by messing around with the settings on CRU? Or it sure means that the monitor simply cannot handle 75Hz at those resolutions?

I'll attach a few images from my current settings, I've been messing around with timings for a while now, with no luck, but the weird thing for me is that the flashing has no pattern at all, sometimes it occurs watching videos, sometimes does not, sometimes I can play a game for almost an hour without any issue, sometimes it's just impossible. I lowered the FreeSync range from 40-75 to 48-75, to see if it could help, but no deal. Also, since I could not find something specific about my case when searching for clues, I've added HDMI and HDMI 2.0 blocks, but I have no idea if it makes any difference or not in this scenario.

Thank you in advance.
[attachment=527]
[attachment=528]
[attachment=529]
[attachment=530]

(07-19-2020 02:48 PM)wild0077 Wrote: [ -> ]I own an LG 29WK600 (29" UWD 2560x1080 75Hz "HDR"), and am currently using it with an RTX2080S through DisplayPort (1.2 I believe, GPU-Z shows 5,4Gbps). Some time ago I was experimenting with nVidia custom resolution, typed in 3440x1440 just for the kicks and for my surprise it "worked", I mean, the image came right up, stuff on the screen were smaller, and no glitches that I could see. Typed in 3840x1600, and it also worked, same way described before, both at 75Hz. For some reason the image became a lot darker when using custom resolutions through nvidia panel, but at least I knew it might be possible.

After that, I decided to try CRU and see if I could create new resolutions properly, and I could, this time I went only for 3840x1600 75Hz, everything worked fine, the OSD from the monitor itself showed that resolution. However, from time to time the screen goes black for like 1 second, and than comes back. Happens at 3440x1440 75Hz as well, everything seems to work beautifully, and then out of the blue screen flashes black and comes back.

Naturally I tried lowering refresh rate, and both resolutions work flawlessly at 60Hz, no flashes at all, but since the monitor is rated 75Hz, I was hoping to actually be able to use those resolutions at the "desired" refresh rate.

What I would like to know, please, is if there is any possibility that the "flashing behavior" is something that can be solved by messing around with the settings on CRU? Or it sure means that the monitor simply cannot handle 75Hz at those resolutions?

With the NVIDIA control panel, did you change the active pixels or was it a scaled resolution? CRU doesn't create scaled resolutions. The blacking out sounds like a signal quality problem, or the monitor can't handle the resolution. I don't recommend using "LCD reduced" with higher resolutions. You might need to increase the vertical total for the monitor to handle it correctly.