Blender 2.90.1 crashing when OptiX viewport denoising is enabled #81116

Closed
opened 2020-09-24 02:11:51 +02:00 by Sedat Kanatli · 61 comments

System Information
Operating system: Win 10 Pro Version 10.0.19041 Build 19041
Graphics card: NVIDIA GeForce GTX 1070
CPU: AMD Ryzen 5 2600
RAM: 16 GB

Blender Version
Broken: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0, type: Release
Worked: unknown

Short description of error
When I choose Cycles, GPU Compute and the Viewport OptiX Denoiser is activated it crashes when i switch viewport to render. Blender window just abruptly closed. No error window from windows.

Exact steps for others to reproduce the error

  1. Set render engine to "Cycles"
  2. Set device to "GPU Compute"
  3. Set Viewport Denoiser to Automatic" or "OptiX"
  4. Set Viewport Shading to "Rendered"

szene.JPG

room.crash.txt
system-info.txt

**System Information** Operating system: Win 10 Pro Version 10.0.19041 Build 19041 Graphics card: NVIDIA GeForce GTX 1070 CPU: AMD Ryzen 5 2600 RAM: 16 GB **Blender Version** Broken: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: 3e85bb34d0d7, type: Release Worked: unknown **Short description of error** When I choose Cycles, GPU Compute and the Viewport OptiX Denoiser is activated it crashes when i switch viewport to render. Blender window just abruptly closed. No error window from windows. **Exact steps for others to reproduce the error** 1. Set render engine to "Cycles" 2. Set device to "GPU Compute" 3. Set Viewport Denoiser to Automatic" or "OptiX" 4. Set Viewport Shading to "Rendered" ![szene.JPG](https://archive.blender.org/developer/F8914033/szene.JPG) [room.crash.txt](https://archive.blender.org/developer/F8914029/room.crash.txt) [system-info.txt](https://archive.blender.org/developer/F8914030/system-info.txt)
Author

Added subscriber: @sedatk

Added subscriber: @sedatk

#84955 was marked as duplicate of this issue

#84955 was marked as duplicate of this issue

#83015 was marked as duplicate of this issue

#83015 was marked as duplicate of this issue

#82938 was marked as duplicate of this issue

#82938 was marked as duplicate of this issue

#82809 was marked as duplicate of this issue

#82809 was marked as duplicate of this issue

#82185 was marked as duplicate of this issue

#82185 was marked as duplicate of this issue

#82083 was marked as duplicate of this issue

#82083 was marked as duplicate of this issue

#81440 was marked as duplicate of this issue

#81440 was marked as duplicate of this issue

#81325 was marked as duplicate of this issue

#81325 was marked as duplicate of this issue

#81219 was marked as duplicate of this issue

#81219 was marked as duplicate of this issue

#81224 was marked as duplicate of this issue

#81224 was marked as duplicate of this issue

#81159 was marked as duplicate of this issue

#81159 was marked as duplicate of this issue

#81154 was marked as duplicate of this issue

#81154 was marked as duplicate of this issue
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

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

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

Are you able to try clearing your OptiX cache and trying again? This can be done by:

  1. Navigate to %LOCALAPPDATA%\NVIDIA\ (You can also find this folder manually by navigating to C:\Users\YOUR_NAME\AppData\Local\NVIDIA)
  2. Delete the folder called OptixCache
Are you able to try clearing your OptiX cache and trying again? This can be done by: 1. Navigate to `%LOCALAPPDATA%\NVIDIA\` (*You can also find this folder manually by navigating to `C:\Users\YOUR_NAME\AppData\Local\NVIDIA`*) 2. Delete the folder called `OptixCache`

Added subscriber: @RushDZN

Added subscriber: @RushDZN

I have the same problem, and I followed in your steps and the problem persists

I have the same problem, and I followed in your steps and the problem persists
Member

Added subscriber: @VstavitTekst

Added subscriber: @VstavitTekst
Member

Added subscriber: @pmoursnv

Added subscriber: @pmoursnv
Member

Sorry, I'm not sure exactly where to go from here. Maybe try a clean install of the latest GPU drivers (even if you're already running the latest drivers). https://www.nvidia.com/download/index.aspx?lang=en-us
Maybe resetting Blender settings then enabling the GPU again will help? To do this select from the top of Blender File -> Defaults -> Load Factory Settings then re-enable the GPU and test again.

For those where these suggestions did not help resolve the crashing, then I would like you to provide crash logs for me. This can be done by:

  1. Navigate to the installation location of Blender.
  2. Open the file blender_debug_log.cmd.
  3. Cause Blender to crash by enabling the OptiX denoiser.
  4. Now a window should pop up containing two files, upload both of them here.
  5. Along with those two files, upload the file blender.crash.txt found in your temp folder (I believe the default location is C:\Users\YOUR_NAME\AppData\Local\Temp)

You may also want to give Blender 2.91 a try, however, expect bugs as it's still in early development: https://builder.blender.org/download/

CC @pmoursnv As you seem to be heavily involved with the development of OptiX for Blender and this issue seems to only affect OptiX. I'm not sure there's much you can do at this current point in time, but I'm tagging you here so you can keep an eye on things.

Sorry, I'm not sure exactly where to go from here. Maybe try a clean install of the latest GPU drivers (even if you're already running the latest drivers). https://www.nvidia.com/download/index.aspx?lang=en-us Maybe resetting Blender settings then enabling the GPU again will help? To do this select from the top of Blender `File -> Defaults -> Load Factory Settings` then re-enable the GPU and test again. For those where these suggestions did not help resolve the crashing, then I would like you to provide crash logs for me. This can be done by: 1. Navigate to the installation location of Blender. 2. Open the file `blender_debug_log.cmd`. 3. Cause Blender to crash by enabling the OptiX denoiser. 4. Now a window should pop up containing two files, upload both of them here. 5. Along with those two files, upload the file `blender.crash.txt` found in your temp folder (I believe the default location is `C:\Users\YOUR_NAME\AppData\Local\Temp`) You may also want to give Blender 2.91 a try, however, expect bugs as it's still in early development: https://builder.blender.org/download/ CC @pmoursnv As you seem to be heavily involved with the development of OptiX for Blender and this issue seems to only affect OptiX. I'm not sure there's much you can do at this current point in time, but I'm tagging you here so you can keep an eye on things.
Alaska changed title from Blender Crash Cycles Denoise render view to Blender 2.90.1 crashing when OptiX viewport denoising is enabled 2020-09-25 10:42:44 +02:00
Member

Added subscriber: @JustinWebster

Added subscriber: @JustinWebster
Member

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

Changed status from 'Needs User Info' to: 'Resolved'
Alaska self-assigned this 2020-09-25 10:55:38 +02:00
Member

Upon further investigation I believe this issue is actually fixed. I will notify the developers for the release of 2.90.2

In Blender 2.91, 009971ba7a caused this kind of crashing. It was rolved by 9f12ea496a, however only the first patch made it into Blender 2.90.1. Applying the second patch to Blender 2.90.1, or using Blender 2.91 fixes the issue.

Upon further investigation I believe this issue is actually fixed. I will notify the developers for the release of 2.90.2 In Blender 2.91, 009971ba7a caused this kind of crashing. It was rolved by 9f12ea496a, however only the first patch made it into Blender 2.90.1. Applying the second patch to Blender 2.90.1, or using Blender 2.91 fixes the issue.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

This was caused by 009971ba7a, but fixed by 9f12ea496a.
The former is in 2.90.1 tha later isnt

This was caused by 009971ba7a, but fixed by 9f12ea496a. The former is in 2.90.1 tha later isnt
Member

Ah, we were typing at the same time @Alaska :)

Ah, we were typing at the same time @Alaska :)
Member

In #81116#1023022, @lichtwerk wrote:
Ah, we were typing at the same time @Alaska :)

:)

Although, looking back over this report, the issue seems to even occur when GPU compute is enabled. From my understanding 9f12ea496a is only for CPU rendering... Unless @sedatk only has their CPU selected in the compute device list... Or this is an entirely different crash.

> In #81116#1023022, @lichtwerk wrote: > Ah, we were typing at the same time @Alaska :) :) Although, looking back over this report, the issue seems to even occur when GPU compute is enabled. From my understanding 9f12ea496a is only for CPU rendering... Unless @sedatk only has their CPU selected in the compute device list... Or this is an entirely different crash.

Added subscriber: @carlos13eab

Added subscriber: @carlos13eab
Member

Added subscriber: @AnantRao

Added subscriber: @AnantRao
Member

Added subscriber: @AaronSmithey

Added subscriber: @AaronSmithey
Member

Added subscriber: @iDro040

Added subscriber: @iDro040
Member

Added subscriber: @aronkvh

Added subscriber: @aronkvh

Added subscriber: @SkyDan

Added subscriber: @SkyDan
Alaska was unassigned by Dan 2020-10-20 10:37:48 +02:00

Problem also persists with blender 90.1

Problem also persists with blender 90.1
Member

@SkyDan : yep 2.90.1 has this bug, please try a fresh 2.91 build from https://builder.blender.org/download/

@SkyDan : yep 2.90.1 has this bug, please try a fresh 2.91 build from https://builder.blender.org/download/

Added subscriber: @SuperGlix

Added subscriber: @SuperGlix

Can confirm, it's fixed in the last daily build (2.91.0, alpha, efc2edc47f, 10-20-2020). It completes denoising with no crash (CPU as render device).

Can confirm, it's fixed in the last daily build (2.91.0, alpha, efc2edc47f7a, 10-20-2020). It completes denoising with no crash (CPU as render device).

@SuperGlix Could confirm. It has been fixed in 2.91.0 alpha

@SuperGlix Could confirm. It has been fixed in 2.91.0 alpha

2.91.0 doesn't crash but blank render and : OPTIX_ERROR_INVALID_VALUE in optixdenoiserSetModel (denoiser, OPTIX_DENOISER_KIND_HDR,NULL,0) (device_optix.cpp:916)

openimagedenoise and gpu rendering work. (Kubuntu gtx 1070)

2.91.0 doesn't crash but blank render and : OPTIX_ERROR_INVALID_VALUE in optixdenoiserSetModel (denoiser, OPTIX_DENOISER_KIND_HDR,NULL,0) (device_optix.cpp:916) openimagedenoise and gpu rendering work. (Kubuntu gtx 1070)

Added subscriber: @rjg

Added subscriber: @rjg

@aronkvh Since this is a different error to what was reported in this ticket, please create a new report through Help > Report a Bug in Blender. Open a terminal in Blender's directory and run it with the following command. Try to reproduce the error and attach the log file to your report:

./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1
@aronkvh Since this is a different error to what was reported in this ticket, please create a new report through *Help > Report a Bug* in Blender. Open a terminal in Blender's directory and run it with the following command. Try to reproduce the error and attach the log file to your report: ``` ./blender --debug --debug-gpu > ~/blender_debug_output.txt 2>&1 ```

Added subscriber: @CapitanManzana

Added subscriber: @CapitanManzana
Member

Added subscriber: @olhapi

Added subscriber: @olhapi

Added subscriber: @john.stopforth

Added subscriber: @john.stopforth

I have same issue, with 2.9 the Renders were rock solid.

Upgraded to 2.9.1 with a new pc build and crash,

It seems to be a cycles issue when denoising is turned on (either automatic or optix)

image.png

I have same issue, with 2.9 the Renders were rock solid. Upgraded to 2.9.1 with a new pc build and crash, It seems to be a cycles issue when denoising is turned on (either automatic or optix) ![image.png](https://archive.blender.org/developer/F9119455/image.png)

@john.stopforth This issue was introduced in 2.90.1 and fixed in 2.91 which is currently in beta.

@john.stopforth This issue was introduced in 2.90.1 and fixed in 2.91 which is currently in beta.

Added subscriber: @augusto3691

Added subscriber: @augusto3691

i was with same error, upgraded to 2.91, works like a charm thanks!

i was with same error, upgraded to 2.91, works like a charm thanks!

Added subscriber: @PiloeGAO

Added subscriber: @PiloeGAO

Added subscriber: @robot_mitchum

Added subscriber: @robot_mitchum

Added subscriber: @DavideFrasca

Added subscriber: @DavideFrasca

Added subscriber: @justme-4

Added subscriber: @justme-4

Added subscriber: @merill

Added subscriber: @merill

It appears that error is back with 2.93

It appears that error is back with 2.93

Added subscriber: @Gurasis-Anand

Added subscriber: @Gurasis-Anand

I am having the same issue in 2.93 as well.

I am having the same issue in 2.93 as well.

@merill @Gurasis-Anand Please create new bug reports through Help > Report a Bug in Blender.

Open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

2019_12_04_upload_icon_developer_blender_org.png

@merill @Gurasis-Anand Please create new bug reports through *Help > Report a Bug* in Blender. Open Blender's installation directory and double click on the `blender_debug_gpu.cmd`. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt` (or simply type `%TEMP%` into the path bar of the Windows Explorer). ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Hi @rjg , may be there is a report already #88831 (Viewport denoising broken after NVIDIA driver update)

Hi @rjg , may be there is a report already #88831 (Viewport denoising broken after NVIDIA driver update)

@PratikPB2123 Could be, but that report is about a hang/freeze not a crash.

@merill @Gurasis-Anand If you are experiencing a hang/freeze as described in the other report you don't have to create a new ticket.

@PratikPB2123 Could be, but that report is about a hang/freeze not a crash. @merill @Gurasis-Anand If you are experiencing a hang/freeze as described in the other report you don't have to create a new ticket.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
16 Participants
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: blender/blender#81116
No description provided.