Issue Type (Required):
Crash - During Play
Issue Description (Required):
crashing often
I have played for about 2 months but crashing seems to have been happening in the last month or so. No updates I am aware of that would change the game to this extent I feel. I have not yet took screenshots or figured out what other information I should have wielded, as this is my first time posting so please let know what else I could provide for this issue.
Game crashing at seemingly random points. Game crashes sometimes at startup almost or a few seconds after pressing “Play” at the Launcher. Game will sometimes crash when all players have readied themselves for the match, regardless of time left in the count down. Game will crash often during gameplay using all classes. Game will crash after a match has finished or about to enter the Morning Star. Game will crash when sometimes looking inside the Player Inventory. Often in crashes related to gameplay the launcher/game will repeat crashing a few times before I can successfully log back into the game and reconnect. When reconnecting to a match in the ship loading screen, after a crash, the game will also sometimes crash once it gets to “awaiting players” message in the bottom right corner. Not certain this is related, however it only occurred a few times in only Darktide, but at the time of a crash the my computer will restart by itself. When using Discord, already in a voice call, I will get disconnected from the call for a second or two then immediately get connected back. Also, in a Discord voice call, I will sometimes be disconnected outright from my voice call and have to manually rejoin myself. Some sessions can go a lot longer without crashing like a few hours, but some can crash with as little as about 30 minutes.
I’ve tried some troubleshooting options that are recommended. I have tried the %appdata% percent method, the problem persists. I have tried lowering/turning off settings such as player portraits and worker threads, the problem persists. One method was trying to to update graphics drivers which will include my only note of change I’ve experienced. My previous driver was outdated when the crashing arrived so I forget the orginal version, but it was a 560.-- driver. I have in the last few days, been testing with the nvidia game ready driver version 591.74. The note of change was the crash reporting a different “in build” number which is: f147244e716446ea75ee624e45278695e2b70910. Though these crash windows wouldn’t always be the same regardless. Other applications and games run without any bugs or issues so it seems to unfortunately be Darktide. The game is fun, however these bugs/issues are not. All answers appreciated.
CPU: Intel i9-14900k
GPU: Nvidia 4090 rtx 24gb
RAM: 64gb
PSU: 1300w
[PC] Do You Use Mods? (Optional):
No, I don’t use mods
Reproduction Rate (Required):
Common (<50%)
Platform (Required):
PC - Steam
[PC] Crash Report (Optional):
GUID: 40a4035b-ef88-413d-b531-448642ed0f10
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build f147244e716446ea75ee624e45278695e2b70910
accessing address 0000000000000A6A from 00007FFC982C1060
The issue could be related to the following modules found in the stack trace:
module ‘nvwgf2umx’.
This CPU is notorious with instability issues with games & having overvoltage problems. I used to have this same issue & CPU. The fix is updating your BIOS, so it sets your voltage to the correct amounts, permanently. I’d either look up a Youtube video on how to update that for your PC’s correct specifications or seek somebody that knows what they’re doing if you’re uncomfortable with doing that. Don’t use Intel’s Extreme Tuning, that’s just a temporary band-aid fix, you want this to be permanent, so update that BIOS. You’ll be good for about a year or more. It takes a bit, like about 10-20 mins roughly & you’ll be good as new, promise. It should fix all your gaming woes. I would do this ASAP because you never know it could potentially cause more damage within time you don’t update it. After you’re done with that, I would do some CPU stress tests as well to make sure it’s still in a solid state. If there’s still issues after the update & if it’s under warranty, I’d honestly get my money back for something else or replace it, that’s up to your discretion. 
Been running stress tests in the time I have available. Everything seems to check out on the surface. Checked tempts for both CPU and GPU and are within ideal temperatures. I’m not too savvy and I won’t rule out the CPU being the cause. That said, I recently ran the game with hwinfo on to monitor temps and whatnot, but the game still crashed with the same message. It’s every sesh. Even rolled back a driver and that run I crashed 5 minutes in just being in the lobby. Crashes are at random seems like, but it will never not crash during a sesh. Still testing other games but no crashes I can trigger so far, things like the new battlefield or older titles.
Yeah, some less demanding games won’t likely crash because it doesn’t consume much power/voltage, so you’re likely good on that front & it will seem normal at face value. But yes, this is one of those things where a BIOS update would most likely fix this for the long haul, it’s one of those non-negotiables, I’m afraid… if you want an actual fix. There’s just no other way around it. If you want a more permanent fix, you’ll have to muster up the courage & do it. It’s not too hard, honestly… You just need a USB flash drive your PC specs & maybe a video tutorial. But yes, if you’re not too tech-savvy & feel uncomfortable with updating BIOS, then I’d honestly take it to your local PC repair place. Trust me, I’ve been through this entire dog & pony show before with the same CPU in fact & this game did the exact same thing in terms of errors, etc. BIOS is completely free to update as long as you have the correct PC specs & site to download the new updates from your exact Motherboard model on whatever website that it is on in terms of your brand. But yeah, if you decide not to do it yourself it might cost a small fee or whatever they charge. I’d just watch a video on your exact PC specs, but that’s just me. Free is always better for sure. If you don’t want to do either than hey, that’s your free will, I’m just saying that it’s the smart & correct move for sure. It’s better to be safe than sorry as mothers usually say. If you leave it be, I’m sure you’ll be fine for a while, but I personally wouldn’t do this because most likely you’ll be risking more damage potentially to the CPU as time passes by. You’ll end up getting the blue screen of death & even more errors, etc. Then you’ll have to replace your CPU with something else if it does go that far that is. This is hypothetical of course, but that’s what happens to this exact model of Intel CPU’s, sadly. Not trying to scare you of course… It’s just the reality of the situation from somebody who has had one.
Some crash info I collected from the last handful of times. Didn’t know how to post it the first time.
console-2026-03-22-19.37.55-9d8ddd7f-f60f-46a9-ae2a-ae26d0b415e2.log (188.9 KB)
console-2026-03-22-06.20.28-78ab531d-885d-49d0-8f4e-4f788e6f78c5.log (8.6 KB)
console-2026-03-22-06.22.41-6ab8086e-f1bd-4dbe-a66e-b6eb41b921e7.log (16.3 KB)
console-2026-03-22-06.42.58-89c42ab9-a89f-4796-9dc0-a0d923ebe3f1.log (132.2 KB)
console-2026-03-22-06.51.58-bb2eb4a4-09fb-43ad-ab0e-c089fd8b60c2.log (17.8 KB)
console-2026-03-22-06.54.18-0fc1c78a-ad21-4705-9375-31939229f811.log (17.2 KB)
console-2026-03-22-06.55.16-32de05d8-e1a2-489d-ad1a-d55ffd0ba38d.log (7.7 KB)
console-2026-03-22-07.02.54-c1be2b0f-131a-4bd6-95a5-0ee204b39ab7.log (6.1 KB)
console-2026-03-22-07.05.52-7ad2da22-bc41-4e22-90f6-8a18eaf2c149.log (145.0 KB)
console-2026-03-22-07.22.38-cfd92c9d-9bda-4e8c-aa50-cbd9d0f43bec.log (196.8 KB)
GUID: 9d8ddd7f-f60f-46a9-ae2a-ae26d0b415e2
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build f147244e716446ea75ee624e45278695e2b70910
accessing address FFFFFFFFFFFFFFFF from 00007FF61AD8A2C0
GUID: 345c63b7-2fda-4a7b-b2b2-792617b79d16
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build f147244e716446ea75ee624e45278695e2b70910
accessing address 0000000000000024 from 00007FF7330FD083
GUID: 9d8ddd7f-f60f-46a9-ae2a-ae26d0b415e2
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build f147244e716446ea75ee624e45278695e2b70910
accessing address FFFFFFFFFFFFFFFF from 00007FF61AD8A2C0
GUID: 820497c8-b9a1-4072-a41b-ff8685131b7a
Log File:
Info Type:
[Engine Error]: Access violation (0xc0000005) in build f147244e716446ea75ee624e45278695e2b70910
accessing address 0000000000000001 from 00007FF60EDAFCA4
Updating the bios to stop the damage is a good idea. But updating won’t always fix the crashing depending on how much damage was done to the CPU. Some people still need to under-clock their CPU to regain stability.
So, it solely depends on which brand the Motherboard is & the actual contents of the update. Because depending on the Motherboard it generally does auto-set the correct voltage amounts which would fix the crashing from the update. But… also, how long has he had the CPU for too, right? If it’s just recent within maybe a year or so than it should fix it. If he’s had it for year’s plural, it might not fix it because unsaid damage could’ve fried some of his pin’s overtime, hypothetically speaking depending on the time-span that is. I would still do the BIOS update reguardless & then test the same games afterwards to be safe. If the games still crash or he has instability issues, I’d get a refund or replace it entirely. I replaced mine just because I didn’t trust keeping it. I went with AMD after a bit & I’m happy I did. Another factor is… How long since he’s done an actual BIOS update with his PC, some people never do it & that’s a huge mistake. I always recommend doing that at least once a year or so. There’s a bunch of unanswered questions there to factor in as well. It’s not a bad CPU at all, but of course Intel didn’t preset their voltage amounts for the latest CPU’s, very typical of them. They’ve actually done things similar like this before. So, you can use Intel’s Extreme Turning just to see if it’s the voltage amounts as a test, but this is only as a test. I wouldn’t do this permanently… When BIOS can set the correct amounts & fix other potential harms to his PC updating whatever else he needs from that update. I never used E.T. after that & I was fine, it set everything perfectly & it was smooth sailing never had issues after.
Not sure why this is a thing. Just update the BIOS like these mates suggested. It’s not much more complicated than a simple windows update. 
I seem to have already responded to this via the Support Portal, noting the same issues with the 13th and 14th Gen Intel CPUs as mentioned above. I’ve included Performance Core workaround in my reply. 
Updated BIOS, thanks Brad and Julia for the replies. I’m testing all I can in Darktide and out. Temps and power again seem fine and within ideal ranges and the crashing, for the most part seems resolved or lessened a great deal for Darktide. On the initial day of updating my BIOS I only encountered one crash with the “Access violation (0x0000005)” message, was playing with a friend. On the next day however might be the same or different issue, but I was doing my first Expedition match and about after reaching the first shop instance I black screened while my pc was still running. Had to restart. Normal matches and sessions seem normal, but I have no idea what happened at that black screen during the Expedition.
Yeah, it’s all in the magic of the BIOS update, I’m glad it at least fixed something for you. You’ll be good pretty much from now on. All you have to do now is upkeep your Windows/GPU updates & update BIOS like once a year if that, honestly. Should be smooth sailing from here on out theoretically unless there’s something else faulty, hypothetically speaking that is.
If your screen goes black, I’d make sure your monitor is set to your max hertz, etc & everything is plugged in tight. I’d even unplug from monitor to PC & blow into the cords. To make sure it’s not a faulty wire, perhaps to be super safe. That happened with me & that also fixed my issues. If it keeps happening, you might have to reset your graphics driver from black screening, but I’d do a little bit more research on that one before trying that (Youtube video perhaps, but this is a last kind of deal option if you know what I mean, a last resort). Resetting your GPU is really simple actually, simpler than that BIOS update for sure. Unless this is a common occurrence for other people in Expeditions itself? I’m not too sure on that one, sorry. If it only happens there then I really have no clue as to why that is. That’s strange on how it works elsewhere, but not there.
Another thing is that try to run the game unmodded if you use them & also maybe verify game files in Steam Library too. Something more drastic is to clear your \AppData\Roaming\Fatshark\Darktide folder, but this will reset everything, keybinds, etc, sadly… It’s totally up to you, but I’ve also heard that it can fix issues too. Clearing your appdata is a last option though, as is resetting GPU. You could try the other stuff first & go back in & if it still continues you could technically try the more drastic methods… Sorry, I’m very long-winded.
After the millionth edit lol:
A few other things to try too. Just throwing that out there if you haven’t yet. If all of that doesn’t work, man… I’m throwing my hands up on this one lol.
