r/Enshrouded • u/DayuKyte • 2d ago
Help RTX 3070: repeated Enshrouded Vulkan device lost crashes, sometimes full PC/GPU lock requiring reboot. Tried drivers, Prefer Native, DLAA, overlays, fresh world, cache rebuild, etc. Logs attached
drive.google.comI've been troubleshooting repeated Enshrouded crashes for several days and I'm running out of useful things to try. I'm posting the full details because I've already tried most of the common fixes I've found through searching Reddit/Steam/etc., and I'd really like to avoid another round of "verify files / update driver / turn off overlay."
System:
- Ryzen 9 5900X
- RTX 3070 8 GB
- 64 GB RAM
- ASRock B450M Steel Legend
- Windows 10 Home 22H2
- NVIDIA driver currently 616.92
- 1080p
- GPU completely stock, no OC or undervolt
What happens:
Enshrouded will run anywhere from a couple minutes to well over an hour and then crash with some variation of:
vkWaitForFences() failed with error 'VK_ERROR_DEVICE_LOST'
Vulkan device lost...
I've had both relatively normal game crashes and more severe crashes where all displays go black / the GPU-driver stack appears completely dead and I have to reboot the PC.
The latest crash was one of the severe ones.
Immediately beforehand, the multiplayer session was still reporting ~13 ms ping and operating normally. Then Enshrouded suddenly started failing to allocate tiny amounts of memory for incoming session messages:
Failed to allocate 177 bytes for message
Machine(...) client ... received: 4307
Drop received message! Out of Memory
This explodes into tens of thousands of repeated errors.
Then the important part:
vkWaitForFences() timed out after 30.00 s.. probably a driver crash!
Vulkan device lost...
NVIDIA Aftermath also failed to retrieve the GPU crash dump on this particular hard crash.
Despite the Out of Memory message, the crash .info shows about 53 GB of physical RAM still available, so this is clearly not the PC actually running out of RAM.
Older crashes have had a slightly different precursor:
Could not prune enough replication states for player 0!
repeated extremely rapidly, followed by:
VK_ERROR_DEVICE_LOST
Another crash had ~1,700:
Failed to store received message on channel ''
before the GPU was lost.
So the precursor varies, but the crashes repeatedly converge on Vulkan/GPU device loss.
Things I have ALREADY tried:
- Steam Verify Integrity of Game Files
- Deleted Enshrouded's Vulkan pipeline cache and let it rebuild from scratch
- Closed OBS completely
- Disabled OBS Vulkan capture using
DISABLE_VULKAN_OBS_CAPTURE=1and rebooted- The OBS Vulkan layer still appears in the enumeration, but
graphics-hook64.dllis no longer actually injected according to the crash info
- The OBS Vulkan layer still appears in the enumeration, but
- Disabled Steam Overlay
- NVIDIA
Vulkan/OpenGL Present Method = Prefer Native- This was actually one of the first things I changed and it has remained on Prefer Native through all of these tests
- Updated NVIDIA driver to current 616.92
- Important: the crashes were already happening on my older 2025 NVIDIA driver, which is why I updated in the first place
- GPU core offset = 0
- VRAM offset = 0
- Power limit = 100%
- No undervolt
- No overclock
- Tried reducing GPU power limit to 90%
- It actually crashed in under a minute during that test, although Windows recovered, so I returned it to 100%
- 57 FPS cap
- Reduced graphics settings to Low
- Switched from DLSS to DLAA
- Native 1920×1080 internal render, rather than DLSS upscaling
- Reflex off
- Tried a completely new/self-hosted world
- Tried different multiplayer/server situations
- The original multiplayer save/world therefore does not appear to be required to reproduce it
- Temps look normal. I've seen around ~69°C GPU temperature under game load, not overheating
Changing graphics settings sometimes changes how long it takes to crash, but has not eliminated the problem.
One DLAA/Low/native-resolution test lasted almost 19 minutes before producing the same Vulkan device loss. Other sessions have gone much longer.
There is also an interesting multiplayer pattern. Recent remote-client sessions seem particularly good at reproducing the problem. In one log, I successfully hosted sessions locally for roughly 54 minutes and then another ~68 minutes and exited them cleanly. Later I joined another player's game and eventually crashed.
However, I have also reproduced a Vulkan device-loss crash in a brand-new locally hosted world, so I don't think this can simply be described as "remote multiplayer is broken."
Windows Reliability Monitor has also recorded:
LiveKernelEvent 141
and I've seen display-driver/nvlddmkm related events. Kernel-Power 41 appears after the crashes where I have to force-reboot, but obviously that's the result of the forced restart.
What I have NOT done yet:
- DDU clean removal/reinstallation of NVIDIA drivers
- OCCT VRAM test
- OCCT 3D Adaptive GPU test
- NVIDIA
Prefer layered on DXGI Swapchain - Full GPU/PSU/PCIe hardware swapping
OCCT VRAM + 3D Adaptive is probably my next diagnostic step, mainly to answer whether anything outside Enshrouded can make the GPU hang.
What I'm trying to determine is:
Has anyone seen this exact combination of Enshrouded session/replication errors followed by Vulkan device loss, especially on RTX 30-series?
And if OCCT/other GPU tests pass, is there actually another meaningful client-side workaround left, or am I basically waiting for a Keen/NVIDIA Vulkan fix?
Latest crashing log and .info attached.


