KNOWN ISSUE: Assertion failed! / Microsoft Visual C++ Runtime Library

HUA · April 26, 2024, 2:41pm

When I start Darktide, the event has an warning.
Event from DistributedCOM, event ID 10016.
LogName: System
From: Microsoft-Windows-DistributedCOM
Date: 2024/4/26 22:29:33
Event ID: 10016
任务类别: 无
级别: 警告
关键字: 经典
用户: HUA\HUA
计算机: HUA
描述:
应用程序-特定权限设置并未向在应用程序容器不可用 SID (不可用)中运行的地址 LocalHost (使用 LRPC) 中的用户 HUA\HUA SID (S-1-5-21-2360811839-4248678144-869857891-500)授予针对 CLSID 为
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
、APPID 为
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
的 COM 服务器应用程序的本地激活权限。此安全权限可以使用组件服务管理工具进行修改。
事件 Xml:

10016
0
3
0
0
0x8080000000000000

176024

System
HUA

应用程序-特定
本地
激活
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
HUA
HUA
S-1-5-21-2360811839-4248678144-869857891-500
LocalHost (使用 LRPC)
不可用
不可用

HUA · April 26, 2024, 2:45pm

It should have something to do with it, because when I tried to fix the problem and launch the game, the error message was changed.

Now the error report is:

Microsoft Visual C+ + Runtime Library
Assertion failed!
Program: .rhammer 40,000 DARKTIDE\binaries\DStorageCore.dll
File: C\ w\1\s\dstoragecore\ib\Request.cpp
Line: 1038

Expression: m_ state != Requestate::Completed

For information on how your program can cause an assertion
failure, see the Visual C+ + documentation on asserts

(Press Retry to debug the application - JIT must be enabled)

HUA · April 27, 2024, 4:40pm

In another pc,windows server 2022 version 20348.2113, I can play Darktide.
But in Windows server 2022 version 20348.2402, the error happened again.
I deployed Windows Server 2022, version 20348.2402 on a new hard drive, but the error still appeared.
Now, after re-installing Darktide and testing it, I will try to deploy Windows Server 2022, version 20348.2113 on a new hard drive.
I don’t know what this is about, I think it has something to do with Microsoft’s update. But I wonder why I can play almost any game including Vermintide2, except Darktide.

HUA · April 27, 2024, 4:41pm

Oh NO, I can’t play Darktide, I’m gonna die!

HUA · April 28, 2024, 6:29pm

Regardless of the Windows Server 2022 version, regardless of the graphics driver version, I installed Windows 11 on a different platform, Darktide started successfully, otherwise, no matter how I use Windwos Server 2022, this problem will occur, The other Windows Server 2022 does not have this problem.

Axloss · April 29, 2024, 6:05am

did you follow Julias advice how to turn direct storage off from settings? In the uploaded data if it contains all user settings it’s looks like you are lacking that setting.

If you did follow the advice, you can also try add the setting in the user config and then double click on the exe for ensure that the launcher doesnt override your changes somehow. (not sure if it does).

edit: the user_settings.config file i see has 68 rows.

Axloss · April 29, 2024, 6:10am

To clarify it feels like this should fix your issue, since it looks like this happens a few moments after the exe starts.

Axloss · April 29, 2024, 6:12am

check, I will forward this to microsoft since I’m going to ask them about some other direct storage issues.

FatsharkJulia · May 2, 2024, 1:51pm

FYI: We’ve updated the experimental build with improved logging.

Axloss · May 3, 2024, 2:02pm

update.

we’ve managed to reproduce this specific issue with the popup. What we’ve found out in our case is that if we initialize direct storage as if we were running on a HDD (even if it’s a SSD). Then we will be able to run the game without this error popup.

FatsharkJulia · May 7, 2024, 3:08pm

New instructions incoming…

FatsharkJulia · May 7, 2024, 3:08pm

We’ve put a number of changes on our experimental build, to address issues that have recently arisen with the ‘Path of Redemption’ update.

You may be recommended this build, if you are experiencing the issues below:

Fatal Error! Failed to read:
Assertion failed! / Microsoft Visual C++ Runtime Library
Stuttering, performance and sound issues
A specific start-up crash that presents after the shader cache has been built
NOTE: With this issue only, it is not necessary to perform the steps outlined in ‘Part 2’ or ‘Part 3’

Part 1: How Do I Switch to The `Experimental` Build?

Open the Steam client
Right-click Darktide in your Steam library
Select ‘Properties’
Select ‘Betas’
Enter the password cTYPtKTsfMDsLHAV
Select ‘Check Code’
Select the ‘None’ dropdown, and experimental - Experimental Builds should now be within the list
Select experimental - Experimental Builds
Close the pop-up window
A download should now start

Part 2: Setting Feature Flags

Navigate to your Darktide AppData by:

Press the Windows key + R
Enter %appdata% within the search input and select ‘OK’
Navigate to AppData\Roaming\Fatshark\Darktide

Open the user_settings.config
At the VERY TOP of the user_settings.config, enter the lines below:

direct_storage = {
    enabled = true
    disable_bypass_io = true
    force_file_buffering = true
    force_mapping_layer = false
}

Save your changes
Play!
Post here to let us know the outcome

NOTE: If you currently have disable_dstorage = true in your user_settings.config from previous instructions, please remove it and replace with the updated version above.

Part 3: Didn’t Work?

In the event the instructions above did not help with your issue, please try:

Navigate to your Darktide AppData by:

Press the Windows key + R
Enter %appdata% within the search input and select ‘OK’
Navigate to AppData\Roaming\Fatshark\Darktide

Open the user_settings.config
Remove the changes made previously
At the VERY TOP of the user_settings.config, enter the line below:

direct_storage = {
    enabled = false
}

Save your changes
Play!
Post here to let us know the outcome

NOTE: If you currently have disable_dstorage = true in your user_settings.config from previous instructions, please remove it and replace with the updated version above.

What Does the `Experimental` Build Include?

The ability to experiment with direct storage options in the user_settings.config, which are suspected to be causing a number of issues
Improved error reporting, including stall warnings to help us identify newly introduced performance issues
Changes to our PSOs, to identify certain start-up crashes that present after the shader cache has been built

To learn more about direct storage, please see: DSTORAGE_CONFIGURATION1 - Win32 apps | Microsoft Learn

FatsharkJulia · May 22, 2024, 8:31am

We have been made aware of a crash that can occur on startup for AMD users, when using the experimental build.

FatsharkJulia · May 22, 2024, 8:59am

We are now encouraging anybody playing on the experimental build that does not have performance issues, to revert to the live build.

If you are experiencing performance issues, please continue to use the experimental build as this contains important information on the stalls you’re experiencing.

The options to change direct storage are now supported in the live build, meaning you can make the changes below without using the experimental build.

It’s possible these changes will remain in place, so it’s possible no other action will be needed once you have switched builds.

For your information, we are looking at including these options within Darktide’s launcher, to make the process easier.

Part 1: Setting Feature Flags

Navigate to your Darktide AppData by:

Press the Windows key + R
Enter %appdata% within the search input and select ‘OK’
Navigate to AppData\Roaming\Fatshark\Darktide

Open the user_settings.config
At the VERY TOP of the user_settings.config, enter the lines below:

direct_storage = {
    enabled = true
    disable_bypass_io = true
    force_file_buffering = true
    force_mapping_layer = false
}

Save your changes
Play!
Post here to let us know the outcome

NOTE: If you currently have disable_dstorage = true in your user_settings.config from previous instructions, please remove it and replace with the updated version above.

Part 2: Didn’t Work?

In the event the instructions above did not help with your issue, please try:

Navigate to your Darktide AppData by:

Press the Windows key + R
Enter %appdata% within the search input and select ‘OK’
Navigate to AppData\Roaming\Fatshark\Darktide

Open the user_settings.config
Remove the changes made previously
At the VERY TOP of the user_settings.config, enter the line below:

direct_storage = {
    enabled = false
}

Save your changes
Play!
Post here to let us know the outcome

NOTE: If you currently have disable_dstorage = true in your user_settings.config from previous instructions, please remove it and replace with the updated version above.

Topic		Replies	Views
Error while starting DarkTide Technical Support acknowledged	1	24	October 7, 2024
Reinstall fails to start, shows blank error Technical Support need-more-info	4	25	September 26, 2024
Error 0xc0000142 on launch Technical Support acknowledged	4	393	December 1, 2022
GUID: 14cbf1bd-daca-4f87-a0ca-94c358fcbcff Log File: Info Type: ----------------------------------------------- ----------------------------------------------- [Crash Link]: crashify://14cbf1bd-daca-4f87-a0ca-94c358fcbcff Technical Support acknowledged	1	219	December 28, 2023
Error at launch after shader caching on Linux Technical Support acknowledged	4	800	May 21, 2024

KNOWN ISSUE: Assertion failed! / Microsoft Visual C++ Runtime Library

Part 1: How Do I Switch to The Experimental Build?

Part 2: Setting Feature Flags

Part 3: Didn’t Work?

What Does the Experimental Build Include?

Part 1: Setting Feature Flags

Part 2: Didn’t Work?

Related topics

Part 1: How Do I Switch to The `Experimental` Build?

What Does the `Experimental` Build Include?