Regression: 5K 60Hz (DSC) no longer works on Samsung ViewFinity S9 – causes persistent black screen until power cycle

Graphics / Linux Linux
1

GPU: NVIDIA GeForce RTX 5070 Ti

Monitor: Samsung ViewFinity S9 (5K, 5120x2880)

Connection: DisplayPort (original Samsung cable, directly connected to the GPU; also tested with other cables)

Problem: 5K @ 60Hz no longer works on recent drivers. The display only works at:

  • 4K @ 60Hz

  • 5K @ 30Hz

  • or lower resolutions

Attempting to use 5K @ 60Hz results in a black screen.

In many cases, the monitor enters a persistent no-signal state where:

  • even the BIOS does not display

  • rebooting the system does not resolve the issue

  • only removing power from the monitor restores functionality

Important:

  • The issue occurs on both Windows and Linux with newer drivers. On Windows, using older drivers (e.g. 576.88), the display works normally at 5K 60Hz

  • The same monitor works at 5K 60Hz via USB-C on a MacBook (DSC functioning correctly)

Suspected cause: DSC (Display Stream Compression) negotiation failure or EDID/timing validation regression.
The behavior suggests a failed DisplayPort link training process, leading to a persistent invalid state.

Steps to reproduce:

  1. Connect the Samsung ViewFinity S9 via DisplayPort

  2. Set the resolution to 5120x2880 @ 60Hz

  3. The screen goes black

  4. The monitor may require a full power cycle to recover

2

I have this exact same issue currently. Samsung S9 ViewFinity 5K monitor was previously working under Windows 11 (for nearly a year), new driver version installed via Windows update on 30 May 2026 and screen no longer displayed an image at native resolution 5120 x 2880 @ 60Hz. If refresh rate changed down to 30Hz then screen did display @ 5120 x 2880, and also at a few other resolutions/refresh rate combinations, but not at the native 5120 x 2880 @ 60 Hz.

After taking usual remediation steps with no success, found this post describing my exact issue. As suggested, installed 573.96-quadro-rtx-desktop-notebook-win10-win11-64bit-international-dch-whql.exe (T1000 8GB driver v573.96) as a Clean Driver Installation. After reboot screen displayed correctly at native resolution 5120 x 2880 @ 60Hz.

Please address this issue, as the S9 ViewFinity screen is an extremely expensive monitor.

3

Same problem on both Linux and Windows 11 for me as well on my Asus Rog PG42UQ monitor.

This has been going on now for about 2 months. This is also an DSC monitor. But its only when using the DSC function on 138hz that is the max on the monitor. If I turn it down to 120hz, it works as it should.

4

I had a G9 for a while and that monitor, and it seems like all monitors from Samsung are just cursed. In my case it would flash randomly, drop half of the horizontal resolution if a certain color combination would be displayed on the screen, fail to start (because of firmware being awful) and would have horrible popping noises.

All of these issues would also happen regardless of the OS, so in all honesty you could just be experiencing amazing Samsung hardware at it’s finest. (I love their phones though)

I have an aorus something atm, which is also a 5k (32:9) and uses DSC if I remember correctly and don’t experience any issues on win 10, using a 5090

5

So far, no solution…572.60 still works ok on RTX 4060

6

Any update on whether the issue was resolved?

7

I’ve been pressing the Driver Feedback team for months over e-mail. Nothing yet.

8

Same on Windows with Viewfinity S9 and Studio Display XDR, works without DSC(on 4K or lower), but black screen if switched to 5K.

Both 596 and 610 does not working, backscreen, works after downgrading to 576.88.

Driver from Windows update version 32.0.15.9658 does always failsafe and the desktop is still completely unusable.

Nvidia really should take a closer look at this bug.