Skip to content

[SOLVED]Monitor starts flickering when I go above 120Hz and Alex Deucher patch does not resolve it.

(Please read all the text)

Brief summary of the problem:

Hello, So basically, I bought a 1440p 165Hz monitor, every time I set it at 144Hz or 165Hz, it starts flickering and show weird artifacts. I found a similar issue here, and Alex Deucher suggested to do a patch that resolves the issue but it doesn't:

Proof -> I am using CachyOS, which uses the latest kernel (6.10) and also applied the patch that Alex suggested

Hardware description:

  • CPU: Intel i5-9400F
  • GPU: VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7)
  • System Memory: 15,6 gb
  • Display(s): 1440p 165hz (AOC Q24G2A)
  • Type of Display Connection: DisplayPort 1.2

System information:

  • Distro name and Version: CachyOS
  • Kernel version: 6.10.1-3-cachyos (64-bit)
  • Custom kernel: linux-cachyos
  • AMD official driver version: N/A (I didn't install drivers from AMD's website)

How to reproduce the issue:

  1. Use KDE plasma, Wayland
  2. Set the refresh rate to a value above 120Hz

Things worth mentioning :

  • When I set 165Hz and brawlhalla (a game) it still shows artifacts, but, the second I get into a match it stops flickering, but as soon as I leave it starts flickering.
  • I tried to set adaptive sync to on, off and automatic and it still shows the same issue.
  • The LiveIso of CachyOS ran 165Hz with no issues which is weird.

Attached files:

Screenshots/video files

attachedVID20240724180352

Logs

https://paste.cachyos.org/p/d564810

Update : The issue is fixed. I don't know how.

Update 2 : After shutting down and booting the issue came back.

⚠️⚠️ UPDATE 3 : ⚠️⚠️ So I figured out the issue by accident -> Basically as a startup app I have CoreCtrl in order to undervolt and overclock my GPU. Today when I booted my PC, I forgot to put the password in order to run CoreCTRL (since it requires privileges), so it did not run in the background. And then out of curiosity I decided to test whether my 165Hz will glitch or not, and it didn't. And that was the moment I noticed that CoreCTRL wasn't running, the second I ran CoreCTRL the screen started to flicker even after closing CoreCTRL.

NOTE : I also tried the same with LACT with stock and undervolt/overclock settings and it also flickered in both cases.

@agd5f Please consider reading .

Edited by Don CAPP