Enshrouded
Vulcan device lost error in crash dump
So, i can't run the demo for some reason, keeps kicking me out saying it lost a Vulcan device. any idea how to fix this error?

Error here:
[E 00:00:06,224] [graphics] Vulkan device lost...
[E 00:00:06,224] no checkpoint data, NV_device_diagnostic_checkpoints is not enabled/supported (make sure you have renderdoc disabled!)
[E 00:00:06,224] Stopping process due to unrecoverable GPU crash!
< >
1630/30 megjegyzés mutatása
too. 1080ti 10900 :aaaaa:
Same issue 1080ti
Vega 64 here as well. Random CTD, though seems worse around the first tower. In the crash dump logs I am getting:

[W 00:05:35,099] [ecsc] Message Storage full, remove oldest server message tick 1,435,334 for message tick 1,435,398
[W 00:05:35,099] [ecsc] Message Storage full, remove oldest server message tick 1,435,335 for message tick 1,435,399
[W 00:05:35,099] [ecsc] Message Storage full, remove oldest server message tick 1,435,336 for message tick 1,435,400

...

[W 00:05:35,099] [ecsc] Message tick 1,435,280 older than oldest storage tick 1,435,338 - discard
[W 00:05:35,099] [ecsc] Message tick 1,435,280 older than oldest storage tick 1,435,338 - discard
[W 00:05:35,099] [ecsc] Message tick 1,435,281 older than oldest storage tick 1,435,338 - discard

...

[ecsp] tick - htick = 121, reset all ticks
[W 00:05:35,101] [ecsc] processMessage UpdateEntity: Entity 69,534 not found
[W 00:05:35,101] [ecsc] processMessage UpdateEntity: Entity 69,535 not found
[W 00:05:35,101] [ecsc] processMessage UpdateEntity: Entity 69,534 not found

...

[E 00:05:35,114] [graphics] Vulkan device lost...
[E 00:05:35,114] Stopping process due to unrecoverable GPU crash!


... = same messages repeating, next text is where the log continues with new data.

Almost seems like a memory handling issue in the graphics dedicated RAM. Possibly a memory leak in how vulkan is instructed to handle it's instructions. I don't know, I know just enough programming to be dangerous and nowhere near enough to figure this out.

Edit: reminds me of a buffer overflow exploit, but in this case accidental instead of malicious.
Legutóbb szerkesztette: Valdyr; 2024. jan. 27., 14:52
do not install the latest nvidia driver version 551.23, rollback install the driver before this. It worked for me
Did extensive testing with my vulkan drivers today. Found that manually uninstalling the drivers by moving the files from SysWOW64 folder to a backup location and then installing the Vulkan Runtime version 1.3.261.1 got my time between crashes up to 25 minutes between crashes (up from 10 min). It's not a fix but definitely better than it was before. Hoping for a fix from the devs soon, but until then this is what I've been able to find. Going to work on it more tomorrow.
Rethys eredeti hozzászólása:
Did extensive testing with my vulkan drivers today. Found that manually uninstalling the drivers by moving the files from SysWOW64 folder to a backup location and then installing the Vulkan Runtime version 1.3.261.1 got my time between crashes up to 25 minutes between crashes (up from 10 min). It's not a fix but definitely better than it was before. Hoping for a fix from the devs soon, but until then this is what I've been able to find. Going to work on it more tomorrow.

What files did you move exactly ?
My friend had an issue with Vulkan first starting up for the game, and I was able to find a fix. Here is what you do:

1) Ensure graphics driver is up to date
2) Open an command prompt (cmd)
3) Run the command vulkaninfo

Running the command should give you a ton of information. If it doesn't, or perhaps even if it does, check at the top right after the command was run for a list of errors and warnings. Ignore any errors about not finding JSON files.

- Check if there are any warnings about applications forcing Vulkan to run at a lower version. For each program that gives an issue, either update them or remove them until you get all the vulkan info and there are no more warnings about running at a lower version.

In my friend's case, his OBS was very out of date and it was forcing Vulkan 1.2 to run instead of 1.3 and he also had an old screen capture program that was forcing Vulkan 1.1 to run. Updating OBS and uninstalling the old program fixed his game immediately.
Guys, just restart your pc. Works wonders.

MY grandpa told me to do it, im not even surpised it worked
Kakarona eredeti hozzászólása:
Guys, just restart your pc. Works wonders.

MY grandpa told me to do it, im not even surpised it worked

no, restart does not help with this issue. I checked vulcan info with command above and also found warning with old OBS version as in above message, and uninstall OBS. Looks like this can help. Trying to check.
Legutóbb szerkesztette: Gother-ninja; 2024. jan. 28., 13:30
same problem here with 2070 super on win 11 with newest driver
Hello, it's getting annoying, I had a dump error yesterday. Nothing helped so I formatted everything and reinstalled it and it then ran for a few hours. It's Steam but the game is installed and today I get this message again, it can't be true. finally fixes this error and NO I don't have AMD
Same here, but my game crashes in random moments, not a specify action
Same, fix your game it work at one point !
just started getting these crashes last week.. I tried everything, updating vulken runtime and even sdk, checked video drivers, verified files in steam and so on... going through the crash logs near line 120 where "creating Vulkan Device" begins there is a list of "Found Vulkan Instance Layer" it uses to construct the renderer... i found these in the list -

[graphics] Found vulkan instance layer 'VK_LAYER_OBS_HOOK'

[graphics] Found vulkan instance layer 'VK_LAYER_ROCKSTAR_GAMES_social_club'

First I updated OBS (it was out of date)

Second I had to do a windows search for "Rockstar" (I had NO rockstar games installed) and found a backup folder i had on another drive that had a Rockstar Social Club folder.. inside were two different 'Renderer' folders that had old vulkan crap... deleted those

it has been 3 days now with NO crashes.. hope this helps some one, good luck gamers

check your crash log, near the top is where is this list can be found, look where it is finding these instance layers and track it down!
Hey guys,


I also have the same problem with an RTX 2070 on Windows 10.


I have a guess as to when this problem occurs. I recently switched completely to "fertilized farm soil" for obvious reasons. The flax grows exprem fast, it's a matter of a few minutes. I start planting the seedlings and when I get somewhere around 300, the game quits. This didn't happen with normal farm soil. And as other users have already described, the error goes away at the earliest when you restart the computer. However, if the plants are still growing, the game immediately shuts down again.


I hope this helps you with troubleshooting.

BR
Ingeborg

EDIT:
In the meantime, the error has also occurred. I started a private game and then went back to the server. That worked.
Legutóbb szerkesztette: Ingeborg; 2024. febr. 11., 5:38
< >
1630/30 megjegyzés mutatása
Laponként: 1530 50

Közzétéve: 2023. okt. 9., 22:33
Hozzászólások: 30