Memory Access Violations Crashing Entire Mission, Cannot Rejoin

Issue Type (Required):

Crash - During Play

Issue Description (Required):

Memory Acess Violation Crashes During Mission that result in the entire mission crashing and not able to be rejoined. I see a whole bunch of stuff in the log about enemies being “out of bounds”. This seems like a server related crash as I have been playing with friends who crashed at the exact same time I did, also unable to rejoin mission.

This has happened to me twice on 2 different PCs in the last 3 days.

You might see some stuff about CollectibleFinder mod in the log just before the crash, but that is definitely not the reason for the crash as my friend doesn’t use that mod and he crashed too.

[PC] Do You Use Mods? (Optional):

Yes, but I haven’t tried disabling them

Reproduction Rate (Required):

Rare (<10%)

Platform (Required):

PC - Steam

[PC] Crash Report (Optional):

03:23:07.188 <>Access violation (0xc0000005) in build 45655a28c941675d0b79acf3959d4e8c6a0242ad
accessing address 0000000000000000 from 0000000000000000<>

Full log attached.

[PC] Upload Console Log & darktide_launcher.log (Optional):

console-2024-12-15-23.37.15-e859f1b8-a259-4085-90a3-493fdf07c75b.log (2.06 MB)

1 Like

I believe this is the result of an outdated DLL being present in your installation, but it would be unusual for it to occur on 2 PCs, and potentially to your buddies too. Could you try verifying your install anyway?

1 Like

Did you follow Vizra’s AMD fix guide? Swapping the DLL just disables AGS and your log has the same error mine did when I tried. Not user upgradable like the upscaler DLLs sadly. I’ve since edited my posts to clarify that but Vizra forgot to mention that part.

1 Like

Even if it is a DLL-related crash, why would that prevent me from rejoining the mission? The only reason that would happen is if ALL 4 players crashed at the same time, or a server crash.

The other PC is running on an NVIDIA GPU (RTX 3080Ti). Also, my friend does not have the updated DLLs installed when he had the same crash at the exact same time.

I did update both the AMD AGS and FSR DLLs in my game on both machines. However, I have been doing that for a couple months now, and never had these kind of crashes until the last few days (after the Havoc patch).

I removed the new AGS DLL and that AGS error in the log went away. I did also try some of those tweaks in the linked thread, and it seems to have improved my stability and performance.

These crashes always occur during combat in missions with lots of things going on. But they are very intermittent. Only crashed on 2 out of like 20 games in the last 3 days.

1 Like

Just happened again with default DLL files. Everyone in the party crashed out and ended the mission. Log attached.

console-2024-12-16-20.51.05-1a154dac-e381-4f90-8b44-df9adeccb85e.log (2.0 MB)

1 Like

Oh I just noticed that is a massive mod list dude. You said you didn’t try disabling them and this only happened after the update so I’m willing to bet they’re interacting with something. Not a guarantee the session itself crashed if your friend also uses mods. Sometimes during a crash I just don’t get a prompt to rejoin even if the others from my group stay in.

Both of your logs also show your GPU twice for some reason.

1 Like

His mod list is very small. Again, we cannot rejoin the Havoc mission, so ALL players are crashing (or the server). Or there is some other bug with rejoining mission, though it does not block from starting another Havoc.

I’ve been using this many mods for a long time. Never had Access Violation until last 3 days. This is why people don’t bother making crash reports. Just get gaslit that it’s the mods’ fault.

Not sure what the video adapter listing has to do with anything, but OK. It’s a virtual display adapter for Parsec. Nothing to do with Darktide and is completely insignificant.

1 Like

Here’s someone having Access Violation Crash at Login. He doesn’t use mods. Clearly there are issues from recent updates.

The crash linked above is unrelated.

I’ve shot this over to our developers, but it would be helpful to have a log with mods disabled.

1 Like

The only way to get that would be to play for some unknown amount of time with mods disabled, hoping that the crash would occur.

I don’t know that I have the mental fortitude to go through that ordeal to get you a mod-free crash log lmao.

Here’s a crash log from my friend with a much smaller mod list. He has crashed at the exact same time as me in the same Havoc mission multiple times with the same Access Violation crash (null from null).

console-2024-12-14-18.19.56-099e6314-05e7-4a7f-8460-4b8aaa46b750.log (349.9 KB)

1 Like

this happened to me at least four times since the update, last one being fifteen minutes ago in a duo who crashed with “access violation” at the same time(same as me). there’s no way this issue hasn’t been properly looked into. it doesn’t seem to be a mod problem because it happens to every person in the lobby, completely forfeiting the match.

1 Like