Constant Crashes and freezes

I have a problem with system freezing and then crashing out of nowhere
and I also have to manually restart the system.
Also tried using w10 and worked fine so the issue is hidden somewhere in Garuda

I tried garuda-update or even updating my drivers but nothing helped.

System:
Kernel: 6.9.7-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=ebed6cff-30a0-4478-a55d-e7ed3e8c1b70 rw rootflags=subvol=@
quiet resume=UUID=3651864e-f610-4353-8d3c-d132bc390596 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.1.2 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX B360-G GAMING v: Rev 1.xx
serial: <superuser required> part-nu: ASUS_MB_CNL uuid: <superuser required>
UEFI: American Megatrends v: 1703 date: 09/02/2019
CPU:
Info: model: Intel Core i5-9400F bits: 64 type: MCP arch: Coffee Lake
gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xF6
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB
desc: 1x9 MiB
Speed (MHz): avg: 3495 high: 4085 min/max: 800/4100 scaling:
driver: intel_pstate governor: performance cores: 1: 4080 2: 4003 3: 800
4: 4085 5: 4002 6: 4002 bogomips: 34798
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GA106 [GeForce RTX 3060 Lite Hash Rate]
vendor: Micro-Star MSI driver: nvidia v: 555.58.02
alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of
2024-06; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
built: 2020-2023 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s ports: active: none off: DP-2,HDMI-A-1 empty: DP-1,DP-3
bus-ID: 01:00.0 chip-ID: 10de:2504 class-ID: 0300
Device-2: Sonix Foscam Webcam W41 Audio driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3
chip-ID: 2c45:6366 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,nouveau
alternate: fbdev,nv,vesa gpu: nvidia,nvidia-nvswitch display-ID: :0
screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 108 s-size: 1054x342mm (41.50x13.46")
s-diag: 1108mm (43.63")
Monitor-1: DP-2 note: disabled pos: primary,top-left model: VG27AQL1A
serial: <filter> built: 2023 res: 2560x1440 dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: bottom-r
model: Acer EK240Y serial: <filter> built: 2020 res: 1920x1080 dpi: 94
gamma: 1.2 size: 520x320mm (20.47x12.6") diag: 611mm (24.1") ratio: 16:10
modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3060/PCIe/SSE2
memory: 11.72 GiB
API: Vulkan v: 1.3.279 layers: 14 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3060 driver: nvidia v: 555.58.02
device-ID: 10de:2504 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 18.1.8 256 bits) driver: mesa llvmpipe v: 24.1.3-arch1.1 (LLVM
18.1.8) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel alternate: snd_soc_skl, snd_soc_avs, snd_sof_pci_intel_cnl
bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GA106 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 01:00.1 chip-ID: 10de:228e
class-ID: 0403
Device-3: Sonix Foscam Webcam W41 Audio driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3
chip-ID: 2c45:6366 class-ID: 0102 serial: <filter>
API: ALSA v: k6.9.7-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.0 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd
Drives:
Local Storage: total: 2.05 TiB used: 632.22 GiB (30.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Seagate
model: XPG GAMMIX S11 Pro size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 42A4SANA temp: 39.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM008-2FR102
size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 7200 serial: <filter> fw-rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 51.6 GiB size: 51.6 GiB (100.00%) used: 35.67 GiB (69.1%)
fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-2: /boot/efi raw-size: 512.6 MiB size: 511.6 MiB (99.80%)
used: 588 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p6 maj-min: 259:6
ID-3: /home raw-size: 935.28 GiB size: 935.28 GiB (100.00%)
used: 596.55 GiB (63.8%) fs: btrfs dev: /dev/sda2 maj-min: 8:2
ID-4: /var/log raw-size: 51.6 GiB size: 51.6 GiB (100.00%)
used: 35.67 GiB (69.1%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
ID-5: /var/tmp raw-size: 51.6 GiB size: 51.6 GiB (100.00%)
used: 35.67 GiB (69.1%) fs: btrfs dev: /dev/nvme0n1p7 maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.26 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 6 dev: /dev/zram0
ID-2: swap-2 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p5 maj-min: 259:5
Sensors:
System Temperatures: cpu: 39.0 C mobo: N/A gpu: nvidia temp: 46 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
Memory: total: 32 GiB available: 31.26 GiB used: 4.19 GiB (13.4%)
Processes: 337 Power: uptime: 14m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.46 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 256 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2026 libs: 560 tools: octopi,paru Compilers:
gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.35
Garuda (2.6.26-1):
System install date:     2024-03-30
Last full system update: 2024-07-08 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:

1 Like

If you are experiencing system instability, I would suggest you first update your BIOS to the latest version. There has been a few releases since the version you have listed, and a few of them state they “Improve system stability”.

Also, since you have this:

The BIOS update would also provide:
“Add Resizable BAR support for Nvidia RTX 30 series cards to potentially deliver more performance to gamers in select titles.”

7 Likes

The ↻ at the end means you need to restart your pc to finalize the updates, depending on your hybernation/sleep settings you might need to restart instead of shut down for that to happen.

Did you triy with another RAM and continues?

I have a brand new ram, bought it like 2 weeks ago 2x 16GB

Ram can still be part of the issue even when it’s brand new. Remove one stick and use that single stick until the systen crashes, (or not). If it still crashes, shut down and switch Ram sticks again. If it doesn’t crash with the remaining stick, RMA the faulty stick.

Are you running at your MOBO manufaturer’s recommended timings for your new ram, or have you elevated them trying to squeeze more performance out of your system. Overclocking is often a cause of system instability, you should not be overclocking or undervolting until this issue is resolved.

As you’ve already been told, you should update your bios so that you can eliminate that as a potential cause. Most people won’t waste time attempting to help someone who refuses to update their bios, as that is an obligatory primary troubleshooting step.

3 Likes