Error on load when NvLink is enabled

[sudolsky]

Hi,
I am having this error that is preventing me from starting Chaos Vantage. When I disable Nvlink/SLI it starts to work again. When I have Nvlink/SLI on it works in other applications but Vantage is the only one that is not working.
Does anyone had the same experience b4? I have 2x2080ti's on TR2970x with nvidia driver 512.15

Thanks for any advice.

Here is the debug_log.txt

Chaos Vantage v1.7.1 (build 1339879, hash f19ae267)
Build date: Apr.12.2022
Window initialized in 931.0 ms
NVIDIA driver version 512.15 detected.
Driver check warning: Driver 512.15 is newer than the latest tested version which is 497.29
System memory: 63.89 GB
Windows version is 10.0.22000.
Device #0: NVIDIA GeForce RTX 2080 Ti, 11049 MB (DevId=0x1E07, SubSysId=0x37151462)
Device #1: Microsoft Basic Render Driver, 0 MB (DevId=0x8C, SubSysId=0x0)
Using device #0 [2 nodes].
Base renderer initialized in 265.0 ms
Starting local HTTP command server on port 20702.
GUI initialized in 10.2 ms
Created ThreadManager for 48 threads
Loading 504 V-Ray plugins took 13 ms.
createStateObject call with D3D12_STATE_OBJECT_TYPE_RAYTRACING_PIPELINE took 909 milliseconds !
Creating raytracing pipeline state(s) took 910 ms.
new TextureManager time : 0.03 seconds
Initing denoiser took 352 ms.
new Scene time : 0.00 seconds
Creating output resources took 25 ms.
Scene cleared.
Gizmo geometry generated in 2 ms
Using 0 lights !
Using 49.88 Mbytes for shadow rays buffer on device 0.
Using 49.88 Mbytes for shadow rays buffer on device 1.
Updating GPU lights took 6 milliseconds to execute.
Copying geometry data to GPU took 2 ms, copy scheduling alone took 0 ms!
build schedule create buffers : 0 ms, build schedule command (CPU) : 0 ms, build schedule total : 0 ms
Build schedule : 16 ms; Build command (GPU) : 22 ms
BLAS schedule and build took 39 ms !
ERROR: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. (0x887A0005)

at vrdx::TLASWrapper::compactBLASesInternal:1189

This is either a bug or the system ran out of resources.

[Vladislav Vulchev]

Hi sudolsky,

Could you submit a support request here: https://support.chaos.com/hc/en-us/requests/new
We'll find a similar setup and try to reproduce the problem on our end.

[sudolsky]

Thanks Vlad ..I will

[npg]

We are only able to reproduce this on a machine with Windows 11 and the new 510+ driver series. The workaround is to downgrade to driver version 497. We're not sure what causes the issue. Could be a driver bug.