protonscr

[Cyberpunk 2077] VK_ERROR_DEVICE_LOST after view map pressure on NVIDIA 580.x

vkd3dopen
HansKristian-Work/vkd3d-proton#2756 · opened 2025-12-16 by Heaven671 · updated 2025-12-16 · 3 comments · github
HHeaven671 2025-12-16 github

Cyberpunk 2077 crashes consistently with VK_ERROR_DEVICE_LOST on NVIDIA 580.x driver after 5-45 minutes of gameplay. The crash appears related to descriptor heap pressure ("Intense view map pressure" in logs). Hardware is confirmed stable via stress testing. Multiple workarounds attempted without success.

Software information

Cyberpunk 2077 (Steam, AppID 1091500)

System information

  • Arch Linux, kernel 6.17.9-zen
  • NVIDIA RTX 2080, driver 580.105.08
  • Ryzen 9 9950X3D, 96GB RAM
  • Proton Experimental / GE-Proton (both affected)

Problem

Game freezes with VK_ERROR_DEVICE_LOST after variable playtime (5-45 minutes depending on settings). GPU utilization drops from 99% to 1%.

Log shows

Intense view map pressure, recreating view maps (2048 -> 3072)
vkd3d_queue_wait_idle: vkQueueWaitIdle failed, vr -4 (VK_ERROR_DEVICE_LOST)

Tested workarounds (all still crash eventually):

  • VKD3D_CONFIG=no_upload_hvv (best result, ~45min before crash)
  • VKD3D_FEATURE_LEVEL=12_0
  • PROTON_HEAP_DELAY_FREE=1
  • PROTON_ENABLE_NVAPI=0
  • Ray Tracing OFF, lowest graphics settings
  • Driver downgrade failed (DKMS incompatible with kernel 6.17).

GPU stress test: gpu-burn 5 minutes, 0 errors - hardware is stable.

steam-1091500.log

HHansKristian-Work maintainer 2025-12-16 github

Intense view map pressure

This is completely benign. And 3k is nothing here. It's expected when RT is enabled.

HHeaven671 2025-12-16 github

Looking at the logs more closely, the crash happens ~14 seconds after "Intense view map pressure! Got 5120 views". Between the warning and the crash, there's no other error - just QueryInterface warnings which seem unrelated.

Timeline:

  • 1773.845: "Intense view map pressure! Got 5120 views"
  • 1788.417: "Failed to submit queue(s), vr -4" → VK_ERROR_DEVICE_LOST

This was with RT OFF and lowest settings. Is 5120 views still considered normal?

I can provide dmesg/kernel logs from the crash if that would help identify the driver-side failure.

HHeaven671 2025-12-16 github

Additional findings from further testing:

No kernel errors

No kernel/dmesg errors during the crash. The GPU device lost happens purely at Vulkan/userspace level - the NVIDIA kernel driver (580.105.08) doesn't report any fault or timeout.

System-wide freeze

The freeze affects the entire desktop, not just the game process. Mouse/keyboard become unresponsive for several seconds. This happens because the RTX 2080 handles display output - when the GPU hangs on a Vulkan operation, the entire system freezes.

Two behaviors observed

  1. Temporary freeze (few seconds) then recovery - no VK_ERROR_DEVICE_LOST
  2. Permanent freeze requiring process kill - VK_ERROR_DEVICE_LOST in logs

The driver's hang recovery seems inconsistent. Is there additional debug output I can enable to help narrow this down?

Proton versions

Launch options