Game: NVIDIA RTX 5080 crashes with VK_ERROR_DEVICE_LOST during startup shader preparation #1491
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1491
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
Log
See attached
longshot_log.txtfrom Discord message 1572411746990161980. It identifies nightly-464-310e7c9d and the hardware/renderer context. The log's device-lost diagnostic suggests tryingRX_VK_PRESENT_QUEUE=0inlongshot_env.txtas 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=0changes the outcome.Files from the Discord report:
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=0tolongshot_env.txtbeside
longshot.exe, start the game as before, and tell us whether it still crashes at the start? That tells us whetherthe present queue is the cause on your RTX 5080.
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
.jsonfiles from theperf_pendingfolder; please add them if provided.