LG 27GX790A-B stuck at 10 Gbps/lane with RTX 5060 Ti - should it be 13.5?

[Shade7]

I’m having a weird issue with my LG 27GX790A-B and RTX 5060 Ti and wanted to see if anyone here has run into the same thing.

GPU-Z is showing:
Current Link Rate: 10.0 Gbps
Max Link Rate: 10.0 Gbps
Lane Count: 4

So it looks like the monitor is only running at UHBR10 / 40 Gbps instead of UHBR13.5 / 54 Gbps.

I’m running 2560x1440 at 480 Hz, 8-bit RGB. G-SYNC is off, Windows HDR is off, and DAS is on.

Right now I’m using a 6.6 ft IVANKY DP80 cable that is supposedly VESA certified:
https://www.amazon.com/dp/B0F6LJ5Q6R

I also ordered a shorter 3.3 ft Silkland DP80 cable that should arrive later today:
https://www.amazon.com/dp/B0DQ7F64L5

I’ve updated to the latest NVIDIA driver, checked MSI’s support page and don’t see any VBIOS/firmware update for the card, and the GPU otherwise seems to be working normally.

I also ordered the USB-A to USB-B cable for the monitor so I can check LG Switch for any monitor firmware updates.

Is this a known issue with this monitor and RTX 50-series cards, or does it sound like something specific to my setup?

If anyone has this monitor with a 50-series GPU, what link rate does GPU-Z show for you? And if you were stuck at 10.0 Gbps, was there anything that fixed it?

I'm hoping to run the monitor without needing DSC.

[kyube]

--snip--

It requires a registry edit.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000

DP2X_IGNORE_CABLE_ID_CAPS 1

to fix uhbr on nvidia gpus

[Shade7]

--snip--

It requires a registry edit.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000

DP2X_IGNORE_CABLE_ID_CAPS 1

to fix uhbr on nvidia gpus

Really? That's it?

I'll try that as soon as I get home.

What is the highest 4:3 resolution you think I could use at 480Hz without triggering DSC?

[Shade7]

--snip--

It requires a registry edit.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000

DP2X_IGNORE_CABLE_ID_CAPS 1

to fix uhbr on nvidia gpus

Might be a stupid question, but would you recommend running as Win 11 defaults to (UHBR10) or using Regedit to maximize to 13.5 UHBR?

I mainly play games at 1920x1440 @ 480 Hz. I think my monitor uses DSC either way. Not sure if one configuration is more "stable" or performs better than the other.

[kyube]

Might be a stupid question, but would you recommend running as Win 11 defaults to (UHBR10) or using Regedit to maximize to 13.5 UHBR?

I mainly play games at 1920x1440 @ 480 Hz. I think my monitor uses DSC either way. Not sure if one configuration is more "stable" or performs better than the other.

I don't see a point to not maximize the bandwidth.
1920x1440 @ 480Hz @ 8bit would be within UHBR13.5 bandwidth, as per this calculator, therefore no DSC.

[Shade7]

Might be a stupid question, but would you recommend running as Win 11 defaults to (UHBR10) or using Regedit to maximize to 13.5 UHBR?

I mainly play games at 1920x1440 @ 480 Hz. I think my monitor uses DSC either way. Not sure if one configuration is more "stable" or performs better than the other.

I don't see a point to not maximize the bandwidth.
1920x1440 @ 480Hz @ 8bit would be within UHBR13.5 bandwidth, as per this calculator, therefore no DSC.

But when I try to set 1920x1440 using CRU, it shows red text if I try to create it in the detailed res block, and it won't allow 1920x1440 at 440 Hz unless I add it as a res in the extension block. Correct me if I'm wrong, but I thought that was a sign that DSC is required to achieve that.

EDIT: I was following a random guide on YouTube that suggested copying the settings of my native res, then creating a new res, pasting the native configuration, and finally changing the resolution to 1920x1440. But with those timings, it wouldn't allow it.

[kyube]

But when I try to set 1920x1440 using CRU, it shows red text if I try to create it in the detailed res block, and it won't allow 1920x1440 at 440 Hz unless I add it as a res in the extension block. Correct me if I'm wrong, but I thought that was a sign that DSC is required to achieve that.

EDIT: I was following a random guide on YouTube that suggested copying the settings of my native res, then creating a new res, pasting the native configuration, and finally changing the resolution to 1920x1440. But with those timings, it wouldn't allow it.

Create a custom resolution in the Extension Block with DisplayID 1.3 or use Nvidia Control Panel's custom resolution feature.
You could also create a GPU scaled resolution by using Toasty's SRE.