Linux - Recurring "Verify Integrity of Game Files" Crash

[Motives]

For the past few months, I've been getting a recurrent crash message instructing me to verify the integrity of my game files. Typically post-crash, Deadlock will perform a small update (presumably replacing whatever file was bad), and function perfectly fine afterwards- although occasionally I'll have to repeat this process once or twice. Today specifically it happened about 4 times in a row. This typically happens immediately after finding a match, or after the intro cut scene before the menu appears, but I've had it happen throughout the course of matches before as well. I haven't noticed any specific crash triggers when it happens in a match.

Here's the pop-up that appears.
System specs if it helps:
Linux Mint 22
Ryzen 7 5800X3D
Geforce RTX 4070
16gb DDR4 RAM

I haven't been able to find any useful crash logs and haven't been able to do too much troubleshooting as a result, but I have:
- Uninstalled and reinstalled the game with no luck.
- Attempting to verify integrity of game files prior to launching will still cause the crash on occasion.
- Checked my hard drive for bad sectors, there's no evidence that the drive is dying from what I can tell

 

[markivanov0138]

Just install Windows and no problem, what's your problem bruh

 

[Motives]

Just install Windows and no problem, what's your problem bruh

I wouldn't be shocked if it's a Linux thing. I swapped to Linux a few months ago and don't recall having the problem on Windows.

 

[f1delity666]

No idea, if hard drive/ssd is okay.

But do you have a spare hard drive somewhere to put Deadlock on?

 

[van17ino6]

I wouldn't be shocked if it's a Linux thing. I swapped to Linux a few months ago and don't recall having the problem on Windows.

Just to add my personal experience:

Windows 10 - Ryzen 9, RTX 4070, 32GB
>Started having bad net jitter and visual rubberbanding at late 2024. Only in Deadlock, I wasn't having the same issues with any other game.
>Tried everything, including changing ISP and even upgraded speed. Configs in Deadlock, cable and wifi, different house, almost everything. Nothing changed (same PC though).

Nobara Linux KDE - Ryzen 9, RTX 4070, 32GB
>I swapped to Linux the other day just to test and to my surprise I'm having +20fps average and my constant netjitter DISAPPEARED (or at least the game now predicts perfectly and has stopped rubberbanding)

Windows 10 - Ryzen 9, RTX 4070, 32GB
>Swapped back to Windows in the same clean NVMe hard drive, to test if it was because of the clean hard drive
>The net jitter is back and exactly the same as before and my fps keep dropping frequently, as well as the extreme rubberbanding every 3 minutes

So I again swapped back to Linux and I'm staying just to play Deadlock because finally it's playable again for me.
I think it's something with my hardware combination + some Deadlock config. But I don't even know at this point.

Good luck with the fix, maybe address it in a private forum
BTW did it start in a game update or something else you can think?

 

[Playeroth]

i read that you can ask someone to give the same pak to you so you swap with their non-broken one. It should fix

 

[Motives]

i read that you can ask someone to give the same pak to you so you swap with their non-broken one. It should fix

After this post, I did some digging and found /steam/root/logs/content_log.txt and could see which files are corrupt. It seems to be a different file (or files) every time. The last crash I had was for game\citadel\pak_01_083 and 092. Before that was the map street_test. In each case the logs say there was a "write gap". So unless I swap every .vpk file.
Interestingly, I dont seem to have ever had the same pak01_xxx file go bad on me (at least, not yet), but I have had the same map files go bad on me a few different times.

Good luck with the fix, maybe address it in a private forum
BTW did it start in a game update or something else you can think?

I want to say it started shortly after the christmas update? But that was also around the time I moved everything over to Linux in the first place, so I can't say if the correlation is between the update or the OS change.

No idea, if hard drive/ssd is okay.

But do you have a spare hard drive somewhere to put Deadlock on?

I do! Somehow this didn't occur to me lol, I'll give it a shot.

 

[Deleted member 145742]

That's not normal, I'd check your disk before anything. Check you have enough disk space and that your disk is healthy. If those are both fine, try disabling the write cache on your disk for the duration of the download.

 

[f1delity666]

Any new knowledge or did you even solve your problem?

 

[Motives]

Any new knowledge or did you even solve your problem?

I took your suggestion and swapped to a new hard drive 2 days ago. I've played maybe 4-5 matches on it and no issues so far. The OG drive was a WD SN770 nvme drive, the "new" drive it's on is a Samsung 980 PRO nvme ssd. Still want to give it some time before I say it's officially solved (and no clue what the issue with the first hard drive was), but things are looking good!

edit: some additional info if it's relevant to anyone:
- both file systems are ext4 (because linux)
- Crashes were occurring on the hard drive Linux boots from
- I have to manually mount the new drive to Steam every time I restart Steam / PC (this seems to be a known thing for debian based steam, doesn't really bother me too much)
- Since the content.log file was calling out "write gaps", it might be relevant to note that the 980 PRO SSD I switched to has very slightly faster write speed, and considerably faster read speed than the old hard drive.

 

[back_biter+deadlock]

For the past few months, I've been getting a recurrent crash message instructing me to verify the integrity of my game files. Typically post-crash, Deadlock will perform a small update (presumably replacing whatever file was bad), and function perfectly fine afterwards- although occasionally I'll have to repeat this process once or twice. Today specifically it happened about 4 times in a row. This typically happens immediately after finding a match, or after the intro cut scene before the menu appears, but I've had it happen throughout the course of matches before as well. I haven't noticed any specific crash triggers when it happens in a match.
View attachment 46535
Here's the pop-up that appears.
System specs if it helps:
Linux Mint 22
Ryzen 7 5800X3D
Geforce RTX 4070
16gb DDR4 RAM

I haven't been able to find any useful crash logs and haven't been able to do too much troubleshooting as a result, but I have:
- Uninstalled and reinstalled the game with no luck.
- Attempting to verify integrity of game files prior to launching will still cause the crash on occasion.
- Checked my hard drive for bad sectors, there's no evidence that the drive is dying from what I can tell

I play on Linux with a comparable system,

Operating System: Arch Linux
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Kernel Version: 6.15.2-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 5900XT 16-Core Processor
Memory: 125.7 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XTX

Essentially no issues, however processing vulkan shaders happens each time, and I skip it, and it gives me a few instances of minor stutter a couple times after each launch of the game, and then it's basically without any issues.

 

[sannnagy]

Check your RAM. I was constantly getting corrupted files when my RAM was dying