Would anybody be willing to try deleting their DirectX Shader Cache via Disk Clean-up, to see if this resolves the issue?
You can do this by:
Disk Clean-upDirectX Shader Cache (as pictured below)
Nothing even with this one… I think it’s related to the update, since it was working fine this morning.
I also reinstalled the game, deleting the various folders that aren’t removed automatically.
In my case, it didn’t work. In any case, I also checked other games (Vermintide 2, Diablo 4, DRG)… they all run without issues.
I guess I’ll be going back to Deep Rock Galactic for a couple of months :\
Would you (or anybody else reading this) be willing to try enabling the DirectX Debug Layer, and sharing the corresponding console log with us?
This would really help in our investigation, but I appreciate it’s a hassle!
All the solutions proposed here have been tested after a clean, new installation and we haven’t achieved anything. We’ll have to wait for Fatshark to fix this problem. The levels of complexity that would require deeper repair attempts are beyond my abilities, and I trust that the development team will be quick so as not to spoil the excitement of the new features.
Omnisiah be praised
I completely agree.
Honestly, this is the first time I’ve had to provide so many explanations for an issue they introduced themselves.
I want to point out that I appreciate the effort of a couple of people here on the forum, but unfortunately, after all these years, I can clearly see that their tech team is significantly weaker and much less “responsive” compared to the Vermintide team, which has always been far more effective in resolving similar issues.
I’m not expecting a fix anytime soon … probably not before two months. In the meantime, we’ll just play some DRG and HD2, which still seem to be working 
Crash - After Building Shader Cache
I start the game from Steam and the launcher appears. When I click play the shaders load, the screen goes black and then crashes. I have cleared the shaders, verified game install, and reinstalled the game onto a different SSD without fixing the issue.
No, I don’t use mods
Constant (100%)
PC - Steam
[Engine Error]: HRESULT: 0x80070057 = E_INVALIDARG, assert: shader '#ID[8860321b]'
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
Do you think they can afford to leave us without a product we’ve paid for and that was working until a few hours ago for two months?
I would be very surprised by such gross negligence, not to mention the contempt it shows for customers and the damage to the product’s and the studio’s image.
The truth is, I expect a solution within a few hours; any other timeframe wouldn’t be reasonable.
I completely understand the concern. For transparency, this is a particularly complex crash that we haven’t yet been able to reproduce on our end. When cases like this arise, we do sometimes have to call upon our amazing community to help us investigate which in turn speeds up a resolution. 
Yes, after this update, I encountered the same problem and error code. At first, I thought it was caused by my mod, but it wasn’t until I removed the mod and reinstalled the game twice that I realized it was a game issue. Everything was normal before this update. My graphics card is RTX2060. I also tried all the methods in the post, but none of them worked.
Log File:
Info Type:
[Engine Error]: HRESULT: 0x80070057 = E_INVALIDARG, assert: shader '#ID[8860321b]'
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
console-2026-03-18-13.13.55-c8f0dead-f1e5-426f-99bf-e290f906a483.log (15.2 KB)
darktide_launcher.log (828.0 KB)
user_settings.config (1.3 KB)
Hi all, we’ve identified that this crash occurs due to an incompatibility on older versions of Windows 10.
We’re working on addressing this in a hotfix, and I’ll update here as soon as I know which version this will be.
ID3D12Device::CreateVertexShader: Shader must be vs_6_4, vs_6_3, vs_6_2, vs_6_1, vs_6_0, vs_5_1, vs_5_0, vs_4_1, vs_4_0. Shader version provided: vs_6_5.
ID3D12Device::CreatePixelShader: Shader must be ps_6_4, ps_6_3, ps_6_2, ps_6_1, ps_6_0, ps_5_1, ps_5_0, ps_4_1, ps_4_0. Shader version provided: ps_6.5.
Log File:
Info Type:
[Engine Error]: HRESULT: 0x80070057 = E_INVALIDARG, assert: shader '#ID[8860321b]'
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
Yes the same happened to me that caused it not to be able to enter the game
As expected, they’ve made a mess of compatibility. The funny part is that the launcher initially checks and says the game is compatible (just like the official specs only mention Windows 10, without any reference to specific service packs or updates).
I stand by what I said earlier… we’ll be without the game for quite a while, and above all we’re in the hands of a completely inexperienced team compared to the one that delivered Vermintide 2.
I’m honestly speechless, disappointed, and at this point I’m just hoping for the next Vermintide chapter.
GG Darktide team …
A quick update to say this will be resolved in 1.11.2.
Log File:
Info Type:
[Engine Error]: HRESULT: 0x80070057 = E_INVALIDARG, assert: shader '#ID[8860321b]'
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
Still persists……..
still getting the error
Log File:
Info Type:
[Engine Error]: HRESULT: 0x80070057 = E_INVALIDARG, assert: shader '#ID[8860321b]'
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
Yes, the patch this time is 1.11.1, not the 1.11.2 they mentioned. I’m curious how much longer we have to wait.
Good day, please clarify the planned release date for version 1.11.2