Corrupt Files + Steam Refusing to Verify

[Treebeard]

I had this issue a long while back, and it had disappeared for some time. Unfortunately it seems to have returned.

The game will have a stuttering issue after being open for some time, and upon resetting and starting the game it will say the a file has corrupted and I need to verify my files. I don't remember the full string, but most often contains "map/citaldel1". However, when I go to verify the files, Steam refuses to recognize it, and the game stays locked at "Downloading: 0%". Within the past 2 weeks, this has happened on roughly 4 occasions with 3 resulting in penalties. As such, I am now in low priority queue and banned until tomorrow from playing the game. I have not intentionally ever left a match, and it really does suck to miss out on the release of today's character.

I have done everything I can on my end short of taking apart my pc and rebuilding it, which I will be doing shortly. I'd love to work with whoever I can to find what is causing this and hopefully see it fixed.

Specs: Nvidia GeForce RTX 3070, 16 GB Ram, AMD Ryzen 5700X 8-Core Processor

Match ID's in which this occurred (That I can immediately recall): 54539949, 54412813,

 

[pikokino]

My friend had this same issue. The only solution we could find was downloading the game to a different hard drive and going from there. Their main drive was C:, and their alternative one was D: (the one Deadlock was originally installed to, and was bugging out on), and after switching their game to download in C:, it worked flawlessly thereafter.

 

[Gendo]

My friend had this same issue. The only solution we could find was downloading the game to a different hard drive and going from there. Their main drive was C:, and their alternative one was D: (the one Deadlock was originally installed to, and was bugging out on), and after switching their game to download in C:, it worked flawlessly thereafter.

I tried doing this and it seemed to help for a short while, but then when Celeste was added it started again. Dunno if that was related or just happened by coincidence

 

[An Unoriginal Name]

I tried doing this and it seemed to help for a short while, but then when Celeste was added it started again. Dunno if that was related or just happened by coincidence

Unfortunately, it is just a coincidence. There are multiple things people have tried historically, including moving the install to another drive, which might reduce the perceived frequency of this specific issue occurring, but it does not remedy the actual issue.

If you specifically get a corrupt .vpk error, try reducing or disabling XMP/EXPO in your motherboard BIOS/UEFI. If that fails, try updating or resetting the BIOS/UEFI to defaults, lower RAM frequency in 500-1000 MHz steps from stock, and if problems continue to persist, test and/or replace the RAM altogether. This issue often indicates unstable RAM and occurs in other Source 2 games, even when other games or applications seem to run as expected. You can run disk integrity checks/repairs e.g. chkdsk in Windows but it is unlikely to return anything of value regarding this issue.

You can find threads in these forums where, ultimately, the solution was confirmed to be either reducing the RAM frequency so that it is stable once again, or replacing the RAM.

You can also find similar discussions on other forums dating back years:

vpk is corrupt verify integrity of game files at DuckDuckGo

DuckDuckGo. Privacy, Simplified.

duckduckgo.com

 

[Gendo]

Unfortunately, it is just a coincidence. There are multiple things people have tried historically, including moving the install to another drive, which might reduce the perceived frequency of this specific issue occurring, but it does not remedy the actual issue.

If you specifically get a corrupt .vpk error, try reducing or disabling XMP/EXPO in your motherboard BIOS/UEFI. If that fails, try updating or resetting the BIOS/UEFI to defaults, lower RAM frequency in 500-1000 MHz steps from stock, and if problems continue to persist, test and/or replace the RAM altogether. This issue often indicates unstable RAM and occurs in other Source 2 games, even when other games or applications seem to run as expected. You can run disk integrity checks/repairs e.g. chkdsk in Windows but it is unlikely to return anything of value regarding this issue.

You can find threads in these forums where, ultimately, the solution was confirmed to be either reducing the RAM frequency so that it is stable once again, or replacing the RAM.

You can also find similar discussions on other forums dating back years:

vpk is corrupt verify integrity of game files at DuckDuckGo

DuckDuckGo. Privacy, Simplified.

duckduckgo.com

I attempted the ram fix as well and it led to nothing, same unpredictable crashes. Just seems odd that this is the only game that has this issue. Even Monster Hunter Wilds even runs without crashing, and many other RAM intensive games are still running smooth with no issues.

The bigger issue to me is that Valve has a game in BETA, that has bug post about crashes, including this one, all over the forums... so why is their ban system so aggressive? I'm banned for the 4th time because the game wont let me reconnect in time because the game has to download more files each time it crashes.

This crashing did not start happening for me until the old/new gods update, game ran fine all of last year up until that update

 

[An Unoriginal Name]

The bigger issue to me is that Valve has a game in BETA, that has bug post about crashes, including this one, all over the forums... so why is their ban system so aggressive? I'm banned for the 4th time because the game wont let me reconnect in time because the game has to download more files each time it crashes.

The bans are indeed an unfortunate side effect of this issue, but I do not think there is any reasonable way of discerning a player disconnecting and eventually abandoning whether by malice or misfortune. It might seem odd to consider, and I am oversimplifying this, but it would just become another way for certain types of players to game and abuse any possible leniency the system gives them to otherwise ruin a match.

Valve has crash telemetry in place so it goes without saying that they can quickly address emergent issues that affect a wide range of configurations (updates with crash fixes will almost never get a mention in changelogs or in the Discord unless Yoshi specifically comments on them), but outside of that there is not really anything else for them to take action on. That said, these systems are not final and are subject to change at any time. I am certain these are things that they routinely think about but cannot simply change or implement on a whim without proper internal testing.

 

[Seltkirk]

hello. check my post for the latest update on this issue! Thanks.