Blender crashing a lot randomly in the rendered viewport #81102

New Issue

ENZO GUIBBANI · 2020-09-23T19:02:34+02:00

ENZO GUIBBANI commented

2020-09-23 19:02:34 +02:00

System Information
Operating system: Win10 Pro
Graphics card: GeForce GTX 770/PCIe/SSE2 4.5.0 NVIDIA 456.38
CPU : Ryzen 9 3900X

Blender Version
2.90.1
Also crashed on 2.83LTS

Short description of error
Blender crashes within few minutes looking around in rendered view (Cycles CPU mode)
Crashes even in very simple scenes like a default cube
sudden GPU usage spike a the moment of the crash
Tried using 2 versions, default settings, uninstalling all addons.
Video card drivers are up to date
Windows is up to date too.

I'm unable to understand the nature of crash by looking at the cmd or the crash log.

wtf.blend
wtf.crash.txt

Stack trace:
blender.exe         :0x00007FF633BEED80  embree::avx2::BVHNIntersector1<4,1,0,embree::avx2::ArrayIntersector1<embree::avx2::InstanceIntersec
blender.exe         :0x00007FF6332A4C80  rtcIntersect1
blender.exe         :0x00007FF6330DA860  ccl::kernel_path_trace
blender.exe         :0x00007FF633086280  ccl::kernel_cpu_avx2_path_trace
blender.exe         :0x00007FF632D9A700  ccl::CPUDevice::render
blender.exe         :0x00007FF632D9B590  ccl::CPUDevice::thread_render
blender.exe         :0x00007FF632D9BA30  ccl::CPUDevice::thread_run
blender.exe         :0x00007FF632D960B0  std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call
blender.exe         :0x00007FF63534F520  tbb::internal::function_task<std::function<void __cdecl(void)> >::execute
tbb.dll             :0x00007FFE631037A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFE631037A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFE630F51D0  tbb::interface7::internal::isolate_within_arena
tbb.dll             :0x00007FFE630FA490  tbb::task_scheduler_init::terminate
tbb.dll             :0x00007FFE631019C0  tbb::thread_bound_filter::try_process_item
tbb.dll             :0x00007FFE631019C0  tbb::thread_bound_filter::try_process_item
ucrtbase.dll        :0x00007FFE8C2F1430  configthreadlocale
KERNEL32.DLL        :0x00007FFE8C5A6FC0  BaseThreadInitThunk
ntdll.dll           :0x00007FFE8E3BCEA0  RtlUserThreadStart

**System Information** Operating system: Win10 Pro Graphics card: GeForce GTX 770/PCIe/SSE2 4.5.0 NVIDIA 456.38 CPU : Ryzen 9 3900X **Blender Version** 2.90.1 Also crashed on 2.83LTS **Short description of error** Blender crashes within few minutes looking around in rendered view (Cycles CPU mode) Crashes even in very simple scenes like a default cube sudden GPU usage spike a the moment of the crash Tried using 2 versions, default settings, uninstalling all addons. Video card drivers are up to date Windows is up to date too. I'm unable to understand the nature of crash by looking at the cmd or the crash log. [wtf.blend](https://archive.blender.org/developer/F8912518/wtf.blend) [wtf.crash.txt](https://archive.blender.org/developer/F8912514/wtf.crash.txt) ![Capture.PNG](https://archive.blender.org/developer/F8912515/Capture.PNG) ``` Stack trace: blender.exe :0x00007FF633BEED80 embree::avx2::BVHNIntersector1<4,1,0,embree::avx2::ArrayIntersector1<embree::avx2::InstanceIntersec blender.exe :0x00007FF6332A4C80 rtcIntersect1 blender.exe :0x00007FF6330DA860 ccl::kernel_path_trace blender.exe :0x00007FF633086280 ccl::kernel_cpu_avx2_path_trace blender.exe :0x00007FF632D9A700 ccl::CPUDevice::render blender.exe :0x00007FF632D9B590 ccl::CPUDevice::thread_render blender.exe :0x00007FF632D9BA30 ccl::CPUDevice::thread_run blender.exe :0x00007FF632D960B0 std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call blender.exe :0x00007FF63534F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute tbb.dll :0x00007FFE631037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFE631037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFE630F51D0 tbb::interface7::internal::isolate_within_arena tbb.dll :0x00007FFE630FA490 tbb::task_scheduler_init::terminate tbb.dll :0x00007FFE631019C0 tbb::thread_bound_filter::try_process_item tbb.dll :0x00007FFE631019C0 tbb::thread_bound_filter::try_process_item ucrtbase.dll :0x00007FFE8C2F1430 configthreadlocale KERNEL32.DLL :0x00007FFE8C5A6FC0 BaseThreadInitThunk ntdll.dll :0x00007FFE8E3BCEA0 RtlUserThreadStart ```

ENZO GUIBBANI commented

2020-09-23 19:02:34 +02:00

Added subscriber: @enzoguibbani

blender-admin commented

2020-09-23 19:02:34 +02:00

#81855 was marked as duplicate of this issue

blender-admin commented

2020-09-23 19:02:34 +02:00

#81587 was marked as duplicate of this issue

blender-admin commented

2020-09-23 19:02:34 +02:00

#81158 was marked as duplicate of this issue

Robert Guetzkow commented

2020-09-23 21:37:23 +02:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-09-23 21:37:23 +02:00

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

Robert Guetzkow commented

2020-09-23 21:37:23 +02:00

Based on the screenshot it appears that the crash is caused by the Megascans add-on trying to bind a socket to an address that is already in use and not handling the error properly. Please try to deactivate the Megascans add-on and check if Blender still crashes.

ENZO GUIBBANI commented

2020-09-23 21:41:01 +02:00

Yeah I thought that would be looking weird on the screenshots, but I have completely uninstalled the megascans plugin and the problem is still here...
I can provide a screenshot too, it's the same error without the "megascans" lines in the cmd.

Yeah I thought that would be looking weird on the screenshots, but I have completely uninstalled the megascans plugin and the problem is still here... I can provide a screenshot too, it's the same error without the "megascans" lines in the cmd.

Robert Guetzkow commented

2020-09-23 21:50:10 +02:00

I see. It seems your install is missing the debug symbols though, which is why the stack trace is missing from the crash log. Are you using the official Windows build provided from https://www.blender.org/download/ ?

ENZO GUIBBANI commented

2020-09-23 22:00:26 +02:00

I'm using the lastest blender version found on Steam, I'll try to get it from blender.org if that can cause an issue

ENZO GUIBBANI commented

2020-09-23 22:01:43 +02:00

The crash log i provided isn't complete?

Robert Guetzkow commented

2020-09-23 22:18:57 +02:00

Yes. Usually Blender on Windows comes with so called "debug symbols" that essentially tell us where the crash occurred. In your build they are missing, the crash log states:

Stack trace:
blender.exe         :0x00007FF7E988EFFF  Symbols not available

The issue will be the same in a build with debug symbols, but the additional info may help us identify the cause. I've contacted other developers to check why the Steam version is missing the symbols.

Please try it again with the build from our website (portable version .zip only needs to be extracted) or from the Microsoft Store. Open Blender's 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 two files. Add them to your bug report by clicking on the upload button as shown in the screenshot below. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\blender.crash.txt.

Yes. Usually Blender on Windows comes with so called "debug symbols" that essentially tell us where the crash occurred. In your build they are missing, the crash log states: ``` Stack trace: blender.exe :0x00007FF7E988EFFF Symbols not available ``` The issue will be the same in a build with debug symbols, but the additional info may help us identify the cause. I've contacted other developers to check why the Steam version is missing the symbols. Please try it again with the build from [our website](https://www.blender.org/download/) (portable version .zip only needs to be extracted) or from the Microsoft Store. Open Blender's 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 two files. Add them to your bug report by clicking on the upload button as shown in the screenshot below. Please also upload the crash log located in `C:\Users\[your username]\AppData\Local\Temp\blender.crash.txt`. ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

ENZO GUIBBANI commented

2020-09-23 22:24:05 +02:00

Thank you a lot, I'll try that and keep you informed within 3 hours.

ENZO GUIBBANI commented

2020-09-23 23:48:36 +02:00

Here's the files you requested from portable blender, there's 2 debug output from 2 .blend but same error. and the file from the tmp folder

blender.crash.txt

blender_debug_output1.txt

blender_system_info.txt

blender_debug_output2.txt

Here's the files you requested from portable blender, there's 2 debug output from 2 .blend but same error. and the file from the tmp folder [blender.crash.txt](https://archive.blender.org/developer/F8913089/blender.crash.txt) [blender_debug_output1.txt](https://archive.blender.org/developer/F8913033/blender_debug_output1.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8913032/blender_system_info.txt) [blender_debug_output2.txt](https://archive.blender.org/developer/F8913031/blender_debug_output2.txt)

Robert Guetzkow commented

2020-09-23 23:57:31 +02:00

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

ENZO GUIBBANI commented

2020-09-24 00:26:47 +02:00

A friend just gave me his GTX 1070 to test if the problem was still here, i installed it, with a fresh install of the latest drivers, and still, it crashes within 5min of fairly simple work on blender.
Here's again the crash logs with the new graphics card :

blender_debug_output.txt

blender_system_info.txt

wtf.crash.txt

A friend just gave me his GTX 1070 to test if the problem was still here, i installed it, with a fresh install of the latest drivers, and still, it crashes within 5min of fairly simple work on blender. Here's again the crash logs with the new graphics card : [blender_debug_output.txt](https://archive.blender.org/developer/F8913492/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8913477/blender_system_info.txt) [wtf.crash.txt](https://archive.blender.org/developer/F8913487/wtf.crash.txt)

Robert Guetzkow commented

2020-09-24 00:55:16 +02:00

The crash appears to be caused by Embree in a functions that uses AVX2 instruction on the CPU. As far as I can tell the GPU is not involved in this crash. There was another AVX2 related report #79707, but that one was fixed and your CPU supports AVX2 unlike the affected hardware from the other report.

ENZO GUIBBANI commented

2020-09-24 01:03:12 +02:00

Yeah, i also thought it wasn't gpu involved since i changed it.
i'm not familliar with the way a CPU works, does this type of error is induced by a faulty CPU or it is only a software problem ?
I haven't seen many reports on people having troubles using blender on a Ryzen 9 3900x

Yeah, i also thought it wasn't gpu involved since i changed it. i'm not familliar with the way a CPU works, does this type of error is induced by a faulty CPU or it is only a software problem ? I haven't seen many reports on people having troubles using blender on a Ryzen 9 3900x

Alaska commented

2020-09-24 01:39:51 +02:00

Added subscriber: @Alaska

Alaska commented

2020-09-24 01:39:51 +02:00

Just thought I'd add that I personally experience crashes from time to time while using the CPU rendered viewport on Windows. However Linux doesn't appear to show issues (will need to keep playing around). I will play around with my Windows install and post a crash log as well.

CPU: Ryzen 9 3900X
GPU: RTX 2060 Super 452.06

Just thought I'd add that I personally experience crashes from time to time while using the CPU rendered viewport on Windows. However Linux doesn't appear to show issues (will need to keep playing around). I will play around with my Windows install and post a crash log as well. CPU: Ryzen 9 3900X GPU: RTX 2060 Super 452.06

Alaska commented

2020-09-24 02:05:28 +02:00

Blender 2.90.0:
blender_system_info.txt
blender_debug_output.txt
Alaska crash #81102 - 2.90.0.txt

Blender 2.90.1:
blender_system_info.txt
blender_debug_output.txt
Alaska crash #81102 - 2.90.1.txt

Blender 2.90.0: [blender_system_info.txt](https://archive.blender.org/developer/F8914005/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8914006/blender_debug_output.txt) [Alaska crash #81102 - 2.90.0.txt](https://archive.blender.org/developer/F8914013/Alaska_crash_T81102_-_2.90.0.txt) Blender 2.90.1: [blender_system_info.txt](https://archive.blender.org/developer/F8914051/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8914052/blender_debug_output.txt) [Alaska crash #81102 - 2.90.1.txt](https://archive.blender.org/developer/F8914054/Alaska_crash_T81102_-_2.90.1.txt)

ENZO GUIBBANI commented

2020-09-24 02:10:37 +02:00

Thanks for the help Alaska 👍

ENZO GUIBBANI commented

2020-09-24 12:07:23 +02:00

I also noticed today, that my CPU is heating way more when in the rendered viewport than in any stress tests (tested Aida64, Prime95 and OCCT)
Stress tests don't trigger any error and CPU is slowly ramping up to 80°c.
On blender in the rendered viewport, the CPU ramp up almost immediately to 80°c then up to 85°c.
If that can help to find what's going on.

I also noticed today, that my CPU is heating way more when in the rendered viewport than in any stress tests (tested Aida64, Prime95 and OCCT) Stress tests don't trigger any error and CPU is slowly ramping up to 80°c. On blender in the rendered viewport, the CPU ramp up almost immediately to 80°c then up to 85°c. If that can help to find what's going on.

ENZO GUIBBANI commented

2020-09-28 12:37:47 +02:00

I just did fresh install of windows 10, almost only blender installed on the pc and essential drivers, the problem is still occuring.

Evan Wilson commented

2020-10-11 17:00:14 +02:00

Added subscriber: @EAW

Evan Wilson commented

2020-10-11 17:00:14 +02:00

@rjg I believe AVX2 is a red herring. I get the same Stack Trace on a CPU that only supports SSE42.

Stack trace:
blender.exe         :0x00007FF686C64030  embree::sse2::TriangleMi<4>::loadTriangle
blender.exe         :0x00007FF687F332E0  embree::sse42::BVHNIntersector1<4,1,1,embree::sse42::ArrayIntersector1<embree::sse42::TriangleMiInt
blender.exe         :0x00007FF688026640  embree::sse42::InstanceIntersector1::intersect
blender.exe         :0x00007FF687F3C2A0  embree::sse42::BVHNIntersector1<4,1,0,embree::sse42::ArrayIntersector1<embree::sse42::InstanceInter
blender.exe         :0x00007FF6869A4F10  rtcIntersect1
blender.exe         :0x00007FF686671E50  ccl::kernel_path_trace C:\blender-git\blender\intern\cycles\kernel\kernel_path.h:692
blender.exe         :0x00007FF686669A60  ccl::kernel_cpu_sse41_path_trace C:\blender-git\blender\intern\cycles\kernel\kernels\cpu\kernel_cpu_impl.h:99
blender.exe         :0x00007FF6864B7D60  ccl::CPUDevice::render C:\blender-git\blender\intern\cycles\device\device_cpu.cpp:937
blender.exe         :0x00007FF6864B8D30  ccl::CPUDevice::thread_render C:\blender-git\blender\intern\cycles\device\device_cpu.cpp:1291
blender.exe         :0x00007FF6864B91D0  ccl::CPUDevice::thread_run C:\blender-git\blender\intern\cycles\device\device_cpu.cpp:552
blender.exe         :0x00007FF6864B2F00  std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\include\functional:903
blender.exe         :0x00007FF6889B68F0  tbb::internal::function_task<std::function<void __cdecl(void)> >::execute C:\blender-git\lib\win64_vc15\tbb\include\tbb\task.h:1049
tbb.dll             :0x00007FFDA6C737A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFDA6C737A0  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFDA6C651D0  tbb::interface7::internal::isolate_within_arena
tbb.dll             :0x00007FFDA6C6A490  tbb::task_scheduler_init::terminate
tbb.dll             :0x00007FFDA6C719C0  tbb::thread_bound_filter::try_process_item
tbb.dll             :0x00007FFDA6C719C0  tbb::thread_bound_filter::try_process_item
ucrtbase.dll        :0x00007FFDC1650D40  beginthreadex
KERNEL32.DLL        :0x00007FFDC4197BC0  BaseThreadInitThunk
ntdll.dll           :0x00007FFDC42ECE30  RtlUserThreadStart

Full crash text: {F8979293}
This was while using {F8958666} from T81468 / T81595.

Using my file from {T81587} to consistently reproduce the crash in this section of code, I've noticed that stack traces will cut off part or all of the of the following randomly:

blender.exe         :0x00007FF687F332E0  embree::sse42::BVHNIntersector1<4,1,1,embree::sse42::ArrayIntersector1<embree::sse42::TriangleMiInt
blender.exe         :0x00007FF688026640  embree::sse42::InstanceIntersector1::intersect
blender.exe         :0x00007FF687F3C2A0  embree::sse42::BVHNIntersector1<4,1,0,embree::sse42::ArrayIntersector1<embree::sse42::InstanceInter
blender.exe         :0x00007FF6869A4F10  rtcIntersect1```
This leads me to think that the stack trace in the task description is likely missing the upper part.

@rjg I believe AVX2 is a [red herring](https://en.wikipedia.org/wiki/Red_herring). I get the same Stack Trace on a CPU that only supports SSE42. ```lines Stack trace: blender.exe :0x00007FF686C64030 embree::sse2::TriangleMi<4>::loadTriangle blender.exe :0x00007FF687F332E0 embree::sse42::BVHNIntersector1<4,1,1,embree::sse42::ArrayIntersector1<embree::sse42::TriangleMiInt blender.exe :0x00007FF688026640 embree::sse42::InstanceIntersector1::intersect blender.exe :0x00007FF687F3C2A0 embree::sse42::BVHNIntersector1<4,1,0,embree::sse42::ArrayIntersector1<embree::sse42::InstanceInter blender.exe :0x00007FF6869A4F10 rtcIntersect1 blender.exe :0x00007FF686671E50 ccl::kernel_path_trace C:\blender-git\blender\intern\cycles\kernel\kernel_path.h:692 blender.exe :0x00007FF686669A60 ccl::kernel_cpu_sse41_path_trace C:\blender-git\blender\intern\cycles\kernel\kernels\cpu\kernel_cpu_impl.h:99 blender.exe :0x00007FF6864B7D60 ccl::CPUDevice::render C:\blender-git\blender\intern\cycles\device\device_cpu.cpp:937 blender.exe :0x00007FF6864B8D30 ccl::CPUDevice::thread_render C:\blender-git\blender\intern\cycles\device\device_cpu.cpp:1291 blender.exe :0x00007FF6864B91D0 ccl::CPUDevice::thread_run C:\blender-git\blender\intern\cycles\device\device_cpu.cpp:552 blender.exe :0x00007FF6864B2F00 std::_Func_impl_no_alloc<<lambda_d884e08a7877f415f05ce8ffda8f97b4>,void>::_Do_call C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\include\functional:903 blender.exe :0x00007FF6889B68F0 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute C:\blender-git\lib\win64_vc15\tbb\include\tbb\task.h:1049 tbb.dll :0x00007FFDA6C737A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFDA6C737A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFDA6C651D0 tbb::interface7::internal::isolate_within_arena tbb.dll :0x00007FFDA6C6A490 tbb::task_scheduler_init::terminate tbb.dll :0x00007FFDA6C719C0 tbb::thread_bound_filter::try_process_item tbb.dll :0x00007FFDA6C719C0 tbb::thread_bound_filter::try_process_item ucrtbase.dll :0x00007FFDC1650D40 beginthreadex KERNEL32.DLL :0x00007FFDC4197BC0 BaseThreadInitThunk ntdll.dll :0x00007FFDC42ECE30 RtlUserThreadStart ``` Full crash text: {F8979293} This was while using {F8958666} from T81468 / T81595. Using my file from {T81587} to consistently reproduce the crash in this section of code, I've noticed that stack traces will cut off part or all of the of the following randomly: ```blender.exe :0x00007FF686C64030 embree::sse2::TriangleMi<4>::loadTriangle blender.exe :0x00007FF687F332E0 embree::sse42::BVHNIntersector1<4,1,1,embree::sse42::ArrayIntersector1<embree::sse42::TriangleMiInt blender.exe :0x00007FF688026640 embree::sse42::InstanceIntersector1::intersect blender.exe :0x00007FF687F3C2A0 embree::sse42::BVHNIntersector1<4,1,0,embree::sse42::ArrayIntersector1<embree::sse42::InstanceInter blender.exe :0x00007FF6869A4F10 rtcIntersect1``` This leads me to think that the stack trace in the task description is likely missing the upper part.

Robert Guetzkow commented

2020-10-11 18:04:27 +02:00

@EAW Thanks for investigating this. If I'm understanding this correctly, we should merge the tickets. I will see if I can reproduce this on any hardware I have access to.

Evan Wilson commented

2020-10-11 18:49:20 +02:00

Added subscribers: @KRODU, @dfelinto

Evan Wilson commented

2020-10-11 18:50:50 +02:00

Added subscriber: @LazyDodo

Robert Guetzkow commented

2020-10-12 21:46:58 +02:00

I can't reproduce this on my hardware, but given several people being able to reproduce this, including you and @LazyDodo, I'll mark this as confirmed.