(12-08-2022 02:48 AM)ToastyX Wrote: [ -> ] (12-07-2022 04:29 AM)Carnage6 Wrote: [ -> ]Hello. I must be doing something wrong because I can't get this to work. I have an LG monitor. I installed Windows 10 fresh on an old computer running an old Geforce GTX470 card.
Windows recognizes my monitor as LGE2250 however it only lets me have 1280X1024 as my maximum resolution when the max for this monitor is 1920X1080 60hz.
When I use this application it shows the correct resolution as the detailed resolution (1920X1080 60hz).
When I click OK and run the restart program it doesn't change the resolution and when I go into display settings the LG profile is not recognized anymore and is replaced by "Display 1: Wired Display" now and the resolution is greyed out and I can't change it at all anymore.
When I go back into this program it now shows two monitor profile choices (the LG and "generic non-pnp" monitor.
What am I doing wrong?
Also, I tried updating my graphics card and when I try to download the latest driver it bricks my system so I gave up on that. Same if I try to update with Windows Update.
Also, downloaded the supposed latest driver from the LG website but none of the files seem to be an actual update that I can execute.
Like I said, I'm sure I'm doing something wrong but I have no idea what. Any help?
Post a screen shot of Device Manager that shows what's under display adapters and monitors.
I added before and after using the program.
Let me know
(12-09-2022 02:57 AM)Carnage6 Wrote: [ -> ]I added before and after using the program.
You need to install NVIDIA's driver for CRU to work and to get the correct resolutions, and "Generic Non-PnP Monitor" usually means there's a problem with the EDID, possibly because some bits got corrupted in the EEPROM, which can happen sometimes with older monitors.
When you say installing NVIDIA's driver bricks the system, do you mean the system won't boot, or do you mean the monitor won't display anything? If it boots but the monitor won't display anything with the driver installed, the EDID might be invalid. If that's the case, the easiest workaround is to use a different port on the monitor because that will have a different EDID.
(12-09-2022 12:15 AM)RocZi Wrote: [ -> ]I then do a clean install of Nvidia drivers instead of the usual overwriting installation and low and behold! my 144Hz returns and the windows display settings recommended my monitor native resolution at 1440p. I then enabled NIS and the recommended resolution became 4K and my refresh rate options drop to 60Hz max. Well, that's one way I found that messes with my EDID. I did not try and find what else could have changed my EDID.
The monitor does include 3840x2160, but the monitor is not making that the native resolution. NVIDIA's driver is doing that probably because some 4K TVs define 1080p as the native resolution, so they made the driver use the highest resolution available for DSR and NIS. You need to remove 3840x2160 using the same steps as this guide:
https://www.monitortests.com/blog/guide-...4096x2160/
(12-08-2022 01:37 PM)iakoboss7 Wrote: [ -> ]My target is to get the "correct/best" settings for my monitor to achieve "LFC" (which requires the maximum freesync range to be at least x2 of the minimum freesync range).
I have it already working except a weird "tear/stuttering" that happens at ~@38fps probably because it is just about double and not even 1hz more as I get blank screen above 76.1/76.2 Hz.
But I am not sure if the monitor timings are correct and maybe hurting something 
Honestly there's probably not much you can do. The FreeSync range should be at least 2.5x to handle edge cases correctly, so if the monitor can't handle a larger range, then there's no way to make it work.
(12-09-2022 11:15 PM)ToastyX Wrote: [ -> ] (12-08-2022 01:37 PM)iakoboss7 Wrote: [ -> ]My target is to get the "correct/best" settings for my monitor to achieve "LFC" (which requires the maximum freesync range to be at least x2 of the minimum freesync range).
I have it already working except a weird "tear/stuttering" that happens at ~@38fps probably because it is just about double and not even 1hz more as I get blank screen above 76.1/76.2 Hz.
But I am not sure if the monitor timings are correct and maybe hurting something
Honestly there's probably not much you can do. The FreeSync range should be at least 2.5x to handle edge cases correctly, so if the monitor can't handle a larger range, then there's no way to make it work.
thank you for your reply!
is it ok that i kept the default monitor timings of the 75hz profile for my 76.1hz profile?
should i change them maybe for better compatibility with amd drivers?
(12-09-2022 11:13 PM)ToastyX Wrote: [ -> ] (12-09-2022 02:57 AM)Carnage6 Wrote: [ -> ]I added before and after using the program.
You need to install NVIDIA's driver for CRU to work and to get the correct resolutions, and "Generic Non-PnP Monitor" usually means there's a problem with the EDID, possibly because some bits got corrupted in the EEPROM, which can happen sometimes with older monitors.
When you say installing NVIDIA's driver bricks the system, do you mean the system won't boot, or do you mean the monitor won't display anything? If it boots but the monitor won't display anything with the driver installed, the EDID might be invalid. If that's the case, the easiest workaround is to use a different port on the monitor because that will have a different EDID.
Well even if I cut out all the extras and just choose to install the drivers this happens. After the first time the monitor flashes to black during the install Windows comes up with a message saying "Windows encountered a problem and needs to close". Then Windows repairs itself and if I try to install again same problem. Never ending loop.
Also, here is the link to my monitor driver software which doesn't seem to actually have an executable program in it:
https://www.lg.com/us/support/product/lg-E2250V-SN.AUS
(12-10-2022 02:05 PM)Carnage6 Wrote: [ -> ]Well even if I cut out all the extras and just choose to install the drivers this happens. After the first time the monitor flashes to black during the install Windows comes up with a message saying "Windows encountered a problem and needs to close". Then Windows repairs itself and if I try to install again same problem. Never ending loop.
Also, here is the link to my monitor driver software which doesn't seem to actually have an executable program in it:
https://www.lg.com/us/support/product/lg-E2250V-SN.AUS
Then the video card is defective, or the driver is choking on a broken EDID. You shouldn't need to do anything special to get the monitor to work other than installing NVIDIA's driver, and if you can't install the driver, that often indicates a hardware problem. You don't need LG's monitor driver to get the correct resolutions.
My use case is a VM I have with an Nvidia GPU passthrough, it's an older Quadro P2000. It works fine. I connect to it via Moonlight to use Gamestream on my iPad 12.9" Pro. I use it for remote work but also some gaming and video stuff. It works pretty good. I currently have an LG 32'' UltraGear FHD 165Hz HDR10 Monitor with G-SYNC hooked up to it.
I used CRU to add my custom resolution to get native on the iPad which is 2732x2048 and 120hz. I have that working as well.
My issues was when I tried to start using a dummy plug. I only have display port and I tried a couple of them now from Amazon. I can add all the same settings in there but the resolutions don't show. I assume it's because they are showing as single lane and the resolutions and hz just don't work on them.
You have to have a monitor active for Gamestream to work. So for now I just leave the monitor on behind a server rack that runs my proxmox cluster, seems like just a waste of power and a monitor.
Any ideas?
(09-07-2012 09:06 PM)ToastyX Wrote: [ -> ][*]Passive DisplayPort to HDMI adapters are limited to 165 MHz unless the driver is patched.
Hi,
I'm trying to get a resolution of 3072x1728 @ 30 Hz to run via an old passive DisplayPort to HDMI cable on Intel UHD Graphics, but so far to no avail.
The cable is limited to 165 MHz, but even a 163.80 MHz configuration of said resolution, as calculated using your Pixel Clock Calculator, won't be displayed.
I've tried several manual blanking settings, but the resolution just won't appear in the Windows Display Settings pull-down menu. It will work at 24 or 25 Hz, though, so there seems to something other than the cable's bandwith limit to be limiting the reported output capabilities.
Do you know a solution to this?
I was able to successfully establish 3008x1728 @ 30 Hz as the highest resolution on this cable, but I believe a bit more should be possible with regards to the reported bandwidth requirements.
Real Phobo