Oodle Crash after every single mission

Issue Description:
Crashing (sometimes repeatedly) upon leaving a mission and returning to mission hub.

Crash Report (If Applicable):

GUID: bf876d11-e60f-4d54-a2db-19d07013b844
Log File:
Info Type:

Error Displayed (If Applicable):
Oodle crash - blah blah corrupt files (hint: No files are corrupt)

Steps to Reproduce:
Play a mission, return to hub.

Mission Name (If Applicable):
Any mission


Player ID:

Approx. Time of Issue & Timezone:
Any time of day. Easter Time zone.

Reproduction Rate:
Often to Constant

Upload Supporting Evidence:
[Screenshots, recordings, links to Twitch VODs, etc.]

Upload Console Log & darktide_launcher.log:
[Instructions: https://forums.fatsharkgames.com/t/how-to-provide-a-crash-report-console-log-or-darktide-launcher-log/5516] <— this link gives me a “page doesn’t exist” error. How fitting.

There will be an underlying reason for your persistent data corruption. For example, a common culprit we see is mismatched RAM speeds. Please see the article below:

I don’t have mismatched RAM speeds, and every single time I scan I don’t have data corruption.

Also, I went through the checklist above and here’s the results.

Verify integrity - I’ve done this about 10+ times so far (and that’s not hyperbole) nothing is corrupt.

Disable Mods - Vermintide 2. I know this is VT2 only, but I don’t run any mods.

Firewall\AV Exceptions - these are in place for the both the entire Steam folder and the 2 Anti Cheat folders - EasyAntiCheat and EasyAntiCheat_EOS.

Check you drives - all brand new drives (new system) and no errors on any drive.

Check your RAM - everything checks out just fine.

Check your Ram Speeds - I have 4 DIMMS all running at 3600.

Disable Overclocks - nothing is overclocked

Rescan MSI Afterburner - No MSI Overclocks

Check for Viruses - Yep, none of those. Clean system.

Disabled Background Apps - Done this and it didn’t affect crashes.

I come from an IT background and I know how annoying it is to send someone an article and then it feels like they didn’t bother to read it. :slight_smile: So just wanted you guys to know that I have followed that one.


There’s the exact error message I’m getting. Clearly it isn’t corruption.

Ok… let’s break this down. I just played a mission. Game crashed upon leaving the mission.

I immediately go into Steam and tell it to check all the files. Here’s the result.

There are no files corrupt. There are NEVER any files corrupt. Can someone please actually pay attention to this thread?

Anyone at Fatshark care about this? I’m getting a multiple crashes before and after missions. In mission I’m fine, but it’s annoying to restart over and over again.

Today I did the following:
Uninstalled the game and moved it to a new drive.
Lowered Worker Threads to 4.
Lowered Worker Threads to 1.
Set graphics to low.
Set everything I possibly could to off.

Did this make a difference? Nope. Still same “oodle compression crash”. I’ve scanned my files close to 20 times now (that’s not hyperbole, two scans today) and that’s on top of the uninstall and reinstall.

Would someone from @FatsharkJulia @Fatshark_Hedge @FatsharkCatfish @FatsharkPdr or @Fatshark_Stormcaller please look at this and respond?

I’m now crashing after each mission, and crashing starting a mission, then crashing 2-3 times trying to get back into the mission.

I’ve queried this with our Engine Developers, to see if they can share any other ideas on your issue.

Awesome. Thank you for the information. I’m trying REALLY hard to overlook these crashes, but at this point I can generally get a mission done, but there are three or more crashes per mission. Thankfully none of them are DURING the mission, just before and after. And I’ve had one crash that cost me the run (right at the end) and I couldn’t get back in before the mission finished, so I got nothing for it.

Also here are the latest crash results
crash_dump-2023-05-15-15.26.10-c66e30d3-d664-4a70-b21d-820e33666c20.dmp (971.0 KB)
console-2023-05-15-15.26.10-c66e30d3-d664-4a70-b21d-820e33666c20.log (3.1 MB)
crash_report-2023-05-15-15.26.10-c66e30d3-d664-4a70-b21d-820e33666c20.log (1.9 KB)

@FatsharkJulia - here you go!
Note, there are no corrupt data files. Or if there are, the file scan doesn’t find them.
Here’s a file scan literally JUST completed!

Ok… I give up. This is trying to finish one mission… ONE.

Another attempt at a game tonight. 6:45 to 7:04 I was actually able to play continously, but of course it crashed mid mission (we had three scripts!) and the game wouldn’t let me back in.

This is using the “beta” build. The regular build is even less stable.

I don’t get this. I have a pretty damn good system:

This is extremely frustrating.

Our Engine Developers have identified an underlying issue that may be related to what you’re experiencing here. I apologise I have no immediate solutions for you, but I can help with processing a refund should you rather take that option.

I don’t want a refund. I want a working game. This game you guys have created is absolutely freaking gorgeous! The art is amazing. The look and feel is spot on for 40k. Vermintide looks great on it’s own, but compared to this it looks like absolute crap.

So I’ll just whine and moan and wait on a solution. Instead of a refund, can you complete my Melk’s quests on my Ogryn character? Since I can’t get in to do them. Occasionally responding to threads like mine makes it easier to have these issues.

Bumpity bump to keep reminding Fatshark that this game is currently unplayable for me. @FatsharkJulia - any word from the devs?

Hi bwood42, I had the same problem as you and I noticed you have the i9-13900k

This CPU seems to have stability issues for few people. Yes this includes data corruption.

What fixed it for me was underclocking the Performance Core speed a little bit using XTU.

Thanks man, I’ll give that a try. Just turned my PErformance Core down from 55x to 50x. We’ll see how it goes.

Hey man let us know, I personally only needed to turn it down to x53

x50 definitely works perfect. Zero crashes since activating that. I’ll turn it up to 53 and try, but for right now, I seriously owe you a beer! @FatsharkJulia make of note of this in your knowledgebase!