Page MenuHome

Blender crashes when click on shading tab
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Windows 10, 64-bit
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87

Blender Version
Broken:

  • version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28
  • version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release

Short description of error
Blender crashes when clicking on the shading tab. It closes and goes back to the desktop.

Exact steps for others to reproduce the error
See short description.


Event Timeline

Your report is not complete, please fill all request in bug form as Blender version (2.82a/2.83beta/2.90alpha) and Blender hash (you can read these info on top right of Splash Screen (little cenetred window ) when you open Blender. I can suppose that report will be Invalid if you not update it with request info

@reza salartayefeh (rezast) can you test this workaround? https://developer.blender.org/T72098#906441

Robert Guetzkow (rjg) changed the task status from Needs Triage to Needs Information from User.EditedApr 19 2020, 12:08 AM

Please update your graphics driver and check if the crash still occurs. If it does, 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. The Windows Explorer should open and show you two files. Add them to your bug report by clicking on the upload button as shown in the screenshot below.

Please update your graphics driver and check if the crash still occurs. If it does, 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. The Windows Explorer should open and show you two files. Add them to your bug report by clicking on the upload button as shown in the screenshot below.


my graphic drivers are update

Your report is not complete, please fill all request in bug form as Blender version (2.82a/2.83beta/2.90alpha) and Blender hash (you can read these info on top right of Splash Screen (little cenetred window ) when you open Blender. I can suppose that report will be Invalid if you not update it with request info

@reza salartayefeh (rezast) can you test this workaround? https://developer.blender.org/T72098#906441

i edit this report.thank u

@reza salartayefeh (rezast) You're not using an official Blender build, but one from OTOY for OctaneRender. Please download the most recent daily build of Blender and check if the issue occurs there as well. If it does, please run the blender_debug_gpu.cmd again, make it crash and attach both files (blender_debug_output.txt and blender_system_info.txt).

@reza salartayefeh (rezast) You're not using an official Blender build, but one from OTOY for OctaneRender. Please download the most recent daily build of Blender and check if the issue occurs there as well. If it does, please run the blender_debug_gpu.cmd again, make it crash and attach both files.

thank u ?which one?alpha or beta?

in each other versions crash in shading tab is happening

Robert Guetzkow (rjg) renamed this task from blender crash when click on shading tab to Blender crashes when click on shading tab .EditedApr 19 2020, 4:41 PM
Robert Guetzkow (rjg) updated the task description. (Show Details)
Robert Guetzkow (rjg) updated the task description. (Show Details)

The crash is happening in the VCRUNTIME140.dll.

There are also a couple GPUShaderInterface warnings which could also be related to the cause. The graphics driver is already the most recent version though.

GPUShaderInterface: Warning: Uniform 'depthBuffer' not found!
[...]
GPUShaderInterface: Warning: Uniform 'texelSize' not found!
GPUShaderInterface: Warning: Uniform 'paddingSize' not found!
GPUShaderInterface: Warning: Uniform 'StudioLightMatrix' not found!
GPUShaderInterface: Warning: Uniform 'outputSssId' not found!
GPUShaderInterface: Warning: Uniform 'outputSssId' not found!
GPUShaderInterface: Warning: Uniform 'attr' not found!
GPUShaderInterface: Warning: Uniform 'hairPointBuffer' not found!
GPUShaderInterface: Warning: Uniform 'hairUVBuffer' not found!
GPUShaderInterface: Warning: Uniform 'hairColBuffer' not found!
GPUShaderInterface: Warning: Uniform 'depthBuffer' not found!
[...]
GPUShaderInterface: Warning: Uniform 'texJitter' not found!
GPUShaderInterface: Warning: Uniform 'inScattering' not found!
GPUShaderInterface: Warning: Uniform 'inTransmittance' not found!
Robert Guetzkow (rjg) changed the task status from Needs Information from User to Needs Triage.Apr 19 2020, 4:50 PM
This comment was removed by Robert Guetzkow (rjg).

@reza salartayefeh (rezast) Have you tried the suggested approach by @dark999 (dark999) to enable the compatibility mode? This shouldn't be necessary, but apparently there are some recent issues where this has helped. The cause of the issue should still be identified and fixed though, this would only be a temporary workaround.

yes i try it but nothing .graphic driver is update.i install all of Visual C++ Redistributable version.please help me :-((((

@reza salartayefeh (rezast) You shouldn't have to install the redistributables, Blender already includes the required .dlls in the blender.crt directory.

@Ray molenkamp (LazyDodo) @Jeroen Bakker (jbakker) I could only find one other recent ticket (T75194) that also had a crash in the vcruntime140.dll. Any idea what might have gone wrong?

@reza salartayefeh (rezast) You shouldn't have to install the redistributables, Blender already includes the required .dlls in the blender.crt directory.

@Ray molenkamp (LazyDodo) @Jeroen Bakker (jbakker) I could only find one other recent ticket (T75194) that also had a crash in the vcruntime140.dll. Any idea what might have gone wrong?

i am testing any way but it is crashing

There's really no good way of trouble shooting this beyond repro on a developer work station or having the user do a debug build, there is some work being done to get proper stack traces from reports like these, but that has been dragging on since 2018 or so ( D3576 )

There's really no good way of trouble shooting this beyond repro on a developer work station or having the user do a debug build, there is some work being done to get proper stack traces from reports like these, but that has been dragging on since 2018 or so ( D3576 )

help me i am beginner

The crash is happening in the VCRUNTIME140.dll.

new report with ver 2.80 is different

Clément Foucault (fclem) changed the subtype of this task from "Report" to "Bug".Jul 1 2020, 7:35 PM
Clément Foucault (fclem) moved this task from Backlog to Bugs on the EEVEE & Viewport board.

@Clément Foucault (fclem): If it is a bug, it should be confirmed? If it is not confirmed, it should probably still be a report (possibly set to Needs Developer To Reproduce)?

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Confirmed.Nov 18 2020, 1:10 PM

Changing this to Confirmed now [following @Clément Foucault (fclem) 's choice on the workboard]

Could this be related to the GPU memory being hit at maximum on the GTX1050? Is there a way to know the used graphic memory at the moment of the crash? This card is being rated at 2GB of VRAM...