Blender crashes when going into "rendered" viewport mode using cycles. #70490

New Issue

Keith Weatherby II · 2019-10-03T20:22:08+02:00

2019-10-03 20:22:08 +02:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449
Worked: (optional)

Short description of error
So essentially Blender 2.80 AND 2.81 crashes when I switched to rendered viewport mode using Cycles, after modifying the material on my object. Material(tab)->Settings->Surface->Displacement(Displacement and Bump)

Exact steps for others to reproduce the error
I'm going through a tutorial (Blender Guru's Beginner tutorial for 2.8 video level 2 part 4: Procedural displacement) so it has several steps. I don't remember it all, however, i'm going to go ahead and attach the actual blend file and to be able to reproduce the problem from the blend file, make sure the renderer is set to cycles, with sample size of 32 for both render and viewport. Then simply make sure Dispacement and Bump is set on the material tab as outlined above. And select "Rendered" viewport shading. It should start to render in cycles and go for a bit and then after less than a minute it should crash.

Donut_00001.blend

Here is the texture should be in the same folder/directory as the blend file

AS A QUICK UPDATE: It appears that if in the shading tab you change the scale in the displacement node from 1 to something really small like 0.001 it doesn't crash then. So presumably scale of 1 caused some super massive geometry that kills the GPU. In fact it won't crash in CPU mode.

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: (optional) **Short description of error** So essentially Blender 2.80 AND 2.81 crashes when I switched to rendered viewport mode using Cycles, after modifying the material on my object. Material(tab)->Settings->Surface->Displacement(Displacement and Bump) **Exact steps for others to reproduce the error** I'm going through a tutorial (Blender Guru's Beginner tutorial for 2.8 video level 2 part 4: Procedural displacement) so it has several steps. I don't remember it all, however, i'm going to go ahead and attach the actual blend file and to be able to reproduce the problem from the blend file, make sure the renderer is set to cycles, with sample size of 32 for both render and viewport. Then simply make sure Dispacement and Bump is set on the material tab as outlined above. And select "Rendered" viewport shading. It should start to render in cycles and go for a bit and then after less than a minute it should crash. [Donut_00001.blend](https://archive.blender.org/developer/F7787758/Donut_00001.blend) Here is the texture should be in the same folder/directory as the blend file ![Doughnut Tutorial Texture.png](https://archive.blender.org/developer/F7787791/Doughnut_Tutorial_Texture.png) **AS A QUICK UPDATE: It appears that if in the shading tab you change the scale in the displacement node from 1 to something really small like 0.001 it doesn't crash then. So presumably scale of 1 caused some super massive geometry that kills the GPU. In fact it won't crash in CPU mode.**

Keith Weatherby II commented

2019-10-03 20:22:08 +02:00

Added subscriber: @Uhfgood

Germano Cavalcante commented

2019-11-07 19:52:04 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-11-07 19:52:04 +01:00

I can't reproduce the crash in my GPU (OpenCL)

Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12028.2

I can't reproduce the crash in my GPU (OpenCL) **Operating system:** Windows-10-10.0.18941 64 Bits **Graphics card:** Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12028.2

Richard Antalik commented

2020-01-14 12:49:55 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-01-14 12:49:55 +01:00

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

Richard Antalik commented

2020-01-14 12:49:55 +01:00

@Uhfgood Is this still an issue with latest build? https://builder.blender.org/download/

Jacques Lucke commented

2020-01-21 13:45:22 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2020-01-21 13:45:22 +01:00

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

Jacques Lucke closed this issue

2020-01-21 13:45:22 +01:00

Jacques Lucke self-assigned this 2020-01-21 13:45:22 +01:00

Jacques Lucke commented

2020-01-21 13:45:22 +01:00

Closing because there has not been a response for a week. If you are still able to reproduce the issue in the latest builds and with latest gpu drivers, reopen the report please.

Drew Heo commented

2020-01-24 21:20:59 +01:00

Added subscriber: @brokenstyli

Drew Heo commented

2020-01-24 21:20:59 +01:00

I'd like to chime in and say that I'm having a similar issue, but the crash appears to only occur when using Eevee and wireframe/solid mode viewport renderers, not Cycles (in fact, I'm able to render out an image completely as expected in Cycles).

I'm following along the same tutorial series. My machine's information are as follows;

System Information
WIndows 10 Education, Version 1803. 64 Bit

Blender Version
2.81, Release

Graphics Card
Intel HD Graphics 4000

Steps to Reproduce

Create the above pictured material node graph, apply material to a torus mesh. Enable Displacement + Bump in the settings of the material panel, as mentioned in the OP. Switch from Shading workspace tab to Modeling/Sculpting/Layout workspace tabs. Crash happens a few seconds after switching workspaces.

Other important details;

The machine I'm working on does NOT have a discrete/dedicated GPU.
The crash only seems to occur when on a workspace tabs that is NOT the Shading tab. Project file immediately crashes on open if the project was saved on a tab that isn't the Shading tab.
Crashing requires both that the mesh with the Displacement applied is visible in the View Layer panel, and any onscreen viewports have their renderer to any renderer EXCEPT Cycles - Wireframe, Solid Mode, and Eevee lookdev mode will crash, but Cycles will not crash.

I'm not able to check the latest builds, and do not know how to reopen a report.

I'd like to chime in and say that I'm having a similar issue, but the crash appears to only occur when using Eevee and wireframe/solid mode viewport renderers, not Cycles (in fact, I'm able to render out an image completely as expected in Cycles). I'm following along the same tutorial series. My machine's information are as follows; > **System Information** > WIndows 10 Education, Version 1803. 64 Bit > > **Blender Version** > 2.81, Release > > **Graphics Card** > Intel HD Graphics 4000 **Steps to Reproduce** ![bugreport.PNG](https://archive.blender.org/developer/F8300005/bugreport.PNG) Create the above pictured material node graph, apply material to a torus mesh. Enable Displacement + Bump in the settings of the material panel, as mentioned in the OP. Switch from Shading workspace tab to Modeling/Sculpting/Layout workspace tabs. Crash happens a few seconds after switching workspaces. Other important details; - The machine I'm working on does NOT have a discrete/dedicated GPU. - The crash only seems to occur when on a workspace tabs that is NOT the Shading tab. Project file immediately crashes on open if the project was saved on a tab that isn't the Shading tab. - Crashing requires both that the mesh with the Displacement applied is visible in the View Layer panel, and any onscreen viewports have their renderer to any renderer EXCEPT Cycles - Wireframe, Solid Mode, and Eevee lookdev mode will crash, but Cycles will not crash. I'm not able to check the latest builds, and do not know how to reopen a report.

Richard Antalik commented

2020-01-24 23:13:37 +01:00

In #70490#857962, @brokenstyli wrote:
I'd like to chime in and say that I'm having a similar issue, but the crash appears to only occur when using Eevee and wireframe/solid mode viewport renderers, not Cycles (in fact, I'm able to render out an image completely as expected in Cycles).

I'm following along the same tutorial series. My machine's information are as follows;

System Information
WIndows 10 Education, Version 1803. 64 Bit

Blender Version
2.81, Release

Graphics Card
Intel HD Graphics 4000

Steps to Reproduce

Create the above pictured material node graph, apply material to a torus mesh. Enable Displacement + Bump in the settings of the material panel, as mentioned in the OP. Switch from Shading workspace tab to Modeling/Sculpting/Layout workspace tabs. Crash happens a few seconds after switching workspaces.

Other important details;

The machine I'm working on does NOT have a discrete/dedicated GPU.

The crash only seems to occur when on a workspace tabs that is NOT the Shading tab. Project file immediately crashes on open if the project was saved on a tab that isn't the Shading tab.

Crashing requires both that the mesh with the Displacement applied is visible in the View Layer panel, and any onscreen viewports have their renderer to any renderer EXCEPT Cycles - Wireframe, Solid Mode, and Eevee lookdev mode will crash, but Cycles will not crash.

I'm not able to check the latest builds, and do not know how to reopen a report.

I would recommend to file new repor if this is not reported and please follow guidelines (include.blend file)

> In #70490#857962, @brokenstyli wrote: > I'd like to chime in and say that I'm having a similar issue, but the crash appears to only occur when using Eevee and wireframe/solid mode viewport renderers, not Cycles (in fact, I'm able to render out an image completely as expected in Cycles). > > I'm following along the same tutorial series. My machine's information are as follows; >> **System Information** >> WIndows 10 Education, Version 1803. 64 Bit >> >> **Blender Version** >> 2.81, Release >> >> **Graphics Card** >> Intel HD Graphics 4000 > > **Steps to Reproduce** > ![bugreport.PNG](https://archive.blender.org/developer/F8300005/bugreport.PNG) > Create the above pictured material node graph, apply material to a torus mesh. Enable Displacement + Bump in the settings of the material panel, as mentioned in the OP. Switch from Shading workspace tab to Modeling/Sculpting/Layout workspace tabs. Crash happens a few seconds after switching workspaces. > > Other important details; > - The machine I'm working on does NOT have a discrete/dedicated GPU. > - The crash only seems to occur when on a workspace tabs that is NOT the Shading tab. Project file immediately crashes on open if the project was saved on a tab that isn't the Shading tab. > - Crashing requires both that the mesh with the Displacement applied is visible in the View Layer panel, and any onscreen viewports have their renderer to any renderer EXCEPT Cycles - Wireframe, Solid Mode, and Eevee lookdev mode will crash, but Cycles will not crash. > > I'm not able to check the latest builds, and do not know how to reopen a report. I would recommend to file new repor if this is not reported and please follow guidelines (include.blend file)

Jörg Dittmer commented

2020-02-10 15:35:11 +01:00

Added subscriber: @NoHow

Jörg Dittmer commented

2020-02-10 15:35:11 +01:00

Hi,
i have a gut feeling that this is again a problem with the Windows TDR feature, espacialy if it happens after a >2sec GUI freeze!

SubstancePainter had this issue and they wrote a nice documentation/fix for that:
https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html

I've found this so often across various projects on the internet, wasting the precious developers time.
So, if it solves this problem.... please spread the word!

Hi, i have a gut feeling that this is again a problem with the Windows TDR feature, espacialy if it happens after a >2sec GUI freeze! SubstancePainter had this issue and they wrote a nice documentation/fix for that: https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html I've found this so often across various projects on the internet, wasting the precious developers time. So, if it solves this problem.... please spread the word!

Steffen Dünner commented

2020-02-10 15:43:10 +01:00

Added subscriber: @SteffenD

Steffen Dünner commented

2020-02-10 15:43:11 +01:00

This is a main cause for errors, especially with less experienced users. The problem is that any Windows or nVidia drivers update can reset these values in the Registry :(
Allegorithmic had enough "bug" reports because of this issue and so they not only released a documentation on how to fix it but also added a check during the startup of Substance Painter that warns you in case your TdrDelay and TdrDdiDelay values were too low.

Maybe such a check should be added to the Windows version of Blender.

This is a main cause for errors, especially with less experienced users. The problem is that any Windows or nVidia drivers update can reset these values in the Registry :( Allegorithmic had enough "bug" reports because of this issue and so they not only released a documentation on how to fix it but also added a check during the startup of Substance Painter that warns you in case your TdrDelay and TdrDdiDelay values were too low. Maybe such a check should be added to the Windows version of Blender.

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

Blender crashes when going into "rendered" viewport mode using cycles. #70490