Display randomally going black/no signal

Issues & Assistance
1

inxi -Faz output

System:    Kernel: 5.15.7-zen1-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=b70e1dba-766b-4320-8bd5-8ee6b5f69997
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B250M-A v: Rev X.0x serial: <superuser required>
UEFI: American Megatrends v: 0810 date: 09/08/2017
CPU:       Info: Dual Core model: Intel Pentium G4560 bits: 64 type: MT MCP arch: Kaby Lake family: 6
model-id: 9E (158) stepping: 9 microcode: EA cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 27999
Speed: 800 MHz min/max: 800/3500 MHz Core speeds (MHz): 1: 961 2: 2212 3: 818 4: 2554
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
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: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte driver: nvidia v: 495.46
alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1c82 class-ID: 0300
Display: x11 server: X.Org 1.21.1.1 compositor: kwin_x11 driver: loaded: nvidia
unloaded: modesetting alternate: fbdev,nouveau,nv,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x301mm (20.6x11.9") s-diag: 604mm (23.8")
Monitor-1: HDMI-0 res: 1920x1080 hz: 144 dpi: 94 size: 521x293mm (20.5x11.5")
diag: 598mm (23.5")
OpenGL: renderer: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 495.46
direct render: Yes
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 00:1f.3 chip-ID: 8086:a2f0 class-ID: 0403
Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403
Sound Server-1: ALSA v: k5.15.7-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.41 running: yes
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A
Drives:    Local Storage: total: 931.51 GiB used: 70.65 GiB (7.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: 1A02 scheme: GPT
Partition: ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 70.65 GiB (7.6%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%) used: 576 KiB (0.2%) fs: vfat
dev: /dev/sda1 maj-min: 8:1
ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 70.65 GiB (7.6%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 70.65 GiB (7.6%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%) used: 70.65 GiB (7.6%) fs: btrfs
dev: /dev/sda2 maj-min: 8:2
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 7.7 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 45 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 38%
Info:      Processes: 235 Uptime: 11m wakeups: 0 Memory: 7.7 GiB used: 2.33 GiB (30.2%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 Packages: pacman: 1306 lib: 374 Shell: fish
v: 3.3.1 default: Bash v: 5.1.12 running-in: konsole inxi: 3.3.09

So I'm having a problem where my display will randomally cut out for no reason and display no signal, and I have to power down my computer for it to work again. This can be when I'm playing games or using a browser, sometimes I can use the computer for a day or two without this happening so I don't think its uptime dependent. I don't think it's a kernel crash because I can still here sounds playing from the game or whatever I was watching, but only around 50% of the time will the keyboard stay functional. I also think when this happens KDE breaks (I can't see tell for sure though since nothings on the monitor) based on alt-tab behaviour not really working as it should (like I'll alt tab out of a game then alt tab back in but I can tell the focus isn't on the game since I can't hear me moving around when trying to etc). Not really sure what's going on so I would appreciate the help, thank you.

2

Ok literally right after posting this it just happened again, caps lock/num lock light not changing when pressing those keys so I guess the kernel died? Computer was on for maybe 15 minutes max

3

is it external monitor or built in like laptop?

its not a fix but more of a test if its external. unplug from computer and plug back in?

4

external monitor, yeah I tried that but it's still not working

5

ok s all i could think of in these late hours ..im sure you have checked firmware....tried bigger hammer :stuck_out_tongue: alternate WM? gl

6

You could try another hdmi/display port lead, but it sounds like your monitor is on its way out, how old is it
Try the live usb and see if it does it with that

1 Like
7

I have tried another hdmi cable and tried the other port on my GPU, I wouldn't say it's the monitor because with the crash that happened just now the keyboard wasn't responding.

(forgot to add this monitor is around a year old)

8

Try

sudo journalctl --since=today

see if it shows any errors

9

I'm seeing alot of Nvidia errors, I'll post try and post the logs here before it crashes again, there's quite a few

10

Here's the log before I force rebooted

Dec 19 20:26:02 phrog-pc xdg-desktop-portal-kde[4676]: xdp-kde-background: GetAppState called: no parameters
Dec 19 20:27:33 phrog-pc systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Dec 19 20:27:33 phrog-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapper>
Dec 19 20:27:33 phrog-pc kernel: audit: type=1130 audit(1639909653.278:552): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:27:33 phrog-pc dbus-daemon[504]: [system] Activating via systemd: service name='org.opensuse.Snappe>
Dec 19 20:27:33 phrog-pc systemd[1]: Starting DBus interface for snapper...
Dec 19 20:27:33 phrog-pc dbus-daemon[504]: [system] Successfully activated service 'org.opensuse.Snapper'
Dec 19 20:27:33 phrog-pc systemd[1]: Started DBus interface for snapper.
Dec 19 20:27:33 phrog-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapper>
Dec 19 20:27:33 phrog-pc kernel: audit: type=1130 audit(1639909653.399:553): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:27:33 phrog-pc systemd-helper[5205]: running cleanup for 'root'.
Dec 19 20:27:33 phrog-pc systemd-helper[5205]: running number cleanup for 'root'.
Dec 19 20:27:33 phrog-pc systemd-helper[5205]: running timeline cleanup for 'root'.
Dec 19 20:27:33 phrog-pc systemd-helper[5205]: running empty-pre-post cleanup for 'root'.
Dec 19 20:27:33 phrog-pc systemd[1]: snapper-cleanup.service: Deactivated successfully.
Dec 19 20:27:33 phrog-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapper->
Dec 19 20:27:33 phrog-pc kernel: audit: type=1131 audit(1639909653.852:554): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:27:43 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3428>
Dec 19 20:27:43 phrog-pc systemd[3056]: Started Konsole - Terminal.
Dec 19 20:27:43 phrog-pc konsole[5208]: Icon theme "gnome" not found.
Dec 19 20:27:52 phrog-pc dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name=>
Dec 19 20:27:52 phrog-pc systemd[3056]: Starting Accessibility services bus...
Dec 19 20:27:52 phrog-pc dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.a>
Dec 19 20:27:52 phrog-pc systemd[3056]: Started Accessibility services bus.
Dec 19 20:28:33 phrog-pc systemd[1]: snapperd.service: Deactivated successfully.
Dec 19 20:28:33 phrog-pc kernel: audit: type=1131 audit(1639909713.868:555): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:28:33 phrog-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=snapperd>
Dec 19 20:28:40 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5498>
Dec 19 20:28:40 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 54>
Dec 19 20:28:40 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 5499>
Dec 19 20:28:40 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 54>
Dec 19 20:29:03 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6124>
Dec 19 20:29:43 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 6313>
Dec 19 20:32:34 phrog-pc systemd[1]: Starting Cleanup of Temporary Directories...
Dec 19 20:32:34 phrog-pc systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Dec 19 20:32:34 phrog-pc systemd[1]: Finished Cleanup of Temporary Directories.
Dec 19 20:32:34 phrog-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd>
Dec 19 20:32:34 phrog-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd->
Dec 19 20:32:34 phrog-pc kernel: audit: type=1130 audit(1639909954.675:556): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:32:34 phrog-pc kernel: audit: type=1131 audit(1639909954.675:557): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:38:28 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2658>
Dec 19 20:38:28 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 26>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:29 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 27>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:30 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 28>
Dec 19 20:38:32 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3172>
Dec 19 20:38:32 phrog-pc systemd[3056]: app-org.kde.konsole-795c4b4e706e44978a50e003939c7537.scope: Consumed >
Dec 19 20:38:32 phrog-pc kwin_x11[3203]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 3174>
Dec 19 20:38:59 phrog-pc kernel: NVRM: GPU at PCI:0000:01:00: GPU-1223b948-0fc6-6f40-df97-161bc3cca86a
Dec 19 20:38:59 phrog-pc kernel: NVRM: Xid (PCI:0000:01:00): 79, pid=3203, GPU has fallen off the bus.
Dec 19 20:38:59 phrog-pc kernel: NVRM: GPU 0000:01:00.0: GPU has fallen off the bus.
Dec 19 20:38:59 phrog-pc kernel: NVRM: GPU 0000:01:00.0: GPU serial number is .
Dec 19 20:38:59 phrog-pc kernel: NVRM: A GPU crash dump has been created. If possible, please run
NVRM: nvidia-bug-report.sh as root to collect this data before
NVRM: the NVIDIA kernel module is unloaded.
Dec 19 20:39:12 phrog-pc kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: >
Dec 19 20:39:17 phrog-pc kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: >
Dec 19 20:39:17 phrog-pc kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: >
Dec 19 20:50:58 phrog-pc kernel: r8169 0000:03:00.0 enp3s0: Link is Down
Dec 19 20:51:02 phrog-pc NetworkManager[505]: <info>  [1639911062.6986] device (enp3s0): carrier: link connec>
Dec 19 20:51:02 phrog-pc NetworkManager[505]: <info>  [1639911062.6987] device (enp3s0): DHCPv4 lease renewal>
Dec 19 20:51:02 phrog-pc kernel: r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
Dec 19 20:51:02 phrog-pc NetworkManager[505]: <info>  [1639911062.7017] dhcp4 (enp3s0): canceled DHCP transac>
Dec 19 20:51:02 phrog-pc NetworkManager[505]: <info>  [1639911062.7017] dhcp4 (enp3s0): state changed bound ->
Dec 19 20:51:02 phrog-pc NetworkManager[505]: <info>  [1639911062.7020] dhcp4 (enp3s0): activation: beginning>
Dec 19 20:51:04 phrog-pc NetworkManager[505]: <info>  [1639911064.7145] dhcp4 (enp3s0): state changed unknown>
Dec 19 20:51:04 phrog-pc dbus-daemon[504]: [system] Activating via systemd: service name='org.freedesktop.nm_>
Dec 19 20:51:04 phrog-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 19 20:51:04 phrog-pc dbus-daemon[504]: [system] Successfully activated service 'org.freedesktop.nm_dispat>
Dec 19 20:51:04 phrog-pc systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 19 20:51:04 phrog-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=Network>
Dec 19 20:51:04 phrog-pc kernel: audit: type=1130 audit(1639911064.723:558): pid=1 uid=0 auid=4294967295 ses=>
Dec 19 20:51:15 phrog-pc systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 19 20:51:15 phrog-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkM>
Dec 19 20:51:15 phrog-pc kernel: audit: type=1131 audit(1639911075.278:559): pid=1 uid=0 auid=4294967295 ses=>
-- Boot 3a189273e2384d92808cfebcdee6f2f1 --

Looks like my GPU is crashing? Things were still reporting while my screen was black it seems like based on the times, so why did my keyboard not work, doesn't that only happen in a kernel crash?

11

Try the lts kernel

2 Likes
12

Alright while installing the LTS kernel the display cutout once again but it did install in the background (kernel hadn't died). Booted into the LTS kernel, logged into the KDE desktop and after about 20 seconds the display cuts out again and this time the keyboard stops responding as well. This has happened more today than it has in total for the past week. I was about to do a journalctl on the LTS kernel and see if it was the same error but couldn't get to it in time.

13

Can you try a live usb see if it does it then as this is looking like a hardware issue
ie power supply ,motherboard?

1 Like
14

Have you tested using the free video driver yet?

Test the linux kernel as well.

1 Like
15

I did try the normal linux kernel and got the same issue, I'll try running the liveusb now for around an hour and if that doesn't crash I'll give the open source drivers a shot.

16

Alright I've been running from the liveusb for around 2 hours now (with the proprietary drivers), letting youtube autoplay in firedragon for a good while and idling at the desktop for a little while. No display crashes have happened so far, so I'm not sure what the deal is. I don't think it's hardware related because the crashes were happening every 2-15 minutes last night and so far everything has been running fine on the liveusb. But then again my computer was running fine for a few days without crashing so I can't tell if this is just another instance of this.

Any commands you want me to run from the liveusb? I'll chroot into my system and check if those crashes were the same reason as what I posted in journalctl.

Edit: Can't seem to view journalctl when chrooted into the system, says no logs were found. Also the drivers in the live environment are 495.44 and the ones I have installed on the system are 495.46. I also remember the first day I installed garuda on this system after getting everything setup I experienced the black display (maybe because it updated to the bad driver?) but I thought it was because I was fiddling with my audio cables on my motherboards IO and might have bumped something. Is there a way to downgrade back to those drivers you think?

17

Alright downgraded the nvidia packages to the ones used in the live environment. Will let it run for a little while and see how it goes.

1 Like
18

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