Issue Description:
Randomly when I start a matchup, I get greeted with “Oodle detected corruption in compressed segment, Make sure that your game files are not corrupt by in steam.” error.
This happens at least once a day at random occasion, and goes away, then randomly comes back.
And no, I don’t have a defective RAM (tested via various testing tools such as memtest, etc), and Steam’s file verification found no errors within the files. Only game that’s been crashing had been Darktide.
Error Displayed (If Applicable):
Oodle detected corruption in compressed segment, Make sure that your game files are not corrupt by in steam."
[19f0ad72]
Steps to Reproduce:
Launch a match finder
Match is found
Game crashes
Game will crash again if I try to reconnect. Mourning Star lobby is loading OK
Mission Name (If Applicable):
Platform:
[Steam/Microsoft Store]
Steam
Player ID:
76561197986587780
Approx. Time of Issue & Timezone:
approximate time of issue - random
timezone -EST/EDT
Reproduction Rate:
Once - Rare (<10%) - Unusual (<25%) - Common (<50%) - Often (<75%) - Constant (100%)
at least once every day while playing.
Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]
Are there any remaining solutions on that list you haven’t tried? They are the only known solutions we have for these particular corruption errors unfortunately - any time a new solution is uncovered, we add it to the list.
I understand this is disappointing if you’ve exhausted everything already. I can assist with a refund alternatively.
Apologies for late reply. There really haven’t been any solutions to this but to keep trying and get in a match somehow.
Crash isn’t midgame. it’s always immediately after game lobby of 4men party is formed, and when screen goes black, which is right before the loading screen (Valkyrie scene).
The oodle crashes started appearing for me right when the class rework patch was released and seem to have increased in frequency since the 1 year anniversary patch. Leaving a match is usually a given to trigger a crash.
I do not recall having this issue before the class rework patch and crashes were very rare.
I have a i9-13900KF cpu and per the recommendation I have now lowered the performance core speed to 53 with Intel XTU. I have not had time to play test enough yet so not sure yet if this fixes it for me.