Tried this, thanks for the advice
Crashed on starting the game…
GUID: 40edaa33-fe0d-47a9-9925-a1a3429669f5
Yes, setting worker threads to 1 has fixed it for me too (so far)
1 Like
As he said, he was referring 1000 MV (mv ), undervolting GPU using MSI Afterburner, google the guides.
It’s usually a great way to drastically reduce heat+fan noise and possibly even gain performance. YMMV with silicon lottery and you should turn undervolting off when troubleshooting, off in this game; reset GPU to defaults.
P.S. OT, Be careful with overclocking GPU mem, some games like Metro Exodus enhanced RT crashes big time with OC mem, undervolted GPU seems fine in pretty much every other game.
I only spoke about undervolting/underclocking the Core and memory.
only Overclock if you know what you are doing, you can seriously damage your hardware with bad overclocks!!
that is also why I only mentioned Negative Offsets, and some GPUs go up to 1600mV at like 2050Mhz which is waaaay to much and it really increases the heat output.
I do NOT know about 40XX series cards and the voltage needed but for 30XX series and below you do not really need more than 1000mV for anything up to 2000Mhz on the core.
and lets be honest the game can care less if you run 2000Mhz or 1850Mhz, the FPS stay pretty much the same.
BUT somehow Darktide manages to Crash on anything that runs a Factory OC, pretty sure that is also why they recommend the Debug mode for Nvidia cards.
The debug mode just doesn’t really help with the crashes, the only thing that actually does and which does not really impact performance is the underclocking (for me that is the case at least).
That was my biggest Issue with the single workerthread “fix” because it just shafts your performance from behind.
For me the “drastic” Underclock of 150Mhz on the core and 500Mhz on the Memory just lets me use all Workerthreads and DLSS to my hearts content without sacrificing any noticeable performance (maybe 1-5fps if even that).
I managed to play for around 5h without a crash, that does not mean the game crashed after 5h, no I just was done Playing and had to do something else.
I don’t even know why I am typing all this as a response but it just made sense to me.
I only wanted to share my findings and want to see if other people can profit from my troubleshooting.
2 Likes
I’d already told him about misreading from 1000mv to 1000Mhz. Thank you for more info about undervolting GPU, right now im using 500Mhz offset on Clock speed and very stable so far.
1 Like
Another GPU hang.
console-2022-12-04-18.26.33-bdbfbd74-b30e-4338-ada1-199229c03f6a.log (448.8 KB)
crash_dump-2022-12-04-18.26.33-bdbfbd74-b30e-4338-ada1-199229c03f6a.dmp (805.9 KB)
New Update, new crash. Welcome to Darktide, The Ultimate Crash Simulator.
GUID: 030ce6fa-3cbb-45b7-a07a-468f81570d76
Log File:
Info Type:
2 Likes
GUID: 5c5a7ddf-b70a-4af9-991d-fc47ba58d555
Log File:
Info Type:
console-2022-12-02-22.26.50-5c5a7ddf-b70a-4af9-991d-fc47ba58d555.log (191.5 KB)
crash_dump-2022-12-02-22.26.50-5c5a7ddf-b70a-4af9-991d-fc47ba58d555.dmp (1.1 MB)
gpu overclocking is usually safe since the voltage is limited anyway
my gpu is limited to 1175 mv
Which clock GPU or MEM and which offset, + or - ?
I’m assuming you meant -500 Mhz on MEM like Fasel did?
I’m curious:
-150Mhz is a pretty big chunk on GCORE have you tried only -500 Mhz GMEM?
I too hated the “single worker thread fix”, I have a hunch 4-8 worker threads is ideal, maybe more so on older CPUs.
I even did a mission on my usual 900mV curve (had nV and Steam overlays off though fwiw, and ShadowPlay , all off for days now).
Also, are you on experimental version? Expi crashes me very quickly if RT is on, but seems to run fine otherwise so far, did 4 maps before. it seems a bit better than yesterday, hard to say.
Mine is: -500 Mhz on Core Clock. Still stable so far (after 6 long games ;-;), have to rest abit since one match took awhile to test. I’m thinking about raising - offset because this way seems to sacrifice so much although very smooth gameplay with 4 threads and high settings.
Ouch -500 on core clock is a big drop! It shows you on a 3060TI, AMD Ryzen 5 3600 6-Core Processor.
Windows 11 WinVer 22623 is on the insider preview branch is it not?
I’d be curious if on your CPU setting 6 worker threads (or 4) but setting CPU core affinity to the physical (even) cores would help. It has to be set on the LAUNCHER via Task Manager and it will pass it down to game exe.
OR You can use this PowerShell 1 liner to do it too (in PowerShell console or save to .PS1 file script (Run after Launcher window shows, it beeps):
Get-Process "Launcher" | Where-Object {$_.Path -like "*\Steam\*"} | ForEach-Object {$_.ProcessorAffinity=0x555 ; Write-Output $_.Path;[console]::beep(400,150);[console]::beep(500,150);}
The older logs I posted are mostly from my W11 insider branch like you pointed out. But I reinstalled W11 ver 22621.900 - official W11 version a day ago and joined Darktide Experimental branch since.
About -500 Mhz Core Clock drop, I purely based on common 3060Ti Base Clocks from market GPUs to test out since it’s not undervolt and core clock is just like others GPU Base Clock (so I think it won’t break my GPU).
Yes I am running my test following Fasel guide with 4 threads, will try out with 6 threads like you suggest via launcher settings.
What GPU do you have fasel? I have a 3080 ti Asus tuf. I might be willing to give this a crack…
Noticed the experimental branch got a new update, no change for me.
GUID: 8ef0588c-61a9-469e-b4d2-562a81d83088
Log File:
Info Type:
crash_dump-2022-12-05-05.25.53-8ef0588c-61a9-469e-b4d2-562a81d83088.dmp (801.1 KB)
console-2022-12-05-05.25.53-8ef0588c-61a9-469e-b4d2-562a81d83088.log (56.0 KB)
THe most frustrating thing with this s*** fest of a bug is, that you wait in the elevator for the last guy that has the URGE to mow down the last 20 enemies instead of running into the mission end.
Then you crash just before he enters and you lose all of the goddamn progress.
Honestly Fatshark, get that s*** done.
Here my crashes from yesterday and this morning…
crash_dump-2022-12-04-15.57.43-22d63038-90e6-4ec4-86ce-ecb07fa94e02.dmp (779.5 KB)
crash_dump-2022-12-04-15.12.26-5c2dc710-dcb2-4f6b-9f4b-2231c74a38bc.dmp (793.8 KB)
crash_dump-2022-12-04-10.11.01-30073ff4-fd50-451f-805b-0551d0376f9b.dmp (804.9 KB)
crash_dump-2022-12-04-08.25.50-b4861b92-bd6d-4b26-98fe-e518ed46c1af.dmp (792.2 KB)
crash_dump-2022-12-04-19.21.28-e322120f-a75d-4b42-b3ae-341ff411902c.dmp (771.7 KB)
crash_dump-2022-12-04-19.34.29-a42bd382-c477-4ff7-9e0d-14c43553efd5.dmp (790.8 KB)
crash_dump-2022-12-05-05.35.50-d9730820-534e-488b-817f-462710e423cd.dmp (793.8 KB)
crash_dump-2022-12-04-20.43.39-3bc37fd7-eaf3-4b80-8958-06cc68bc2b5a.dmp (776.4 KB)
2 Likes
Same, 9.x mb but nothing changed (as usual).
Would really like to see some type of update/communication from FatShark on this issue… It’s ruining an otherwise great game for me. Level 30 on one character but can’t bring myself to play much more when it’s either running poorly on one thread or running great on more but crashing often.
I’ve just been checking more than I’d like to admit to see if there’s an update on the way.