[web] Repeatable NVIDIA Vulkan Ray Tracing Crash – RTX 4060 Laptop / Driver 617.42 / Slipstream 1.4.1.1 #1070

New issue

Open

opened 2026-10-25 19:48:13 +00:00 by slipstream-reports · 0 comments

slipstream-reports commented

2026-10-25 19:48:13 +00:00

Collaborator

Source: website form (slipstreamviewer.org/report.html)

Reporter (avatar name as given; not verified):

(not given)

System

Version: 1.4.1.1
OS: Windows 11 Home 64-bit
GPU: NVIDIA RTX 4060 Laptop 8GB - Driver 617.42

Description

Hello Slipstream Development Team,

I would like to report a reproducible crash affecting Slipstream Viewer 1.4.1.1 when Vulkan ray tracing is enabled on my NVIDIA RTX 4060 Laptop GPU.

System specifications:

Viewer: Slipstream Release 1.4.1.1

Operating System: Windows 11 Home 64-bit

Laptop: MSI Katana 17 B13VFK

CPU: Intel Core i7-13620H

GPU: NVIDIA GeForce RTX 4060 Laptop, 8 GB VRAM

NVIDIA Driver: 617.42

RAM: 16 GB DDR5

Display: 3840 × 2160 (4K), 165 Hz

Graphics API: Vulkan 1.4.351

Upscaling: FSR Quality (1.5x)

Problem description:

Slipstream initially ran successfully with Vulkan ray tracing enabled, delivering approximately 40–50 FPS.

After installing ReShade 6.8.0 with Vulkan support, the viewer began crashing unexpectedly.

I initially suspected ReShade, but completely uninstalling it through the official ReShade installer did not resolve the crashes.

Windows Reliability Monitor consistently reports the following error:

Faulting application: SlipstreamViewer.exe
Application version: 1.4.1.1
Faulting module: nvgpucomp64.dll
Module version: 32.0.16.1742
Exception code: 0x80000003
Fault offset: 0x0000000000589eb2

The same module, exception code, and fault offset appeared across multiple crashes.

Troubleshooting performed:

Tested Slipstream with ray tracing enabled.

Installed ReShade 6.8.0 using Vulkan.

Experienced repeated application crashes.

Completely uninstalled ReShade.

Confirmed that the crashes continued without ReShade.

Set RenderVKAsyncCompute = 0, but the crashes persisted.

Set RenderVKRayTracing = 0 and restarted the viewer.

Current result:

With RenderVKRayTracing = 0, Slipstream has remained stable during initial testing.

This strongly suggests an issue involving the Vulkan ray tracing rendering path, although additional testing is needed to confirm the exact cause.

Additional findings from Slipstream.log:

The log contains several relevant entries:

Ray tracing was requested, supported, and enabled.

Ray-query pipeline compilation showed unusually high memory consumption.

One pipeline compilation batch reported approximately 7 GB of additional memory usage.

Vulkan reported VK_ERROR_OUT_OF_DEVICE_MEMORY during some geometry buffer allocations.

The viewer repeatedly crashed inside nvgpucomp64.dll.

The final crash stack trace identified nvgpucomp64.dll+0x589eb2.

I have retained the Slipstream.log file and can provide it for further investigation.

Questions:

Is this a known compatibility issue involving NVIDIA driver 617.42 and Vulkan ray tracing?

Could this be related to ray-query shader compilation or pipeline memory management?

Are there recommended settings that would allow me to use ray tracing without crashes?

Is a fix planned for an upcoming Slipstream release?

I really appreciate the work being done on Slipstream. Performance has been promising on my system, and I would love to continue using its advanced rendering features.

Thank you for your time and for investigating this issue.

Steps to reproduce

1. Launch Slipstream Viewer 1.4.1.1 on Windows 11 with NVIDIA driver 617.42.
2. Set RenderVKRayTracing = 1 and restart the viewer.
3. Log into Second Life and load a region using Vulkan and FSR Quality.
4. The viewer crashes unexpectedly after running for a short period.
5. Windows reports exception 0x80000003 in nvgpucomp64.dll, consistently at offset 0x589eb2.
6. Uninstalling ReShade 6.8.0 does not resolve the issue.
7. Setting RenderVKAsyncCompute = 0 does not resolve the issue.
8. Setting RenderVKRayTracing = 0 appears to prevent the crashes during initial testing.

Expected result: The viewer should remain stable with ray tracing enabled.

Actual result: Repeated crashes involving the NVIDIA shader compiler.

_{Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.}

**Source:** website form (slipstreamviewer.org/report.html) **Reporter** (avatar name as given; not verified): ~~~text (not given) ~~~ ### System ~~~text Version: 1.4.1.1 OS: Windows 11 Home 64-bit GPU: NVIDIA RTX 4060 Laptop 8GB - Driver 617.42 ~~~ ### Description ~~~text Hello Slipstream Development Team, I would like to report a reproducible crash affecting Slipstream Viewer 1.4.1.1 when Vulkan ray tracing is enabled on my NVIDIA RTX 4060 Laptop GPU. System specifications: Viewer: Slipstream Release 1.4.1.1 Operating System: Windows 11 Home 64-bit Laptop: MSI Katana 17 B13VFK CPU: Intel Core i7-13620H GPU: NVIDIA GeForce RTX 4060 Laptop, 8 GB VRAM NVIDIA Driver: 617.42 RAM: 16 GB DDR5 Display: 3840 × 2160 (4K), 165 Hz Graphics API: Vulkan 1.4.351 Upscaling: FSR Quality (1.5x) Problem description: Slipstream initially ran successfully with Vulkan ray tracing enabled, delivering approximately 40–50 FPS. After installing ReShade 6.8.0 with Vulkan support, the viewer began crashing unexpectedly. I initially suspected ReShade, but completely uninstalling it through the official ReShade installer did not resolve the crashes. Windows Reliability Monitor consistently reports the following error: Faulting application: SlipstreamViewer.exe Application version: 1.4.1.1 Faulting module: nvgpucomp64.dll Module version: 32.0.16.1742 Exception code: 0x80000003 Fault offset: 0x0000000000589eb2 The same module, exception code, and fault offset appeared across multiple crashes. Troubleshooting performed: Tested Slipstream with ray tracing enabled. Installed ReShade 6.8.0 using Vulkan. Experienced repeated application crashes. Completely uninstalled ReShade. Confirmed that the crashes continued without ReShade. Set RenderVKAsyncCompute = 0, but the crashes persisted. Set RenderVKRayTracing = 0 and restarted the viewer. Current result: With RenderVKRayTracing = 0, Slipstream has remained stable during initial testing. This strongly suggests an issue involving the Vulkan ray tracing rendering path, although additional testing is needed to confirm the exact cause. Additional findings from Slipstream.log: The log contains several relevant entries: Ray tracing was requested, supported, and enabled. Ray-query pipeline compilation showed unusually high memory consumption. One pipeline compilation batch reported approximately 7 GB of additional memory usage. Vulkan reported VK_ERROR_OUT_OF_DEVICE_MEMORY during some geometry buffer allocations. The viewer repeatedly crashed inside nvgpucomp64.dll. The final crash stack trace identified nvgpucomp64.dll+0x589eb2. I have retained the Slipstream.log file and can provide it for further investigation. Questions: Is this a known compatibility issue involving NVIDIA driver 617.42 and Vulkan ray tracing? Could this be related to ray-query shader compilation or pipeline memory management? Are there recommended settings that would allow me to use ray tracing without crashes? Is a fix planned for an upcoming Slipstream release? I really appreciate the work being done on Slipstream. Performance has been promising on my system, and I would love to continue using its advanced rendering features. Thank you for your time and for investigating this issue. ~~~ ### Steps to reproduce ~~~text 1. Launch Slipstream Viewer 1.4.1.1 on Windows 11 with NVIDIA driver 617.42. 2. Set RenderVKRayTracing = 1 and restart the viewer. 3. Log into Second Life and load a region using Vulkan and FSR Quality. 4. The viewer crashes unexpectedly after running for a short period. 5. Windows reports exception 0x80000003 in nvgpucomp64.dll, consistently at offset 0x589eb2. 6. Uninstalling ReShade 6.8.0 does not resolve the issue. 7. Setting RenderVKAsyncCompute = 0 does not resolve the issue. 8. Setting RenderVKRayTracing = 0 appears to prevent the crashes during initial testing. Expected result: The viewer should remain stable with ray tracing enabled. Actual result: Repeated crashes involving the NVIDIA shader compiler. ~~~ --- <sub>Filed by the Slipstream report relay. The reporter's identity is not verified; system details are as sent by the reporter.</sub>

slipstream-reports added the

from-viewer

triage

labels

2026-10-25 19:48:13 +00:00

slipstream-reports added this to the Slipstream project

2026-10-25 19:48:13 +00:00

No milestone

No project

No assignees

1 participant

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

sky_line/Slipstream#1070

No description provided.

Rows
Columns