Screen randomly blacks out for a second every few minutes (randomly)

Support Graphics & Display
,
1

I am running into an issue where every couple of minutes, my monitor will black out for about 1 second, then come back to life.. Sometimes it’ll happen multiple times in a minute, sometimes it will happen every couple of minutes. I have tried with all adaptive sync settings (reported as solution in other threads), and every setting leads to me getting the random black screen flicker..

System:
  Kernel: 6.17.1-0-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.17-x86_64
    root=UUID=d6bdd869-3f6e-4655-a4b3-c50476f4a1f3 rw rootflags=subvol=@
    quiet splash resume=UUID=3900a000-2254-4e18-9355-5a234e51a797
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B550M-PLUS WIFI II v: Rev X.0x
    serial: <superuser required> part-nu: SKU uuid: <superuser required>
    UEFI: American Megatrends v: 3002 date: 02/23/2023
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 32 GiB available: 31.25 GiB used: 4.79 GiB (15.3%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM_A1 type: no module installed
  Device-2: DIMM_A2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3733 MT/s volts: curr: 1 width (bits): data: 64
    total: 64 manufacturer: Corsair part-no: CMH32GX4M2D3600C18 serial: N/A
  Device-3: DIMM_B1 type: no module installed
  Device-4: DIMM_B2 type: DDR4 detail: synchronous unbuffered (unregistered)
    size: 16 GiB speed: 3733 MT/s volts: curr: 1 width (bits): data: 64
    total: 64 manufacturer: Corsair part-no: CMH32GX4M2D3600C18 serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
    level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
    model-id: 0x21 (33) stepping: 2 microcode: 0xA201211
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 1938 min/max: 614/5363 boost: disabled scaling:
    driver: amd-pstate-epp governor: powersave cores: 1: 1938 2: 1938 3: 1938
    4: 1938 5: 1938 6: 1938 7: 1938 8: 1938 9: 1938 10: 1938 11: 1938 12: 1938
    13: 1938 14: 1938 15: 1938 16: 1938 bogomips: 134404
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total cqm_occup_llc
    cr8_legacy cx16 cx8 de debug_swap decodeassists erms extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt ht hw_pstate ibpb
    ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce misalignsse mmx
    mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx
    ospke osvw overflow_recov pae pat pausefilter pclmulqdq pdpe1gb
    perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni popcnt pse
    pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep sha_ni
    skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3 stibp
    succor svm svm_lock syscall tce topoext tsc tsc_scale umip user_shstk
    v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall vpclmulqdq
    wbnoinvd wdt x2apic xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
    xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate] vendor: Gigabyte
    driver: nvidia v: 580.82.09 alternate: nouveau,nova_core,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-08; EOL~2026-12-xx)
    arch: Ampere code: GAxxx process: TSMC n7 (7nm) built: 2020-2023 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, DP-3,
    HDMI-A-1, HDMI-A-2 bus-ID: 08:00.0 chip-ID: 10de:2216 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: nvidia
    gpu: nv_platform,nvidia,nvidia-nvswitch display-ID: 0
  Monitor-1: DP-1 model: AOC AG274QS8R1B serial: <filter> built: 2023 res:
    mode: 2560x1440 hz: 240 scale: 100% (1) dpi: 109 gamma: 1.2 chroma: red:
    x: 0.694 y: 0.302 green: x: 0.212 y: 0.706 blue: x: 0.153 y: 0.051 white:
    x: 0.314 y: 0.329 size: 597x336mm (23.5x13.23") diag: 685mm (27")
    ratio: 16:9 modes: 2560x1440, 1920x1080, 1280x1440, 1280x1024, 1280x720,
    1024x768, 800x600, 720x576, 720x480, 640x480
  EDID-Warnings: 1: parse_edid: unknown tag 112
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
    x11: drv: nvidia inactive: device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.82.09
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2
    memory: 9.77 GiB display-ID: :1.0
  API: Vulkan v: 1.4.321 layers: 6 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3080 driver: nvidia v: 580.82.09
    device-ID: 10de:2216 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA102 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel alternate: nova_core pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:1aef class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech Logi Z407 driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.1.3:8
    chip-ID: 046d:0a4c class-ID: 0102 serial: <filter>
  Device-4: C-Media Blue Snowball driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-1.2:7
    chip-ID: 0d8c:0005 class-ID: 0300 serial: <filter>
  API: ALSA v: k6.17.1-0-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: AzureWave driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 bus-ID: 06:00.0 chip-ID: 14c3:7961 class-ID: 0280
  IF: wlp6s0 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: f000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, smbd, systemd-timesyncd
  WAN IP: <filter>
Bluetooth:
  Device-1: IMC Networks Wireless_Device driver: btusb v: 0.8 type: USB
    rev: 2.1 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 13d3:3563
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.07 TiB used: 85.81 GiB (4.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA
    model: KBG50ZNS512G NVMe 512GB size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 11200109 temp: 57.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:4 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: 2B2QEXM7 temp: 27.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 840 PRO Series
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 5B0Q scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SDSSDH3512G
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 7000 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 85.81 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: d6bdd869-3f6e-4655-a4b3-c50476f4a1f3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 636 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 616B-5A9A
  ID-3: /home raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 85.81 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: d6bdd869-3f6e-4655-a4b3-c50476f4a1f3
  ID-4: /var/cache raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 85.81 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: d6bdd869-3f6e-4655-a4b3-c50476f4a1f3
  ID-5: /var/log raw-size: 467.84 GiB size: 467.84 GiB (100.00%)
    used: 85.81 GiB (18.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: d6bdd869-3f6e-4655-a4b3-c50476f4a1f3
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: 3900a000-2254-4e18-9355-5a234e51a797
Unmounted:
  ID-1: /dev/nvme1n1p1 maj-min: 259:5 size: 100 MiB fs: vfat label: N/A
    uuid: 8A18-1F38
  ID-2: /dev/nvme1n1p2 maj-min: 259:6 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-3: /dev/nvme1n1p3 maj-min: 259:7 size: 930.64 GiB fs: ntfs label: N/A
    uuid: BC5418E35418A266
  ID-4: /dev/nvme1n1p4 maj-min: 259:8 size: 779 MiB fs: ntfs label: N/A
    uuid: BCB491D9B491968C
  ID-5: /dev/sda1 maj-min: 8:1 size: 128 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-6: /dev/sda2 maj-min: 8:2 size: 238.35 GiB fs: ntfs label: Games 2
    uuid: BE94EA5F94EA19A3
  ID-7: /dev/sdb1 maj-min: 8:17 size: 476.94 GiB fs: ntfs label: Games
    uuid: 72B2F9C2B2F98ABD
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-1:2 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 2109:2817
    class-ID: 0900
  Hub-3: 1-1.1:5 info: VIA Labs USB2.0 Hub ports: 4 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 2109:2817
    class-ID: 0900
  Device-1: 1-1.1.3:8 info: Logitech Logi Z407 type: HID,audio
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 046d:0a4c
    class-ID: 0102 serial: <filter>
  Device-2: 1-1.1.4:11 info: Corsair iCUE LS100 Smart Lighting Strip
    Starter Kit type: HID driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 50mA
    chip-ID: 1b1c:0c1e class-ID: 0300 serial: <filter>
  Device-3: 1-1.2:7 info: C-Media Blue Snowball type: audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 0d8c:0005 class-ID: 0300 serial: <filter>
  Device-4: 1-1.3:10 info: Corsair K60 RGB PRO Low Profile Mechanical
    Gaming Keyboard type: keyboard,HID,mouse driver: usbfs interfaces: 4
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
    chip-ID: 1b1c:1bad class-ID: 0301 serial: <filter>
  Device-5: 1-5:3 info: IMC Networks Wireless_Device type: bluetooth
    driver: btusb interfaces: 3 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1
    mode: 2.0 power: 100mA chip-ID: 13d3:3563 class-ID: e001 serial: <filter>
  Device-6: 1-6:4 info: ASUSTek AURA LED Controller type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 16mA chip-ID: 0b05:1939 class-ID: 0300
    serial: <filter>
  Hub-4: 1-7:6 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0608 class-ID: 0900
  Hub-5: 1-7.1:9 info: Genesys Logic Hub ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 05e3:0610 class-ID: 0900
  Device-1: 1-7.1.2:13 info: Corsair Lighting Node CORE type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 50mA chip-ID: 1b1c:0c1a class-ID: 0300
    serial: <filter>
  Device-2: 1-7.1.4:14 info: Corsair iCUE Commander CORE type: HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
    chip-ID: 1b1c:0c1c class-ID: 0300 serial: <filter>
  Device-3: 1-7.2:12 info: Corsair Commander PRO type: HID
    driver: corsair-cpro,usbhid interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 chip-ID: 1b1c:0c10
    class-ID: 0300 serial: <filter>
  Hub-6: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 2-1:2 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 2109:0817
    class-ID: 0900
  Hub-8: 2-1.1:3 info: VIA Labs USB3.0 Hub ports: 4 rev: 3.1
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 2109:0817
    class-ID: 0900
  Hub-9: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-1:2 info: Razer USA Mamba 2018 (Wireless) type: mouse,keyboard
    driver: razermouse,usbhid interfaces: 3 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 500mA chip-ID: 1532:0072 class-ID: 0300
  Hub-10: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 46.1 C mobo: 24.2 C
  Fan Speeds (rpm): fan-2: 615 fan-3: 568 fan-4: 621 fan-5: 601
Repos:
  Packages: 1804 pm: pacman pkgs: 1785 libs: 406 tools: pamac pm: flatpak
    pkgs: 19
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    2: https://manjaro.grena.ge/stable/$repo/$arch
    3: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
    4: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    5: http://ossmirror.mycloud.services/os/linux/manjaro/stable/$repo/$arch
    6: https://mirrors.eric.ovh/manjaro/stable/$repo/$arch
    7: https://mirror.truenetwork.ru/manjaro/stable/$repo/$arch
    8: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    9: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    10: https://ftp.linux.org.tr/manjaro/stable/$repo/$arch
    11: https://mirror.hostiko.network/manjaro/stable/$repo/$arch
    12: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    13: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    14: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
    15: https://mirror.23m.com/manjaro/stable/$repo/$arch
    16: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
    17: https://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    18: https://manjaro.mirror-services.net/pub/stable/$repo/$arch
    19: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
    20: https://repo.iut.ac.ir/repo/manjaro/stable/$repo/$arch
    21: https://mirror.kku.ac.th/manjaro/stable/$repo/$arch
    22: https://mirror1.sox.rs/manjaro/stable/$repo/$arch
    23: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
    24: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
    25: https://muug.ca/mirror/manjaro/stable/$repo/$arch
    26: https://mirror.dc.uz/manjaro/stable/$repo/$arch
    27: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    28: https://manjaro.ynh.ovh/stable/$repo/$arch
    29: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    30: https://mirrors.ucr.ac.cr/manjaro/stable/$repo/$arch
    31: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
    32: https://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/$repo/$arch
    33: https://linorg.usp.br/manjaro/stable/$repo/$arch
    34: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    35: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
    36: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    37: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    38: https://mirror.easyname.at/manjaro/stable/$repo/$arch
    39: https://ftp.snt.utwente.nl/pub/linux/manjaro/stable/$repo/$arch
    40: https://mirror.alwyzon.net/manjaro/stable/$repo/$arch
    41: https://kartolo.sby.datautama.net.id/manjaro/stable/$repo/$arch
    42: https://ct.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    43: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
    44: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
    45: https://mirror.fcix.net/manjaro/stable/$repo/$arch
    46: https://mirrors.sjtug.sjtu.edu.cn/manjaro/stable/$repo/$arch
    47: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
    48: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
    49: https://ftp.caliu.cat/pub/distribucions/manjaro/stable/$repo/$arch
    50: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
    51: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
    52: https://mirror.aarnet.edu.au/pub/manjaro/stable/$repo/$arch
    53: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    54: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
    55: https://ba.mirror.garr.it/mirrors/manjaro/stable/$repo/$arch
    56: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
    57: https://fosszone.csd.auth.gr/manjaro/stable/$repo/$arch
    58: https://manjaro.repo.cure.edu.uy/stable/$repo/$arch
    59: https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch
    60: https://mirrors.ocf.berkeley.edu/manjaro/stable/$repo/$arch
    61: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    62: https://manjarolinux-mirror.cloud.mu/stable/$repo/$arch
    63: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
    64: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    65: https://mirror.xeonbd.com/manjaro/stable/$repo/$arch
    66: https://manjaro.mirror.liquidtelecom.com/stable/$repo/$arch
    67: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    68: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
    69: https://ftp.psnc.pl/linux/manjaro/stable/$repo/$arch
    70: https://mirror.netcologne.de/manjaro/stable/$repo/$arch
    71: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
    72: https://distrohub.kyiv.ua/manjaro/stable/$repo/$arch
    73: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    74: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
    75: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    76: https://ftp.tu-chemnitz.de/pub/linux/manjaro/stable/$repo/$arch
    77: https://mirrors.dotsrc.org/manjaro/stable/$repo/$arch
    78: https://mirrors.atlas.net.co/manjaro/stable/$repo/$arch
    79: https://mirror.mobinhost.com/manjaro/stable/$repo/$arch
    80: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
    81: https://free.nchc.org.tw/manjaro/stable/$repo/$arch
    82: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
    83: https://ftpmirror1.infania.net/mirror/manjaro/stable/$repo/$arch
    84: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
    85: https://mirrors.sonic.net/manjaro/stable/$repo/$arch
    86: https://ftp.belnet.be/mirrors/manjaro/repos/stable/$repo/$arch
    87: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
    88: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
    89: https://mirror.dimensiondata.com/mirrors/manjaro.org/stable/$repo/$arch
    90: https://ftp.halifax.rwth-aachen.de/manjaro/stable/$repo/$arch
    91: https://mirror.kamtv.ru/manjaro/stable/$repo/$arch
    92: https://manjaro.kurdy.org/stable/$repo/$arch
    93: https://manjaro.syxpi.fr/manjaro/stable/$repo/$arch
    94: https://mirrors2.manjaro.org/stable/$repo/$arch
    95: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
    96: https://mirrors.gigenet.com/manjaro/stable/$repo/$arch
    97: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
    98: https://manjaro.mirror.garr.it/manjaro/stable/$repo/$arch
    99: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
    100: https://mirror.init7.net/manjaro/stable/$repo/$arch
    101: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 439
  1: cpu: 95.5% command: duplicity started-by: python pid: 4666
    mem: 42.6 MiB (0.1%)
  2: cpu: 56.6% command: deja-dup pid: 4559 mem: 217.4 MiB (0.6%)
  3: cpu: 26.1% command: ollama pid: 3946 mem: 45.8 MiB (0.1%)
  4: cpu: 13.0% command: librewolf pid: 2107 mem: 496.9 MiB (1.5%)
  5: cpu: 10.4% command: kwin_wayland pid: 1193 mem: 397.9 MiB (1.2%)
  Memory top: 5 of 439
  1: mem: 831.1 MiB (2.5%) command: alpaca started-by: python3 pid: 2706
    cpu: 3.6%
  2: mem: 496.9 MiB (1.5%) command: librewolf pid: 2107 cpu: 13.0%
  3: mem: 475.0 MiB (1.4%) command: plasmashell pid: 1350 cpu: 1.8%
  4: mem: 397.9 MiB (1.2%) command: kwin_wayland pid: 1193 cpu: 10.4%
  5: mem: 308.5 MiB (0.9%) command: librewolf pid: 2411 cpu: 6.7%
Info:
  Processes: 439 Power: uptime: 12m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.39
2

Please be aware that the “Relevant Sysinfo” is nothing like enough for a Support Request.

Please provide the output of inxi -zv8 (which is privacy-filtered) and add three backticks ``` (usually the key below ESC) on an otherise-blank line above and below the pasted output, or select all pasted output and click the </> button at the top of the Reply window.

1 Like
3

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading
Highly Recommended

Work with us, not against us

Be prepared to provide output from commands when asked. It is equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Simply waiting for others to ask you questions can be counter-productive – typically, nobody has a :crystal_ball: at their disposal – instead, please help others to make informed suggestions based on information you provide.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

a) inxi command (long-form):

inxi --filter --verbosity=8

b) inxi command (short-form):

inxi -zv8
Running `inxi` within a `chroot` environment
Your privacy is respected

Update Announcements

Technical Resources

4

If the screen blacks out it can be anything.

Is it a dual gpu laptop?

Are you using hybrid driver?

Which version of the driver are you using

Which driver is in use when it happens?

Have you tried lowering the refresh rate e.g. 120 or even 60?

Please use the relevant inxi command to provide relevant info

inxi -ezc0

For plasma an additional kinfo could prove useful

kinfo
6

Can we please re-list this post? I have updated my post to include inxi -zv8 output.

7

It’s a single GPU desktop with no integrated GPU
Using proprietary Nvidia driver version 580.82.09

I have not tried experimenting with lowering the refresh rate, but that is something I will try and report back.

kinfo output:

Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.17.1-0-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080
9

Hmmh. I’ve had a similar issue for years. It has happened on both Windows 10 and Manjaro. Mine is periodical, though. Sometimes it might be a week or two with nothing happening, and then I can get the shut-downs happening several times a day, sometimes 3-5 in a row. I haven’t been able to find any working solution to this.

First thing I checked was if our monitors have something common, but I have a Samsung (T24D390) and you have AOC. That doesn’t rule out some components being same, but… Also, the only connecting factor on our GPUs is the main brand (Nvidia). I got GTX 1070 Ti.

I’ll keep following this thread just in case I get a sudden idea. Hopefully there’s a solution that would help both of us.

10

Anecdotal:- I have experienced similar blanking on Windows – usually coinciding with there being a new graphics driver released – though, I’m sure that factor was purely coincidental. Most times updating the drivers seemed to resolve it.

Apart from one occasion, when finding that positioning of the monitor cable or a less-than-secure physical HDMI connection seemed to play a part, I’ve not experienced anything similar with other OS I use; including BSD, Debian, MacOS or Manjaro.

11

These type of symptoms can happen when your power supply is kind of unstable. I have heard about cases where lowering the window blinds draw so much current that monitors shortly black out. Of course, there could be other reasons for power supply fluctuations.

2 Likes
14

Yes indeed. Was going to mention that this often happens when my uplighter comes on (via a timer, it’s also an inductive load having an MV lamp).

It also caused the disk in the dock to spin down and back up again.

It’s also possible that a poorly-shielded interface cable (e.g. HDMI) may act as an antenna and pick up RF spikes caused by such switching. Maybe try another cable?

3 Likes
15

I haven’t ever had this issue happen on Windows, it only happens when using Manjaro. It’s OS-specific for sure. Through further testing I found that my screen does NOT black out when adaptive sync is set to “always”. If it’s set to never or automatic, my screen will begin blacking out. This leads me to believe this is a driver issue of sorts…

This is a bit anecdotal, but I would like to add that it appears the duration between screen blanking seems to decrease for every time it happens… For example if I disable adaptive sync, it will be a couple minutes before the first blanking happens. Once it happens for the first time, the next time it happens will be sooner…

16

Before making such a claim, what were the results of all suggestions made (above)?

Adaptive Sync, also known as FreeSync (AMD) or G-Sync (Nvidia), synchronises the refresh rate of a monitor and the frame rate of a GPU – this typically helps with artefacts such as stuttering and tearing of video playback, but can also help with screen blanking, as you have already found.

Lowering the refresh rate is a valid suggestion. Did you try it?

There are potentially many scenarios that might contribute to screen blanking such as you describe; including, but not limited to, your choice of driver, it’s configuration; the respective combination of monitor and GPU; cables; connectors; related hardware issues; the list goes on… “it could be anything”, as commented earlier.

I mentioned my experience with similar screen blanking on Windows, noted as anecdotal – because the experience proves nothing; it only illustrates that screen blanking is not uncommon, no matter the OS. That you have never experienced it on Windows, likewise, means nothing.

You haven’t specified exactly what further testing was performed. Please list what you have done (and the results) to avoid others repeating the same suggestions.

Setting Adaptive Sync to “always” may not be an ideal resolution, nor is it a substitute for properly investigating every possible contributor, but at least it seems to work for you. Perhaps you could take some consolation in that. :slight_smile:

Regards.

17

I cannot know if this is relevant - I have to ask - have you tried stopping the ollama service while troubleshooting this?

ollama is likely configured to use your GPU and one could speculate if - even if you actively query a LLM - could it interfere in a manner where your screen would black out?

I have ollama running as well - and I have had a couple of weird issues - I still don’t know what caused those - but revisiting this topic made me think if a conflict could occasionally occur?

18

Poor choice of words, when I say I did “further testing”, I meant that I used my computer normally to see if the blanking would occur or not depending on what sync setting I had selected.

What I tried with no success: I stopped ollama service for the time being (suggested by linux-aarhus). I tried using 2 different HDMI cables (I use DP primarily), tried 2 display port cables, tried other ports on my GPU for both HDMI&DP. I am using high-quality vesa-certified display port cables that meet or exceed my display capabilities.

What I tried WITH success: enabling adaptive sync OR setting refresh rate to 200hz or below stops screen blanking.

1 Like
19

I use a Samsung Odyssey G9 at 240Hz with no issues - connection using display port - but I am not using Nvidia either - except for a newly acquired testing laptop Lenovo Legion with the Intel-Nvidia combo.

If enabling adaptive sync fix the issue - why don’t you keep it that way?

You may be correct - Ryzen 7 5800X has no GPU - so you are solely relying on Nvidia driver.

Have you tried both open and proprietary - that is linux617-nvidia and linux617-nvidia-open ?

I use the cable that came with the monitor - but given that you already thought of it - I won’t even suggest the cable :slight_smile:

A while back I experimented with the refresh rate 60, 120 and 240 on with my eyes - I cannot see a difference - I guess it is gaming that is driving the increasing specifications of GPU and displays - and at some point it becomes irrelevant.

5 Likes
20

I didn’t know the kernel modules had an open and closed version. I tried the proprietary linux617-nvidia and the screen blanking issues still persist :frowning:

Sometimes it flickers a bit, only noticeable on dark backgrounds. That’s a separate issue I don’t really care to fix..

Really, I could just forget about it and choose 200hz… It is really indistinguishable from 240hz, but part of me wants to get it working completely.

21

This is probably your best resolve; indeed, it solves the issue that is the focus of this topic. I suggest remaining with 200MHz – perhaps test higher frequencies every few months on the remote chance that newer combinations of system software might show any marked improvement.

I note that the choice of cables, connectors, or the hardware combination can still play a major part in screen blanking revealing itself at higher frequencies. Using a lower frequency is only a workaround, nonetheless it solves your immediate issue.

Regards.

Mod edit:- Typographical errors due to latency corrected. A minor annoyance.

2 Likes
22

Those are not kernel modules. The drivers themselves are fully proprietary, but the -nvidia-open driver uses an Open-Source interface for interacting with the kernel, whereas the other one still has a proprietary kernel interface — and thus, nobody knows what it’s doing.

3 Likes
23

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.