CS2 Hangs X.org; Arch Linux Arc A750 Graphics Card
Hello @limitedAtonement, please do not intentionally open duplicate issue reports. Closing as a duplicate of ValveSoftware/csgo-osx-linux#4018.
I understand why you would think this is a duplicate, but this is a different bug. I was going to comment on that issue when I noticed that there are many differences:
- In the stack trace, this issue has 17
libcef.soat the top of the stack trace, but the other issue doesn't mention this shared object at all - In the other issue, the core dump is like this:
systemd-coredump[22037]: Process 21837 (cs2), but this issue,systemd-coredump[77680]: [🡕] Process 76831 (steamwebhelper)(in other words,cs2was crashing, but nowsteamwebhelperis crashing) - This issue has the following lines
which seem completely different from what I was getting before(process:77222): Pango-CRITICAL **: 16:54:06.389: pango_layout_line_get_x_ranges: assertion 'start_index <= end_index' failed Fontconfig warning: FcPattern object weight does not accept value "Regular" src/clientdll/steamengine.cpp (2876) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
That said, if you're convinced that this is the same problem, I'm happy to add these comments to ValveSoftware/csgo-osx-linux#4018 and ignore this ticket.
Thank you for your consistent helpfulness organizing this issue tracker!
I'd say you also need to dump the last few lines of 'dmesg' kernel log to see if there is some memory or CPU corruption going on. If there is, it will show something like 'invalid instruction'.
Can you try enabling the compatibility with say Proton Hotfix and see if it still crashes?
I would also try something like OpenSUSE Leap on an external drive, if there is no change on the crashes.
The end of sudo journalctl --follow after a crash is like this:
Jul 15 11:47:55 baxter systemd[1372]: Started tmux child pane 4737 launched by process 1862.
Jul 15 11:48:02 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:48:02 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:48:02 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:48:03 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:48:03 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:48:03 baxter pipewire[1516]: mod.client-node: detected old client version 4
Jul 15 11:48:08 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:48:08 baxter pipewire[1516]: mod.client-node: detected old client version 4
Jul 15 11:48:09 baxter xdg-desktop-por[2008]: Realtime error: Could not get pidns for pid 4855: Could not fstatat ns/pid: Not a directory
Jul 15 11:50:34 baxter kernel: i915 0000:23:00.0: [drm] [CRTC:134:pipe B] DSB 0 queue setup failed, will fallback to MMIO for display HW programming
Jul 15 11:59:06 baxter systemd[1372]: Starting Xfce configuration service...
Jul 15 11:59:06 baxter systemd[1372]: Started Xfce configuration service.
Jul 15 11:59:06 baxter systemd-coredump[6001]: Process 3039 (steamwebhelper) of user 1000 terminated abnormally with signal 5/TRAP, processing...
Jul 15 11:59:06 baxter systemd[1]: Created slice Slice /system/systemd-coredump.
Jul 15 11:59:06 baxter systemd[1]: Started Process Core Dump (PID 6001/UID 0).
Jul 15 11:59:07 baxter (sd-parse-elf)[6004]: Could not parse number of program headers from core file: invalid `Elf' handle
Jul 15 11:59:07 baxter (sd-parse-elf)[6004]: Could not parse number of program headers from core file: invalid `Elf' handle
Jul 15 11:59:07 baxter systemd-coredump[6002]: [🡕] Process 3039 (steamwebhelper) of user 1000 dumped core.
Module /run/host/usr/lib/libicudata.so.76.1 without build-id.
Module /run/host/usr/lib/libicudata.so.76.1
Module /run/host/usr/lib/libicuuc.so.76.1 without build-id.
Module /run/host/usr/lib/libicuuc.so.76.1
Stack trace of thread 3039:
#0 0x00007ff3e910dfbf n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x670dfbf)
#1 0x00007ff3e910da8b n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x670da8b)
#2 0x00007ff3e910e039 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x670e039)
#3 0x00007ff3e79e1857 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4fe1857)
#4 0x00007ff3e79deca6 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4fdeca6)
#5 0x00007ff3e79dd8fb n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4fdd8fb)
#6 0x00007ff3e79e93c8 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4fe93c8)
#7 0x00007ff3e79ea7c7 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4fea7c7)
#8 0x00007ff3e7804f91 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4e04f91)
#9 0x00007ff3e78693bb n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4e693bb)
[#10](/issue/ValveSoftware/steam-for-linux/10) 0x00007ff3e78695d1 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x4e695d1)
[#11](/issue/ValveSoftware/steam-for-linux/11) 0x00007ff3e915e06f n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x675e06f)
[#12](/issue/ValveSoftware/steam-for-linux/12) 0x00007ff3e917ef86 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x677ef86)
[#13](/issue/ValveSoftware/steam-for-linux/13) 0x00007ff3e91e4621 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x67e4621)
[#14](/issue/ValveSoftware/steam-for-linux/14) 0x00007ff3e917f721 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x677f721)
[#15](/issue/ValveSoftware/steam-for-linux/15) 0x00007ff3e913f6be n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x673f6be)
[#16](/issue/ValveSoftware/steam-for-linux/16) 0x00007ff3e913ff6c n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x673ff6c)
[#17](/issue/ValveSoftware/steam-for-linux/17) 0x00007ff3e531931c n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x291931c)
[#18](/issue/ValveSoftware/steam-for-linux/18) 0x000055b3a99bf78d n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/steamwebhelper + 0x49778d)
[#19](/issue/ValveSoftware/steam-for-linux/19) 0x000055b3a9a16ae9 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/steamwebhelper + 0x4eeae9)
[#20](/issue/ValveSoftware/steam-for-linux/20) 0x000055b3a9a1f4d8 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/steamwebhelper + 0x4f74d8)
[#21](/issue/ValveSoftware/steam-for-linux/21) 0x00007ff3e1a376b5 n/a (/run/host/usr/lib/libc.so.6 + 0x276b5)
[#22](/issue/ValveSoftware/steam-for-linux/22) 0x00007ff3e1a37769 n/a (/run/host/usr/lib/libc.so.6 + 0x27769)
[#23](/issue/ValveSoftware/steam-for-linux/23) 0x000055b3a982a02a n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/steamwebhelper + 0x30202a)
Stack trace of thread 3050:
#0 0x00007ff3e1b1c5eb n/a (/run/host/usr/lib/libc.so.6 + 0x10c5eb)
#1 0x00007ff3e91ca9c3 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x67ca9c3)
#2 0x00007ff3ea64b0f4 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x7c4b0f4)
#3 0x00007ff3ea6c2af5 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x7cc2af5)
#4 0x00007ff3ea6c390a n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x7cc390a)
#5 0x00007ff3e915e06f n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x675e06f)
#6 0x00007ff3e918f3fe n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x678f3fe)
#7 0x00007ff3e918efc5 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x678efc5)
#8 0x00007ff3e918eab9 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x678eab9)
#9 0x00007ff3e9198f4e n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x6798f4e)
[#10](/issue/ValveSoftware/steam-for-linux/10) 0x00007ff3e9198c9d n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x6798c9d)
[#11](/issue/ValveSoftware/steam-for-linux/11) 0x00007ff3e9198bad n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x6798bad)
[#12](/issue/ValveSoftware/steam-for-linux/12) 0x00007ff3e91b6e23 n/a (/home/lawsa/.local/share/Steam/ubuntu12_64/libcef.so + 0x67b6e23)
[#13](/issue/ValveSoftware/steam-for-linux/13) 0x00007ff3e1aa57eb n/a (/run/host/usr/lib/libc.so.6 + 0x957eb)
[#14](/issue/ValveSoftware/steam-for-linux/14) 0x00007ff3e1b2918c n/a (/run/host/usr/lib/libc.so.6 + 0x11918c)
ELF object binary architecture: AMD x86-64
Jul 15 11:59:07 baxter systemd[1]: [email protected]: Deactivated successfully.
Jul 15 11:59:07 baxter systemd[1]: [email protected]: Consumed 1.056s CPU time, 507.1M memory peak.
The launch happened around 11:48:03 and the crash happened around 11:49. The core dump happened after I pkill steam in another TTY. I'll try Proton Hotfix next.
I configured the game to use Proton Hotfix and it started an update. During this update, I was able to reproduce the problem without launching CS2! That makes me think the steam web helper (in-game browser) may be to blame? The computer slowed to a halt and was unusable. I used another machine, sshed to this machine, did pkill steam, but it didn't help this time. I killed all the steam processes (steam web helper, launchpad something something, etc.) and the computer was still unusable. I restarted the computer.
journalctl -b -1 looks similar: there is a coredump report for steamwebhelper at the time when I killed it, but otherwise apparently nothing helpful.
It is likely you have defective hardware. Have you run through the standard Memtest86+ and/or Prime95 torture?
Since you're on Threadripper, I would also try 'mcelog' and 'ras-mc-ctl --summary' to check for runtime errors.
MCELog will show you hardware errors after rebooting, if that was the case. RASDaemon I'm not sure, mine sometimes shows empty for no reason. I'm on an AM4 platform.
Thank you for your input. It looks like mcelog is deprecated (https://unix.stackexchange.com/a/451684/10896). When I ran it, I got AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported. I systemctl start rasdaemon and saw it start in journalctl. I ran cs2 and it says:
My launch options is empty. I changed from proton hotfix to proton 9, restarted and got the same thing. I turned off rasdaemon and still got the same thing.
I just downloaded opensuse leap, so I'll try running cs2 there. I have executed memtest86 a long time ago and everything was fine, but I'll try it again tonight to put this concern to rest.
That is not correct. Mcelog, the command and software, will still store and allow to read the errors from the kernel.
I'm surge of this because this is a Zen 3 system while yours is older Zen 2.
It is correct that you need to load that module, upon which it will read mce errors.
My ASRock board works with both meclog and rasdaemon but ras does not seem to read errors that caused a reboot.
This is with the latest BIOS and AGESA.
On an ASUS board, it worked with mcelog but a BIOS update made it work through RASdaemon only. Zen 1 chip. Im not sure why.
If everything is working, you should ser on dmesg: MCE: in kernel decoding enabled.
I would also disable CPU boost through the kernel 'boost' tunable just to be sure it is not some issie with CPU degradation.
IIRC it is "echo 0 > /sys/devices/system/cpu/cpufreq/boost"
Should still clock high enough that CS2 is playable.
From: limitedAtonement @.>
Sent: 15 July 2025 18:29
To: ValveSoftware/steam-for-linux @.>
Cc: Tiago Marques @.>; Comment @.>
Subject: Re: [ValveSoftware/steam-for-linux] CS2 Hangs X.org; Arch Linux Arc A750 Graphics Card (Issue #12172)
[https://avatars.githubusercontent.com/u/7562490?s=20&v=4]limitedAtonement left a comment (ValveSoftware/steam-for-linux#12172)https://github.com/ValveSoftware/steam-for-linux/issues/12172#issuecomment-3074557541
Thank you for your input. It looks like mcelog is deprecated (https://unix.stackexchange.com/a/451684/10896). When I ran it, I got AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. CPU is unsupported. I systemctl start rasdaemon and saw it start in journalctl. I ran cs2 and it says:
image.png (view on web)https://github.com/user-attachments/assets/dd151484-820c-4e60-92af-f6ed61895eff
My launch options is empty. I changed from proton hotfix to proton 9, restarted and got the same thing. I turned off rasdaemon and still got the same thing.
I just downloaded opensuse leap, so I'll try running cs2 there. I have executed memtest86 a long time ago and everything was fine, but I'll try it again tonight to put this concern to rest.
—
Reply to this email directly, view it on GitHubhttps://github.com/ValveSoftware/steam-for-linux/issues/12172#issuecomment-3074557541, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AABIXG3O6MCJZ7JISMNWBSD3IU3ADAVCNFSM6AAAAACA44RFE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANZUGU2TONJUGE.
You are receiving this because you commented.Message ID: @.***>
I ran memtest for about 12 hours last night; all good. ras-mc-ctl says
$ sudo ras-mc-ctl --summary
No Memory errors.
No PCIe AER errors.
No ARM processor errors.
No Extlog errors.
No devlink errors.
No MCE errors.
$
Oh, that clears that part of the hardware.
On the e-mail I had not seen the CS2 screenshot. That is a different thing, could be storage related since everything else seems fine.
rasdaemon logs should log some disk errors though.
What is your distro and file system? For the kind of errors you have here, I would migrate the data to a BTRFS install with xxhash64.
BTRFS would catch silent data corruption and you could catch it at runtime. Other file systems mostly do not do data checksumming.
Steam file verification, unfortunately, also doesn't checksum the files. It only checks they are present and (possibly) that the size is correct.
I didn't make this clear, but I can play offline with bots all day. I'll delete the game from ~/.local/share/Steam/steamapps/common/Counter-Strike\ Global\ Offensive/game/csgo and let it reinstall to try to get the anti-cheat error fixed...
The bots running well is indeed strange.
On your Xorg logs, is there anything when Steam crashes? You should also run Steam from the terminal - just execute 'steam' - so that it will give you output that is not on Systemd.
I always run it from the command line. In the original comment, I listed the output of steam after the crash. I can't get it to crash anymore because I get the VAC warning now every time I try to play match making. I deleted that directory and let it reinstall, but that didn't help. I've restarted a couple times, too.
The first time I did systemctl start rasdaemon, I saw this problem (see comment here: https://github.com/ValveSoftware/steam-for-linux/issues/12172#issuecomment-3074557541). Restarting the computer (rasdaemon is not enabled; it doesn't run on startup) corrected this, but now I can't get past the VAC problem.
I got it to play! I unchecked "Force the use of a specific Steam Play compatibility tool" under Compatibility in Counter-Strike 2 settings. I joined a round in progress and the game froze when the bomb went off (the terrorists had planted). Just to make sure, I played against bots and made sure the bomb exploded, and everything was fine. I ran it again and this time when it crashed, I didn't pkill steam and eventually steam crashed and exited. This is what I saw on standard out/standard error for steam:
src/clientdll/steamengine.cpp (2876) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
src/clientdll/steamengine.cpp (2876) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
assert_20250724171204_36.dmp[76122]: Uploading dump (out-of-process)
/tmp/dumps/assert_20250724171204_36.dmp
assert_20250724171204_36.dmp[76122]: Finished uploading minidump (out-of-process): success = yes
assert_20250724171204_36.dmp[76122]: response: CrashID=bp-6bf98a35-78c3-4e02-b1cc-6f6252250724
assert_20250724171204_36.dmp[76122]: file ''/tmp/dumps/assert_20250724171204_36.dmp'', upload yes: ''CrashID=bp-6bf98a35-78c3-4e02-b1cc-6f6252250724''
src/common/pipes.cpp (882) : fatal stalled cross-thread pipe.
src/common/pipes.cpp (882) : fatal stalled cross-thread pipe.
src/common/pipes.cpp (882) : Fatal assert; application exiting
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
assert_20250724171448_39.dmp[76188]: Uploading dump (out-of-process)
/tmp/dumps/assert_20250724171448_39.dmp
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
src/common/processpipe_posix.cpp (519) : Assertion Failed: CCrossProcessPipe::BWrite: 32 (Broken pipe)
assert_20250724171447_4.dmp[76191]: Uploading dump (out-of-process)
/tmp/dumps/assert_20250724171447_4.dmp
assert_20250724171448_39.dmp[76188]: Finished uploading minidump (out-of-process): success = yes
assert_20250724171448_39.dmp[76188]: response: CrashID=bp-dcc2c52b-9d7e-491a-99ef-2c9e42250724
assert_20250724171448_39.dmp[76188]: file ''/tmp/dumps/assert_20250724171448_39.dmp'', upload yes: ''CrashID=bp-dcc2c52b-9d7e-491a-99ef-2c9e42250724''
assert_20250724171447_4.dmp[76191]: Finished uploading minidump (out-of-process): success = yes
assert_20250724171447_4.dmp[76191]: response: Discarded=1
assert_20250724171447_4.dmp[76191]: file ''/tmp/dumps/assert_20250724171447_4.dmp'', upload yes: ''Discarded=1''
pid 76191 != 76190, skipping destruction (fork without exec?)
Adding process 76190 for gameID 730
steamwebhelper.sh[76202]: Starting steamwebhelper under bootstrap steamrt steam runtime via: /home/lawsa/.local/share/Steam/steamrt64/steam-runtime-steamrt/_v2-entry-point
steamwebhelper.sh[76202]: Starting steamwebhelper with steamrt steam runtime at /home/lawsa/.local/share/Steam/steamrt64/steam-runtime-steamrt/_v2-entry-point
Game Recording - game stopped [gameid=730]
Removing process 76190 for gameID 730
Removing process 75681 for gameID 730
Removing process 75680 for gameID 730
Removing process 75679 for gameID 730
Removing process 75678 for gameID 730
Removing process 75676 for gameID 730
Removing process 75674 for gameID 730
Removing process 75577 for gameID 730
Removing process 75576 for gameID 730
Removing process 75575 for gameID 730
exec ./steamwebhelper -nocrashdialog -lang=en_US -cachedir=/home/lawsa/.local/share/Steam/config/htmlcache -steampid=75100 -buildid=1751405894 -steamid=76561198372529575 -logdir=/home/lawsa/.local/share/Steam/logs -uimode=7 -startcount=1 -steamuniverse=Public -realm=Global -clientui=/home/lawsa/.local/share/Steam/clientui -steampath=/home/lawsa/.local/share/Steam/ubuntu12_32/steam -launcher=0 --valve-initial-threadpool-size=20 --valve-enable-site-isolation --enable-smooth-scrolling --password-store=basic --log-file=/home/lawsa/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --disable-component-update --enable-features=PlatformHEVCDecoderSupport --disable-features=SpareRendererForSitePerProcess,DcheckIsFatal,BlockPromptsIfIgnoredOften,ValveFFmpegAllowLowDelayHEVC
[2025-07-24 17:15:25] Shutdown
Looks like it was able to upload a dump of sorts! X logs while I ran the game are here:
[ 85930.554] (II) event8 - USB PnP Audio Device: is tagged by udev as: Keyboard
[ 85930.554] (II) event8 - USB PnP Audio Device: device is a keyboard
[ 85930.556] (II) event5 - HID 05f3:0007: is tagged by udev as: Keyboard
[ 85930.556] (II) event5 - HID 05f3:0007: device is a keyboard
[ 85930.558] (II) event7 - HID 05f3:0007 Consumer Control: is tagged by udev as: Keyboard
[ 85930.558] (II) event7 - HID 05f3:0007 Consumer Control: device is a keyboard
[ 85930.560] (II) event2 - Shinetek Technology USB Gaming Keyboard: is tagged by udev as: Keyboard
[ 85930.560] (II) event2 - Shinetek Technology USB Gaming Keyboard: device is a keyboard
[ 85930.562] (II) systemd-logind: got resume for 13:64
[ 85930.563] (II) event0 - Power Button: is tagged by udev as: Keyboard
[ 85930.563] (II) event0 - Power Button: device is a keyboard
[ 85930.569] (II) systemd-logind: got resume for 13:76
[ 85930.571] (II) event12 - Generic USB Audio Consumer Control: is tagged by udev as: Keyboard
[ 85930.571] (II) event12 - Generic USB Audio Consumer Control: device is a keyboard
[ 85930.571] (II) systemd-logind: got resume for 13:65
[ 85930.572] (II) event1 - Power Button: is tagged by udev as: Keyboard
[ 85930.572] (II) event1 - Power Button: device is a keyboard
[ 85930.572] (II) systemd-logind: got resume for 13:75
[ 85930.573] (II) event11 - NZXT, Inc. NZXT LIFT MOUSE Mouse: is tagged by udev as: Mouse
[ 85930.574] (II) event11 - NZXT, Inc. NZXT LIFT MOUSE Mouse: device is a pointer
[ 85930.574] (II) systemd-logind: got resume for 13:67
[ 85930.575] (II) event3 - Shinetek Technology USB Gaming Keyboard: is tagged by udev as: Keyboard
[ 85930.575] (II) event3 - Shinetek Technology USB Gaming Keyboard: device is a keyboard
[ 85930.576] (II) systemd-logind: got resume for 13:73
[ 85930.577] (II) event9 - NZXT, Inc. NZXT LIFT MOUSE Keyboard: is tagged by udev as: Keyboard
[ 85930.577] (II) event9 - NZXT, Inc. NZXT LIFT MOUSE Keyboard: device is a keyboard
[ 85930.578] (II) systemd-logind: got resume for 13:70
[ 85930.579] (II) event6 - HID 05f3:0007 System Control: is tagged by udev as: Keyboard
[ 85930.579] (II) event6 - HID 05f3:0007 System Control: device is a keyboard
[ 85930.579] (II) systemd-logind: got resume for 13:77
[ 85930.581] (II) event13 - Generic USB Audio: is tagged by udev as: Keyboard
[ 85930.581] (II) event13 - Generic USB Audio: device is a keyboard
[ 85968.373] (II) event11 - NZXT, Inc. NZXT LIFT MOUSE Mouse: Enabling spurious button debouncing, see https://wayland.freedesktop.org/libinput/doc/1.28.1/button-debouncing.html for details
This is really weird. Seems like a hardware issue to me.
Can you try prime95 (mersenne.org) with big allocations? Do Torture test -> Large FFTs -> Customize Y -> 8192 + 32768.
Then allocate as much as you can without slowing down the system. Let it run for at least 12h to see if it catches any interconnect or IODie issues.
I always run it from the command line. In the original comment, I listed the output of
steamafter the crash. I can't get it to crash anymore because I get the VAC warning now every time I try to play match making. I deleted that directory and let it reinstall, but that didn't help. I've restarted a couple times, too. The first time I didsystemctl start rasdaemon, I saw this problem (see comment here: [#12172 (comment)](https://github.com/ValveSoftware/steam-for-linux/issues/12172#issuecomment-3074557541)). Restarting the computer (rasdaemonis notenabled; it doesn't run on startup) corrected this, but now I can't get past the VAC problem.
Steam validation is useless, it does not do checksumming. You need to use BTRFS to find disk drive issues or some other form of monitoring like SMART or NVMe commands.
At this point, if Prime95 cannot find an issue, I am afraid this would need to be looked at with GDB and debug symbols, which are not really available for the games.
I am not sure you system is logging MCE errors properly.
My suggestion is, everything else going well, install something like OpenSUSE Leap on an external drive and then install Steam and try to exclude an OS library conflict of some kind.
...try to exclude an OS library conflict of some kind.
That's a good idea. I have two other computers that have the same graphics card, but are very different machines. They both have the same problem. One AMD Ryzen 7 3700X, and an AMD Ryzen 5 5600X. I wish I had a comparable non-Intel graphics card handy to compare...
I'll try to run it on OpenSUSE Leap!
I should point out that I have one arch linux computer that can run CS2. It has a GeForce RTX 3080 Mobile graphics card. Processor is 11th Gen Intel i7-11800H. Notably, it is not using an intel (especially Intel Arc) graphics card!
I discovered ~/.local/share/Steam/logs (how have I not heard of this directory before?). I let cs2 run to a crash and I'm looking through the logs. By the way, the crash was slightly different because I actually got a message in a modal dialog box. It was a very simple dialog box with only "OK" button, but I forgot what the error message said.
webhelper-linux.txt (starting with a log message from yesterday; I started cs2 at 08:29 and it crashed at 08:37):
[2025-08-05 15:16:08] [0805/151608.176998:ERROR:ffmpeg_common.cc(959)] Unsupported pixel format: -1
[2025-08-06 08:37:49] [0806/083749.857338:ERROR:zygote_communication_linux.cc(292)] Failed to send GetTerminationStatus message to zygote
[2025-08-06 08:37:49] [0806/083749.857376:WARNING:zygote_communication_linux.cc(304)] Socket closed prematurely.
[2025-08-06 08:37:49] [0806/083749.861701:ERROR:network_service_instance_impl.cc(600)] Network service crashed, restarting service.
[2025-08-06 08:37:49] [0806/083749.864929:WARNING:crashpad_client_linux.cc(432)] prctl: Invalid argument (22)
[2025-08-06 08:37:49] [0806/083749.870876:ERROR:zygote_communication_linux.cc(292)] Failed to send GetTerminationStatus message to zygote
[2025-08-06 08:37:49] [0806/083749.870904:WARNING:zygote_communication_linux.cc(304)] Socket closed prematurely.
[2025-08-06 08:37:49] [0806/083749.872511:ERROR:zygote_communication_linux.cc(292)] Failed to send GetTerminationStatus message to zygote
[2025-08-06 08:37:49] [0806/083749.872537:WARNING:zygote_communication_linux.cc(304)] Socket closed prematurely.
[2025-08-06 08:37:49] [0806/083749.875273:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:49] [0806/083749.875297:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 1 time(s)
[2025-08-06 08:37:49] [0806/083749.876096:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:49] [0806/083749.876112:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 2 time(s)
[2025-08-06 08:37:49] [0806/083749.890080:WARNING:crash_reporting.cc(271)] Failed to set crash key: UserID with value: 0
[2025-08-06 08:37:49] [0806/083749.890130:WARNING:crash_reporting.cc(271)] Failed to set crash key: BuildID with value: 1751405894
[2025-08-06 08:37:49] [0806/083749.890133:WARNING:crash_reporting.cc(271)] Failed to set crash key: SteamUniverse with value: Public
[2025-08-06 08:37:49] [0806/083749.890135:WARNING:crash_reporting.cc(271)] Failed to set crash key: Vendor with value: Valve
[2025-08-06 08:37:49] [0806/083749.890137:WARNING:crash_reporting.cc(271)] Failed to set crash key: Platform with value: Linux
[2025-08-06 08:37:49] [0806/083749.890214:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[2025-08-06 08:37:49] [0806/083749.890730:WARNING:crashpad_client_linux.cc(377)] prctl: Invalid argument (22)
[2025-08-06 08:37:49] [0806/083749.890781:INFO:crash_reporting.cc(238)] Crash reporting enabled for process: utility
[2025-08-06 08:37:50] [0806/083750.050659:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.050694:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 3 time(s)
[2025-08-06 08:37:50] [0806/083750.053711:ERROR:zygote_communication_linux.cc(292)] Failed to send GetTerminationStatus message to zygote
[2025-08-06 08:37:50] [0806/083750.053736:WARNING:zygote_communication_linux.cc(304)] Socket closed prematurely.
[2025-08-06 08:37:50] [0806/083750.057611:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.057630:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 4 time(s)
[2025-08-06 08:37:50] [0806/083750.059070:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.059086:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 5 time(s)
[2025-08-06 08:37:50] [0806/083750.059743:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.059764:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 6 time(s)
[2025-08-06 08:37:50] [0806/083750.060361:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.060374:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 7 time(s)
[2025-08-06 08:37:50] [0806/083750.061230:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.061246:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 8 time(s)
[2025-08-06 08:37:50] [0806/083750.062045:ERROR:gpu_process_host.cc(996)] GPU process launch failed: error_code=1002
[2025-08-06 08:37:50] [0806/083750.062061:WARNING:gpu_process_host.cc(1436)] The GPU process has crashed 9 time(s)
[2025-08-06 08:37:50] [0806/083750.062069:FATAL:gpu_data_manager_impl_private.cc(449)] GPU process isn't usable. Goodbye.
I think it's trying to tell me something ^_^ I wish I had the source code so I could look at what these lines do (gpu_process_host.cc lines 1436 and 996)! Someone does, though? 🥲
webhelper.txt starting with a log message from yesterday, then I launched cs2 at 08:29 and the crash happened at 08:37.
[2025-08-05 17:55:00] UB-1114126: Applying safe browser shutdown workaround
[2025-08-06 08:29:19] SP Shared JS Context-'SharedJSCo': CreatingPopup name:PopupWindow_:rj: browser:65536 parent:0 pid:119080 type:4 flags:98: (2580.00, 409.00) 600.00x286.00: url:about:blank?createflags=2¢erOnBrowserID=3
[2025-08-06 08:29:19] CBrowserComposerSystem::CreateOutputWindow: Creating browser window at: 2580,409 size: 600x286
[2025-08-06 08:29:19] PopupWindow_:rj:: Created window: size: 600,286 pos: 2580,409 mode: System window: 0x86000e2
[2025-08-06 08:29:19] PopupWindow_:rj:: AfterCreated handle:1703950 type:4: (0, 0) 600x286
[2025-08-06 08:29:19] PopupWindow_:rj:-'Launching.': WasHidden 0: (0, 0) 600x286
[2025-08-06 08:29:22] PopupWindow_:rj:-'Launching.': Applying safe browser shutdown workaround
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-US --service-sandbox-type=none --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=gpu-process --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=gpu-process --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=gpu-process --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Applying workarounds due to GPU process restarts: browser:0 gpu:3 uptime:62523.848605
[2025-08-06 08:37:49] Triggering shutdown due to GPU process restarts
[2025-08-06 08:37:49] Quit message loop
[2025-08-06 08:37:49] SteamBrowser-'Welcome to': Applying safe browser shutdown workaround
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=gpu-process --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:49] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:50] Applying workarounds due to GPU process restarts: browser:0 gpu:4 uptime:62524.029404
[2025-08-06 08:37:50] Triggering shutdown due to GPU process restarts
[2025-08-06 08:37:50] Browser - launching child process with: /proc/self/exe --type=gpu-process --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:50] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:50] Applying workarounds due to GPU process restarts: browser:0 gpu:5 uptime:62524.030878
[2025-08-06 08:37:50] Triggering shutdown due to GPU process restarts
[2025-08-06 08:37:50] Browser - launching child process with: /proc/self/exe --type=gpu-process --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:50] Browser - launching child process with: /proc/self/exe --type=utility --utility-sub-type=storage.mojom.StorageService --lang=en-US --service-sandbox-type=utility --no-sandbox --user-agent-product=Valve Steam Client --lang=en_US.UTF-8 --user-data-dir=/home/lawsa/.local/share/Steam/config/htmlcache --crashpad-handler-pid=119264 --buildid=1751405894 --steamid=0 --valve-initial-threadpool-size=20
[2025-08-06 08:37:50] Applying workarounds due to GPU process restarts: browser:0 gpu:6 uptime:62524.031552
[2025-08-06 08:37:50] Triggering shutdown due to GPU process restarts
What it seems from these logs is that the GPU is crashing multiple times, which is why sometimes Xorg is also gone with it.
I would run CS2 with Vsync to see if lower load still causes crashes. If it does, it could be a driver issue. Otherwise, maybe the hardware is broken.
You can also try latest vs longterm kernels, though I don't know if Arch has those available. That would be a way to go to a kernel from 1y ago that may be stable. (though here, there is also Mesa to look at)
I've had an intel iGPU crash multiple times on HL2, which I attributed to maybe some issue with the platform, due to the CPU being always at 85C+.
Given this report and the fact that my PC was super stable for everything else, I am starting to think there may be something else going on with Linux and Intel Linux drivers.
Thank you for your response, @tmarques.
...run CS2 with Vsync to see if lower load still causes crashes...
I doubt load is the problem because the game runs fine with bots.
...there may be something else going on with Linux and Intel Linux drivers.
That's my thought. I have other Arch Linux computers that run fine (and I'm sure lots of people run CS2 fine with Arch Linux), but my Intel Arc A750 (I have three computers with this configuration) all have this same problem.
Run with this, stops my Debian system A750 hanging.
export VK_INSTANCE_LAYERS=VK_LAYER_MESA_vram_report_limit
export VK_VRAM_REPORT_LIMIT_DEVICE_ID=0x8086:0x56a1
export VK_VRAM_REPORT_LIMIT_HEAP_SIZE=4096
May need to install layer from source. Latest mesa git Vulkan driver used too fixed other crashing.
Was seeing on some hangs in dmesg
[TTM] Buffer eviction failed
@jonhere Thank you for the tip. How do I set environment variables for steam? Is this set within steam (launch options?) or do I do this in the terminal before running steam;?
EDIT:
I tried doing export VK_INSTANCE... etc. before running steam so that those variables were in the environment when steam ran, but it didn't help (much). I verified the Device ID using MESA_VK_DEVICE_SELECT=list vulkaninfo which output: GPU 0: 8086:56a1 "Intel(R) Arc(tm) A750 Graphics (DG2)" discrete GPU 0000:23:00.0 (which vendor ID and product ID match what was listed by @jonhere).
@jonhere I used VK_INSTANCE_LAYERS=VK_LAYER_MESA_vram_report_limit .... %command% for steam launch parameters and it doesn't seem to have helped. While using CS2, I ran nvtop and it shows:
PID USER DEV TYPE GPU GPU MEM CPU HOST MEM Command
32059 lmat 0 Graphic 0% 10406MiB 100% 206% 8943MiB /home/lawsa/.local/share/Steam/steamapps/common/Counter-Strike Global Of
10406 MiB is a bit confusing because it seems like it's greater than the maximum memory of 8G? Also, it can sit at that level for a bit before crashing. I'm guessing the system can handle the memory pressure by deallocating, but eventually it can't deallocate any more and steam/cs2 crashes.
Any other ideas?
I used mangohub, and it reflects that the CS2 process is using up to 8gib of RAM. When it gets to 8gib and stays there a bit, cs2 crashes. This makes me think that these environment variables (which should limit graphics card RAM to ~4 gb) are not working?
@jonhere I just noticed this part of your post
...May need to install layer from source. Latest mesa git Vulkan driver used too fixed other crashing. Was seeing on some hangs in dmesg
[TTM] Buffer eviction failed
I'm seeing several "layers":
- https://archlinux.org/packages/extra/x86_64/vulkan-extra-layers/
- https://archlinux.org/packages/extra/x86_64/vulkan-mesa-layers/
- https://archlinux.org/packages/extra/x86_64/vulkan-validation-layers/
Also, https://wiki.archlinux.org/title/Vulkan talks about layers, but that looks like selecting a graphics device which is not a concern for me because I only have one device.
Proton versions
proton hotfixx5 2025-07
Launch options
MESA_VK_DEVICE_SELECT=listx1 2025-10
Sometimes I can play several rounds, but just now I cannot actually get to play. The game freezes after I join a casual match and watch some of the end of a round. Sometimes I get to the start of the next round, and the game freezes when it looks like my character is chambering a round in his pistol but often it doesn't even get to that. I have tried running
steamandsteam-native, and I get the same thing either way.journalctlshows the following:The terminal output from steam is:
System information in steam shows the following: