[SOLVED] PC crashes while gaming

Stef99 · 2024-09-06 19:18:26

Hello! While im gaming on steam after playing a couple minutes the pc freezes, not only the game, which requires me to restart via the powerbutton as everything is unresponsive. Im suspecting a ram issue as my system uses 28 gb of ram (the game is quite intensive) and at random times it might spike beyond 28 causing the crash but im not 100% sure.

Here's some info:

Operating System: Arch Linux 
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2
Kernel Version: 6.10.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B450M DS3H

xrandr --verbose 
Screen 0: minimum 16 x 16, current 2560 x 1440, maximum 32767 x 32767
HDMI-A-1 connected primary 2560x1440+0+0 (0x23) normal (normal left inverted right x axis y axis) 597mm x 336mm
        Identifier: 0x21
        Timestamp:  258803
        Subpixel:   unknown
        Gamma:      inf:inf:inf
        Brightness: 0.45
        Clones:    
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
        RANDR Emulation: 1 
        non-desktop: 0 
                supported: 0, 1

lscpu
Architecture:             x86_64
  CPU op-mode(s):         32-bit, 64-bit
  Address sizes:          48 bits physical, 48 bits virtual
  Byte Order:             Little Endian
CPU(s):                   16
  On-line CPU(s) list:    0-15
Vendor ID:                AuthenticAMD
  Model name:             AMD Ryzen 7 5800X3D 8-Core Processor
    CPU family:           25
    Model:                33
    Thread(s) per core:   2
    Core(s) per socket:   8
    Socket(s):            1
    Stepping:             2
    Frequency boost:      enabled
    CPU(s) scaling MHz:   69%
    CPU max MHz:          4548.8281
    CPU min MHz:          2200.0000
    BogoMIPS:             6803.16
    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
                           pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor sss
                          e3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a mis
                          alignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_ps
                          tate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_n
                          i xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local user_shstk clzero irperf xsaveerptr rdpru wb
                          noinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vm
                          load vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm debug_swap
Virtualization features:  
  Virtualization:         AMD-V
Caches (sum of all):      
  L1d:                    256 KiB (8 instances)
  L1i:                    256 KiB (8 instances)
  L2:                     4 MiB (8 instances)
  L3:                     96 MiB (1 instance)
NUMA:                     
  NUMA node(s):           1
  NUMA node0 CPU(s):      0-15
Vulnerabilities:          
  Gather data sampling:   Not affected
  Itlb multihit:          Not affected
  L1tf:                   Not affected
  Mds:                    Not affected
  Meltdown:               Not affected
  Mmio stale data:        Not affected
  Reg file data sampling: Not affected
  Retbleed:               Not affected
  Spec rstack overflow:   Mitigation; Safe RET
  Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:             Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP always-on; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
  Srbds:                  Not affected
  Tsx async abort:        Not affected

Can provide more if needed.

Last edited by Stef99 (2024-09-11 12:16:37)

Nikolai5 · 2024-09-07 17:35:02

Share the output of journalctl, if you've had to reboot following a crash then you can use

sudo journalctl -b -1

to get the logs from the last boot, or -2 for the one before that.

But share the full log of a boot that had a crash please. I personally may or may not be able to help depending on what it is, but anyone that can help you is going to need at least that info.

Stef99 · 2024-09-07 21:08:37

Nikolai5 wrote:

Share the output of journalctl, if you've had to reboot following a crash then you can use
sudo journalctl -b -1
to get the logs from the last boot, or -2 for the one before that.
But share the full log of a boot that had a crash please. I personally may or may not be able to help depending on what it is, but anyone that can help you is going to need at least that info.

Heres the one immediately after a crash with me having to hit the shutdown button :

[stefanos@archlinux ~]$ sudo journalctl -b -1
Sep 07 23:07:41 archlinux kernel: Linux version 6.10.8-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20240805, GNU ld (GNU Binutils) 2.43.0) #1 SMP PREEMP>
Sep 07 23:07:41 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=23f4c7c6-4cdf-4dbc-baca-c64a6c980c2b rw zswap.enabled=0 rootfstype=e>
Sep 07 23:07:41 archlinux kernel: BIOS-provided physical RAM map:
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009c3efff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x0000000009c3f000-0x0000000009ffffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000baecffff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000baed0000-0x00000000bc63cfff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000bc63d000-0x00000000bc796fff] ACPI data
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000bc797000-0x00000000bce7dfff] ACPI NVS
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000bce7e000-0x00000000bdbfefff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000bdbff000-0x00000000beffffff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000bf000000-0x00000000bfffffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x0000000100000000-0x000000083f37ffff] usable
Sep 07 23:07:41 archlinux kernel: BIOS-e820: [mem 0x000000083f380000-0x000000083fffffff] reserved
Sep 07 23:07:41 archlinux kernel: NX (Execute Disable) protection: active
Sep 07 23:07:41 archlinux kernel: APIC: Static calls initialized
Sep 07 23:07:41 archlinux kernel: e820: update [mem 0xae4bd018-0xae4cb057] usable ==> usable
Sep 07 23:07:41 archlinux kernel: e820: update [mem 0xae49e018-0xae4bc057] usable ==> usable
Sep 07 23:07:41 archlinux kernel: extended physical RAM map:
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009c3efff] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x0000000009c3f000-0x0000000009ffffff] reserved
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x000000000a20e000-0x000000000affffff] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x000000000b020000-0x00000000ae49e017] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x00000000ae49e018-0x00000000ae4bc057] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x00000000ae4bc058-0x00000000ae4bd017] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x00000000ae4bd018-0x00000000ae4cb057] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x00000000ae4cb058-0x00000000baecffff] usable
Sep 07 23:07:41 archlinux kernel: reserve setup_data: [mem 0x00000000baed0000-0x00000000bc63cfff] reserved

Heres one before that just in case:

[stefanos@archlinux ~]$ sudo journalctl -b -2
[sudo] password for stefanos: 
Sep 07 17:53:03 archlinux kernel: Linux version 6.10.8-arch1-1 (linux@archlinux) (gcc (GCC) 14.2.1 20240805, GNU ld (GNU Binutils) 2.43.0) #1 SMP PREEMP>
Sep 07 17:53:03 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=23f4c7c6-4cdf-4dbc-baca-c64a6c980c2b rw zswap.enabled=0 rootfstype=e>
Sep 07 17:53:03 archlinux kernel: BIOS-provided physical RAM map:
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009c3efff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x0000000009c3f000-0x0000000009ffffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000baecffff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000baed0000-0x00000000bc63cfff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000bc63d000-0x00000000bc796fff] ACPI data
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000bc797000-0x00000000bce7dfff] ACPI NVS
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000bce7e000-0x00000000bdbfefff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000bdbff000-0x00000000beffffff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000bf000000-0x00000000bfffffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x0000000100000000-0x000000083f37ffff] usable
Sep 07 17:53:03 archlinux kernel: BIOS-e820: [mem 0x000000083f380000-0x000000083fffffff] reserved
Sep 07 17:53:03 archlinux kernel: NX (Execute Disable) protection: active
Sep 07 17:53:03 archlinux kernel: APIC: Static calls initialized
Sep 07 17:53:03 archlinux kernel: e820: update [mem 0xae494018-0xae4a2057] usable ==> usable
Sep 07 17:53:03 archlinux kernel: e820: update [mem 0xae475018-0xae493057] usable ==> usable
Sep 07 17:53:03 archlinux kernel: extended physical RAM map:
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009c3efff] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x0000000009c3f000-0x0000000009ffffff] reserved
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x000000000a20e000-0x000000000affffff] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x000000000b000000-0x000000000b01ffff] reserved
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x000000000b020000-0x00000000ae475017] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x00000000ae475018-0x00000000ae493057] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x00000000ae493058-0x00000000ae494017] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x00000000ae494018-0x00000000ae4a2057] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x00000000ae4a2058-0x00000000baecffff] usable
Sep 07 17:53:03 archlinux kernel: reserve setup_data: [mem 0x00000000baed0000-0x00000000bc63cfff] reserved

I also updated my motherboard's BIOS to the latest one and checked if its due to some problematic ram of mine with memtest86 and my system passed, no errors with full test that took 5 hours which leads me to think this is a software issue.

Could it also be that i might have installed steam with the wrong drivers? When installing the steam it asked which drivers I should install and i chose the 5th which was amd-radeon, could it be that issue? To be fair the whole freeze issue started after I did

 sudo pacman -Syu

and installed the latest updates but im not 100% sure.

Stef99 · 2024-09-08 08:56:24

More info that might help:

glxinfo -B    # mesa-utils
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.8, DRM 3.57, 6.10.8-arch1-1) (0x73df)
    Version: 24.2.2
    Accelerated: yes
    Video memory: 12288MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 10908 MB, largest block: 10908 MB
    VBO free aux. memory - total: 15763 MB, largest block: 15763 MB
    Texture free memory - total: 10908 MB, largest block: 10908 MB
    Texture free aux. memory - total: 15763 MB, largest block: 15763 MB
    Renderbuffer free memory - total: 10908 MB, largest block: 10908 MB
    Renderbuffer free aux. memory - total: 15763 MB, largest block: 15763 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12288 MB
    Total available memory: 28296 MB
    Currently available dedicated video memory: 10908 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.8, DRM 3.57, 6.10.8-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.2.2-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.2.2-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.2.2-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

vulkaninfo --summary  #vulkan-tools
==========
VULKANINFO
==========

Vulkan Instance Version: 1.3.279


Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display             : extension revision 1
VK_EXT_acquire_xlib_display            : extension revision 1
VK_EXT_debug_report                    : extension revision 10
VK_EXT_debug_utils                     : extension revision 2
VK_EXT_direct_mode_display             : extension revision 1
VK_EXT_display_surface_counter         : extension revision 1
VK_EXT_headless_surface                : extension revision 1
VK_EXT_surface_maintenance1            : extension revision 1
VK_EXT_swapchain_colorspace            : extension revision 4
VK_KHR_device_group_creation           : extension revision 1
VK_KHR_display                         : extension revision 23
VK_KHR_external_fence_capabilities     : extension revision 1
VK_KHR_external_memory_capabilities    : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2         : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2       : extension revision 1
VK_KHR_portability_enumeration         : extension revision 1
VK_KHR_surface                         : extension revision 25
VK_KHR_surface_protected_capabilities  : extension revision 1
VK_KHR_wayland_surface                 : extension revision 6
VK_KHR_xcb_surface                     : extension revision 6
VK_KHR_xlib_surface                    : extension revision 6
VK_LUNARG_direct_driver_loading        : extension revision 1

Instance Layers: count = 4
--------------------------
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207  version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_32   Steam Overlay Layer          1.3.207  version 1
VK_LAYER_VALVE_steam_overlay_64   Steam Overlay Layer          1.3.207  version 1

Devices:
========
GPU0:
        apiVersion         = 1.3.289
        driverVersion      = 24.2.2
        vendorID           = 0x1002
        deviceID           = 0x73df
        deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
        deviceName         = AMD Radeon RX 6700 XT (RADV NAVI22)
        driverID           = DRIVER_ID_MESA_RADV
        driverName         = radv
        driverInfo         = Mesa 24.2.2-arch1.1
        conformanceVersion = 1.3.0.0
        deviceUUID         = 00000000-0900-0000-0000-000000000000
        driverUUID         = 414d442d-4d45-5341-2d44-525600000000

DRI_PRIME=1 glxinfo -B
name of display: :1
Inconsistent value (1) for DRI_PRIME. Should be < 1 (GPU devices count). Using: 0
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.8, DRM 3.57, 6.10.8-arch1-1) (0x73df)
    Version: 24.2.2
    Accelerated: yes
    Video memory: 12288MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 10904 MB, largest block: 10904 MB
    VBO free aux. memory - total: 15746 MB, largest block: 15746 MB
    Texture free memory - total: 10904 MB, largest block: 10904 MB
    Texture free aux. memory - total: 15746 MB, largest block: 15746 MB
    Renderbuffer free memory - total: 10904 MB, largest block: 10904 MB
    Renderbuffer free aux. memory - total: 15746 MB, largest block: 15746 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12288 MB
    Total available memory: 28296 MB
    Currently available dedicated video memory: 10904 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.8, DRM 3.57, 6.10.8-arch1-1)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.2.2-arch1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.2.2-arch1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.2.2-arch1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Stef99 · 2024-09-08 16:38:12

Update: I tried other games and I had 0 freezes compared to the other one I had so I unistalled and reinstalled it and this time it didn't freeze the system. Coincidentally while playing the total ram used was 23gb instead of 28gb so it leads me to believe this issue is as i said earlier a ram issue so is there a way to limit my ram so it doesn't reach the limit and freeze?

Nikolai5 · 2024-09-09 07:09:30

Your journal looks like it might have been a copy and paste from the terminal, it's incomplete.
Use

sudo journal -b -# | curl -F 'file=@-' 0x0.st

replace # with value, then share the result with us.

That's really high memory usage for a single game, but ignoring that, what is your swap setup? Do you have a swap parition, zram or nothing?
Run

cat /proc/swaps

if you don't know.

Stef99 · 2024-09-09 07:30:56

Nikolai5 wrote:

Your journal looks like it might have been a copy and paste from the terminal, it's incomplete.
Use
sudo journal -b -# | curl -F 'file=@-' 0x0.st
replace # with value, then share the result with us.
That's really high memory usage for a single game, but ignoring that, what is your swap setup? Do you have a swap parition, zram or nothing?
Run
cat /proc/swaps
if you don't know.

Sure here you go.:

cat /proc/swaps
Filename                                Type            Size            Used            Priority
/dev/zram0                              partition       4194300         0               100

The game im playing is unoptimized RTS and I have it on ultra settings which gives you a notice you need to have 32gb of ram which I have.

 sudo journal -b -# | curl -F 'file=@-' 0x0.st
 http://0x0.st/XxiT.txt

Stef99 · 2024-09-09 11:08:53

This one is immediately after a freeze,

 https://0x0.st/Xx-w.txt

Also increased how much swap is available at 38GB from 4GB and still the freezing persists. Noticed my gpu load is at 100% 12gb and the freezing 2 times now has happened after some effects in the game intensify so maybe that has something to do with it?

drtebi · 2024-09-09 15:21:17

This may sound like a silly comment... but have you checked all connections? Are the fans all running?

I just experienced very similar problems, and after trying all kinds of solutions, taking the computer out and re-seating the connections did the trick for me.

Stef99 · 2024-09-09 15:27:32

I did for the fans at least and all are working fine, coolercontrol (temp and fan manager) shows everything in order with the only thing that bugs me atm is the GPU load being at 100% all time while playing the game. On the motherboard i also enabled XMP profile1 for both CPU and Ram so the system can have everything. I don't think this is the issue cause a few days ago I installed arch from mint which there the game run fine with the same settings, I think the gpu load was 100% even there so its very strange that it happens now which makes me think theres a setting or driver i have missed installing that is causing this. Unless i have so much bad luck that something went wrong component wise but I checked ram+cpu health and got no errors.

Last edited by Stef99 (2024-09-09 15:30:48)

jl2 · 2024-09-09 19:30:41

Hello, just reading through to see we still do not know which game.

Also, if that game needs 30G of memory it also might need a little more than 12G vram.
Does the game also crash without ultra settings and RT?

Last, if you suspect RAM issues, have you done some memtesting?

Last edited by jl2 (2024-09-09 19:31:11)

Stef99 · 2024-09-09 19:55:56

jl2 wrote:

Hello, just reading through to see we still do not know which game.

Also, if that game needs 30G of memory it also might need a little more than 12G vram.
Does the game also crash without ultra settings and RT?
Last, if you suspect RAM issues, have you done some memtesting?

Game is gates of hell ostfront. Tried at very low and the game didn't crash, seems at ultra or high settings in general the freezing happens. This is strange cause neither on windows nor on linuxmint this was happening. As for memtest yes I did and let it for 5 hours to test which returned a pass and no errors. Honestly I don't know this could be a issue with the game only since I tried another one and nothing happened for 2 hours or so, and only happens with GOH ostfront.
Also tried going back from kernel 9.10.8 to .7 and didnt fix the issue, tried with the latest .9 and nothing as well. Honestly I have exhausted all options I don't know what could be causing this anymore and im kinda tired.

Last edited by Stef99 (2024-09-09 19:56:17)

seth · 2024-09-10 07:16:49

On the motherboard i also enabled XMP profile1 for both CPU and Ram so the system can have everything.

XMP is an intel thing?
But disable that, neiter XMP nor https://en.wikipedia.org/wiki/Serial_pr … ing_(EXPO) tend to make things more stable.

Speaking of which:

Sep 09 10:20:27 archlinux coolercontrold[681]: Initialized CPU Devices: ["AMD Ryzen 7 5800X3D 8-Core Processor"]

https://wiki.archlinux.org/title/Ryzen#Troubleshooting

Honestly I have exhausted all options

Have you tried to
* Disable zram, add a swap file, https://wiki.archlinux.org/title/Zram#Usage_as_swap https://wiki.archlinux.org/title/Swap#Swap_file
* Disable THP, "transparent_hugepage=never", https://wiki.archlinux.org/title/Kernel_parameters
* Cut out plasma & wayland, test thegame on an uncomposited X11 session (openbox, icewm, i3 - stuff like that, no picom) - steam will otherwise run on xwayland anyway.
* Try the LTS kernel.

Other than the hardware configuration (less aggresive, more core voltage) the goal should be to simplify the environment until it stops failing and from there return complexity until you hit a weak spot.
Obviously also keep an eye on the temperatures.

Stef99 · 2024-09-10 10:33:49

seth wrote:

On the motherboard i also enabled XMP profile1 for both CPU and Ram so the system can have everything.
XMP is an intel thing?
But disable that, neiter XMP nor https://en.wikipedia.org/wiki/Serial_pr … ing_(EXPO) tend to make things more stable.
Speaking of which:
Sep 09 10:20:27 archlinux coolercontrold[681]: Initialized CPU Devices: ["AMD Ryzen 7 5800X3D 8-Core Processor"]
https://wiki.archlinux.org/title/Ryzen#Troubleshooting
Honestly I have exhausted all options
Have you tried to
* Disable zram, add a swap file, https://wiki.archlinux.org/title/Zram#Usage_as_swap https://wiki.archlinux.org/title/Swap#Swap_file
* Disable THP, "transparent_hugepage=never", https://wiki.archlinux.org/title/Kernel_parameters
* Cut out plasma & wayland, test thegame on an uncomposited X11 session (openbox, icewm, i3 - stuff like that, no picom) - steam will otherwise run on xwayland anyway.
* Try the LTS kernel.
Other than the hardware configuration (less aggresive, more core voltage) the goal should be to simplify the environment until it stops failing and from there return complexity until you hit a weak spot.
Obviously also keep an eye on the temperatures.

Tried on those and nothing. I now think this is exclusive to the game itself for I tried tickering with some of the steam workshop mods that I set it up and by doing that the game freezes on the menu where there's no stress with ram or anything. Im gonna ticker with proton and unistalling the mods and see if it works. Strange how the game freezing freezes the whole system as well, how can it do that?

Last edited by Stef99 (2024-09-10 10:39:13)

seth · 2024-09-10 13:48:39

Please don't fully-quote previous posts, they're preserved in the forum and most of the time I can even remember what I wrote so you just end up bloating the thread.

Strange how the game freezing freezes the whole system as well, how can it do that?

How do you define "freezes the whole system"?
#8 has "This one is immediately after a freeze" but you could not draw that from a "frozen" system.
You called journalctl from konsole, so not even the GUI was "frozen"?
Or (since it'S only like 3 minutes into the session) did you reboot the system?

Try to not do that.
See whether you can switch the VT (ctrl+alt+F3), ssh into the system or use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (nb. you'll have to explicitly enable that *before* the system freezes!)

Generally, if eg. the amdgpu kernel module causes a kernel panic the system will halt (except for usually blinking keyboard LEDs) and the linked issues specific to your Ryzen CPU (what specifically did you test itr - and how) will simply knock out the CPU, ie the software triggers a hardware issue that immediately affects everything.

Stef99 · 2024-09-10 14:10:53

When i mean freeze the whole system it means everything is unresponsive for example ctrl+alt+F3 doesn't work (even variations like maybe f1 or f2 and for the record it works if the system is not frozen), alt f4 and alt tab don't work either etc etc only way out is holding down the power button as nothing happens. I tried to let it sit for 1 hour and it was still unresponsive. But I haven't tried alt+sysrq+b to reboot, currently im testing so if it freezes ill try it (I have enabled it).

I called journalctl from console after shutting the system down.

Last edited by Stef99 (2024-09-10 14:46:16)

joske · 2024-09-11 08:26:06

I'm having similar issues (but not during gaming - I don't game), complete lockups (doesn't even respond to ping), but sysreq still works. Several crashes today while running `cargo test` on big rust project. I had several of these over the course of the last few days. At first I thought it was virtualbox, but today I was not running any VMs. Nothing in logs about the crash.

Kernel was updated today to (6.10.9-arch1-2) but it does not fix the issue. Also running on AMD GPU (RX580). System was rock solid before. Seems like a kernel regression.

info:

CPU: 24-core (8-mt/16-st) 13th Gen Intel Core i9-13900K (-MST AMCP-)
speed/min/max: 811/800/5500:5800:4300 MHz Kernel: 6.10.9-arch1-2 x86_64
Up: 17m Mem: 5.47/31.09 GiB (17.6%) Storage: 3.29 TiB (13.5% used) Procs: 536
Shell: fish inxi: 3.3.35

Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
    driver: amdgpu v: kernel
  Device-2: Logitech Logitech Webcam C925e driver: snd-usb-audio,uvcvideo
    type: USB
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
    resolution: 1: 2560x1440~60Hz 2: 2560x1440~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.2-arch1.1
    renderer: AMD Radeon RX 580 Series (radeonsi polaris10 LLVM 18.1.8 DRM 3.57
    6.10.9-arch1-2)

joske · 2024-09-11 09:18:53

Ok, seems to be related to memory pressure. When I run 'cargo test' on my project, it consumes ridiculous amounts of memory, and this crashes the kernel EVERY single time. With LTS kernel, the OOM killer kills the terminal and kernel does not crash.

Out of memory: Killed process 306333 (snarkvm_synthes) total-vm:52890776kB, anon-rss:29081172kB, file-rss:512kB, shmem-rss:0kB, UID:1000 pgtables:72928kB oom_score_adj:200

Last edited by joske (2024-09-11 09:19:58)

Stef99 · 2024-09-11 12:16:08

I think i fixed my issue either by reinstalling the mods or/and turning the HDR off since my monitor isn't HDR either way. Tested it during a very ram intense season with firefox+many other apps open and the game as well and nothing happened. The new kernel might also have fixed it but can't confirm it.

Arch Linux

#1 2024-09-06 19:18:26

[SOLVED] PC crashes while gaming

#2 2024-09-07 17:35:02

Re: [SOLVED] PC crashes while gaming

#3 2024-09-07 21:08:37

Re: [SOLVED] PC crashes while gaming

#4 2024-09-08 08:56:24

Re: [SOLVED] PC crashes while gaming

#5 2024-09-08 16:38:12

Re: [SOLVED] PC crashes while gaming

#6 2024-09-09 07:09:30

Re: [SOLVED] PC crashes while gaming

#7 2024-09-09 07:30:56

Re: [SOLVED] PC crashes while gaming

#8 2024-09-09 11:08:53

Re: [SOLVED] PC crashes while gaming

#9 2024-09-09 15:21:17

Re: [SOLVED] PC crashes while gaming

#10 2024-09-09 15:27:32

Re: [SOLVED] PC crashes while gaming

#11 2024-09-09 19:30:41

Re: [SOLVED] PC crashes while gaming

#12 2024-09-09 19:55:56

Re: [SOLVED] PC crashes while gaming

#13 2024-09-10 07:16:49

Re: [SOLVED] PC crashes while gaming

#14 2024-09-10 10:33:49

Re: [SOLVED] PC crashes while gaming

#15 2024-09-10 13:48:39

Re: [SOLVED] PC crashes while gaming

#16 2024-09-10 14:10:53

Re: [SOLVED] PC crashes while gaming

#17 2024-09-11 08:26:06

Re: [SOLVED] PC crashes while gaming

#18 2024-09-11 09:18:53

Re: [SOLVED] PC crashes while gaming

#19 2024-09-11 12:16:08

Re: [SOLVED] PC crashes while gaming

Board footer