Wrongfully Banned due to Pak01.vpk Corruption Bug

[flyy]

I'm having to create tons of alt accounts because your stupid banning system. Deadlock keeps crashing after a Pak01.vpk corruption error. It takes me forever to get back into game. And sometimes I am able to get in and still win the match, yet I still get banned. This error has been happening to tons of players and zero of the complaints have had any response from the team. I will be officially uninstalling the game as well as actively telling users to avoid this garbage.

I wouldn't be this petty, but it seems to me that the team prioritizes character updates and in-game fixes over MAJOR FLAWS THAT MAKE THE GAME UNPLAYABLE / UNFAIRLY PUNISHING PLAYERS.

Good luck to all the players who decide to suffer through this crap. Probably will be another game that stays in alpha / beta for 5+ years.

 

[.divined]

This will happen if your computer overheats or something like that, restarting your PC and launching deadlock exe directly from the Steam folder is the fastest way to fix it.

 

[An Unoriginal Name]

Set your computer BIOS/UEFI back to defaults according to your manufacturer's documentation and don't use any applications which apply an overclock from within the operating system.

 

[flyy]

Set your computer BIOS/UEFI back to defaults according to your manufacturer's documentation and don't use any applications which apply an overclock from within the operating system.

To be fair, I shouldn't have to alter my PC (which isn't overclocked nor operating at any of its limits) nor limit its capabilities simply because of what seems to be an issue with steam / Deadlock. I was able to find a thread with someone who is perform troubleshooting on their own for this bug. Here is a link to their post for reference: https://forums.playdeadlock.com/threads/pak01-vpk-corruption-workaround.67321/

 

[An Unoriginal Name]

You're right, nobody should have to alter anything, but if it's not functional at default settings and reducing capability alleviates the problem, this would seem to indicate the issue lies elsewhere.

I've seen that thread before but it doesn't really add up and just sounds like a lot of struggling around addressing the true cause of the problem. I can guarantee we would have a lot higher volume of reports if what they described was accurate.

I've expanded upon this in a different post in hopes that someone may find it useful.

A

Post in thread 'Game Crashed, got a temp ban as a result...'

Yesterday at 5:07 PM

I recall the OP responded to a post of mine from a while back with regard to disabling XMP having resolved this issue for them. Here's what I would recommend in no particular order to everyone else:

• Set your computer BIOS/UEFI back to defaults according to your manufacturer's documentation and don't use any applications which apply an overclock from within the operating system.
• Reduce the frequency of your RAM until it doesn't crash irrespective of XMP (or EXPO) being disabled.
• Test your RAM with a bootable drive, not within Windows. https://www.memtest.org/
• Consider...

• An Unoriginal Name