Monitor refresh rate bugs out after going to sleep

I am using a Alienware AW3225QF monitor that can run (on Windows) with the following settings in the Nvidia App: 3840x2160 resolution, 240hz refresh rate, 12bit color mode

However, on Linux, whenever I use HDMI 2.1, I seem to have a strange issue that happens only after the monitor has been in sleep mode for a period of time. What will happen is that my monitor gets limited to 60hz only, which only can be fixed by restarting the PC, which will fix the issue and I can select 240hz again. What I can see is that whenever this bug occurs, my monitor will say that the current signal is: 2160p 36bit

If the bug doesn’t occur, it will instead say something like “3840x2160,30bit,240hz”.

I have attached two Nvidia Bug Report files in this post, one before the bug occurs and one after the bug has occured, hoping it will show you what has changed once the bug has occured.

nvidia-bug-report.log_before-bug.gz (1.0 MB)

nvidia-bug-report.log_after_bug.gz (1021.2 KB)

Hi @VirtualBoost_v2

We have already filed a bug 5667607 internally for tracking purpose.

I will try to duplicate issue locally and will get back if required any additional information.

Hi @amrits!

Awesome, please let me know if you need any help. I have noticed that this doesn’t seem to happen when I use DisplayPort, but then my VRR seems to glitch out so I prefer using HDMI.

This is also happening to me. Willing to provide logs if needed. Running Driver Version: 580.95.05 with RTX3070. Also on HDMI.

Still an issue. Driver 590 via CachyOS.

240hz gets stuck at 60hz until I turn the monitor off and on or reboot. Happens regardless of distro, DE etc. Using Wayland on HDMI 2.1

Hi All,

Please ignore the earlier mentioned bug tracking number, it turned out to be a different bug.

I have filed a new bug 5801388 for it.

Hi @dhfragged @VirtualBoost_v2 @StarMech67

Will be really helpful if you can share nvidia bug report from repro state along display model.

Hi @amrits,

I believe that my initial attached files should cover this, my monitor is a AW3225QF. Can you confirm?

Dear @VirtualBoost_v2

I was able to find exact same display in our lab but unfortunately not able to reproduce issue.
I have tried suspend/resume operation around 5 times and kept system in suspended mode for 20-30 mins.

System - ASRock TRX40 Taichi
OS - Arch Linux with kernel 6.12.63-1-lts
GPU - NVIDIA GeForce RTX 4090
Driver 590.48.01
KDE Plasma 6.5.4
Wayland Protocol
Display Alienware AW3225QF connected via HDMI with resolution 3840 x 210 and refresh rate as 240 Hz

Could you please confirm how long you keep system in sleep mode and what is repro frequency.

Hi, If it helps, I am still experiencing this issue, albeit with a different monitor. This has been an issue for months now and I have not received any kind of feedback from my bug reports.

System/Motherboard - ROG STrix Z690-G Gaming Wifi
OS - Bazzite (latest build)

GPU - NVIDIA GeForce RTX 4090 (MSI Gaming Trio)
Driver 590.48.01
KDE Plasma 6.5.5
Wayland
Display: Samsung G93SC connected via HDMI with resolution of 5120x1440 and refresh rate as 240 Hz

If I connect the display via displayport, after the monitor sleeps, it never comes back. I have to use TTY (F4 to F2) to bring the monitor back or reboot.

I have the same problem like @dhfragged, first posted here.

In addition, the 240 Hz mode appears to be unstable. Sometimes the monitor loses connection and has to be reset to factory settings in order to work again. This problem does not occur in 120 Hz mode.

My System:

  • OS: CachyOS latest
  • GPU: NVIDIA GeForce RTX 4090
  • Driver: 590.48.01
  • KDE Plasma 6.5.5 (Wayland)
  • Display: Odyssey G9 Neo (5120x1440 and refresh rate 240 Hz), EDID here
1 Like

Hi @amrits

What I do is lower the time when KDE puts the monitor into sleep to 1 minute, and then I wait for it go to sleep. Another way is just locking your PC, then press ESC on the login screen to force it go to sleep. Finally, I wait until the on/off-button starts blinking white, so I know that the monitor has gone into sleep.

After that, after I wake the monitor up again by moving the mouse, it will most of the times go into the 60hz only mode.

One thing I noticed that seems to be different is that I use a later kernel as I’m using CachyOS and not LTS. I doubt it has anything to do with the problem, but could you perhaps try with CachyOS (latest version is fine) and see if it happens then?

Hi @VirtualBoost_v2

I installed Cachy OS with kernel 6.19.2-2 but did not observe repro.

Setup - ASRock TRX40 Taichi + CachyOS + kernel 6.19.2-2-cachyos + NVIDIA GeForce RTX 4090 + 590.48.01 + Alienware AW3225QF monitor with 3840x2160 resolution and 240hz refresh rate connected via HDMI 2.1 + KDE Plasma + Wayland

Steps Tried -

  1. Make changes in power setting so that system go to sleep after a min.
  2. Upon resume, display comes up back with 240 Hz
  3. Tried above steps 10 times but did not observe repro.
  4. Enter system into sleep mode via GUI multiple but times and did not observe any issue upon resume.

Checking if any changes in monitor settings are done at your end or any specific display setting causing this issue.
Do you see this issue with previous drivers as well ?

I’m having the same issue with the same builds, except with a Samsung GS80D 4k 240hz. It seems intermittent, but most of the time if the monitor sleeps due to PC sleep, monitor off, or just turning the monitor off it will sometimes lock at 60hz with no way to return to 240 unless I reboot or unplug/replug monitor. If I can provide logs or more info please let me know. FYI this was fine until 2 weeksish ago.

I’m having the same issue, after resuming from sleep the refresh rate bugs out and I can no longer set it to 240Hz, only 60Hz.

Setup - Intel 13900k w/ Z790PG Riptide, Arch Linux (kernel linux-6.18.13), RTX 3090 (590.48.01), Samsung G93SC OLED (5120x1440@240Hz), HDMI 2.1 connection, GNOME Wayland (GDM) or Plasma Wayland (SDDM). Also observed on an AMD 9950X3D w/ Gigabyte X870 Gaming X Wifi 7, Arch Linux (kernel linux-6.18.13), RTX 4090 (590.48.01), on the same monitor.

The issue happens regardless of whether VRR and/or HDR are enabled or disabled, both on the monitor and on the OS.

Steps to reproduce reliably:

  1. Disable automatic suspend
  2. Let the system go to sleep (either on its own or manually)
  3. Wait. This is extremely important to reproduce the issue, it won’t happen if you wake it up straight away. I suspect there needs to be enough time for the monitor itself to go to sleep or trigger some other power saving routing, if there even is such a thing, maybe 20/30 minutes.
  4. On resume, the resolution will be (in my case) 3840x1080@120Hz, with the option to go up to 5120x1440@60Hz. I can “fix it” by disconnecting and reconnecting the monitor.

If I had to guess I’d say there’s something broken during maybe some handshake/negotiation on wake? I get a similar behavior when using DisplayPort using a multi monitor KVM switch and switching input.