Halloween Update Crashes

Emo_Guy_345

New member
Ever since the recent Halloween update, my game has been completely unplayable. Every time I try to play a match I get a pop-up error claiming that there's a missing shader, and that I need to verify the integrity of my game files; then the game crashes. The missing file in question has either been

e:\steamlibrary\steamapps\common\deadlock\game\citadel\pak01.vpk

or

e:\steamlibrary\steamapps\common\deadlock\game\citadel\maps [then from here I unfortunately cannot remember the exact file]

It's worth mentioning that this issue persisted for me prior to the update, but has only gotten exponentially worse since the update. I do not have any mods be it UI or skin/cosmetic of any sort. Nor is there a pak01.vpk file anywhere within my files like it claims to be causing the error.

Things I've done:
- Restarted Deadlock (no change)
- Restarted Steam (no change)
- Restarted pc (no change)
- Shutdown pc (no change)
- Verified Integrity of Game files (no change, as it claims all files successfully validated)
- Uninstalled and Reinstalled the game (no change)
- Steam Settings -> Downloads -> Allow Downloads During Gameplay [changed to OFF] -> Clear Download Cache (no change)

Pre-Halloween update: each new day I would want to play Deadlock I would restart the pc, verify file integrity prior to launching the game, wait in the hideout until all shaders are loaded, start a bots match and let it run for about 10 minutes to see if it gives the pak01.vpk error. If yes, then the game crashes, and I re-verify, then get into a bots match again until it successfully doesn't crash, THEN can finally queue pvp without worrying about penalized crashes.

Post-Halloween update: Today I went through my same systematic steps I always, miserably, have to go through to ensure the game doesn't implode. And bots matches would go through just fine. I ran both partial and full-length games to ensure I wouldnt get the pak01.vpk issue; however now when I queue for a pvp game it either gives that error or the missing map shader error on initiating the queue search. This has now happened so many times this morning that I cannot queue anymore, as I am now placed under a queue ban until 16:19

Will update later when removed from queue ban to see if I can get the specific file name for the missing shader.
 
View attachment 65302
Ever since the Early October Patch, and especially after the Halloween October Patch, this specific crash has been increasing in frequency at an alarming rate. I've been playing the game again a lot since the recent Hero Update, and I have had no problems with crashing up until this October. The only game performance problem I've had up to this point is a gradually degrading optimization and framerate during extended play sessions. That problem can be fixed with a quick restart.

Anyway, this corrupt file is quite peculiar. It happened once, maybe two weeks ago, and was quickly resolved with a single game restart. Now, when the Halloween update hit, I encountered this same file corruption again pretty quickly. Still, I was able to restart the game quickly and reconnect after that. Then, day after another extended Deadlock session, I encountered this crash again, except this time I couldn't just validate my game files and restart. View attachment 65303
No, this time, the game refused to open and got stuck in an infinite loop trying to verify the integrity of Files. (This occurred both when I tried to launch the game and when it automatically tried to validate the game, and also when I manually instigated the integrity check through the properties of the game.) I had to restart my game, and luckily, a friend managed to pause it long enough for a full restart.

This has now escalated to happening multiple times a session. No quick game restart fixes this. I had this crash three times in the past 2 days, all of which have prompted me to get queue-banned for abandoning the game. All of these crashes happened in-game and at some point, but this latest crash (10/30) occured just as I loaded in and the game was starting. In addition, a full computer restart didn't even allow me to verify the files again. I basically get to play less of the game each time this crash happens.

Although it's rather unfortunate that I have leaver penalties because of this, I am much more concerned about the fact that this is still happening to others on this thread as well. I want to be able to play the game, but the way this is trending, I cannot in good faith start another match, even with my friends clamoring to play, because I will most likely ruin the game and incur an ever-increasing penalty. (Is there a way to detect whether or not a player leaves a game due to this issue?)

I will reinstall the game and see if that fixed anything at all, but I've seen others post about this problem on the thread, and the majority of them have stated that a fresh install does not fix the issue. Will try to update in the replies.

Anyways, please fix this ASAP! If you need any more details or the match ID, please let me know. I wish I could give you the match ID's of the games I left right now, but my game is stuck infinitely validating ¯\_(ツ)_/¯
Hi, I'm trying to collect a lot of people with the same problem on the same thread. Could you run a DXDiag if you are running Windows, or just post your specs? It may be a hardware component issue we have between us
 
Last edited:
I am having the same issue though sometimes the crash does not report the error. I have gone through all of the same solutions stated above, as well as:

- Rendered the game in Vulkan
- Bought 4 new sticks of RAM (this sounds over the top, but I only had 16GB of RAM before and I double bought on amazon on accident)
- Wiped my main drive (the one Deadlock was installed on) and reinstalled Windows
- Turned off XPM in the BIOS and lowered the frequency of my *brand new* sticks of RAM
- Playing without audio by clicking the in game mute button next to settings in the esc menu. (I had hoped this would cause audio files to not load. I am unsure if that was the case.)

Whether or not I get the pak01.vpk error message, the .dmp file reports "Access violation - code c0000005" and it states I have not gone over my now 64GB of RAM nor my 8GB of VRAM.

1761867853108.png

Dxdiag reports no issues. Chkdsk reports no issues. I have a my GPU is a 3060. I was perfectly capable of running the game with no crashes until the new hero update, where I would crash once per game. Now I'm crashing 10 times per pvp match and the experience isn't fun for anybody.

When I wiped my drive, I did not wipe Steam cloud data for the game so my hotkeys and such were maintained.

The attached .dmp file is the latest and is from a bot match, because I even crash in those now.
 

Attachments

Hi, I'm trying to collect a lot of people with the same problem on the same thread. Could you run a DXDiag if you are running Windows, or just post your specs? It may be a hardware component issue we have between us
Sorry for the late response, had a lot going on and havent had time to play. Tried again today and still crashing in my bots matches so I'm not even going to attempt pvp. Here's a dxdiag report of specs. I've tried running the game in both dx11 and Vulkan and have the same issues with either rendering option. The issues started with the new heros added into the game, but have grown far worse with the Halloween update
 

Attachments

  • dxdiag_11_2.png
    dxdiag_11_2.png
    28.2 KB · Views: 1
Sorry for the late response, had a lot going on and havent had time to play. Tried again today and still crashing in my bots matches so I'm not even going to attempt pvp. Here's a dxdiag report of specs. I've tried running the game in both dx11 and Vulkan and have the same issues with either rendering option. The issues started with the new heros added into the game, but have grown far worse with the Halloween update
What kind of GPU do you have?
 
Back
Top