(07-17-2020 07:47 PM)CorneliousJD Wrote: [ -> ]Hi all, I'm having some trouble!
Long story short, new DisplayPort monitor keeps being disconnected from the system when it goes into standby, and I wanted to override the EDID so Windows just thinks it is always connected and I can always render out to it (so it stops messing up my windows/icons constantly!!!)
I could honestly use some help on how to do that in the first place, but my first hiccup is as follows.
It's a Samsung Odysssey G9 (5120x1440)
Every time I try to enter 5120 into the resolution box it shows in red and doesn't let me save it.
Any help is appreciated. Thanks in advance!
Overriding the EDID will not make Windows think it is connected. I don't see the point of adding a resolution that already exists.
(07-17-2020 09:00 PM)ToastyX Wrote: [ -> ]Overriding the EDID will not make Windows think it is connected. I don't see the point of adding a resolution that already exists.
So my limited understanding of this is that the reason this error with the windows keeps happening where they dont get restored where they should be is becuase Windows isn't detecting the EDID properly as it wakes the monitor up, or not fast enough or something? Overriding it seems to fix the problem?
There's a LOT of posts/threads/discussons on other websites that all link back to this utility to help fix the problem.
Here's one that explains it better than most places.
https://superuser.com/questions/982633/g...41#1027641
And here's one where people say that it fixed the problem for them too
https://www.nvidia.com/en-us/geforce/for...em-topolo/
Was hoping to do the same but it wont let me add my resoultion in, and 5120x1440 isn't even listed as a detailed resolution in CRU for some reason when I open it, yet it's my active, native, and recommended resolution?
(07-17-2020 09:19 PM)CorneliousJD Wrote: [ -> ]So my limited understanding of this is that the reason this error with the windows keeps happening where they dont get restored where they should be is becuase Windows isn't detecting the EDID properly as it wakes the monitor up, or not fast enough or something? Overriding it seems to fix the problem?
There's a LOT of posts/threads/discussons on other websites that all link back to this utility to help fix the problem.
Here's one that explains it better than most places.
https://superuser.com/questions/982633/g...41#1027641
And here's one where people say that it fixed the problem for them too
https://www.nvidia.com/en-us/geforce/for...em-topolo/
Was hoping to do the same but it wont let me add my resoultion in, and 5120x1440 isn't even listed as a detailed resolution in CRU for some reason when I open it, yet it's my active, native, and recommended resolution?
5120x1440 is in the DisplayID extension block. There's no point in adding a resolution that already exists. I have no idea why people are recommending CRU for this. CRU can't fix this problem. The problem is the monitor is disconnecting, so Windows moves the windows to another monitor and resizes them to fit, and if another monitor isn't available, it uses a simulated one. The fix is to make sure the simulated monitor has the correct resolution. Running reset-all.exe and rebooting might be enough to do that. If not, you'll have to edit the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration and make sure all the ActiveSize.cx/cy and PrimSurfSize.cx/cy entries have the correct resolution.
(07-17-2020 02:54 AM)4700mq Wrote: [ -> ]not giving a detailed post u guys keep rumbbling about that i might missed something which is false
giving detailed post u guys ignore me, in both siutaions u guys are so rude.
What's rude is you keep posting over and over when I told you what the problem is. CRU creates EDID overrides. It's up to Intel's driver to implement EDID overrides. Why do you keep bugging me about a problem that I can't do anything about? You should be bugging Intel, but they won't do anything for an old GPU. CRU works fine with AMD and NVIDIA. Intel support is spotty depending on the driver. If the driver listed in the first post doesn't work, then there's nothing you can do. There's no way to bypass the Intel GPU.
(07-16-2020 01:04 PM)ToastyX Wrote: [ -> ] (07-16-2020 07:07 AM)maftul Wrote: [ -> ]I am trying to get 4K DSR working on my new 2K 144 monitor but all my games see are these phantom resolutions and refresh rates. I don't understand why there even is a 4k resolution in Nvidia's list of resolutions when my monitor does not support such resolution by default. For the record, the monitor model is Lenovo Legion Y27q-20. I have already tried removing all the TV resolutions in the CEA-861 extension block shown with CRU but it made no difference.
4K should not exist if you remove it from CRU. Export what you have into a file and post it here.
I exported the monitor config using CRU and have attached the bin file. Would appreciate it if you could take a look.
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
Thanks in advance!
(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?
(07-18-2020 07:12 AM)maftul Wrote: [ -> ]I exported the monitor config using CRU and have attached the bin file. Would appreciate it if you could take a look.
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.
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.
[
attachment=525]
(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.