Crash - During Play
It takes a couple loading/rejoigning in a game or ending some. Then the crash happens, mods or not. I’ve tried a couple of graphics settings but none work.
Yes, and I’ve tried disabling them
Constant (100%)
Steam (PC)
they gonna ask you to upload your crash files, might be helpful to also send DxDiag file
windowskey+R type in DxDiag enter → safe all information post here.
ps: from that little info you gave it sounds like an overheating problem, have you checked while ingame if your temp is ok?
This is a recurring issue with AMD, and I have also encountered it.
@ORTEGA As mentioned above if you could provide a crash report, or your console logs and launcher log that would be great to take a look at.
Thanks in advance!
I’ll submit the logs on his behalf, as I am also an AMD graphics card user. I’ve encountered the same crash issue, which always occurs when entering maps and during the results screen, both with and without mods.
console-2024-09-30-04.15.45-9841075c-0872-4110-8eab-e2a05b8e7f74.log (3.1 MB)
console-2024-09-30-05.33.12-7390ac45-f4b8-4b25-9150-9b5e8cbb4278.log (1.2 MB)
console-2024-09-30-06.00.45-2e73aa0a-6d00-4b9d-8e29-602246d75ea2.log (2.8 MB)
console-2024-09-30-07.02.46-c2baa851-4142-4340-98be-f7a34d453d30.log (237.3 KB)
console-2024-09-30-08.01.19-223262b5-1ad1-4918-a442-b606734d49c5.log (154.6 KB)
Thanks! The logs all show a GPU-related crash occurring. I’ve passed these reports on to the development team and we’ll take a look.
It may also be worth running through our GPU crash solutions, here:
This is a bug that appeared exclusively when running the game on AMD GPUs after the latest major update. Even after I took my old SATA SSD out of the junk box, installed it on my computer, and reinstalled the system, the latest graphics drivers, and the game, it still crashes when entering the map or the results screen. The crash happens consistently every 2-3 games.
Attached is the new log.
console-2024-10-02-21.25.54-344e5ba8-bbc1-449c-b9e6-bdccc03ca93b.log (759.9 KB)
console-2024-10-02-21.49.03-8a8f8964-5566-426d-8eb0-a2aea05c5bb9.log (4.2 MB)
console-2024-10-02-22.50.41-8dc5d834-1464-4bea-b346-ac7c78153f7f.log (1.3 MB)
console-2024-10-02-23.25.45-c94a0c0b-1984-4485-bee4-b0596e988ddb.log (1.1 MB)
console-2024-10-03-00.24.37-80aef13a-2e49-4563-87f9-e422ce8be6f0.log (408.4 KB)
Yeah, same issue for me.
No mods, fresh install, latest drivers and all that noise. Game will run fine for 2 missions then when I try to queue up for the third when it finds a match it will hang for a few seconds, then crash to desktop and crash the graphics card as well.
Game will run fine for those 2 missions, avg 75fps but nothing that stands out, but without fail its always when I queue up for the third mission it’ll shits itself. Doesn’t matter if the missions I play through before are from start to finish or if I join at the ass end. Every 3rd I connect to CTDs the game and forces the GPU to restart.
Uninstall the current drivers using AMD Cleanup Utility, then download and install the 23.12.1 drivers. Using an older version of the driver can resolve the crashing issue.
AMD Cleanup Utility
AMD Software: Adrenalin Edition 23.12.1 Release Notes
I somehow stopped my mission loading crashes after trying a lot of things and I’m not sure exactly what fixed it but I’ll list what I did. Crashes happened both on the main and experimental version of the game though I’m now on the main version.
Windows 11, 7900X CPU, 7900 XT GPU and 24.9.1 drivers, 32GB RAM, game installed on an NVMe SSD, 3440x1440@144hz main monitor + old 1080p60 secondary monitor
No mods besides replacing the games XeSS dll file with the XeSS 1.3 version from Intel’s Github page which worked before the update.
I had previously messed around with but still had crashes after trying these things:
Changing thread count in the launcher
Changing various in game settings (exclusive/borderless fullscreen, all the graphics quality settings, frame gen on/off, FSR 3.1 or XeSS upscaling, disabling character portraits, lowering ragdoll count/disabling ragdoll interaction)
Disabling/reenabling the mesh shader in the game settings files
Messing with direct storage settings in the experimental build
Disabling Windows fullscreen optimizations for the game (Right click the main Darktide.exe found in the games install folder → properties → compatibility → toggle disable fullscreen optimizations on → change high DPI settings → override high DPI scaling behavior, scaling performed by the application)
Deleting the games shader cache from the game folder and resetting AMDs shader cache from within the AMD software
What worked for a while but still ended up crashing (both done at the same time):
The above worked for a day but still eventually gave me a crash. The next day I tried doing a whole bunch of things and have no crashes since so any one of them may have fixed it.
What eventually fixed it somehow:
I ran the windows system file checker following instructions from the Microsoft support website. This requires doing two commands in a command prompt (run as administrator!) so follow the instructions carefully. Windows installations get corrupted sometimes so I do this once or twice a year or if a Windows update breaks anything. Note that this article is old and only lists up to Windows 10 but it also works on Windows 11
I made sure my windows was fully updated. Under Windows Update → advanced options → optional updates I had two driver updates. One for a USB hub and one for my secondary monitor (huh, weird)
Darktide updated (Hotfix 49, 1.5.2)
AMD driver 24.9.1 released. I didn’t use the cleanup utility but I did hit the Factory Reset button under the additional options section in the installer. Yes, it says it says optional but it will properly get rid of your old drivers. There’s a toggle to keep your user settings if you don’t want to set it all back up again. It also says it requires a restart even if it doesn’t give you a restart button. You should do this every time, seriously! If you never have you may want to use the cleanup utility first and then remember to factory reset each update from now on.
I turned on Memory Integrity in Windows Security. If I remember correctly this requires virtualization to be on in your BIOS settings and how to turn it on depends on your motherboard vendor. Open Windows Security → Device Security → Core Isolation Details → Toggle memory integrity on.
I’m aware memory integrity technically hurts CPU performance in games a bit but if you have a Ryzen 5000 series or better, Windows 11 update KB5041587 recently gave you more performance. You can check if you have it by going to settings → system → about. If you have 23H2 OS build 22631.4112 or later or 24H2 OS build 26100.1301 or later you should have it, otherwise update Windows.
Regarding Windows and Driver updates and the system file checker, I also recommend turning fast startup off (on by default of course). Windows will save some system files/data/drivers/etc on shut down to make the next boot up faster but this can lead to files getting corrupted and weird driver behavior carrying over between bootups. A 1 second faster bootup time if you have an SSD isn’t worth it. This isn’t in the new Windows settings app so open control panel → system and security → power options → change what the power buttons do. The fast startup option will be enabled but greyed out. Click change settings that are currently unavailable and you should be able to change it.
I don’t know which of the things I changed that fixed it but I’m crash free for about 20 hours of gametime now. I average around 130fps playing mostly at high settings (no RT) with some screen effects, bloom and portraits disabled + frame gen and XeSS ultra quality (no messing with the mesh shader yet) and that’s with AMD instant replay on for clipping game moments. Hopefully this helps someone else avoid all the trial and error I went through!
Enabling memory integrity did indeed resolve the crashes during loading and settlement, but it introduced noticeable input and visual lag, similar to the experience of enabling vertical sync (I’m not sure if this issue is widespread). Then I encountered a worse issue: out of memory crashes, which occurred after browsing the store and crafting multiple times. After checking the forums, I found that this bug has existed for over a year and still hasn’t been fixed. I’m not sure if it’s an AMD-specific issue.
Strange. I decided to enable it because the driver crashes were usually accompanied by a notification saying “Microsoft windows operating system has been blocked from accessing graphics hardware” in the windows notification tray. Memory integrity is supposed to stop malicious programs from using drivers to mess with or infect Windows but I figured it could also stop a game from doing something that would cause a crash. I don’t have the weird latency or lag issues you’re mentioning though (aside from the lag that comes with frame gen).
You turned hardware virtualization on in your BIOS right? It says it’s required on the Microsoft support page for core isolation but I know some emulators that also need it like BlueStacks let you run a way slower version without it so I wonder if Windows would do the same. It’s usually off by default on most motherboards but you can check if it’s on by looking at the CPU in the task manager performance tab.
Yes, I use an Android emulator, so I always have VT enabled. The current situation is that if I use the 23.12.1 driver, I don’t experience crashes during loading/settlement, but after playing for a long time, I get out-of-memory crash errors (usually after multiple uses of the crafting system). If I use the 24.9.1 driver, I encounter crashes during loading/settlement. In both cases, memory integrity was enabled.
I’ve been testing all day, controlling the variables, but now I have no idea what the problem is.
Dang, that’s really weird. There’s a couple fixes for the out of memory issue I’ve seen around but I never had any of that happen to me so I’ve never tried and it looks like it can happen to anyone. Something about a Lua heap file reaching a limit when doing inventory things. Did you try anything else I did like the windows system file checker? My windows install is only a year and a half old but it still found a few things to fix. I know there’s an AMD crash that can happen with player portraits on too. Also did you delete the game’s shader cache in the games appdata folder when changing drivers?
I also have these three settings on in Windows. Dunno if the last one effects the game in borderless or not. I’m leaving HAGS on because it’s required for frame gen but I see the occasional post around the internet about some games acting weird with it on. I also don’t have the frame gen issues others are mentioning. Maybe it’s the lens quality effects I leave off? They’re hard to look at anyway.
I have Resizable BAR (AMD SAM) on in the AMD software.
Also display scaling handled by the GPU in the AMD software (settings->display)
I don’t think this is an issue but I do also have my Windows page file set to the default of 4GB. 32GG of physical RAM but I don’t know how yours compares. Bumping it up to 8 or 16 isn’t really bad as long as you have space. Just don’t turn your page file off, that causes big performance issues.
Balanced windows power plan because sometimes changing it can actually be detrimental to some games. Those are all the other settings I can think of off the top of my head so hopefully one of them helps.
Minor update. I noticed that when I close the game I get an application error in the windows event viewer.
Faulting application is Darktide.exe
Faulting module name is gRPC_pluginw64_release.dd_unloaded
However I scrolled back before the update happened and noticed I was getting them back then too, every time the game closes.
I checked the same date/time I had my last crash file generated and I didn’t have the application crash but I did get a warning in system saying “Application dwm.exe has been blocked from accessing Graphics hardware.” That the desktop windows manager, part of windows, and explains the notification I mentioned above that came with the crash. There’s also one in the kernel-pnp device management at the same time mentioning a device removed (the gpu timing out I assume)
Unrelated but I am still getting the rainbow psyker shield bug pop up randomly even with the newest driver. Oh well.
