Cycle Optix fails or crashes on viewport render #70937

New Issue

Eric Klein · 2019-10-19T04:29:58+02:00

Eric Klein commented

2019-10-19 04:29:58 +02:00

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-10-18 14:43, hash: 3de4446959
Worked: (optional)

Short description of error
Cycles Optix rendering on the viewport fails or crashes Windows 10. System console error:
OptiX CUDA error CUDA_ERROR_LAUNCH_FAILED in cuStreamSynchronize(cuda_stream[thread_index]), line 824
OptiX CUDA error CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]), line 824

F12 render image works fine and yesterday's build works fine. It is probably related to yesterday Cycles commit from Optix .

Exact steps for others to reproduce the error
To reproduce on default startup open Blender in preferences make sure Optix is selected. Switch render to Cycles and GPU Compute and now enable viewport rendering.

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30 **Blender Version** Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-10-18 14:43, hash: `3de4446959` Worked: (optional) **Short description of error** Cycles Optix rendering on the viewport fails or crashes Windows 10. System console error: OptiX CUDA error CUDA_ERROR_LAUNCH_FAILED in cuStreamSynchronize(cuda_stream[thread_index]), line 824 OptiX CUDA error CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]), line 824 F12 render image works fine and yesterday's build works fine. It is probably related to yesterday Cycles commit from [Optix ](https://developer.blender.org/D6068). **Exact steps for others to reproduce the error** To reproduce on default startup open Blender in preferences make sure Optix is selected. Switch render to Cycles and GPU Compute and now enable viewport rendering.

Eric Klein commented

2019-10-19 04:29:58 +02:00

Added subscriber: @eklein

cgslav commented

2019-10-19 16:44:07 +02:00

Added subscriber: @cgslav

cgslav commented

2019-10-19 16:44:07 +02:00

I have the same problem on Arch.
Also Blender is crashing in both ways:

Enable Viewport render > error> go to settings > switch to CUDA > Crash.
Enable Viewport render > error> F12 > Crash.

OptiX CUDA error CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]), line 824
OptiX error OPTIX_ERROR_INVALID_DEVICE_CONTEXT in optixDeviceContextCreate(cuda_context, &options, &context), line 250

I have the same problem on Arch. Also Blender is crashing in both ways: 1. Enable Viewport render > error> go to settings > switch to CUDA > Crash. 2. Enable Viewport render > error> F12 > Crash. OptiX CUDA error CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]), line 824 OptiX error OPTIX_ERROR_INVALID_DEVICE_CONTEXT in optixDeviceContextCreate(cuda_context, &options, &context), line 250

Patrick Mours was assigned by Brecht Van Lommel

2019-10-19 20:35:16 +02:00

Dave Stromberger commented

2019-10-20 06:38:19 +02:00

Added subscriber: @DaveStromberger

Jason Clarke commented

2019-10-21 02:59:07 +02:00

Added subscriber: @JasonClarke

Jason Clarke commented

2019-10-21 03:03:51 +02:00

Same issue on Windows 10 1903 + RTX 2070 here. CUDA is fine and F12 render is fine, viewport render with OptiX does not work. Tried both 436.30 and 436.48 drivers.

blender-admin commented

2019-10-21 14:22:24 +02:00

This issue was referenced by blender/cycles@16122909e7

This issue was referenced by blender/cycles@16122909e72884a8fc3c3e11cff7bc354db07461

blender-admin commented

2019-10-21 14:22:24 +02:00

This issue was referenced by d0cba5caf4

This issue was referenced by d0cba5caf464e18e8522c3f890cb1053631374c1

Patrick Mours commented

2019-10-21 14:24:23 +02:00

Changed status from 'Open' to: 'Resolved'

Patrick Mours closed this issue

2019-10-21 14:24:23 +02:00

Eric Klein commented

2019-10-21 15:50:30 +02:00

Patrick,

The fix was committed only to the release 2.81 branch, also please merge fix to the master.

Patrick, The fix was committed only to the release 2.81 branch, also please merge fix to the master.

Patrick Mours commented

2019-10-21 15:55:07 +02:00

Sorry, forgot. Done now!

Auracle commented

2020-08-02 04:04:23 +02:00

Added subscriber: @Auracle

Auracle commented

2020-08-02 04:04:23 +02:00

Changed status from 'Resolved' to: 'Archived'

Auracle commented

2020-08-02 04:04:23 +02:00

I still have the issue on the most recent experimental version of Blender and regular stable release.

Infos : I have a RTX 2060 with game-ready drivers up to date.

Replicable issue : Every time I open blender, put render mode in cycles, then use denoising in viewport, cycles renders in wireframe instead, then if I try to change any option on the viewport denoising, blender crash. Every time.

I still have the issue on the most recent experimental version of Blender and regular stable release. Infos : I have a RTX 2060 with game-ready drivers up to date. Replicable issue : Every time I open blender, put render mode in cycles, then use denoising in viewport, cycles renders in wireframe instead, then if I try to change any option on the viewport denoising, blender crash. Every time.

Auracle commented

2020-08-02 04:41:05 +02:00

I finally found the error.

The text "Loading render kernels (may take a few minutes the first time)" is really small, and I never noticed it.

After waiting like 4 minutes on my Ryzen 7 2700 it ended and everything works.
If you don't notice the text and you don't wait, anything you touch (Almost) will make blender totally crash. There's no error handling, even opening preferences makes blender go boom.

Found the issue, gotta fix it :) hope it helps everyone that reads this

I finally found the error. The text *"Loading render kernels (may take a few minutes the first time)"* is really small, and I never noticed it. After waiting like 4 minutes on my Ryzen 7 2700 it ended and everything works. If you don't notice the text and you don't wait, anything you touch (Almost) will make blender totally crash. There's no error handling, even opening preferences makes blender go boom. ![issue.png](https://archive.blender.org/developer/F8737308/issue.png) Found the issue, gotta fix it :) hope it helps everyone that reads this

Evan Wilson commented

2020-09-24 07:46:56 +02:00

Changed status from 'Archived' to: 'Resolved'

mike commented

2020-10-25 00:01:30 +02:00

Added subscriber: @bennybrady

mike commented

2020-10-25 00:01:30 +02:00

Same issue here - but waiting on the kernel doesn't fix it. Did you do anything else?

Thomas Dinges added this to the 2.81 milestone 2023-02-08 16:46:55 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycle Optix fails or crashes on viewport render #70937