Basically unplayable. Crashing 5-6 times a match. Doesn’t seem to be any particular in-game trigger. I have verified my game files (twice), confirmed that my CPU is set to x53, and my mods have been disabled since Bound by Duty (because I couldn’t even launch the game with them enabled, lol).
I did report this in the original BbD crash thread but haven’t received an acknowledgement, and as it’s still a persistent issue after the last few patches, I decided to give it its own thread.
[PC] Do You Use Mods? (Optional):
Yes, and I’ve tried disabling them
Reproduction Rate (Required):
Often (<75%)
Platform (Required):
PC - Steam
[PC] Crash Report (Optional):
GUID: fd80e93b-7b86-4a49-94f6-6e8c110af4cb
Log File:
Info Type:
[Engine Error]: Failed to decompress: C:\Program Files (x86)\Steam\steamapps\common\Warhammer 40,000 DARKTIDE\binaries..\bundle\data/01/01ceef909b921f5f.stream from package 7b4d5179.
Make sure that your game files are not corrupt by in steam. Contact support if this still occur after verifying the game files.
Any overclocking/power management software? I’ve had another thought - ‘Core Performance Speed’ can be changed both within Intel XTU and the BIOS - any inconsistencies there perhaps?
Depending on how severe the damage is, reducing the multiplier to 53 may not alleviate the issue. Dropping it way down, and slowly raising it until it becomes unstable may help. It should either help find a multiplier that is stable, or show the chip is very badly damaged.
Echoing what Meatshield is saying, your CPU is probably damaged from Intel’s overvolting issue. They extended warranties for affected CPUs but they may also tell you to go through whatever store you got it from. Unfortunately if you bought it used/refurbished within the last year or so you may have been scammed but there’s also a chance they thought it was a GPU problem due to the way it often causes problems with shader compilation.
Here’s the r/intel megathread with some useful info like affected CPUs
One thing that’s not made clear in that thread though: This problem physically damages your CPU. The BIOS update may seem to help for a time but once the damage is done the degradation will still gradually get worse. Some people have had luck really underclocking their CPU and disabling some CPU cores in the BIOS to get some stability back but that’s also not a guarantee if it’s really bad.
This whole situation sucks because if a warranty doesn’t work you either have to downgrade to a compatible non-k series i3 or i5, find a new in box i7 or i9 and hope the seller is honest, or move to a new unaffected CPU generation which would also require a new motherboard. Hopefully an easier option like the warranty/RMA works out.
When I downloaded and opened XTU it was already at x53, I didn’t have to downgrade it.
I did just flash my BIOS. The code issued fixes the voltage issue, although as @DashHandsome mentioned it’s likely physically damaged already… but can’t hurt to try.
I purchased my CPU (i7-13700k) in November 2022, which means my warranty would ordinarily be about to expire, but I don’t have the box anymore anyway so I guess it’s moot. (Also currently not able to endure the downtime it would take to RMA it & receive a new one.)
I’ll give the game a whirl tonight and update again then; if it still doesn’t help I’ll probably drop the multiplier and see how that works. Any suggestions on how low I should start it out?
I haven’t had an Intel system since my 6600K got nerfed by the specter/meltdown patches so the rest of my help is limited but there’s one last interesting thing to look out for. The last few generations of Intel CPUs have separate performance cores and efficiency cores. If you check the specs for your CPU:
there’s 8 of each core type but 24 total threads because only the performance cores get multithreading. You might be able to skip the trial and error of finding the right multiplier by either disable multithreading or just the efficiency cores in bios (I’m assuming Intel says what core is what)
Might because if you’ve had it for 3 years it’s hard to say how bad your CPU could be. If that doesn’t work you’ll have better luck google searching for a reddit post or something from someone with a 13700K to see what works for them.
No matter what you do you’ll be taking a performance hit but it’ll give you some breathing room to work on a replacement. Good luck!
I also bought my 13700KF in November 2022.
Recently, I started getting frequent “Failed Decompress Error” messages in Darktide, and at first, I thought it was caused by a game update. However, it turned out the real cause was excessive CPU voltage.
Updating the BIOS to the latest version should fix it, but if you can’t update for some reason, you’ll need to lower the voltage manually in the BIOS settings.
In my case, after making the changes shown in the image, the “Failed Decompress Error” stopped happening completely during gameplay.
It seems that on default settings—depending on the motherboard model—features like “Gaming Boost” are usually enabled, so it’s probably better to turn them off.
As for XMP, you can try re-enabling it later if your system remains stable.
So I played a regular mission and it had zero crashes, which was really refreshing because I was legitimately getting that error upwards of 4 times each mission.
I did crash once during a Mortis trial, but it was as I was sniped by 3 snipers at the same time, lol, and it was a completely different error. My entire game disappeared, whereas with the previous error it would give me the pop-up and only disappear once I clicked OK.
Here’s the new error:
GUID: 9d8cd638-94f7-402d-8dd3-aed264816ef1
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build 31127afd8f47ef61b5511fb173770edc88494a41
accessing address 000002BA7D28FEFA from 00007FF6C617FC60
