Game: NVIDIA RTX 5080 crashes with VK_ERROR_DEVICE_LOST during startup shader preparation #1491

Open
opened 2026-11-18 00:45:16 +00:00 by BeanIssues · 3 comments
Collaborator

Reported on Discord

Longshot version and channel

Nightly-464 (source fcbd3219), per the attached log. Reporter says nightly 455 is the last one that works; the two subsequent nightlies crash.

System

Windows 11 Pro; AMD Ryzen 7 7800X3D; NVIDIA GeForce RTX 5080; driver 621.24.

What happened and steps

Launching the game consistently crashes during startup while shaders are being prepared. The reporter identifies nightly 455 as the last working build. The log shows the game progressed into rendering, then reports a lost GPU device:

[hos sead::MainThread] vk: device lost: reading the checkpoints
[hos sead::MainThread] vk: device lost: 1 checkpoints (2686 markers set)
[hos sead::MainThread] vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST): the driver stopped or reset the GPU, and nothing sent to it runs any more (on Linux, dmesg or journalctl -k around this time names the reset). The presents were on a queue of their own: RX_VK_PRESENT_QUEUE=0 in longshot_env.txt turns that off; please report your GPU and driver

Log

See attached longshot_log.txt from Discord message 1572411746990161980. It identifies nightly-464-310e7c9d and the hardware/renderer context. The log's device-lost diagnostic suggests trying RX_VK_PRESENT_QUEUE=0 in longshot_env.txt as a diagnostic workaround.

Still unknown

Exact build numbers of both failing nightlies, whether the crash occurs every launch, and the precise steps/timing before the crash. Please also confirm whether setting RX_VK_PRESENT_QUEUE=0 changes the outcome.

Reported on [Discord](https://discord.com/channels/1569849200047427645/1570984952651055114/1572405902613680209) ### Longshot version and channel Nightly-464 (source fcbd3219), per the attached log. Reporter says nightly 455 is the last one that works; the two subsequent nightlies crash. ### System Windows 11 Pro; AMD Ryzen 7 7800X3D; NVIDIA GeForce RTX 5080; driver 621.24. ### What happened and steps Launching the game consistently crashes during startup while shaders are being prepared. The reporter identifies nightly 455 as the last working build. The log shows the game progressed into rendering, then reports a lost GPU device: ```text [hos sead::MainThread] vk: device lost: reading the checkpoints [hos sead::MainThread] vk: device lost: 1 checkpoints (2686 markers set) [hos sead::MainThread] vk: FATAL: the GPU device was lost (VK_ERROR_DEVICE_LOST): the driver stopped or reset the GPU, and nothing sent to it runs any more (on Linux, dmesg or journalctl -k around this time names the reset). The presents were on a queue of their own: RX_VK_PRESENT_QUEUE=0 in longshot_env.txt turns that off; please report your GPU and driver ``` ### Log See attached `longshot_log.txt` from Discord message 1572411746990161980. It identifies nightly-464-310e7c9d and the hardware/renderer context. The log's device-lost diagnostic suggests trying `RX_VK_PRESENT_QUEUE=0` in `longshot_env.txt` as a diagnostic workaround. ### Still unknown Exact build numbers of both failing nightlies, whether the crash occurs every launch, and the precise steps/timing before the crash. Please also confirm whether setting `RX_VK_PRESENT_QUEUE=0` changes the outcome.
Author
Collaborator

Files from the Discord report:

Files from the Discord report: - [longshot_log.txt](https://git.magicbean.dev/attachments/0206d2d9-2dd8-4937-803b-06ce5a07c77d)
Member

Thanks. The log shows DLSS FG at 2x, V-Sync Auto, HDR on, and the presents on their own GPU queue, which nightly-458 turned
on by default for NVIDIA 621.24 (nightly-455 did not have it). Could you add RX_VK_PRESENT_QUEUE=0 to longshot_env.txt
beside longshot.exe, start the game as before, and tell us whether it still crashes at the start? That tells us whether
the present queue is the cause on your RTX 5080.

Thanks. The log shows DLSS FG at 2x, V-Sync Auto, HDR on, and the presents on their own GPU queue, which nightly-458 turned on by default for NVIDIA 621.24 (nightly-455 did not have it). Could you add `RX_VK_PRESENT_QUEUE=0` to `longshot_env.txt` beside `longshot.exe`, start the game as before, and tell us whether it still crashes at the start? That tells us whether the present queue is the cause on your RTX 5080.
Author
Collaborator

From Discord:

The reporter says an error appeared while shutting down the PC. The screenshot shows a Windows dialog titled “NVIDIA GeForce Overlay: NVIDIA Overlay.exe - Application Err...” with: “The exception Breakpoint / A breakpoint has been reached. / (0x80000003) occurred in the application at location 0x00007FFBB8D3967. / Click on OK to terminate the program”. This is NVIDIA Overlay.exe, not Longshot; whether it is related to the game's GPU crash is unknown. Another participant requested session logs and the .json files from the perf_pending folder; please add them if provided.

From [Discord](https://discord.com/channels/1569849200047427645/1570984952651055114/1572446809203408916): The reporter says an error appeared while shutting down the PC. The screenshot shows a Windows dialog titled “NVIDIA GeForce Overlay: NVIDIA Overlay.exe - Application Err...” with: “The exception Breakpoint / A breakpoint has been reached. / (0x80000003) occurred in the application at location 0x00007FFBB8D3967. / Click on OK to terminate the program”. This is NVIDIA Overlay.exe, not Longshot; whether it is related to the game's GPU crash is unknown. Another participant requested session logs and the `.json` files from the `perf_pending` folder; please add them if provided.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1491
No description provided.