Samsung Odyssey G60SD 360Hz @ Max. 200Hz in Windows, 360Hz in Linux

[gojomo]

I can’t get my Samsung Odyssey G60SD 360Hz OLED to run above 200Hz in Windows 11. However, it works flawlessly at 360Hz with HDR enabled in Linux.

My Setup:

Laptop: ASUS TUF Gaming A15 (2022) with the following specs (from ASUS website):

GeForce RTX 3060 6GB Mobile (MUX Switch set to dGPU)

1x USB 3.2 Gen 1 Type-C with DisplayPort™/G-SYNC support (data speed up to 5Gbps)

Cable:
Silkland USB-C to DisplayPort 1.4 cable [8K@60Hz, 4K@240Hz/144Hz, 2K@240Hz, 32.4 Gbps] Thunderbolt 4/3 to DisplayPort

Here’s how things behave under Linux versus Windows:

Linux (EndeavourOS with proprietary NVIDIA drivers, MUX Switch on dGPU):

On first boot, the monitor was immediately detected and activated as a second display. Initially, the refresh rate was capped at 240Hz.

Simply unplugging and replugging the USB-C to DP cable made 360Hz available (new handshake?).

The monitor runs perfectly at 360Hz with HDR enabled (confirmed via the monitor’s OSD).
No further configuration was needed.

   

Windows 11:

The monitor is immediately detected but starts at 60Hz. In the Windows Display Settings, 120Hz is also available and works fine.

In the NVIDIA Control Panel, higher refresh rates are not available. Using the "Customize" option allows me to add a custom refresh rate up to 200Hz, which works but with severely distorted colors (possibly incorrect HDR?).

   

Playing with timing settings in the NVIDIA Control Panel didn’t help. Refresh rates above 200Hz always fail with “Test failed” instantly, without the monitor even blinking (it doesn’t seem to actually test the settings).

   

What I’ve Tried:

-Firmware update for the monitor to 1.003 (dated December 26, 2024)

-Updating NVIDIA drivers

-Running all Windows updates

-Disabling G-SYNC (the monitor doesn’t support it, and Google suggests this might cause issues)

-Installing Samsung’s monitor driver instead of Generic PnP Monitor

-Multiple reboots

-Plugging and unplugging the USB-C to DP cable several times

No change. Still capped at 200Hz.
Using CRU (Custom Resolution Utility):

The range limits (48-360Hz) are correctly detected.

In the Extension Blocks under DisplayID 1.3, the following resolution is listed:

2560x1440 @ 359.999Hz

   

Copying this resolution to another section doesn’t work (as is stated in the documentation of CRU, that high bandwith resolutions only can be saved in extensions block)

I was able to add and test lower refresh rates though(like 144Hz) using CRU, and they work fine.

Additional Steps:

I also tried using the Pixel Clock Patcher (Pixel Clock Unlocker), but it didn’t make any difference.
Any Suggestions?

I know custom refresh rates can be tricky due to hardware limitations, but I’m puzzled because the monitor works perfectly at 360Hz in Linux on the exact same hardware.

edit-test returns

Code:

DISPLAY\SAM75CB\5&27916936&1&UID4352 (active):
00 FF FF FF FF FF FF 00 4C 2D CB 75 32 42 55 30
FF FF 01 04 B5 3C 22 78 3B 89 D1 B2 4C 3C B8 24
0E 50 54 21 08 00 81 C0 81 00 81 80 95 00 A9 C0
B3 00 01 01 01 01 14 D9 00 40 A1 A0 A8 50 80 20
3A 00 56 50 21 00 00 1A 00 00 00 FD 0E 30 69 FF
FF A7 01 0A 20 20 20 20 20 20 00 00 00 FC 00 4F
64 79 73 73 65 79 20 47 36 30 53 44 00 00 00 FF
00 48 4E 41 58 38 30 32 30 32 30 0A 20 20 02 9D
02 03 37 F1 44 90 3F 04 03 23 09 07 07 83 01 00
00 E3 05 C0 00 74 1A 00 00 03 07 30 F0 00 A0 60
01 4B 02 68 01 00 00 00 00 00 E6 06 05 01 60 4B
00 E5 01 8B 84 90 39 8A 6C 00 40 A1 A0 A8 50 80
20 3A 00 56 50 21 00 00 1A 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5F
70 12 79 03 00 03 01 64 13 D9 00 84 FF 09 3F 01
7F 80 1F 00 9F 05 A7 00 02 00 09 00 3C 8B 02 04
FF 09 3F 01 7F 80 1F 00 9F 05 A7 00 02 00 09 00
4E 6E 01 04 7F 07 EF 00 57 80 1F 00 37 04 7D 00
02 00 09 00 14 B2 01 04 FF 09 3F 01 7F 80 1F 00
9F 05 A7 00 02 00 09 00 23 F4 00 04 7F 07 EF 00
57 80 1F 00 37 04 7D 00 02 00 09 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 96 90

Does anyone have any advice?

[ToastyX]

I can only think of two possibilities. Either it's a cable quality issue and the Windows driver is negotiating a lower speed than the Linux driver, or the Windows driver is not allowing DSC with your hardware for some reason. 2560x1440 @ 360 Hz requires DSC, but you should be able to get 240 Hz at 8 bpc without DSC with CVT-RB timing. The 240 Hz timing defined by the monitor exceeds the limit without DSC.