I few days ago I posted about my games freezing on my new pc here:
https://lemmy.ml/post/41956931
I thought my issue was an outdated motherboard bios and also having screen locking/sleep mode on. It appears that was wrong because I am still having the issue. I have come prepared this time though! I have several proton logs of games freezing up. Some of the logs are the game freezing and continuing, other logs are the gsne freezing and completely stopping.
I also had a weird error popup that would come up when enabling proton logs for cyberpunk. I put that image with the proton logs. I put in my journalctl with the most recent cyberpunk freeze/crash that happened as well.
I am beginning to think that it is a driver issue with my 5070ti. I found this post on the linux gaming subreddit that has many people expressing the same issue:
My overall concern is if this is a hardware issue rhat I need to get rma’d or just a linux issue.
Crash logs:
Any help is appreciated!! Thank you all for your time!
what DE/WM are you using on Cachy?
I had a very similar problem as you but ONLY with x11 DE’s/WM’s. My machine would do the exact same thing with some games. play for a bit, then the visual and only the visual would freeze or show a black screen or simply just show the desktop but the game was still running as the audio and what have you was still working. This would also happen when alt tabbing or moving to another workspace and back. Essentially because my system had an onboard amd gpu AND a discrete Nvidia GPU gaming on x11 was a no go and I had to use wayland and it would ONLY flawlessly work on KDE. Using things like Niri or Hyprland or whatever had separate issues with mouse constraints.
Also have you tried using a different version of Proton? I know the latest GE Proton isn’t honestly Eggrolls best work as I’ve also had issues with it and have heard others having issues as well.
From your old thread:
ProtonGE 10-28
This version crashes for me constantly too, 10-25 has been my fallback (I haven’t tried the newer releases)
You mentioned that in one game you made it work by forcing mouse capture. It’s possible you’re losing focus in some weird way (I did also see in the system log that you had a PlasmaShell crash around 17:11) does this coincide with a freeze?
Another thing that you can try is changing the focus stealing prevention in KDE to a higher setting, this will prevent windows from stealing focus if that is the problem. It’s in System Settings -> Window Behavior -> Focus tab, change Focus stealing prevention to medium or higher (you can read).
In your Reddit thread they recommended you use Wayland (PROTON_ENABLE_WAYLAND=1 %command% in the launch options), did you try that?
Now onto the logs:
In the Cyberpunk log it looks like the crash is being caused by Steam Input. This is the assertion that triggers all of the cascade of failures:
5755.033:0178:017c:err:msvcrt:_wassert (L"!status",L"../src-lsteamclient/winISteamInput.c",1748)Based on some digging, it looks like the game’s input detection and Steam Input do not get along so you should disable Steam Input for Cyberpunk.
PEAK logs did not show the same error (so, I assume it works just fine).
Do a series of burn in tests. CPU intense, GPU intense, RAM intense, storage intense, network intense if you can, one at a time. It might be that one of these subsystems is broken in such a way that it ceases to function under stress. Video games stress the hell out of all of them, so if you can isolate them like this, it might help narrow down the issue.
My bet is on something overheating, or a bad ram stick.
Nothing pointing to HW issues jumps out from the logs. It looks more like a GPU driver issue to me. To isolate further, I’d suggest:
-
Make sure that Proton doesn’t use your iGPU for Vulkan.
-
Try disabling DirectX12 in Steam game lauch settings.
Bit busy right now, so can’t look up links on how to do those right now, but I hope you can find out how to do those.
-
I’m still crap at deciphering wine logs, but it doesn’t seem to show anything out of the ordinary.
Assuming this is a driver issue, have you tried or are you using akmod-nvidia-open: https://rpmfusion.org/Howto/NVIDIA#Kernel_Open (example for Fedora)
I think some distros still have them split into 2 alternative packages.
Otherwise, do a heavy ram test with memtest86+ (booted) to check your XMP profile and RAM sticks are good based on your previous post.
Maybe do a ram test. I had weird crash issues on Linux that I didn’t experience in windows for whatever reason. Turned out after a lot of blaming Linux, I had a stick of ram that was trash. I pulled out and now I have 16GB and no crashes instead of 32GB with weird crashes and inexplicable behavior mostly when I browse or game.
I tried memtest86 and my ram passed all of the tests. Is there a test you would recommend outside of that?
I just used memtest, but I ran multiple full passes over night. Flaky memory won’t always be caught by a single pass, but in my case it was really bad.
I had a PSU with one malfunctioning GPU power cable, but I spent a year with a half powered 1080 randomly crashing and cursing the state of linux and nvidia drivers. Memcheck said the ram is fine, temps are fine, other games work fine, it has to be the software! Oops…
I have a ram stick going bad. I only figured out it was a ram issue because I started getting “out of memory” crashes while doing things that used to work perfectly fine. The problem is, I only have one stick and ram costs more than my computer now.
Check your warranty. I recently found a bad stick I bought years ago. Turns out lots of ram has a lifetime warranty
If only, if only. It’s a pre-built I got from HP. I never would have if not for the fact that I was able to get it for a steal at only $300, which was about the price of its graphics card at the time.



