Game crashed a few seconds after starting with the error about needing to verify integrity of files

[gamadar]

Started a game earlier(match id 30691244) and it crashed with this error a few seconds after the round started (was on the line heading into lane).

Also, I was unable to verify the integrity of the game afterwards in Steam so I had to uninstall and reinstall to get the game to open up again.

 

[gamadar]

And it looks the game banned me from playing for a little bit.

 

[purplegoopguy]

Exact same thing happened to me - was playing the match, got into lane, about 500 souls in, then crashed, verifying told me "all files verified successfully", try to reconnect, have the error repeat like 4 times, crashing in main menu with the verify error, now I gotta eat the 6h matchmaking ban (Similar issue already got me the 2h ban)

 

[purplegoopguy]

After randomly applying fixes, my new go to is to play a full priv bot match before going into a normal match. If I crash, it doesn't cause any abandon penalties. NOT the co-op bot queue, specifically a solo private bot match.

 

[gamadar]

This just happened again now, but a few minutes into the game. I'm being forced to uninstall/reinstall as attempting to verify the files via steam just gets stuck. Odds are by the time I get back into the game it'll punish me as a leaver. I don't mind the crashes as this is a playtest, but it's frustrating to be *punished* when the game crashes versus people who legitimately leave.

 

[gamadar]

Great, now I've been banned for 6 hours.

 

[gamadar]

Sigh, this just happened again and i'm re-installing. Expecting to see a ban again, sigh.

For reference, this happened as soon waiting area ended and we started the game.

 

[purplegoopguy]

I was having it happen a couple minutes into lane as well, I'd check the file browser for the recently deleted files. Then just delete those since verification will keep looping (I've had this issue for a few other games). Another thing to do is what I recommended earlier, play a private bot match to see if your game runs fine, you can quit halfway through once it's clear things are fine.

 

[gamadar]

Thanks! Yea I’ve been just doing a private bot match before I start and running around the map a little bit before quitting and queueing into a normal round.

 

[duydbui]

I keep getting this error and keeps causing me to get matchmaking bans. Very frustrating. This never happens to me during loading, usually well into the game 10 minutes+ takes several restarts to even start verifying game files and it takes forever to do so once it's able to.

 

[Billy3Toes]

Started a game earlier(match id 30691244) and it crashed with this error a few seconds after the round started (was on the line heading into lane).

Also, I was unable to verify the integrity of the game afterwards in Steam so I had to uninstall and reinstall to get the game to open up again.

bro i had the same issue yesterday, did the full uninstall/reinstall after trying to verify files. got back in game but everyone had already given up and left (i don't blame them, it took about 10 minutes to get everything fixed up again. After that game i was able to play about 5 more but with some frame rate clipping going on.

Cut to today, first game, immediate crash on getting into combat. this time it was a full closing of steam and relaunch that fixed it. but still was about a 5 minute fix and folks all left the game again. Just finished up a great game, to try and queue up again to a 5ish hour ban. Just hurts that we seem to be getting punished for "afk" but its not truly an afk ya know.

 

[gamadar]

bro i had the same issue yesterday, did the full uninstall/reinstall after trying to verify files. got back in game but everyone had already given up and left (i don't blame them, it took about 10 minutes to get everything fixed up again. After that game i was able to play about 5 more but with some frame rate clipping going on.

Cut to today, first game, immediate crash on getting into combat. this time it was a full closing of steam and relaunch that fixed it. but still was about a 5 minute fix and folks all left the game again. Just finished up a great game, to try and queue up again to a 5ish hour ban. Just hurts that we seem to be getting punished for "afk" but its not truly an afk ya know.

Sorry to hear this . Two ideas to potentially help here: 1) disable steam shader cache and 2) verify files before starting and then do a quick bot round where you run around the map.

 

[gamadar]

I keep getting this error and keeps causing me to get matchmaking bans. Very frustrating. This never happens to me during loading, usually well into the game 10 minutes+ takes several restarts to even start verifying game files and it takes forever to do so once it's able to.

Out of curiosity, if you follow the details here(https://forums.playdeadlock.com/thr...-a-specific-file-pak01-vpk.52262/#post-101426) in how to look up your logs, do you see the game updating the day of the crash? You can find this at `"%Steam Root%\logs\content_log.txt"`.

If so, can you try 1) disabling the steam cache if it's not already disabled, 2) verifying the files before starting a game and 3) doing a bot round where you basically run around the map for a few minutes before starting a game?

 

[Billy3Toes]

well did all the above, got the bug again. now its a 24 hour ban with 4 wins required in low priority matchmaking. think its a sign to stop playing the cookie dough game and wait for it to be a proper cookie before biting back in. Soul Crushing to be honest as I love this game. nothing else scratches the same itch at the moment. With no ability to appeal bans n such either, wtf are ya to do.

 

[duydbui]

Still getting this bug and now I'm banned for 12 hours