Hey gang, I’m having trouble running this game. I have a Ryzen 7 7800X3D, RTX 4070 Ti Super, 64GB DDR5 RAM, on a B650 motherboard. My issue is frequent crashing/freezing, meaning I can’t play longer than a few minutes at a time. I have tried re-installing the game, Steam, the entire OS, and then fully wiping the drives to remove Windows dual partition and only installing Mint. Then I was pointed to the drivers, so I tried updating using the ppa(?) driver availability as Mint only offered the nVidia 550 through Driver Manager. I tried each of the separate drivers, rebooting between each load, and still having the same issue. For reference, I was able to run through character creator and early intro of the Streetkid after many failed attempts. But then I get to the ride-along with Dexter DeShawn which does not have skippable sections and takes too long. So the length of that conversation is too long before the game either freezes or outright crashes.
Any suggestions are welcome, it’s really really annoying me and pretty disheartening after hearing how everything just works on Linux (other than competitive online games, which I don’t really play anyway).
Edit to add: I also tried the different Proton versions available through Steam, where I purchased the game.
For me it started crashing frequently as well. But I tried it on my windows partition with the same result (and even more frequent crashes). So I thought it must be some update of the game that introduced that and not Proton/Linux.
Then I tried several Proton versions and one of the older ones seems to be crashing less so I can actually play for some time.
Which Proton Version did you try? I think I’ve been through each of them available on Steam but can retry a specific one to troubleshoot.
I’ve seen other reports of this issue for nVidia cards; people are reporting that updating drivers helps, but it sounds like you’ve done that. If you’re going as far as reinstalling the OS anyway, you might try out a rolling release distro; I’ve been enjoying Garuda quite a bit, and I’ve heard good things about Nobara and Endeavour.
I did try to install Bazzite using Ventoy on an external drive, but it wasn’t working. Someone told me I should use a USB flash drive instead of an external hard drive and that may have been the issue, but I’ll keep this in mind if it fails again!
Yeah, you should probably use a USB for installing stuff.
Bazzite is what I use, and I don’t have any crashes or really any other problems with running Cyberpunk. Might be worth a try.
It was via USB, just not a flash memory stick but rather an external drive.
I had some weird issues with freezing and black screen and changing from Wayland to X11 fixed it.
I do not know what Wayland nor X11 is. I’m running Linux Mint with Cinnamon(?).
X11 and Wayland are essentially the way your computer puts graphics on the screen. X11 is old, and thus missing many modern features, but works with basically anything. Wayland is new, has new features support, and can break shit randomly
Cinnamon defaults to X11, Wayland is available by logging out and clicking the icon that looks like a mountain (cinnamon logo) and choosing Cinnamon Wayland (Beta)
Okay so if X11 is what fixed it for you, I should stick with X11 it sounds like. Is that correct?
Here’s my suggestion.
First, check your RAM with Memtest86+ or similiar tool. This is the first test because failing memory can and will corrupt your whole system, and it’s easy to test.
Second, if RAM is fine, check the logs. This is more effective then just guessing. Just copy-pasting possible errors to your favorite search engine usually points to the right direction. Archwiki has a nice tutorials about logs.
Third option is to test components one-by-one. Remove all unnecessary components, such as extra SSDs/HDDs, wifi cards, USB devices and PCIe cards. If it doesn’t help, test your CPU and GPU by running dedicated CPU and GPU benchmark tools. If you still get hangs, try with another PSU. If your components test fine, it’s likely a driver issue. See Arch wiki article on Nvidia troubleshooting for some tips about that.
Your last option is pure guessing. It’s the most time and money consuming way to debug with the smallest chance of success, but still many people prefer it. Most often issues like these are GPU issues, so it’s a good guess. However it’s still a guess.
I hope this helps.
My issue is frequent crashing/freezing, meaning I can’t play longer than a few minutes at a time
Could be overheating.
I use AMD hardware.
However, a few years back, I had a particular AMD card that, using its default onboard power profiles, tended to overheat with the default on-card power profiles in games which really exercised the thing; I understand that the vendor that made these cards had issues with insufficient thermal paste or the thermal paste detaching or something. That’s the card vendor’s fault – the card shouldn’t reach a point where it can get into trouble via overheating, but regardless, it was still a problem. Some people disassembled the thing and put more thermal paste on. I forced the thing to a more-conservative power profile, and that worked.
I haven’t done this with Nvidia hardware, but it sounds like
nvidia-smican do this:https://forum.level1techs.com/t/how-to-set-nvidia-gpu-power-limit-nvidia-smi/131467
Then to query your power limit:
sudo nvidia-smi -q -d POWERAnd to set it
sudo nvidia-smi -pl (base power limit+11)Might try restricting the power usage and see if your crashing stops.
EDIT: Might also try turning down in-game graphical settings. That’d decrease load and maybe also avoid any potential overheating issues, though it’d be a less-reliable option than the above, as you probably don’t want to make your system freeze just by running some program that happens to throw a lot of load at your card. That also might avoid any issues that the drivers could have that the game is tickling. Worth a shot, at least from an experimentation standpoint, if you are looking for things to try.
EDIT2: If those do successfully address your problem and it looks like it’s an overheating problem, you might also try figuring out whether you can improve the cooling situation on the hardware side, rather than sacrificing performance for stability.
Okay I’ll give this a shot first to determine if it’s overheating. The air from the case doesn’t feel like it’s too hot coming out, and the game seems to run smoothly with no graphical disturbances until the moment of freezing or crashing, but I’m willing to try it out. I’ll be going through these suggestions one by one hopefully tonight and tomorrow and will try to reply/update as I do so!
An easy option to limit the GPU power on Nvidia cards is GreenWithEnvy.
Not sure what else it could be… For me it’s running fine on an RTX 3080 on Mint with the 570 driver… ProtonDB also doesn’t seem to have any relevant reports for the RTX 40 series…
Did you do anything special during setup? I couldn’t find many reports specific to this card on ProtonDB, but lots of people were using different Proton versions that weren’t available on Steam so wasn’t sure if that was it.
Did you do anything special during setup? I couldn’t find many reports specific to this card on ProtonDB, but lots of people were using different Proton versions that weren’t available on Steam so wasn’t sure if that was it.
For me, it defaulted to Proton Experimental. It worked fine so I haven’t changed it. But I can test 9.0 later. At some point I added “–launcher-skip” to skip the launcher, but it was also stable before that.
I’m running the flatpak version of Steam. Maybe you could try switching between the native and flatpak versions of Stream?
I’m also using the default Mint 6.8 kernel. Assuming that you are using the same, you could try switching to the newer HWE kernel.
Honestly, those two already kind-of feel like grasping at straws, but this one is even weirder (I’m only posting it because we both have AMD B650 mainboards): When I first switched to Linux, I noticed that I had a lot more weird crashes than on Windows. Eventually, I got a sufficiently specific error message (dxgi_error_device_reset I think) that led me to a workaround: After I switched the GPU PCIe Gen Mode to Gen4 in the BIOS the crashes were gone. I think the same issue occured on Windows too, but it somehow manages to recover from it. I would be surprised if you have the same issue, but I guess it doesn’t hurt trying.
I also added the launcher skip command in Steam, and have been running with Proton Experimental (though I have tried many other versions). I am running the version of Steam installed via Mint’s Software Manager, not sure what flatpak is or what it would change.
I also am currently running the following kernel: 6.8.0-58-generic (per the Update Manager).
Have you tried GE-Proton? Probably won’t work but might be worth a shot.
A different game, but I recently read about someone having to go all the way back to Proton 3.something to get it to work (forget which game), so maybe try that if you haven’t?
I have almost the exact setup you have, except the RAM and I’m using heroic launcher. I have no issues with CP. My go to with game issues is to monitor the components in game. Install mangohud, configure the OSD to show CPU temps, gpu temps, clocks and also usage. That will help narrow down if the issue is hardware or software.
Please in the future, add a number after the initials.
Would hate for that to be quoted out of context lol
Just the full sentence. With his UN attributed.
Okay I’ll install that to try to get some monitoring in-game. Do you know if that’s available directly through Mint’s Software Manager?
Yes it is. And you can look up a video on how to install it too. There isn’t a GUI, just a text editor. And you set launch parameters for it to show up in steam. Or lutris has the option for it in settings.
Alright I got it installed. This was attempt 2, (Step 1 in another comment basically with no changes to get a baseline).
I installed mangohud and configured to show GPU load, CPU load, VRAM, RAM, GPU temp, and CPU temp. I booted the game again, and this time from pressing Continue and loading into the game, I didn’t even have time to start the timer. I would guess maybe 2s before freezing. Onscreen stats from MangoHUD read “GPU 98%, 53C, CPU 64% 71C, VRAM 7.9GiB, RAM 9.0GiB”.
CPU and GPU both shot way up from the baseline configuration example in GOverlay I used. Looks like this may be the issue. I’ll try to get the temps down and retry.
What kind of an error do you get when the game crashes if you start steam from the terminal?
Okay just tried it again to get a better test. To troubleshoot, I’m starting with nothing and will hopefully only change/monitor 1 thing at a time.
Just booting the PC, opening Steam via Terminal, and playing the game using Proton Experimental selected, it ran for 2m 9s before freezing (my save is right before talking to Padre after leaving the bar for the opening sequence, game freezes during the car ride before I have a chance to save again. I have been able to get past this before, at least enough to make a save on the other side, but this length of time may serve as a good reference for someone.)
Steam has a popup window that reads “steam_app_1091500 is not responding; You may choose to wait a short while for it to continue or force the app to quit entirely.” After about 5 minutes nothing changes, but I can’t even access that popup because it is frozen. I have to CTRL+ALT+Tab to Steam to then click “Stop” there. Here is what the Terminal reads from opening until game force closing:
"[2025-05-01 11:40:55] Nothing to do pid 7527 != 7526, skipping destruction (fork without exec?) Game Recording - game stopped [gameid=1091500] Removing process 7725 for gameID 1091500 Removing process 7707 for gameID 1091500 Removing process 7688 for gameID 1091500 Removing process 7660 for gameID 1091500 Removing process 7639 for gameID 1091500 Removing process 7583 for gameID 1091500 Removing process 7557 for gameID 1091500 Removing process 7544 for gameID 1091500 Removing process 7534 for gameID 1091500 Removing process 7531 for gameID 1091500 Removing process 7529 for gameID 1091500 Removing process 7526 for gameID 1091500 Removing process 7525 for gameID 1091500 Removing process 7524 for gameID 1091500 Removing process 7520 for gameID 1091500 Removing process 7324 for gameID 1091500 Removing process 7323 for gameID 1091500 Removing process 7322 for gameID 1091500 Removing process 7321 for gameID 1091500 Fossilize INFO: Setting autogroup scheduling.
(process:8216): GLib-GObject-CRITICAL **: 11:52:01.198: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed reaping pid: 8216 – gameoverlayui"
I haven’t been starting steam directly from the terminal but will try this when troubleshooting to read the logs!
The freezes and crashes could be caused by your nvidia card, I had the same issue before switching to amd
This whole PC is brand new (built earlier this year), so I don’t want to have to replace a component so soon. Especially since it seems to work fine prior to swapping to Mint in general.
Try downclocking the ddr5 memory. If running at 6000 test it at 5600.
This right here, AM4 motherboards are fucking annoying as shit.
Do you mean AM5?
If so I’ve had (am having) issues with it too… It’s mostly fine, but the one thing I CANNOT figure out is sleep/hibernate… As soon as it enters sleep or hibernates, it immediately turns back on. And I can’t find the related settings in my BIOS that are mentioned online. That’s what I get for buying revision 1.0 gigabyte I guess…
I have revision 1.3 b650m gigabyte board, same issue. With an old bios it works properly. Lots of different solutions in reddit, but none work. I can’t even test it anymore because this piece of shit board won’t recognize the bios file anymore… Booting up is also VERY slow, sometimes takes 10+ minutes to post. Fans spin at full speed and nothing happens until it suddenly wakes up.
As soon as I have the money, I’ll buy a new MSI board and never touch anything gigabyte with a 10ft pole
Hmm for me everything is fine, incl. boot times, only the sleep/hibernate function doesn’t work… Good luck figuring out your other problems 😅
Ive had that issue on Kubuntu. In the end it was one of my USB devices (specifically my controller) that was responsible for turning my PC back on. No idea why, but unplugging it stopped the entire phenomenon. Maybe check if one of your USB devices is doing the same thing?
Not the issue in this case, I disabled all forms of wake on USB from both a BIOS/UEFI level and Linux. There were problems with Ryzen 7000 but that should have been fixed with driver updates supposedly… But maybe gigabyte is just that shite lol. At least the board wasn’t too expensive when I bought it where I live
Yes, yes, yes.
As soon as it enters sleep or hibernates, it immediately turns back on.
I don’t know about sleep, but for hibernation, do you have enough swap space to store a copy of your physical memory? If you don’t, that’s the behavior I’ve seen; there’ll be some system log message, can’t remember if kernel or userspace, about not having enough space to hibernate.
Easy way to test if you think that might be it is to add a page file (rather than page partition, so you don’t have to repartition) to your swap space, activate it with
swapon, and then try re-running a hibernation.I do have swap space that is larger than my physical memory.
