1.0.13 patch
crash_dump-2022-12-02-23.39.24-e635737c-f078-497b-bcfc-6b5375c16da2.dmp (837.5 KB)
managed to get throught ONE mission with no crash. i changed from fullscreen to windows borderless, and kept cores on 1. ran like absolutely garbo but at least no crash. was able to switch to another character too , but getting error 2001 now.
GUID: b6230066-9a9e-46e6-bdf0-8051e2e72281
Log File:
Info Type:
console-2022-12-02-23.43.48-b6230066-9a9e-46e6-bdf0-8051e2e72281.log (537.7 KB)
crash_dump-2022-12-02-23.43.48-b6230066-9a9e-46e6-bdf0-8051e2e72281.dmp (898.3 KB)
Managed to run a full mission now on Worker Threads = 3 (default max) ![]()
How? I changed to Windowed Mode this time.
FPS cap 30 and 60 tested and worked. Game felt more fluid and managed to keep those caps pretty locked.
GPU usage seems very low, like 20%?
For reference, I have Win11, a RTX3080, and a G-sync 144Hz monitor (one with the G-sync HW module.
PS. When I crash, I always crash in missions, never in the hub.
GUID: d5ed6a61-3fb1-4bce-8f79-c66eaae03b47
Was just standing in the Mourningstar after mission complete and boom, right to desktop.
didnt help
If anyone is reading this limiting to 60 fps has cured crashes
*Edit
also enabled vsync
GUID: 1075e14a-474c-4612-a654-99eeab3976b5
Log File:
Info Type:
crash_dump-2022-12-03-02.39.37-1075e14a-474c-4612-a654-99eeab3976b5.dmp (878.7 KB)
console-2022-12-03-03.15.12-5c8444bd-bd0a-4e03-8036-8fcc63d23dcf.log (6.5 KB)
Hey
I have been crashing now since latest hotfix 1.0.13 and new Nvidia driver 527.37
prior to these updates my game ran fine until I updated to the new driver. i then reverted back to previous driver at it worked fine again but since latest hotfix it crashes on both Nvidia drivers.
Win 11, 3090, i9-9900ks
Thanks for your help
GUID: aeca5183-b603-4624-a043-f0784abee755
Log File:
Info Type:
GUID: 5c8444bd-bd0a-4e03-8036-8fcc63d23dcf
Log File:
Info Type:
console-2022-12-03-03.15.12-5c8444bd-bd0a-4e03-8036-8fcc63d23dcf.log (324.6 KB)
crash_dump-2022-12-03-03.15.12-5c8444bd-bd0a-4e03-8036-8fcc63d23dcf.dmp (895.0 KB)
GUID: 4a8f1ea0-6d60-4344-8d59-2f42020e5f2c
Log File:
Info Type:
crash_dump-2022-12-03-03.45.41-4a8f1ea0-6d60-4344-8d59-2f42020e5f2c.dmp (916.9 KB)
console-2022-12-03-03.45.41-4a8f1ea0-6d60-4344-8d59-2f42020e5f2c.log (56.2 KB)
GUID: ad6ef4ee-1bbe-4206-a97b-9dc4104f61eb
Log File:
Info Type:
GUID: 6208be28-dfae-4296-b431-0b9821b01036
Log File:
Info Type:
GUID: 304cce12-871b-4ed2-836f-7804884209be
Log File:
Info Type:
GUID: 2d2615cb-9630-48c6-af20-10c53b9492e8
Log File:
Info Type:
GUID: a869f854-e5f1-47f2-9239-65a5e45684eb
Log File:
Info Type:
console-2022-12-03-05.14.26-a869f854-e5f1-47f2-9239-65a5e45684eb.log (107.5 KB)
crash_dump-2022-12-03-05.14.26-a869f854-e5f1-47f2-9239-65a5e45684eb.dmp (991.0 KB)
after the lastest āfixā patch.. really frustrating. join mission then after less than 5 mins crash.
GUID: a448e111-914b-4894-bf93-912f7ef094bc
Log File:
console-2022-12-03-05.45.10-a448e111-914b-4894-bf93-912f7ef094bc.log (126.3 KB)
Info Type:
crash_dump-2022-12-03-05.45.10-a448e111-914b-4894-bf93-912f7ef094bc.dmp (882.3 KB)
-
console-2022-12-03-06.00.09-77e9f3a4-f8e8-40eb-843d-d54d5aa384b7.log (294.3 KB)
crash_dump-2022-12-03-06.00.09-77e9f3a4-f8e8-40eb-843d-d54d5aa384b7.dmp (840.0 KB)
console-2022-12-03-05.53.02-aaf13a79-f558-4e04-96bf-dc66c4d07ec2.log (100.3 KB)
crash_dump-2022-12-03-05.53.02-aaf13a79-f558-4e04-96bf-dc66c4d07ec2.dmp (877.9 KB)
console-2022-12-03-05.37.43-15aaba8a-4793-457e-b5e0-bdb5ba949faa.log (170.1 KB)
crash_dump-2022-12-03-05.37.43-15aaba8a-4793-457e-b5e0-bdb5ba949faa.dmp (815.5 KB)
console-2022-12-03-04.55.39-8f78f19d-9490-4472-82d6-34429d4dcb44.log (156.1 KB)
crash_dump-2022-12-03-04.51.48-0cde6bc9-4c32-4782-997b-2b9e337b6094.dmp (817.9 KB)
console-2022-12-03-04.51.48-0cde6bc9-4c32-4782-997b-2b9e337b6094.log (102.4 KB)
crash_dump-2022-12-03-04.38.40-d2b0fa48-12d9-4f97-8522-ec369955d90c.dmp (960.3 KB)
console-2022-12-03-04.38.40-d2b0fa48-12d9-4f97-8522-ec369955d90c.log (105.5 KB)
crash_dump-2022-12-03-04.26.21-201d4e55-bc29-4c76-8e2f-a0f7756015e5.dmp (834.8 KB)
console-2022-12-03-04.26.21-201d4e55-bc29-4c76-8e2f-a0f7756015e5.log (164.3 KB)
crash_dump-2022-12-03-04.16.27-96b1c87a-20e9-48a9-9dc0-82ee22bc546d.dmp (816.6 KB)
console-2022-12-03-04.16.27-96b1c87a-20e9-48a9-9dc0-82ee22bc546d.log (64.7 KB)
crash_dump-2022-12-03-03.49.30-fee037f5-781d-4d18-8639-01be996364e1.dmp (833.1 KB)
console-2022-12-03-03.49.30-fee037f5-781d-4d18-8639-01be996364e1.log (219.5 KB)
crash_dump-2022-12-03-03.45.29-dce43431-e5ec-49d6-a121-24b813d85443.dmp (846.5 KB)
console-2022-12-03-03.45.29-dce43431-e5ec-49d6-a121-24b813d85443.log (56.1 KB)
crash_dump-2022-12-03-03.01.37-0b7eadb2-afcd-4951-a2c9-34d204d228ff.dmp (817.7 KB)
Same as everyone above, i have crashed ten times in 2 hours, just started today, was fine and had a stable game during beta and launch. I have my drivers updated, meet min requirements and have tried several fixes to no avail
Looks like Iām 8 hours late to the party, I just looked at several log files and saw Windows 11 ābuild 22621ā too before scrolling up (started at the end) and seeign Dev response.
Yāall using āCore Isolationā ->Memory Integrity ON and Virtual Machine Platform?
Long shots but worth testing?
See Options to Optimize Gaming Performance in Windows 11 - Microsoft Support
Some of the other stuff in Settings , select System > Display > Graphics > Change default graphics settings.
I have Auto-HDR on for instance, all on.
Edit 1:
I also see many āVirtual Adapterā , grasping at straws here. Iād suggest turning Wi-Fi off if hard wired, and even disable the virtual adapter(s) to trouble shoot.
FWIW, those HyperV related virtual adapters have caused me trouble in the past in other games like Borderlands 2 and Division 2, in Win10.
Could it be because of Windows 11? Saw a reddit thread that someone who switched back to Windows 10 hasnt had a crash yet, im not really trying to do that if there is another way
This would be the case, I have a dual setup using both W11 and W10. Till now playing Darktide on W10 very stable for me, on W11 will have 1-2 crashes per match.