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:

https://www.reddit.com/r/linux_gaming/comments/1nn2d5e/games_freezing_randomly_until_i_alt_tab_into_the/

My overall concern is if this is a hardware issue rhat I need to get rma’d or just a linux issue.

Crash logs:

https://gofile.io/d/zft71K

Any help is appreciated!! Thank you all for your time!

  • FauxLiving@lemmy.worldEnglish
    3·
    9 hours ago

    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).