"Vulkan Device Lost"

[Holografix]

what does that error message mean? I get that message when a game crashes.

[Bad 💀 Motha]

Does the game support DX12? That would be another option to try.

Also what NVIDIA GPU Driver Version are you running?

If using 531.41, make sure to go download and install the 531.58 Hotfix Driver Update and see if that helps in any ways.

And also have you even looked in the actual game forums for said game to see if others have same issue and what all is said. Maybe they know something that works. Could be something you might have to edit in the setting file that saves your graphics settings for the game.

[Holografix]

Escrito originalmente por Bad 💀 Motha:

Does the game support DX12? That would be another option to try.

Also what NVIDIA GPU Driver Version are you running?

If using 531.41, make sure to go download and install the 531.58 Hotfix Driver Update and see if that helps in any ways.

And also have you even looked in the actual game forums for said game to see if others have same issue and what all is said. Maybe they know something that works. Could be something you might have to edit in the setting file that saves your graphics settings for the game.

1. how do you try DX12? the game just loads without an option to select DX11. i think it's DX12 native.
2. 531.41
3. i will check out the hotfix driver update, hadn't known there was one.

i have looked and posted n the youngblood forum, i offered my solution of Ray tracing set to OFF to enjoy the game, but no one has solved this crash issue. no one knows anything more than what i've provided here.

[Bad 💀 Motha]

Ok but you are using Vulkan API option right now, correct?
So change it to DX12 if that is an option.
I doubt it would have DX11, since that would not support Ray Tracing, DLSS, etc.

If the game doesn't have a launcher menu where you pick the graphics settings. Go into the game, then the graphics settings and look under Advanced and see if you can switch between Vulkan and DX12

[Holografix]

Escrito originalmente por Bad 💀 Motha:

Ok but you are using Vulkan API option right now, correct?
So change it to DX12 if that is an option.
I doubt it would have DX11, since that would not support Ray Tracing, DLSS, etc.

i should have been clearer: there is no Vulkan API select option, you hit play and the game loads into the main menu. there is no option to select different API's.

i havent seen it, but ill check again.

[Bad 💀 Motha]

Again, once at the main menu, go to settings, where you change all the graphics settings. Look for VULKAN or DX12

A game or driver is never going to say "Vulkan Device Lost" in Windows OS if the game was running using DX12

[Holografix]

Escrito originalmente por Bad 💀 Motha:

Again, once at the main menu, go to settings, where you change all the graphics settings. Look for VULKAN or DX12

A game or driver is never going to say "Vulkan Device Lost" in Windows OS if the game was running using DX12

no option to change API. no mention of DX12 or Vulkan, although the exe file for youngblood is: Youngblood_x64vk

[Bad 💀 Motha]

Ok after doing some searching; yes YoungBlood is Vulkan only. And it uses a more recent Vulkan which supports Ray Tracing (aka VH_KHR_ray_tracing extension). That could be an issue all its own, as this Vulkan w/ RT is so new, it most likely has its own issues (like what you are experiencing).

Hard to say if the game will ever be fixed regarding such bugs.
MachineGames is still intact, but has been acquired by Microsoft.
So not sure how that affects all of this moving forward.


Please refer to here for more info:
https://steamcommunity.com/app/1056960/discussions/0/

https://www.nvidia.com/en-us/geforce/guides/wolfenstein-youngblood-graphics-and-performance-guide/

[Heretic]

Escrito originalmente por Holografix:

what does that error message mean? I get that message when a game crashes.

Dunno, Vulkan relies on physical devices to pick logical devices. The message is too vague, but if you're losing these then you'll crash. It could be a context related error, but without more info.. who knows?

[Bad 💀 Motha]

It's simply a GPU Driver crash basically.

[Holografix]

Escrito originalmente por Bad 💀 Motha:

Ok after doing some searching; yes YoungBlood is Vulkan only. And it uses a more recent Vulkan which supports Ray Tracing (aka VH_KHR_ray_tracing extension). That could be an issue all its own, as this Vulkan w/ RT is so new, it most likely has its own issues (like what you are experiencing).

Hard to say if the game will ever be fixed regarding such bugs.
MachineGames is still intact, but has been acquired by Microsoft.
So not sure how that affects all of this moving forward.


Please refer to here for more info:
https://steamcommunity.com/app/1056960/discussions/0/

https://www.nvidia.com/en-us/geforce/guides/wolfenstein-youngblood-graphics-and-performance-guide/

thx for those links, but i've already looked at those before i made this thread.

Let me ask a question of you:

could it be an issue relating to a timeout problem? as in, the GPU driver crashes to "device lost" when it hits like a set time limit for performing functions. I've read about increasing time delay for program applications that would allow the GPU more time to process before it crashes?

see this quote:

A device lost can also be caused by an operation that takes too long. On windows, TDR will kick in and reset the driver, which will result on a device lost error.

[Bad 💀 Motha]

Well if it's a gpu time out issue, that can be a number of reasons.

> gpu timeout in OS is set too low

> unstable gpu driver either for that gpu or just for that game

> unstable gpu clocks

GPU TDR Delay can be changed via Windows Registry. I always set this a little higher for my own personal reasons.

https://manual.notch.one/0.9.23/en/docs/faq/extending-gpu-timeout-detection/

[Holografix]

Escrito originalmente por Bad 💀 Motha:

Well if it's a gpu time out issue, that can be a number of reasons.

> gpu timeout in OS is set too low

> unstable gpu driver either for that gpu or just for that game

> unstable gpu clocks

GPU TDR Delay can be changed via Windows Registry. I always set this a little higher for my own personal reasons.

https://manual.notch.one/0.9.23/en/docs/faq/extending-gpu-timeout-detection/

excellent. i'm glad we achieved mind meld.

Now, my only question is:
is adjusting GPU TDR delay via registry a safe practice? or will it brick my machine?

another question:
how can i find out if my GPU clocks are unstable?

[Bad 💀 Motha]

No it is safe to do that. Just restart Windows after changing anything to do with TDR in order for the changes you've made to apply.

Honestly I don't see why MS decided to lower the GPU timeout settings regarding that. They were set higher in Vista and Win7.

To test for GPU Clock instability I would test using a series for GPU benchmarks; such as latest version of 3DMark, Unigine Superposition, MSI Kombuster. All are good well known free-ware tools.

[Holografix]

Escrito originalmente por Bad 💀 Motha:

No it is safe to do that. Just restart Windows after changing anything to do with TDR in order for the changes you've made to apply.

Honestly I don't see why MS decided to lower the GPU timeout settings regarding that. They were set higher in Vista and Win7.

To test for GPU Clock instability I would test using a series for GPU benchmarks; such as latest version of 3DMark, Unigine Superposition, MSI Kombuster. All are good well known free-ware tools.

Thx, I appreciate all your work on this issue. I really do.

I will adjust the TDR and write about my findings in this thread. Hoping that's the solution.

[Holografix]

Escrito originalmente por Holografix:

Escrito originalmente por Bad 💀 Motha:

No it is safe to do that. Just restart Windows after changing anything to do with TDR in order for the changes you've made to apply.

Honestly I don't see why MS decided to lower the GPU timeout settings regarding that. They were set higher in Vista and Win7.

To test for GPU Clock instability I would test using a series for GPU benchmarks; such as latest version of 3DMark, Unigine Superposition, MSI Kombuster. All are good well known free-ware tools.

Thx, I appreciate all your work on this issue. I really do.

I will adjust the TDR and write about my findings in this thread. Hoping that's the solution.

I changed the GPU TDR following the instructions in the Notch page you linked, and no dice. Still crashes. GPU clocks are stable too.

i think it may be the Vulkan implementation in Youngblood.