CUDA Rendering Bug (and Fix) for Blender v2.80 RC2 to RC3 #67775

New Issue

Doug Fullerton · 2019-07-27T01:23:58+02:00

Doug Fullerton commented

2019-07-27 01:23:58 +02:00

System Information
Operating system: Windows 10 64-bit
Graphics card: Nvidia Titan X (Pascal)

Blender Version
Broken: v2.80 RC2
(example: 2.79b release)
(example: 2.80, edbf15d3c0, blender2.8, 2018-11-28, as found on the splash screen)
Worked: v2.80 RC3

Hello.  I was noticing while rendering the splash screen test files for "Splash279" with the character shooting a hairdryer that upon reaching the character's hair in rendering, I would hear system fans ramp down and the program forcibly close with no error.  Further in testing, I also saw that while rendering "The Butterfly's Sorrow" animation, in Frame 134, I would receive a red "CUDA ctxMemory" error or something related to CUDA processing that would simply halt the render.  It would not however, close the entire program.  Repeated runs of both scenes caused these issues in v2.80 RC2.

However, I did re-test both scenes and others with the newest release of Blender v2.80 RC3 and both scenes were able to complete successfully.  I am guessing something regarding keeping the CUDA pipeline full, flexibility on errors, or some other bug fix helped allow the previously broken files to now render correctly.

I am still seeing a modeling conflict with the desks in "Classroom" as those will not load in any version of v2.80 RC1, 2 or 3.  However using GPU+CPU compute renders the file of the room just fine.

Looking forward to release of v2.80.  Thank you.

**System Information** Operating system: Windows 10 64-bit Graphics card: Nvidia Titan X (Pascal) **Blender Version** Broken: v2.80 RC2 (example: 2.79b release) (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen) Worked: v2.80 RC3 ``` Hello. I was noticing while rendering the splash screen test files for "Splash279" with the character shooting a hairdryer that upon reaching the character's hair in rendering, I would hear system fans ramp down and the program forcibly close with no error. Further in testing, I also saw that while rendering "The Butterfly's Sorrow" animation, in Frame 134, I would receive a red "CUDA ctxMemory" error or something related to CUDA processing that would simply halt the render. It would not however, close the entire program. Repeated runs of both scenes caused these issues in v2.80 RC2. ``` ``` However, I did re-test both scenes and others with the newest release of Blender v2.80 RC3 and both scenes were able to complete successfully. I am guessing something regarding keeping the CUDA pipeline full, flexibility on errors, or some other bug fix helped allow the previously broken files to now render correctly. ``` ``` I am still seeing a modeling conflict with the desks in "Classroom" as those will not load in any version of v2.80 RC1, 2 or 3. However using GPU+CPU compute renders the file of the room just fine. ``` ``` Looking forward to release of v2.80. Thank you.

Doug Fullerton commented

2019-07-27 01:23:59 +02:00

Added subscriber: @The-Real-Link

Wayne Hawkins commented

2019-07-28 13:19:13 +02:00

Added subscriber: @WayneHawkins

Wayne Hawkins commented

2019-07-28 13:19:13 +02:00

Hi. I may have the same problem. If you try this and find it stable then we may be onto something. Try turning Denoising off. I have found with this off, all is stable. If left on I will get Blender crash when I use more than one video card. For me I have 3 X GTX 1080. If I render with one card and Denoising on, all is well. If with 2 or more it's not.

Something to do with Denoising - or so it seems on my testing.

Hi. I may have the same problem. If you try this and find it stable then we may be onto something. Try turning Denoising off. I have found with this off, all is stable. If left on I will get Blender crash when I use more than one video card. For me I have 3 X GTX 1080. If I render with one card and Denoising on, all is well. If with 2 or more it's not. Something to do with Denoising - or so it seems on my testing.

Doug Fullerton commented

2019-07-29 09:13:35 +02:00

Hello Wayne. I have not been able to re-test that yet with denoising off. However I did receive one other one-off CUDA error on something around frame 175. A simple close and relaunching of the program fixed this. I have not seen any other errors to date.

Sebastian Parborg commented

2019-08-09 15:16:27 +02:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-08-09 15:16:27 +02:00

Is this still and issue with the latest build from here? https://builder.blender.org/download/

We can't seem to be able to reproduce this.

Is this still and issue with the latest build from here? https://builder.blender.org/download/ We can't seem to be able to reproduce this.

Doug Fullerton commented

2019-08-10 00:12:59 +02:00

Hello Sebastian,

I found when Blender was crashing that it registered under Event Viewer's log as stating a Display Driver crash. I was originally running Nvidia 430.86 on my Titan X (Pascal). I have since updated Windows 10 to Ver. 1903, updated GFE, and updated the Display Driver to the Titan Studio release of 431.70 which is a couple months newer. It had no problem rendering the Splash279 benchmark scene. I would have to test repeatedly for sure but I am 99% positive it was just an older driver not playing nice with Blender v2.80 Final. Thanks.

Hello Sebastian, I found when Blender was crashing that it registered under Event Viewer's log as stating a Display Driver crash. I was originally running Nvidia 430.86 on my Titan X (Pascal). I have since updated Windows 10 to Ver. 1903, updated GFE, and updated the Display Driver to the Titan Studio release of 431.70 which is a couple months newer. It had no problem rendering the Splash279 benchmark scene. I would have to test repeatedly for sure but I am 99% positive it was just an older driver not playing nice with Blender v2.80 Final. Thanks.

Bastien Montagne commented

2019-08-20 11:26:37 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2019-08-20 11:26:37 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-08-20 11:26:37 +02:00

Bastien Montagne self-assigned this 2019-08-20 11:26:37 +02:00

Bastien Montagne commented

2019-08-20 11:26:37 +02:00

thanks, think we can consider this as driver issue in any case then.

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

CUDA Rendering Bug (and Fix) for Blender v2.80 RC2 to RC3 #67775