Custom Resolution Utility (CRU)

[mhmiles]

(01-07-2021 10:49 PM)ToastyX Wrote:  

(01-07-2021 09:48 PM)mhmiles Wrote:  I’m experiencing an issue with CRU where my edid is showing a blank serial number after changing my freesync range. I’ve used a couple utilities to view the edid from both windows and Mac and see that the serial number field is blank/0 while the serial number (numeric) field is being edited by cru. This is all causing display arrangement to be totally screwy on my laptop since it seems it’s no longer able to tell the displays apart

What version of CRU are you using?

I don’t remember what version I originally changed the freesync range with. I think I did it couple months ago. I tried to do a reset all today with v1.5 but didn’t have any success

[ToastyX]

(01-08-2021 03:00 AM)mhmiles Wrote:  I don’t remember what version I originally changed the freesync range with. I think I did it couple months ago. I tried to do a reset all today with v1.5 but didn’t have any success

Are you talking about the "ID serial #" or the "Serial number" field? The MG279 doesn't include a "Serial number" descriptor, but the "ID serial #" should be preserved. After running reset-all.exe and restarting, if you click the "Edit..." button at the top, does the "ID serial #" have a value? If so, at what point does it disappear? What are the exact steps you are doing to change the FreeSync range?

[choichoi10]

(01-08-2021 02:36 AM)ToastyX Wrote:  

(01-07-2021 11:02 PM)choichoi10 Wrote:  Im using the latest nvidia 461.09 drivers. this problem only started after I switched to nvidia 750ti. Last time while im using amd 6570 the native resolution is being detected just fine.

Try unplugging the monitor's power for a minute just in case it's a firmware glitch.

If that doesn't help, try importing this file with CRU (and enable "Import complete EDID"):

tried this and still gives me the same bsod

[mhmiles]

(01-08-2021 03:37 AM)ToastyX Wrote:  

(01-08-2021 03:00 AM)mhmiles Wrote:  I don’t remember what version I originally changed the freesync range with. I think I did it couple months ago. I tried to do a reset all today with v1.5 but didn’t have any success

Are you talking about the "ID serial #" or the "Serial number" field? The MG279 doesn't include a "Serial number" descriptor, but the "ID serial #" should be preserved. After running reset-all.exe and restarting, if you click the "Edit..." button at the top, does the "ID serial #" have a value? If so, at what point does it disappear? What are the exact steps you are doing to change the FreeSync range?

Here’s what I did with a clean reset this morning on 1.5:

[ToastyX]

(01-08-2021 06:50 PM)mhmiles Wrote:  Here’s what I did with a clean reset this morning on 1.5:

I'm not seeing the problem. The "ID serial #" (numeric) is showing in your screen shots. The "Serial number" descriptor can only be included if there's a slot available, but the MG279 doesn't have one by default anyway, so that's not causing your display arrangement problem. You have to delete one of the detailed resolutions if you want to include the "Serial number" descriptor.

[choichoi10]

(01-08-2021 03:41 AM)choichoi10 Wrote:  

(01-08-2021 02:36 AM)ToastyX Wrote:  

(01-07-2021 11:02 PM)choichoi10 Wrote:  Im using the latest nvidia 461.09 drivers. this problem only started after I switched to nvidia 750ti. Last time while im using amd 6570 the native resolution is being detected just fine.

Try unplugging the monitor's power for a minute just in case it's a firmware glitch.

If that doesn't help, try importing this file with CRU (and enable "Import complete EDID"):

tried this and still gives me the same bsod

hey toastyx, would buying a dvi to vga adapter fix this problem?

[ToastyX]

(01-09-2021 01:46 AM)choichoi10 Wrote:  hey toastyx, would buying a dvi to vga adapter fix this problem?

An active adapter might work, but you have to be careful to make sure you get an active adapter and not a passive one. A passive DVI to VGA adapter will act the same as a normal VGA port. HDMI to VGA adapters are always active. You will still have to use CRU if it can't read the EDID, but hopefully an active adapter will avoid the driver crash.

[choichoi10]

(01-09-2021 01:57 AM)ToastyX Wrote:  

(01-09-2021 01:46 AM)choichoi10 Wrote:  hey toastyx, would buying a dvi to vga adapter fix this problem?

An active adapter might work, but you have to be careful to make sure you get an active adapter and not a passive one. A passive DVI to VGA adapter will act the same as a normal VGA port. HDMI to VGA adapters are always active. You will still have to use CRU if it can't read the EDID, but hopefully an active adapter will avoid the driver crash.

thanks ill try doing that

[ioannis]

FYI ToastX, with the latest NVIDIA driver the cru settings for freesync range stay after reboot as they should. So it was a driver issue, no problem at all on your side!!

[Epic753]

(12-27-2020 09:50 PM)ToastyX Wrote:  

(12-27-2020 06:34 PM)Epic753 Wrote:  Does this mean that the fix leans away from faulty computer hardware and towards Lenovo (or nvidia) firmware and drivers?

Seems like it.

Update: The new Lenovo Y27Q20 firmware has fixed my intermittent black screens.

CRU patched the issue on DP so I was able to stabilize my computer (monitor) and enjoy my new build while waiting. Then no issues on HDMI while waiting too.

You correct all along helping whittle it down to the final fix.

Thanks!