CUDA error with Optix denoising on shared CPU+GPU rendering (The error is appearing on 2.9 LTS, but not on Stable 3.0) #89521

New Issue

System Information
Operating system: Windows 10 (21H1)
Processor: i7-9700K
Graphics card: RTX 3070 (EVGA XC3 Ultra)

Blender Version
Broken:
2.93.1 Master Branch (Date: 2021-06-22 05:57, Hash: 1b8d33b18c)
2.93.2 Release Candidate (Date: 2021-06-28 02:28, Hash: 03d5c8b4ed)
3.0.0 Alpha, Master Branch (Date: 2021-06-28 02:48, Hash: 7223a0348f)

Worked: 3.0.0 stable

Short description of error
Initial render attempts will run properly, but subsequent rendering attempts will fail imminently with the error (Failed to create CUDA context (Illegal address)) after enabling Optix denoising. After that, all attempts to render in cycles fail with the same error mentioned above. However, Eevee rendering works just fine both before and after the glitch occurs.

Initial troubleshooting steps attempted:

Complete uninstall and reinstall of all blender versions listed.
Complete uninstall and reinstall of all Nvidia programs (Game ready drivers and studio drivers).
Toggled TMP 2.0 on and off in Bois.
Updated all drivers and firmware of the graphics card.
Confirmed that no overclocks were applied to the graphics card.
Tried to enable and disable Optix in settings.
Tried rendering with ReBar enabled and disabled.

All combinations attempted failed to fix the issue.

Exact steps for others to reproduce the error

Load up any file.
In the rendering options, Enable Optix denoising in the rendered view, and make sure that OPTIX rendering is enabled and selected in settings.
Let it attempt a complete single image render.
3a. If it succeeds, redo the render 2-3 times and see if it shows up (usually occurs on the second or third render)
Once the error appears, change the mode from OPTIX to CUDA. The render should still fail with the error mentioned above.

**System Information** Operating system: Windows 10 (21H1) Processor: i7-9700K Graphics card: RTX 3070 (EVGA XC3 Ultra) **Blender Version** Broken: 2.93.1 Master Branch (Date: 2021-06-22 05:57, Hash: 1b8d33b18c2f) 2.93.2 Release Candidate (Date: 2021-06-28 02:28, Hash: 03d5c8b4edf4) 3.0.0 Alpha, Master Branch (Date: 2021-06-28 02:48, Hash: 7223a0348f53) Worked: 3.0.0 stable **Short description of error** Initial render attempts will run properly, but subsequent rendering attempts will fail imminently with the error (Failed to create CUDA context (Illegal address)) after enabling Optix denoising. After that, all attempts to render in cycles fail with the same error mentioned above. However, Eevee rendering works just fine both before and after the glitch occurs. Initial troubleshooting steps attempted: - Complete uninstall and reinstall of all blender versions listed. - Complete uninstall and reinstall of all Nvidia programs (Game ready drivers and studio drivers). - Toggled TMP 2.0 on and off in Bois. - Updated all drivers and firmware of the graphics card. - Confirmed that no overclocks were applied to the graphics card. - Tried to enable and disable Optix in settings. - Tried rendering with ReBar enabled and disabled. All combinations attempted failed to fix the issue. **Exact steps for others to reproduce the error** 1. Load up any file. 2. In the rendering options, Enable Optix denoising in the rendered view, and make sure that OPTIX rendering is enabled and selected in settings. 3. Let it attempt a complete single image render. 3a. If it succeeds, redo the render 2-3 times and see if it shows up (usually occurs on the second or third render) 4. Once the error appears, change the mode from OPTIX to CUDA. The render should still fail with the error mentioned above.

Added subscriber: @x8a3vier

Under.blend
This is the file that it happens in. I did some further testing with other files I have along with stock ones I found online. So far it is only happening in this scene. I can't find anything amiss in any of the settings yet, but I need a fresh set of eyes to see if I am missing anything.

[Under.blend](https://archive.blender.org/developer/F10205834/Under.blend) This is the file that it happens in. I did some further testing with other files I have along with stock ones I found online. So far it is only happening in this scene. I can't find anything amiss in any of the settings yet, but I need a fresh set of eyes to see if I am missing anything.

Added subscriber: @OmarEmaraDev

Changed status from 'Needs Triage' to: 'Needs User Info'

Do you have the latest Nvidea drivers installed?
Can you try on the latest daily Blender version or the stable 3.0 version? https://builder.blender.org/download/daily/

Do you have the latest Nvidea drivers installed? Can you try on the latest daily Blender version or the stable 3.0 version? https://builder.blender.org/download/daily/

I did some more testing in the intermedium. All Nvidia drivers were updated then and are currently updated. The error doesn't appear in blender 3.0 with stock settings (as far as I have been able to tinker so far). I found that the error would come up whenever you do rendering in 2.8 and 2.9 with the following things:

CPU and GPU shared rendering enabled (Shared rendering)
cycles rendering
Optix denoise enabled.

After the initial appearance of the error, all rendering attempts with evee and Workbench also fail with the same error message and will only resolve after either restarting blender or restarting my PC. I haven't been able to test it in blender 3.0 due to tinkering with the new enhancements. I'll do some testing with the release branch of blender 3.01 later tonight (in around ~10 hours from now).

I did some more testing in the intermedium. All Nvidia drivers were updated then and are currently updated. The error doesn't appear in blender 3.0 with stock settings (as far as I have been able to tinker so far). I found that the error would come up whenever you do rendering in 2.8 and 2.9 with the following things: - CPU and GPU shared rendering enabled (Shared rendering) - cycles rendering - Optix denoise enabled. After the initial appearance of the error, all rendering attempts with evee and Workbench also fail with the same error message and will only resolve after either restarting blender or restarting my PC. I haven't been able to test it in blender 3.0 due to tinkering with the new enhancements. I'll do some testing with the release branch of blender 3.01 later tonight (in around ~10 hours from now).

I did some more testing @OmarEmaraDev

The error is appearing on 2.9 LTS, but not on Stable 3.0. The shared rendering appears to be the root of the problem. If I only have rendering enabled on the GPU, the rendering goes fine. The error is only appearing if CPU and GPU are enabled for Optix rendering.

I did some more testing @OmarEmaraDev The error is appearing on 2.9 LTS, but not on Stable 3.0. The shared rendering appears to be the root of the problem. If I only have rendering enabled on the GPU, the rendering goes fine. The error is only appearing if CPU and GPU are enabled for Optix rendering.

Changed status from 'Needs User Info' to: 'Needs Triage'

Added subscriber: @PratikPB2123

The error is appearing on 2.9 LTS, but not on Stable 3.0.

> The error is appearing on 2.9 LTS, but not on Stable 3.0.

Added subscriber: @Peter-Sampson

HI, does this still happen in 2.93.16?: https://builder.blender.org/download/daily/
If yes, please share logs files: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#windows

HI, does this still happen in 2.93.16?: https://builder.blender.org/download/daily/ If yes, please share logs files: https://docs.blender.org/manual/en/dev/troubleshooting/crash.html#windows

Any updates here?

Just tested it. It is still happening in the daily build for April 09, 05:34:38 1668424eef. Same reproduction steps. I would recommend disabling CPU rendering whenever the user tries to use optix rendering. The program does not crash out, but subsequent renders will fail. A full system reboot is the only consistent fix I have seen that works.

Just tested it. It is still happening in the daily build for April 09, 05:34:38 1668424eef81. Same reproduction steps. I would recommend disabling CPU rendering whenever the user tries to use optix rendering. The program does not crash out, but subsequent renders will fail. A full system reboot is the only consistent fix I have seen that works.

blender_debug_output.txt

1.4 KiB

blender_system_info.txt

26 KiB

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

CUDA error with Optix denoising on shared CPU+GPU rendering (The error is appearing on 2.9 LTS, but not on Stable 3.0) #89521