Hello. I have been encountering this issue in VT2 recently. I would like to seek for your assistance regarding this matter. This suddenly happened after I installed the small patch that was recently introduced. I am not sure if that affected my issue, but just letting you know.
Additionally, I have uninstalled using DDU and installed using the latest drivers. Still crashes.
Attached is the console log and the crash report.
Thank you very much.
[PC] Do You Use Mods? (Optional):
Yes, and Iâve tried disabling them
Reproduction Rate (Required):
Often (<75%)
Platform (Required):
Steam (PC)
[PC] Crash Report (Optional):
GUID: 6e3d2893-381c-4e50-abb8-9b0e4520c869
Log File:
Info Type:
At D:\a\d\vt2-stingray\vt2\release\release_hon_2025_03_18_skulls\runtime\d3d12_render_device\d3d12_debug.cpp:482 in function stingray::aftermath::ensure
NVIDIA drivers have also been a little unstable recently, and although driver versions 576.80 and 576.88 have shown better stability, weâre still monitoring the situation. Itâs possible that thereâs some correlation to Steam overlay use, while playing Vermintide 2, which may be triggering GPU crashes - but we havenât been able to fully confirm this.
If youâre on latest drivers, please try disabling the Steam overlay and check how stability goes. Otherwise, you could try rolling back to an older driver version, before 576.40, which may be more stable.
Hello. Thanks for your swift response. After checking the possible solutions, I tried the one wherein I needed to lower my Working Thread Count to 6, as it was set to 21 (!!) on my end. I set mine to 12. Doing that did the trick and I was able to finish a map. Will lower further if I encountered more crashes.
Since we are here, I would also like to ask some additional questions:
1.) I had a CTD issue back then and the solution I got was going to user_settings.config and setting the adapter index to 1. However, whenever I logout of the game, this value changes to 0 automatically. Is there any way to permanently save and set this to 1? It is kind of a hassle to go to this file and set it to 1 every time I want to play the game.
2.) With regards to the DXGI error, is that an issue specifically with the drivers? Iâm ruling out the possibility of a hardware issue due to the fact that the laptop I play with is new and I have stressed-test the hell out of it with zero issues. I would probably hold off rolling back to the older stable drivers because the newest ones have increased performance via increased wattage output for 50-series cards.
No worries glad that lowering worker threads seems to have helped with stability!
Regarding your questions:
1) A couple of things you can try!
In the Vermintide 2 launcher settings, check what options you have available for âDisplayâ. It may be that it shows âDisplay 1â as an option twice; as youâre on a laptop with integrated graphics, so hopefully setting to the alternate Display 1 option will default to your NVIDIA 5090 instead of Intel Graphics.
Ensure that both Steam and Vermintide 2 are set to use your dedicated GPU within the NVIDIA Control Panel by:
Right-click the desktop and select the âNVIDIA Control Panelâ
Navigate to âManage 3D Settingsâ > âProgram Settingsâ
Locate Steam within the list of programs
Within the âSelect the preferred graphics processor for this program:â dropdown, choose the NVIDIA GPU
Then locate Vermintide 2 within the list of programs, and repeat the above step
2) We canât say for certain, but any crashes that include DXGI_ERROR_DEVICE_REMOVED, or DXGI_ERROR_DEVICE_HUNG or similar should be GPU-related. As you have a fresh system itâs less likely to be a hardware issue (though there can be rare cases), and more likely drivers or settings. For example, lowering your Worker Thread count directly affects your CPU. This is where things can get a bit muddy, as CPU issues can still result in GPU crashes, or crashes that appear with the same error No problem sticking with latest drivers though - 576.80 and 576.88 have definitely been more stable than the three versions prior.
Hopefully stability will remain improved for you now Please let me know how things go!
Upon checking the VT2 launcher, there is only one âDisplay 1â option on the list, which suggests that my iGPU isnât selected. In fact, I have already went ahead into BIOS the moment I got my laptop to disable Nvidia Optimus and just force it to use my discrete GPU instead. I also have finished doing the settings under Nvidia Control Panel before posting here. Since the iGPU wasnât selected in my BIOS earlier, there is no dropdown list in my control panel, meaning that all my programs have been running on my 5090 ever since. After all of that though, I still do not know why my user.config setting gets reset every time I launch my game, which is my issue atm.
Good to know about the CPU error sometimes appearing as a GPU crash. Itâs incredibly convoluted as to why it happens and I just wish we didnât have to deal with them as consumers. But then again, the moment we chose PC as our platform already sealed our fate it seems.
Hello again. Just checked, and it wasnât set as read-only already (unchecked) so Iâm still flabbergasted as to why this is happening. Are there any other possible solutions I could try out?
Just curious, when you exit Vermintide 2, do you close the game via menu options or Alt+F4 out? Itâs possible, if you were using Alt+F4 that your settings could not be being saved correctly on game close.
If thatâs not the case, perhaps you could use the âRead-onlyâ setting to your advantage. If you enable Read-only for your user_settings.config file with your adapter_index setting set as 1; perhaps this will then retain the value. The only downside to this, is that to change any other game-related settings you will need to disable Read-only to allow your config file to be editable again.
I never use ALT + F4 when closing games, as I am aware of issues that may arise when doing so. Itâs not only VT2 that gets affected by it. Other games as well.
GUID: 6864e089-5a19-48e2-8432-81dca737f1bb
Log File:
Info Type:
[Engine Error]: No screens connected to current adapter âIntel(R) Graphicsâ. Make sure the game is using the correct adapter/GPU and that the screens are connected to it.
At D:\a\d\vt2-stingray\vt2\release\release_hon_2025_03_18_skulls\runtime\application\rendering\render_interface.cpp:1726 in function stingray::RenderInterface::apply_user_settings
Edited post reads below:
Needless to say, I cannot use the read-only function. By the way, I tried launching the game with the adapter value set to zero, and the game worked, but after some time, itâll crash right back to desktop and the DXGI error will appear yet again. Setting the value to one fixes this, but like mentioned, it is cumbersome to deal with editing a config file every time I want to play the game. Maybe you could pass this issue to your developers and theyâll think of a way so that it doesnât interfere with it anymore? Kind of sounds simple, but tricky to pull off in action.
Resulting in: 18:08:24.481 <<Crash>>No screens connected to current adapter 'Intel(R) Graphics'. Make sure the game is using the correct adapter/GPU and that the screens are connected to it.
So, this suggests that your GPU adapters may have switched; so youâll want to set the adapter_index to 0 instead. You mentioned this working, but a GPU crash still occurring after some time. I recommend to check our general GPU crash solutions again - perhaps your Worker Threads could still need tweaking further, and that though 6 is more stable, there may be a more optimal setting needed for your system. Iâd experiment by changing up/down in small increments.
As this is also occurring with other games, itâs likely to be a local issue - some muddle with the laptop dual-GPU configuration. Past the suggestions weâve already tried though, weâre admittedly stumped at what else to suggest
That is indeed strange. I will see what I can do with the Worker Threads and play with them around to hopefully find the optimal settings on my end. At this point in time, thatâs the route Iâll take that makes the most sense to me.
I appreciate your help and support regarding this matter. Iâll make a new thread in case something new pops up.
You may now close this thread. Thank you very much!
glad that lowering worker threads seems to have helped with stability!
No problem sticking with latest drivers though - 576.80 and 576.88 have definitely been more stable than the three versions prior.
Please let me know how things go!
thanks for checking!