(Please Help!) Been randomly hard crashing for 3 patches now.

[Omarlition]

Hello to anyone who is reading this post,

So, I don't know why this has been happening or what is the result of this but this has been starting since around....maybe with the first time the map got a rework? Possibly but I would be playing Deadlock as of normal, nothing wrong and then all the sudden....

BOOM

I would randomly crash and have to sit restart my entire game and reconnect, resulting myself on having to explain my teammates why all of the sudden I've died in the first damn minute of the game....many times.

_________________________________________________________________________________________________________________________________________

Now, what is possibly causing me to crash? Funniest thing too is that I've recently went through an ENTIRE pc swap, switching my motherboard, cpu, ram, gpu and etc. Just before the upgrade, I was STILL experiencing those crashes, there was no lag, no hints of me crashing, it just HARD CRASHES. There's legit no logs as well that explains what is the problem.

I've recently seen another post just earlier today that explains the same situation as well but the ONLY attempt of a fix is putting "-threads X" so I will be checking this out and see if this is the possible fix, the other is that Windows could be the issue too considering that I ALSO CRASH in other source 2 games as well, noticing this in CS2.

_________________________________________________________________________________________________________________________________________

I will appreciate it and actually come together and see if we can finally come down to the crack of this problem because other people are also experiencing this problem, my PC specs will be posted below this, thank you and good luck.

PC SPECS
- AMD Ryzen 7 7800X3D
- RAM 32 GB DDR5
- ASUSTeK COMPUTER INC. TUF GAMING B650E-E WIFI (AM5)
- NVIDIA GeForce RTX 4070 Ti SUPER
- Samsung SSD 990 PRO 2TB (SSD)
- Windows 11 Home ((KB5074109) (26200.7623)

 

[Omarlition]

Update : -threads did not work.

 

[HerrWinfried]

I’m experiencing the same issue. I think the problem is that updates aren’t being tested. This might sound like a biased take, but I believe the Deadlock team just like the CS2 team pushes updates without proper testing, and that this is only the beginning. In other words, I have a prejudice that every update will be like this. I hope you can fix the issue; I couldn’t solve it even with a custom config. I can’t use DLSS at all anyway.

On low settings, I get 80 FPS on Proton (on Linux), but after 5 minutes it drops to 5 FPS. Even if I try to endure it like that, the game freezes. I have to close and reopen it. I tried both Vulkan and DX11; both are the same. With Vulkan, there are even claims that there’s a memory leak, but I haven’t encountered it yet.

My laptop specs:

RTX 3050 Mobile (4 GB VRAM)
32 GB RAM
i7-11800H Mobile
1.5 TiB M.2 SSD

 

[barlakopofai]

Have you tried getting an uncorrupted pak file from someone else?

 

[Omarlition]

Have you tried getting an uncorrupted pak file from someone else?

Already verified the game and installed the game numerous amounts of times, had no mods too and it would still crash.

 

[barlakopofai]

No you need to get an uncorrupted pak from someone else, reinstalling doesn't fix it when it becomes corrupted.

 

[Omarlition]

No you need to get an uncorrupted pak from someone else, reinstalling doesn't fix it when it becomes corrupted.

Which pak would be corrupted if you don't mind me asking? And where can I get that pak?

Is that really the source of it?

 

[barlakopofai]

Unfortunately I am unsure which one it is but you can start searching for the threads that talk about the corrupted pak error, it should be easy to find since it's a common error. It's as simple as just getting it from anyone who isn't crashing all the time.

The fix I saw specifically was reinstalling, deleting the corrupted pak, then adding the uncorrupted pak and verifying game files.

 

[Omarlition]

Unfortunately I am unsure which one it is but you can start searching for the threads that talk about the corrupted pak error, it should be easy to find since it's a common error. It's as simple as just getting it from anyone who isn't crashing all the time.

Will try that out ASAP, will let you know.