Corrupted file citadel\pak01.vpk- happens too often and now getting banned for leaving

If anyone is using AMD graphics cards, I have moved to the "professional" driver instead of the regular one, which is traditionally more stable. Since this I haven't had a crash.
 
Sadly it happened again... and after a reboot it just sits at 0% downloading even though there was no update
If this happens again (being stuck at 0% after the corrupt pak01.vpk), could you try signing out and signing into your steam account? When I was trying to investigate(link) my own issues the other day, I noticed something interesting in the logs from after I saw the logs about the game being corrupt:

[2024-12-22 17:51:10] Start validating appID 1422450
[2024-12-22 17:51:10] AppID 1422450 scheduler update : Priority First, not played for 121 seconds, update disabled for 137 seconds
[2024-12-22 17:51:10] AppID 1422450 scheduler update : updates disabled by app; blocking attempt Priority First

It seemed to me like Deadlock was actively blocking the updater/verification from running for some reason and I wonder if signing out/signing in again quickly would reset whatever state Deadlock thinks it is in. I'd verify it myself but I haven't encountered the issue since I came up with the potential workaround to the verifying state being stuck.
 
Last edited:
Also getting this error:

System:
32GB DDR5
AMD 7900xt
AMD Ryzen 7 7800x3d


I think also my 4th time encountering the issue, and also issued a 24hr time-out :(
 
I ran the OS's memory diagnostic

From the event logs:
The Windows Memory Diagnostic tested the computer's memory and detected no errors
 
Problem: Game crashes randomly(mostly after you die as every screenshot i found in the forum is from dead players) and indicates a file gets corrupted mostly "...\game\citadel\pak01.vpk"
Sure no problem lets just try to repair game or relaunch:

View attachment 14650

Steam does not respond after you try to relaunch game even after 5 mins, at this point i force close the process with task manager and reopen steam and try to repair which then takes alot of time, in some cases i resorted to deleting the file and it is faster to reaquire it then having to scan and repair, this however has not fixed anything and the game crashes constantly.

-Due to all posts saying it was due to ram or actual hardrive/storage solutions being faulty i made sure to run multiple stress tests this morning, everything ran smoothly and no crashes ever, checked crystal mark just in case all 3 of the ssds i used worked fine and are not damaged whatsoever, game crashed after third game and got banned for an hour


Research indicates this has been happening for months atleast since end of June:

-https://www.reddit.com/r/DeadlockTheGame/comments/1exzuwx/corrupted_file_citadelpak01vpk_crashes_game/
-https://forums.playdeadlock.com/threads/content-file-f-game-citadel-pak01-vpk-is-corrupt.11389/
-https://forums.playdeadlock.com/threads/mid-game-crash-corrupted-file.12488/
-https://forums.playdeadlock.com/threads/pak01-vpk-corrupt-file.18676/
-https://forums.playdeadlock.com/threads/client-crashes-vpk-corrupted.18919/
-https://forums.playdeadlock.com/threads/content-file-f-game-citadel-pak01-vpk-is-corrupt.11389/
and on discord people ask for help with no real solutions confirmed:
View attachment 14646
Solutions attempted as found in other posts:


-Repair game Via Steam r/ Obviously first thing that was done
- Reinstall game r/ Second solution attempted
-Moved game to a different drive /r Nothing changed game still randomly corrupts
- Lower your ram speed r/ Disabled XMP and have ram at default speed 2667MHz hence not related to ram speed
-Disable any overclocks r/ Did that too(went as far as diabling the autoclock manager in bios) did not help, and game now runs like shit because virtually any new cpu has auto overclocking
-Changed Render API- r/ Crashes in both DX 11 and Vulkan regardless of the render API
-No undervolting or any funny buiseness going on with gpu /r found a post saying this could affect it(pure nonsense as you cant corrupt a file from this but w/e)
PC specs:

View attachment 14657


The reddit post has an intel i7 so am taking cpu incompatibility out all toguether, same for gpu as others have had this issue with other graphics cards, and Ram frequency seems to vary on all the different posts mine being the lowest and still experiencing the issue

Because it takes atleast 5 minutes to even repair the game as steam takes a massive dump i have started to get banned for "leaving the game" so am here requesting help


i feel your pain man. i had this happening upon booting up a match. now it simply does it on launch of the game. im not savvy enough to offer solutions but human enough to offer my sympathy. hope the devs can come up with a solution to this problem. ive 3 more 'Low Prio' games to trudge through because of this issue. ima ask the folks if they are in for the same issue. id bet its likely as the first game of LP i played was less than a minute queue time. kinda sus for what is supposed to be the bottom of the barrel for queues. i know with LoL that LP queues are actually 6-7 minutes or more. (i know this because ive played league for well over 10 years now. soo there have been a few overwhelming rage moments.) ive not felt the need or want to rage out of a deadlock game. you can always come back and roaming is super effective in this game.
 
I believe the bug still happens -- however I have found a workaround to not encounter it for the last 2 weeks (good enough for me).

1. Turn off Automatic updates for deadlock -- The last time I noticed it happened was when an update hit while I was playing, and I had high priority automatic updates on
2. Verify Integrity of game files before every launch of deadlock
3. Load into a private bot match and play a little bit of the laning phase to load most of the textures and whatever else
 
Is this bug still happening?
I have not ran into this since I replaced my ram Jan 10th (https://forums.playdeadlock.com/threads/game-crashes-leading-to-6-hour-bans.52379/page-2)

That being said, as with @goodknightdk and @gamadar I am verifying before every launch.

After an update I will ensure all other games are up to date and quit steam to see if there is a steam update as well, then before launching I will verify the files again.

The only thing I dont do is the bot round first, because when it happened it would happen so randomly, not right away.
 
Back
Top