Unpredictable Vulkan crashes with vk::Device::waitForFences: ErrorDeviceLost

Same issue.
Started with crucible league. Already got textures on lowest.
How there's no fix to this after a whole year is unimaginable imo.
i5-6600K 3.5GHz
16 GB RAM
GTX970

Same here. I only played a little last league but I don't remember having this error then but this league it's out of control.
In some cases I play 3-4h sessions without crashing but in other cases I crash every 5 minutes.

I set the textures to medium. Let's see if it helps.

Same Problem

bump still getting crashing.

I am playing on 5700XT, game runs great, but I get the exact same crashes.

On 2022 May drivers, game crashes with device lost error.
On newest 2023 drivers, whole computer hangs and i have to restart it using power button...

Same thing happens on Vulkan and DX12. Sometimes I can play for 4 hours and everything is fine, sometimes it starts crashing after 10 minutes.

These issues started 2 leagues ago, but currently its kinda bad.

Getting this error in the same spot every time.

Towards the start of the last room before final trial in merciless lab.

Have recreated it three times now.

Tilting as all hell.

Edit: Driver 512.15 for my Geforce RTX 3060.

Edit #2: Updating my driver to 531.79 fixed the issue.

I have to restart the game often, because the vulkan renderer is repeatedly crashing with vk::Device::waitForFences: ErrorDeviceLost.

I tried lowering GFX setting under the assumption that a lower texture count or indices might help, but the game is crashing regardless.
Any outside changes (driver, runtime, etc.) will not affect the issue.

The issue can not be fixed by
- setting GFX setting to lower values,
- updating GPU drivers,
- updating Vulkan Runtime,
- Windows updates,
- clearing (shader) caches.
Just saying.

It's a Vulkan render context issue = bug in the engine.
GGG's turn to fix this....

The game feels very buggy right now, not only due to the constant VK layer crashes. It also crashes in the default/fallback DX11 layer (but this is another issue).

Has GGG even responded with anything?

+1

Happening again after last patch.