I have three PCs with the same specs, but one of them is giving me trouble

[TobiJesco]

Hey guys,

I have a problem. I have three new nodes (3 nodes, each with two 5090s); two of them are running perfectly, but one keeps giving me trouble…

Here’s my log:

=======================================================
Error
=======================================================
Error: Renderer returned non-zero error code, -536870911. Check the log for more information.
   at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)

=======================================================
Type
=======================================================
RenderPluginException

=======================================================
Stack Trace
=======================================================
   at Deadline.Plugins.SandboxedPlugin.d(DeadlineMessage bgw, CancellationToken bgx)
   at Deadline.Plugins.SandboxedPlugin.RenderTask(Task task, CancellationToken cancellationToken)
   at Deadline.Slaves.SlaveRenderThread.c(TaskLogWriter aka, CancellationToken akb)

=======================================================
Log
=======================================================



I deleted some parts because there was too much code—there weren't any errors before, but now some errors are popping up: 




2026-06-08 19:18:46:  0: STDOUT: Progress: 75%
2026-06-08 19:18:46:  0: STDOUT: Progress: 76%
2026-06-08 19:18:46:  0: STDOUT: Progress: 77%
2026-06-08 19:18:46:  0: STDOUT: Progress: 78%
2026-06-08 19:18:46:  0: STDOUT: Progress: 79%
2026-06-08 19:18:46:  0: STDOUT: Progress: 80%
2026-06-08 19:18:46:  0: STDOUT: Progress: 81%
2026-06-08 19:18:46:  0: STDOUT: Progress: 83%
2026-06-08 19:18:46:  0: STDOUT: Progress: 84%
2026-06-08 19:18:46:  0: STDOUT: Progress: 85%
2026-06-08 19:18:46:  0: STDOUT: Progress: 86%
2026-06-08 19:18:46:  0: STDOUT: Progress: 87%
2026-06-08 19:18:46:  0: STDOUT: Progress: 88%
2026-06-08 19:18:46:  0: STDOUT: Progress: 89%
2026-06-08 19:18:46:  0: STDOUT: Progress: 90%
2026-06-08 19:18:46:  0: STDOUT: Progress: 91%
2026-06-08 19:18:46:  0: STDOUT: Progress: 92%
2026-06-08 19:18:46:  0: STDOUT: Progress: 93%
2026-06-08 19:18:46:  0: STDOUT: Progress: 95%
2026-06-08 19:18:46:  0: STDOUT: Progress: 96%
2026-06-08 19:18:46:  0: STDOUT: Progress: 97%
2026-06-08 19:18:46:  0: STDOUT: Progress: 98%
2026-06-08 19:18:46:  0: STDOUT: Progress: 99%
2026-06-08 19:18:46:  0: STDOUT: Progress: 100%
2026-06-08 19:18:46:  0: STDOUT: Progress: 7%
2026-06-08 19:18:46:  0: STDOUT: Progress: 14%
2026-06-08 19:18:46:  0: STDOUT: Progress: 21%
2026-06-08 19:18:46:  0: STDOUT: Progress: 28%
2026-06-08 19:18:46:  0: STDOUT: Progress: 35%
2026-06-08 19:18:46:  0: STDOUT: Progress: 42%
2026-06-08 19:18:46:  0: STDOUT: Progress: 50%
2026-06-08 19:18:46:  0: STDOUT: Progress: 56%
2026-06-08 19:18:46:  0: STDOUT: Progress: 64%
2026-06-08 19:18:46:  0: STDOUT: Progress: 71%
2026-06-08 19:18:46:  0: STDOUT: Progress: 78%
2026-06-08 19:18:46:  0: STDOUT: Progress: 85%
2026-06-08 19:18:46:  0: STDOUT: Progress: 92%
2026-06-08 19:18:46:  0: STDOUT: Redshift Debug: Renderer: Render End
2026-06-08 19:18:46:  0: STDOUT: Redshift Debug: Summary: Profile: Update:00:01.306 (00:00.112/00:00.463/00:00.729/00:00.001) Render:02:25.531 (00:21.055/00:00.112) Output:00:00.000 Total:02:26.838
2026-06-08 19:18:56:  0: STDOUT: Redshift Debug: Freeing GPU mem...(device 0)
2026-06-08 19:18:56:  0: STDOUT: Redshift Debug: 	Done (CUDA reported free mem before: 5218 MB, after: 29014 MB)
2026-06-08 19:18:56:  0: STDOUT: Redshift Debug: Freeing GPU mem...(device 1)
2026-06-08 19:18:56:  0: STDOUT: Redshift Debug: 	Done (CUDA reported free mem before: 5098 MB, after: 27820 MB)
2026-06-08 19:19:04:  0: STDOUT: Rendering frame 13 at <Mon Jun  8 19:19:04 2026>
2026-06-08 19:19:04:  0: STDOUT: Progress: 0%
2026-06-08 19:19:06:  0: STDOUT: Rendering Phase: Setup
2026-06-08 19:19:06:  0: STDOUT: Progress: 0%
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Scanning Scene
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Frame 13: Update Start
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Lights
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Environment
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Scanning Materials
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Materials
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Extracting Geometry
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Objects
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:06:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Updating Transforms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Updating Geometry
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Preparing for Rendering
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Registering Objects
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: Summary: Lights:2 Meshes:6302 Instances:5088 PointClouds:0 MatOverrides:2544 Proxies:0 ProxyInstances:0 Volumes:0 TraceSets:0
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Status: Frame 13: Update Completed
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Renderer: Render Begin
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: License for net.maxon.license.app.bundle_cinema4d_rs-release~commercial valid until Jul 04 2026
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: =================================================================================================
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: Rendering frame 13...
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: AMM enabled
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: =================================================================================================
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	  0ms
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: Device 0 (NVIDIA GeForce RTX 5090) uses OptiX RT for ray tracing
2026-06-08 19:19:07:  0: STDOUT: Redshift Info: Device 1 (NVIDIA GeForce RTX 5090) uses OptiX RT for ray tracing
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Preparing ray tracing hierarchy for meshes
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Time to process 6 meshes:   0ms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Time to check if textures need reloading: 0.138094 seconds
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Using streamed texture page cache.
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Processing 26 textures
2026-06-08 19:19:07:  0: STDOUT: Progress: 3%
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Time to process textures: 0.005475 seconds
2026-06-08 19:19:07:  0: STDOUT: Progress: 0%
2026-06-08 19:19:07:  0: STDOUT: Progress: 25%
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Preparing materials and shaders
2026-06-08 19:19:07:  0: STDOUT: Progress: 50%
2026-06-08 19:19:07:  0: STDOUT: Progress: 75%
2026-06-08 19:19:07:  0: STDOUT: Progress: 90%
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Time to process all materials and shaders: 0.001026 seconds
2026-06-08 19:19:07:  0: STDOUT: Progress: 100%
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Time to process 6318 mesh attribute formats: 0.003961 seconds
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Pre-processing for Tesselation Free Displacement
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Time: 1ms
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Freeing OIDN denoise related buffers
2026-06-08 19:19:07:  0: STDOUT: Progress: 0%
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Freeing VRAM because of an OptiX denoiser/RT reset
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Freeing RT related buffers
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 	Freeing stack allocator
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:07:  0: STDOUT: Redshift Debug: Initializing OIDN denoiser
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: Forcing render-time tessellation/displacement
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: Allocating GPU mem...(device 0)
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 	Done (Allocator size: 26113 MB. CUDA reported free mem before: 29014 MB, after: 27606 MB)
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: Allocating GPU mem...(device 1)
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 	Done (Allocator size: 25038 MB. CUDA reported free mem before: 27820 MB, after: 23212 MB)
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: Finished render-time tessellation/displacement. Time: 103ms
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: Initializing OptiX RT, 
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 	Freeing stack allocator
2026-06-08 19:19:08:  0: STDOUT: Redshift Debug: 	[Device 0, 1] will rebuild everything
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	OptiX RT initialized on device 0 (appears to use 2578 MB)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	OptiX RT initialized on device 1 (appears to use 2578 MB)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Time: 6109ms
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: Allocating GPU mem...(device 0)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Done (Allocator size: 23793 MB. CUDA reported free mem before: 26436 MB, after: 22212 MB)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: Allocating GPU mem...(device 1)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Done (Allocator size: 22718 MB. CUDA reported free mem before: 25242 MB, after: 19738 MB)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: Preparing ray tracing hierarchy for deferred meshes
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Time to process 2 meshes:   3ms
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: Ray Tracing Hierarchy Info:
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Max depth: 128. MaxNumLeafPrimitives: 8
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Extents: (-42525.347656 -1708.358154 -31991.210938) - (11419.445312 1293.202515 12795.841797)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Time to create tree: 13 ms (5 7 0)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: Preparing Tesselation Free Displacement for rendering
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Time: 0ms
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: Rendering blocks... (resolution: 2560x3675, block size: 512, unified minmax: [16,8192])
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	[9] Allocating memory for device 0 (NVIDIA GeForce RTX 5090)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 		Redshift can use up to 23793 MB
2026-06-08 19:19:14:  0: STDOUT: Rendering Phase: Main Render
2026-06-08 19:19:14:  0: STDOUT: Progress: 0%
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 		Geo: 0 MB, Tex: 3034 MB, Rays: 4262 MB, NRPR: 786432
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 		Done! (0.3s). Compute API reported free mem: 2642 MB
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	[9] Allocating memory for device 1 (NVIDIA GeForce RTX 5090)
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 		Redshift can use up to 22718 MB
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 		Geo: 0 MB, Tex: 3034 MB, Rays: 4262 MB, NRPR: 786432
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 		Done! (0.1s). Compute API reported free mem: 2350 MB
2026-06-08 19:19:14:  0: STDOUT: Redshift Debug: 	Pre-streaming and uploading out-of-core textures (they fit in GPU memory cache):
2026-06-08 19:19:15:  0: STDOUT: Redshift Debug: 		Device 0 completed.
2026-06-08 19:19:15:  0: STDOUT: Redshift Debug: 		Device 1 completed.
2026-06-08 19:19:15:  0: STDOUT: Redshift Debug: 	Time to pre-stream and upload all out-of-core textures: 0.7026 seconds
2026-06-08 19:19:15:  0: STDOUT: Redshift Debug: 	OptiX msg: [ERROR]: Error recording wait on outstanding request event ( T = 21, H = 187 ) (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
2026-06-08 19:19:15:  0: STDOUT: Failed to allocate internal launch buffer
2026-06-08 19:20:52:  0: INFO: Process exit code: -536870911
2026-06-08 19:20:52:  0: Done executing plugin command of type 'Render Task'

=======================================================
Details
=======================================================
Date: 06/08/2026 19:20:56
Frames: 10-14
Elapsed Time: 00:00:10:32
Job Submit Date: 06/08/2026 18:34:25
Job User: tobias.wendling
Average RAM Usage: 32959055872 (33%)
Peak RAM Usage: 39685582848 (39%)
Average CPU Usage: 14%
Peak CPU Usage: 74%
Used CPU Clocks (x10^6 cycles): 12119195
Total CPU Clocks (x10^6 cycles): 86565684

=======================================================
Worker Information
=======================================================
Worker Name: RENDER31
Version: v10.4.2.3 Release (d44a43016)
Operating System: Windows 11 Pro
Running As Service: No
Machine User: CG
IP Address: 192.168.100.124
MAC Address: 30:C5:99:82:18:41
CPU Architecture: x64
CPUs: 32
CPU Usage: 0%
Memory Usage: 36.0 GB / 95.6 GB (37%)
Free Disk Space: 7.136 TB (3.497 TB on C:\, 3.638 TB on D:\)
Video Card: Microsoft Remote Display Adapter

_________________________________________

I also don’t understand why “Video Card” is referred to as a “remote display adapter”…

I also asked ChatGPT and Claude. They all think that maybe one of the cards is causing problems. Does anyone have any ideas?

I updated the drivers, uninstalled Deadline from my PC, and reinstalled it…

Thanks <3

[anthonygelatka]

OptiX msg: [ERROR]: Error recording wait on outstanding request event ( T = 21, H = 187 ) (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)

Have you tried setting the GPU affinity on the worker, this may help narrow down which card is at fault

Do all machines have exactly the same driver?
Do they all have exactly the same RS version?

Does the issue persist if you submit single frames as tasks rather than batches?

[TobiJesco]

Hey, thanks for the reply.

Yeah, I have the same RS version and driver version on all my machines.

How do I select the affinity? I have 16 GPUs in the list even though I only have two cards installed… Is that normal?

I’m at a loss; I keep getting this message… It just happened again right now…

Really weird.

[jarak]

Disclaimer: I had the ai.bot clean up the phrasing so it would be easier to read than my usual word salad.

If you want to just test RENDER31 and isolate the GPUs one at a time, I’d try these steps:

Submit copies of the same job with Job Environment Variables set to:

CUDA_VISIBLE_DEVICES=0

then again with:

CUDA_VISIBLE_DEVICES=1

(and 2, 3, etc. if the machine has more GPUs)

This exposes only one physical GPU to Redshift at a time. If one version consistently crashes while the others complete, you’ve likely identified the problematic GPU.

For example, on one of our workstations:

nvidia-smi

PS C:\WINDOWS\system32> nvidia-smi
Mon Jun 15 16:15:05 2026
±----------------------------------------------------------------------------------------+
| NVIDIA-SMI 595.79                 Driver Version: 595.79         CUDA Version: 13.2     |
±----------------------------------------±-----------------------±---------------------+
| GPU  Name                  Driver-Model | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 3090      WDDM  |   00000000:19:00.0 Off |                  N/A |
| 95%   73C    P2            314W /  350W |   22581MiB /  24576MiB |     98%      Default |
|                                         |                        |                  N/A |
±----------------------------------------±-----------------------±---------------------+
|   1  NVIDIA GeForce RTX 3090      WDDM  |   00000000:68:00.0  On |                  N/A |
| 98%   79C    P2            270W /  350W |   22581MiB /  24576MiB |     97%      Default |
|                                         |                        |                  N/A |
±----------------------------------------±-----------------------±---------------------+

GPU 0 → Bus ID 19:00.0
GPU 1 → Bus ID 68:00.0

Typically, CUDA_VISIBLE_DEVICES=0 will expose only GPU 0 from the nvidia-smi output, and CUDA_VISIBLE_DEVICES=1 will expose only GPU 1.

You can verify the mapping using Device Manager:

Display Adapters → NVIDIA RTX xxxx → Properties → General

Example:

Location: PCI slot 72 (PCI bus 25, device 0, function 0)

PCI bus 25 (decimal) = Bus 19 (hex)
device 0 = the 00 in 19:00.0
function 0 = the .0 in 19:00.0

Example mapping:

nvidia-smi GPU 0 → Bus ID 19:00.0 → PCI bus 25, device 0, function 0
nvidia-smi GPU 1 → Bus ID 68:00.0 → PCI bus 104, device 0, function 0

While the render is running, monitor with:

nvidia-smi

to confirm that only the expected GPU is being utilized.

Redshift may renumber the visible CUDA devices, so Redshift’s GPU 0 is not always the same thing as nvidia-smi GPU 0.

For this test:

• Uncheck “Override GPU Affinity” in the Worker properties
• Do not set REDSHIFT_GPUDEVICES
• Run a scene long enough to reproduce the issue (a short test frame may not expose an intermittent hardware problem)

If one CUDA_VISIBLE_DEVICES setting consistently fails while the others succeed, you’ve narrowed the problem down to a specific GPU and/or its PCIe slot.

[anthonygelatka]

In the Deadline Worker options it lists all possible available GPU numbers, you should be safe to leave ‘Specify Number of GPU’s’ to 0 (this will use all GPU’s). Then just check either GPU0 or GPU1 which will chose either first or second card.

What maybe easier is to test outside of Deadline with the Redshift benchmark.

Open Command Promt (CMD) and run either

C:\Programdata\Redshift\bin\RunBenchmark.bat

or (newer versions)

C:\Program Files\Maxon Redshift 2026\bin\RunBenchmark.bat

If you run this it will download the benchmark Vultures scene

and begin a render on BOTH cards. I imagine this will fail

You can grab the benchmark scene here
https://s3.amazonaws.com/s3.redshift3d.com/public/benchmark/RedshiftBenchmarkScenes.zip

I placed that here C:\RedshiftBenchmarkScenes\vultures\Vultures.rs

To check each card independently use this command

“C:\Program Files\Maxon Redshift 2026\bin\redshiftCmdLine.exe” -listdevices

This will list devices including your CPU, use the following command to test each card indepently (set the path to the benchmark scene or use your own)

“C:\Program Files\Maxon Redshift 2026\bin\redshiftCmdLine.exe” “C:\RedshiftBenchmarkScenes\vultures\Vultures.rs” -device 0

the -device option was previously -gpu, this will depend on your vesion of RS.

You can then test with each GPU and CPU

“C:\Program Files\Maxon Redshift 2026\bin\redshiftCmdLine.exe” “C:\RedshiftBenchmarkScenes\vultures\Vultures.rs” -device 0 -device 1 -device 2