Hey! i use to use cru on my old monitor which was 165 hz and it worked fine. now on my new 240hz monitor when i try to do the same res (1720x1080) with 240 hz i get a line in the middle that doubles my screen if that makes sense. anyone know how to fix this? btw i tried doing it on 120 hz and i didn’t get the line
(08-09-2025 05:01 PM)WireLess Wrote: [ -> ]Hey! i use to use cru on my old monitor which was 165 hz and it worked fine. now on my new 240hz monitor when i try to do the same res (1720x1080) with 240 hz i get a line in the middle that doubles my screen if that makes sense. anyone know how to fix this? btw i tried doing it on 120 hz and i didn’t get the line
Try a multiple of 16 like 1728x1080.
Hello, I'm posting this knowing full well this sounds like something that may be outside the scope of what the CRU utility can affect. However, there's some pretty amazing coincidences if it's not the culprit in some way. If nothing else this may serve as a potential warning to LG G5 users. That said, I'm running out of ideas on how to fix my issue outside of a full return, so this is also a hail marry attempt.
Recently I purchased an LG G5 for mostly pc use. About 4 days in I decided I wanted to get rid of the 4096 resolution (it messes with NVIDIA's DSR options). Using the utility at first seemed fine. However, after an NVIDIA driver update (note: I use DDU each update) I noticed the 4096 resolution was back. I used CRU again, and everything seemed fine until I switched from 165hz to 120hz for movie playback.
At 120hz or lower there was a large horizontal line near the top of the screen. This, and all other problems I'm about to go into, showed in all of the TV's screens, not just the PC input. Even the TV's WebOS or Picture Test screens. Googling this issue showed that it's not uncommon, however following any steps I found online as a potential fix didn't work (including leaving it unplugged overnight).
Since I had used the export feature in CRU before making any changes I decided to import that file to see if "resetting" things gave any results. That's when the issue got worse, now at 120 or 60hz there was also extremely noticeable banding with the original line issue (again in -all- the tv's screens) in the form of grey horizontal lines, like how rows may be separated on a grid or spreadsheet.
I've tried using CRU about 2 or 3 more times seeing if I could find a fix this way, but now I have the banding issue in all display options. PC Resolution 3840x2160 165hz now has the issue when it didn't at all before, so the tv is now completely unusable.
The problems really seem to progress with each CRU usage. None of the tv options have any affect towards fixing the issue (I've toggled every option that's relevant in any way to its display including full TV reset).
Based on the descriptions of this utility I really don't know how it can be affecting the TV even outside the PC input, but here I am none the less.
I have two LG 27GR83Q-B monitors and I'm using HDMI 2.1 (Strix 3090 OC has two HDMI ports instead of the usual one) so I don't have to use DSC over DisplayPort.
When using HDMI with these monitors, they report that they support 4K resolutions because LG intends you to use DP for PC and HDMI for consoles and they will accept a 4K signal over HDMI and downscale it to QHD. I've run into a few cases where some games/software default to 4K even when QHD is reported as that native resolution and selected in Windows. Additionally, LG is dumb and the monitor ID is 1 digit different when using HDMI than DP, meaning that the Nvidia driver only detects them as officially G-SYNC compatible when using DP, so when using HDMI it has to be manually enabled in the control panel (which is not really a big deal, just dumb).
I want to remove the 4K resolutions and change the display ID so they are detected as G-SYNC compatible. If I use CRU to override the EDID when using HDMI I get a bunch of weird problems that seem totally random.
I first tried to do this early last year and ran into the problem that whenever I override either monitor's EDID using CRU, the monitor would go black for 10-15 minutes before finally recovering and working fine from that point. I have seen a few comments in this post from other people having the exact same issue with other LG monitors, as well as a separate post (which I replied to but nobody every replied to me unfortunately) that basically boiled it down to driver issues. At first I was just giving up because I didn't think they'd ever recover, but then once I walked away and came back later and the monitor had recovered successfully and the EDID was overridden as I specified in CRU.
The second and third issues are brand new, since I recently reinstalled Windows and was trying to use CRU again. The black screen issue still exists, but in addition to that for some reason my main monitor (which is a bit older than the secondary one because the secondary one was replaced 5 months after I got them due to a hardware issue) now recovers after 10-15 minutes with a totally mangled black and white image with weird angled lines across the screen until I run the CRU Restart executable a second time, at which point it recovers immediately and works fine.
The third issue is the craziest and I cannot explain it at all. Sometimes instead of ever recovering, once I save the override in CRU and restart the displays, my entire PC slows down to an unusable crawl, the mouse moves only like once every few seconds, and I essentially cannot do anything until I disconnect the monitor that is blacked out, at which point the PC recovers until I plug that monitor in again. This even persists through a reboot of the PC and power cycle of the monitors (like completely unplugging them from power) and the only way to fix it is to run the CRU Reset executable and then try overriding the monitor again until it eventually works. At first I thought it might have been a refresh rate thing that my PC was not actually being slow, but then I tried to remote into the PC from my phone (using RustDesk) and because the PC was so slow it couldn't even connect.
What I don't understand is A) why this only happens with HDMI, overriding when using DP works fine, B) why the issues seem to only happen sometimes even if I apply the same EDID through CRU multiple times, C) how overriding the EDID could possibly cause my PC to grind to a halt, and lastly, D) why does overriding the EDID with an exact copy of the factory EDID with no changes at all still cause these problems?
One thing I did notice is that I downloaded another tool for editing EDIDs and in both CRU and the other tool I simply changed the last digit of the display ID and then compared the results with a hex editor. With CRU, quite a few bytes were changed where with the other tool only the byte representing the last digit of the ID had changed and one or two in the area that I believe is the EDID checksum. My suspicion is that CRU is creating a malformed EDID but even importing the one from the other tool into CRU causes the same issues so I don't think it's that.
(08-15-2025 09:24 PM)AdmiralSpeedy Wrote: [ -> ]Additionally, LG is dumb and the monitor ID is 1 digit different when using HDMI than DP, meaning that the Nvidia driver only detects them as officially G-SYNC compatible when using DP, so when using HDMI it has to be manually enabled in the control panel (which is not really a big deal, just dumb).
This is completely normal. The IDs are supposed to be different with different connections. This is on NVIDIA to fix. Maybe they only certified DisplayPort as G-SYNC compatible and not HDMI, either because of some issue or lack of testing.
(08-15-2025 09:24 PM)AdmiralSpeedy Wrote: [ -> ]I want to remove the 4K resolutions and change the display ID so they are detected as G-SYNC compatible. If I use CRU to override the EDID when using HDMI I get a bunch of weird problems that seem totally random.
I first tried to do this early last year and ran into the problem that whenever I override either monitor's EDID using CRU, the monitor would go black for 10-15 minutes before finally recovering and working fine from that point. I have seen a few comments in this post from other people having the exact same issue with other LG monitors, as well as a separate post (which I replied to but nobody every replied to me unfortunately) that basically boiled it down to driver issues. At first I was just giving up because I didn't think they'd ever recover, but then once I walked away and came back later and the monitor had recovered successfully and the EDID was overridden as I specified in CRU.
This is an NVIDIA driver bug and not specific to LG. Someone mentioned setting both displays to display scaling in the NVIDIA control panel before using CRU might avoid the problem. There's also a workaround mentioned in the first post using scripts:
https://www.monitortests.com/forum/Threa...wn-scripts
(08-15-2025 09:24 PM)AdmiralSpeedy Wrote: [ -> ]The second and third issues are brand new, since I recently reinstalled Windows and was trying to use CRU again. The black screen issue still exists, but in addition to that for some reason my main monitor (which is a bit older than the secondary one because the secondary one was replaced 5 months after I got them due to a hardware issue) now recovers after 10-15 minutes with a totally mangled black and white image with weird angled lines across the screen until I run the CRU Restart executable a second time, at which point it recovers immediately and works fine.
I haven't heard of this issue since nobody else waited 15 minutes to see what happens. If the problem goes away after restarting the driver, then that indicates an NVIDIA driver bug. One of the workarounds above should help.
(08-15-2025 09:24 PM)AdmiralSpeedy Wrote: [ -> ]The third issue is the craziest and I cannot explain it at all. Sometimes instead of ever recovering, once I save the override in CRU and restart the displays, my entire PC slows down to an unusable crawl, the mouse moves only like once every few seconds, and I essentially cannot do anything until I disconnect the monitor that is blacked out, at which point the PC recovers until I plug that monitor in again. This even persists through a reboot of the PC and power cycle of the monitors (like completely unplugging them from power) and the only way to fix it is to run the CRU Reset executable and then try overriding the monitor again until it eventually works. At first I thought it might have been a refresh rate thing that my PC was not actually being slow, but then I tried to remote into the PC from my phone (using RustDesk) and because the PC was so slow it couldn't even connect.
This is a new NVIDIA driver bug caused by driver version 580.88. Try installing 577.00.
(08-15-2025 09:24 PM)AdmiralSpeedy Wrote: [ -> ]What I don't understand is A) why this only happens with HDMI, overriding when using DP works fine, B) why the issues seem to only happen sometimes even if I apply the same EDID through CRU multiple times, C) how overriding the EDID could possibly cause my PC to grind to a halt, and lastly, D) why does overriding the EDID with an exact copy of the factory EDID with no changes at all still cause these problems?
One thing I did notice is that I downloaded another tool for editing EDIDs and in both CRU and the other tool I simply changed the last digit of the display ID and then compared the results with a hex editor. With CRU, quite a few bytes were changed where with the other tool only the byte representing the last digit of the ID had changed and one or two in the area that I believe is the EDID checksum. My suspicion is that CRU is creating a malformed EDID but even importing the one from the other tool into CRU causes the same issues so I don't think it's that.
The issue is not a malformed EDID. CRU is not a complete EDID editor, so it always sets certain values the same way, which will result in some differences. The issue is NVIDIA's driver is broken. There's nothing particular in the EDID that triggers the problem. Just the presence of an EDID override can trigger the problem, even with no changes. I don't know what conditions trigger the problem because the problem doesn't always happen, even on systems that had the problem before.
(08-15-2025 06:17 PM)BennyLava Wrote: [ -> ]Hello, I'm posting this knowing full well this sounds like something that may be outside the scope of what the CRU utility can affect. However, there's some pretty amazing coincidences if it's not the culprit in some way. If nothing else this may serve as a potential warning to LG G5 users. That said, I'm running out of ideas on how to fix my issue outside of a full return, so this is also a hail marry attempt.
Recently I purchased an LG G5 for mostly pc use. About 4 days in I decided I wanted to get rid of the 4096 resolution (it messes with NVIDIA's DSR options). Using the utility at first seemed fine. However, after an NVIDIA driver update (note: I use DDU each update) I noticed the 4096 resolution was back. I used CRU again, and everything seemed fine until I switched from 165hz to 120hz for movie playback.
At 120hz or lower there was a large horizontal line near the top of the screen. This, and all other problems I'm about to go into, showed in all of the TV's screens, not just the PC input. Even the TV's WebOS or Picture Test screens. Googling this issue showed that it's not uncommon, however following any steps I found online as a potential fix didn't work (including leaving it unplugged overnight).
Since I had used the export feature in CRU before making any changes I decided to import that file to see if "resetting" things gave any results. That's when the issue got worse, now at 120 or 60hz there was also extremely noticeable banding with the original line issue (again in -all- the tv's screens) in the form of grey horizontal lines, like how rows may be separated on a grid or spreadsheet.
I've tried using CRU about 2 or 3 more times seeing if I could find a fix this way, but now I have the banding issue in all display options. PC Resolution 3840x2160 165hz now has the issue when it didn't at all before, so the tv is now completely unusable.
The problems really seem to progress with each CRU usage. None of the tv options have any affect towards fixing the issue (I've toggled every option that's relevant in any way to its display including full TV reset).
Based on the descriptions of this utility I really don't know how it can be affecting the TV even outside the PC input, but here I am none the less.
Just removing resolutions wouldn't cause this to happen, and importing the original EDID certainly wouldn't make it worse. Really sounds like a faulty TV and not anything CRU did.
Hi,
I got a new laptop recently which is causing me a specific issue with missing interlaced resolutions that my previous laptop didn't have. My previous machine was a Surface Pro 8 with an 11th gen Intel Core i7 1185G7processor andan Intel Iris Xe integrated GPU.
When connecting that one to my Samsung TV via a USB-C HDMI adapter, I was able to select from the Windows 10 display settings 1920x1080 @60i (interlaced) which the TV perfers. With the 60hz interlaced setting the image quality on the TV is very sharp, and it supports the advanced TV settings in the TV's menu for color, motion, etc.
The TV also supports progressive resolutions, however, with 1920x1080 @60p as the Windows desktop resolution, the image quality is a fair bit blurrier, and many of those advanced picture control settings are not available, they are greyed out on the TV and only available if the input is interlaced.
So now the new machine is a Surface Pro 11, with a newer Core Ultra 7 268V processor, it has an Intel Arc 140v integrated GPU, and it runs Windows 11 versus Win10 on the older machine.
And when I connect this one to the Samsung TV (using the same USB-C adapter), I am ONLY able to select progressive resolutions from the Windows display settings dropdown, there are no options for the interlaced equivalents like the old machine with Win10. IE, on the old machine I could select either 1920x1080x60p or 1920x1080x60i. The new machine only shows 1920x1080x60p as available, there are no "i" resolutions in the dropdown. And as a result I can't get the TV to show the sharper images, I get the somewhat blurry progressive image.
Am I able to use CRU to add 1920x1080x60i as a selectable resolution & timing to the new laptop?
If so could you please help me by explaining how I enter that into CRU?
Many thanks!
TRJB
(08-18-2025 12:28 AM)therealjoeblow Wrote: [ -> ]So now the new machine is a Surface Pro 11, with a newer Core Ultra 7 268V processor, it has an Intel Arc 140v integrated GPU, and it runs Windows 11 versus Win10 on the older machine.
And when I connect this one to the Samsung TV (using the same USB-C adapter), I am ONLY able to select progressive resolutions from the Windows display settings dropdown, there are no options for the interlaced equivalents like the old machine with Win10. IE, on the old machine I could select either 1920x1080x60p or 1920x1080x60i. The new machine only shows 1920x1080x60p as available, there are no "i" resolutions in the dropdown. And as a result I can't get the TV to show the sharper images, I get the somewhat blurry progressive image.
Am I able to use CRU to add 1920x1080x60i as a selectable resolution & timing to the new laptop?
No, the TV already defines 1920x1080i @ 60 Hz, so there's no point in adding it again. If interlaced resolutions aren't available, that means the graphics driver doesn't support interlaced resolutions for your GPU. That is something you'll have to talk to Intel support about, but interlaced support is low priority for them. AMD and NVIDIA have abandoned interlaced support entirely in their new GPUs.
(08-18-2025 01:47 PM)ToastyX Wrote: [ -> ] (08-18-2025 12:28 AM)therealjoeblow Wrote: [ -> ]So now the new machine is a Surface Pro 11, with a newer Core Ultra 7 268V processor, it has an Intel Arc 140v integrated GPU, and it runs Windows 11 versus Win10 on the older machine.
And when I connect this one to the Samsung TV (using the same USB-C adapter), I am ONLY able to select progressive resolutions from the Windows display settings dropdown, there are no options for the interlaced equivalents like the old machine with Win10. IE, on the old machine I could select either 1920x1080x60p or 1920x1080x60i. The new machine only shows 1920x1080x60p as available, there are no "i" resolutions in the dropdown. And as a result I can't get the TV to show the sharper images, I get the somewhat blurry progressive image.
Am I able to use CRU to add 1920x1080x60i as a selectable resolution & timing to the new laptop?
No, the TV already defines 1920x1080i @ 60 Hz, so there's no point in adding it again. If interlaced resolutions aren't available, that means the graphics driver doesn't support interlaced resolutions for your GPU. That is something you'll have to talk to Intel support about, but interlaced support is low priority for them. AMD and NVIDIA have abandoned interlaced support entirely in their new GPUs.
Ok thank you for the info. A bit disappointing.
My CRU broke after downloading Nvidia driver 580.88. I downloaded the driver to play the BF6 Beta as it was the only way to play. After doing so I realized my CRU was broken with my custom resolution no longer showing up. Everything was pushed to native resolution of 2560x1440. I reverted my Nvidia drivers back to 576.28 but still can't seem to get my custom resolutions to come back when going back through the CRU settings ( Not a monitor wizard just followed a youtube tutorial and it worked last time ). This monitor has the custom resolution section greyed out in the nvidia control panel.
If anyone can help me get 2304x1440 into my choices for custom resolutions that would be amazing as this is driving me crazy.
My Equipment:
Monitor - mag271qx oled
GPU - TUF Gaming 3080
Cables - Display Port