Blender crashes when Windows file viewer is opened #97369

Closed
opened 2022-04-15 19:45:15 +02:00 by Michael · 25 comments

System Information
Operating system: Windows-10-10.0.22000-SP0 64 Bits (I have Windows 11)
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15
CPU: i7 9700K @ 4.7Ghz
RAM: 32 GB DDR4 Corsair Vengeance Pro

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender crashes when Windows file viewer opens, such as, when saving files, choosing image texture.

Exact steps for others to reproduce the error
About 50% of the time Blender will crash when file viewers is opened. I've tried many different version of Blender and all exhibit the same issue.

Every other time I chose an image texture, Blender will crash to Desktop instantly or if I go to save as.

At the same time as this issue appeared I noticed even a simple startup scene will cause 100% CPU usage when moving the camera in Material Shaded view or Render view. Even when a new shader node is added CPU will jump to 100% and Blender will stutter a bit. If the file viewer is open when the CPU is at 100%, Blender will crash to desktop.

I seem to get better results using CUDA instead of OptiX, but box exhibit the same issue.

[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits (I have Windows 11) Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15 CPU: i7 9700K @ 4.7Ghz RAM: 32 GB DDR4 Corsair Vengeance Pro **Blender Version** Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: `c77597cd0e` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender crashes when Windows file viewer opens, such as, when saving files, choosing image texture. **Exact steps for others to reproduce the error** About 50% of the time Blender will crash when file viewers is opened. I've tried many different version of Blender and all exhibit the same issue. Every other time I chose an image texture, Blender will crash to Desktop instantly or if I go to save as. At the same time as this issue appeared I noticed even a simple startup scene will cause 100% CPU usage when moving the camera in Material Shaded view or Render view. Even when a new shader node is added CPU will jump to 100% and Blender will stutter a bit. If the file viewer is open when the CPU is at 100%, Blender will crash to desktop. I seem to get better results using CUDA instead of OptiX, but box exhibit the same issue. [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @NonSmallJohn

Added subscriber: @NonSmallJohn
Michael changed title from Blender crashes when windows file viewer is opened to Blender crashes when Windows file viewer is opened 2022-04-15 19:45:35 +02:00

Added subscriber: @iss

Added subscriber: @iss

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

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

Please check if this happens with latest alpha build from https://builder.blender.org/download/daily/. If it doesn't please run file blender_debug_log.cmd and after crash upload created files.

Can you clarify what is "Windows file viewer"? Do you mean file explorer? or do you mean file open/save dialog within Blender?

Please check if this happens with latest alpha build from https://builder.blender.org/download/daily/. If it doesn't please run file `blender_debug_log.cmd` and after crash upload created files. Can you clarify what is "Windows file viewer"? Do you mean file explorer? or do you mean file open/save dialog within Blender?
Author

Hi, still crashing with the new daily build.

Windows Explorer is probably the better way to have explained it. Open/Save dialog, or Blender file view when selecting an image texture.

I can easily reproduce the issue if you need anything else.

Cheers

blender_debug_output.txt

blender_system_info.txt

Hi, still crashing with the new daily build. Windows Explorer is probably the better way to have explained it. Open/Save dialog, or Blender file view when selecting an image texture. I can easily reproduce the issue if you need anything else. Cheers [blender_debug_output.txt](https://archive.blender.org/developer/F13003521/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F13003522/blender_system_info.txt)

Added subscriber: @rjg

Added subscriber: @rjg

@NonSmallJohn Please also upload the crash log located at C:\Users\curri\AppData\Local\Temp\QuietSlopes-Town-Test.crash.txt.

@NonSmallJohn Please also upload the crash log located at `C:\Users\curri\AppData\Local\Temp\QuietSlopes-Town-Test.crash.txt`.

Also check if this happens when you click on File > Defaults > Load Factory Settings

Also check if this happens when you click on File > Defaults > Load Factory Settings
Author

Still seeing the same issue with default settings.

Had the default cube with the viewport set to Rendered view, switched to Cycles renderer, rotated the camera, clicked CTRL + S to save, crash to desktop.

QuietSlopes-Town-Test.crash.txt

Still seeing the same issue with default settings. Had the default cube with the viewport set to Rendered view, switched to Cycles renderer, rotated the camera, clicked CTRL + S to save, crash to desktop. [QuietSlopes-Town-Test.crash.txt](https://archive.blender.org/developer/F13011103/QuietSlopes-Town-Test.crash.txt)

There are no symbols in crash file. Can you repeat steps to crash with alpha build and re-upload C:\Users\curri\AppData\Local\Temp\QuietSlopes-Town-Test.crash.txt file?

Since with factory settings this still happens, I would guess that problem would be linked to one particular blend file. Is that correct? Can you upload problematic .blend file?

There are no symbols in crash file. Can you repeat steps to crash with alpha build and re-upload `C:\Users\curri\AppData\Local\Temp\QuietSlopes-Town-Test.crash.txt` file? Since with factory settings this still happens, I would guess that problem would be linked to one particular blend file. Is that correct? Can you upload problematic .blend file?
Author

The issue happens with all my blend files. I just started a project and added am image texture to the shader graph, because I can easily cause it to crash by adding a texture image through Windows Explorer file viewer.

For the current Blender crash I changed the image texture interpolation from Linear to Closest and clicked open image, then crash to desktop.

Added text below incase you have issues:
QuietSlopes-Town-Test.crash.txt

Blender 3.2.0, Commit date: 2022-04-14 19:51, Hash 48ff456a4b

bpy.data.materials["Material.001"].node_tree.nodes["Image Texture"].interpolation = 'Linear' # Property
bpy.data.materials["Material.001"].node_tree.nodes["Image Texture"].interpolation = 'Closest' # Property

backtrace

Exception Record:

ExceptionCode : EXCEPTION_ACCESS_VIOLATION
Exception Address : 0x00007FF8315749A8
Exception Module :
Exception Flags : 0x00000000
Exception Parameters : 0x2
Parameters- [x] : 0x0000000000000008
Parameters- [x] : 0x00007FF8315749A8

Stack trace:

                  :0x00007FF8315749A8  Symbols not available

Loaded Modules :
0x00007FF706D50000 3.2.0.0 blender.exe C:\Users\curri\Downloads\blender-3.2.0-alpha+master.48ff456a4bda-windows.amd64-release\blender-3.2.0-alpha+master.48ff456a4bda-windows.amd64-release\blender.pdb
0x00007FF901940000 10.0.22000.527 ntdll.dll
0x00007FF9000C0000 10.0.22000.613 KERNEL32.DLL
0x00007FF8FF280000 10.0.22000.613 KERNELBASE.dll
0x00007FF900990000 10.0.22000.1 WS2_32.dll
0x00007FF900BC0000 10.0.22000.613 RPCRT4.dll
0x00007FF8FFEF0000 10.0.22000.282 USER32.dll
0x00007FF8E0F80000 tbbmalloc.dll
0x00007FF8FF250000 10.0.22000.613 win32u.dll
0x00007FF8FFEC0000 10.0.22000.1 GDI32.dll
0x00007FF8E0FB0000 tbb.dll
0x00007FF8FF010000 10.0.22000.527 gdi32full.dll
0x00007FF8FF1B0000 10.0.22000.1 msvcp_win.dll
0x00007FF8FF600000 10.0.22000.1 ucrtbase.dll
0x00007FF901850000 10.0.22000.434 ADVAPI32.dll
0x00007FF901130000 7.0.22000.1 msvcrt.dll
0x00007FF8FF8A0000 10.0.22000.556 sechost.dll
0x00007FF8E0380000 14.29.30139.0 VCRUNTIME140.dll
0x00007FF900180000 10.0.22000.593 SHELL32.dll
0x00007FF8432C0000 14.29.30139.0 MSVCP140.dll
0x00007FF900FE0000 10.0.22000.1 PSAPI.DLL
0x00007FF900930000 10.0.22000.1 SHLWAPI.dll
0x00007FF8E0370000 14.29.30139.0 VCRUNTIME140_1.dll
0x00007FF8F2190000 10.0.22000.1 dbghelp.dll
0x00007FF900DE0000 10.0.22000.120 ole32.dll
0x00007FF840DE0000 8.0.1.0 openvdb.dll
0x00007FF901470000 10.0.22000.527 combase.dll
0x00007FF8431B0000 10.0.22000.41 OPENGL32.dll
0x00007FF840910000 3.10.2150.1013 python310.dll
0x00007FF900CE0000 10.0.22000.613 shcore.dll
0x00007FF8FF7E0000 10.0.22000.1 IMM32.dll
0x00007FF83ECA0000 58.134.100.0 avcodec-58.dll
0x00007FF83E940000 58.76.100.0 avformat-58.dll
0x00007FF8E0350000 58.13.100.0 avdevice-58.dll
0x00007FF83E670000 56.70.100.0 avutil-56.dll
0x00007FF901380000 10.0.22000.1 OLEAUT32.dll
0x00007FF83E5D0000 5.9.100.0 swscale-5.dll
0x0000000070440000 1.0.28.0 libsndfile-1.dll
0x00007FF83E480000 1.20.1.0 OpenAL32.dll
0x00007FF83E350000 2.0.12.0 SDL2.dll
0x000000006ACC0000 libgmp-10.dll
0x00007FF8E0340000 libgmpxx.dll
0x00007FF8CFCA0000 tbbmalloc_proxy.dll
0x00007FF8FF950000 10.0.22000.469 SETUPAPI.dll
0x00007FF8FEB00000 10.0.22000.1 CFGMGR32.dll
0x00007FF8F9470000 10.0.22000.1 VERSION.dll
0x00007FF8F3FC0000 6.10.22000.120 COMCTL32.dll
0x00007FF8BABD0000 10.0.22000.1 AVIFIL32.dll
0x00007FF896DC0000 10.0.22000.41 GLU32.dll
0x0000000070680000 libfftw3-3.dll
0x00007FF8959D0000 3.9.100.0 swresample-3.dll
0x00007FF8FE810000 10.0.22000.1 bcrypt.dll
0x00007FF8F44B0000 10.0.22000.1 Secur32.dll
0x00007FF8B6A70000 10.0.22000.1 AVICAP32.dll
0x00007FF8F2C50000 10.0.22000.1 WINMM.dll
0x00007FF8F2080000 10.0.22000.1 MSACM32.dll
0x00007FF8959A0000 10.0.22000.1 MSVFW32.dll
0x00007FF8FC680000 10.0.22000.1 dxcore.dll
0x00007FF8FE240000 10.0.22000.556 SSPICLI.DLL
0x00007FF8FE020000 10.0.22000.71 kernel.appcore.dll
0x00007FF8FCFA0000 10.0.22000.593 windows.storage.dll
0x00007FF8FCE30000 10.0.22000.527 wintypes.dll
0x00007FF8FC5A0000 10.0.22000.120 uxtheme.dll
0x00007FF8FF130000 10.0.22000.376 bcryptPrimitives.dll
0x00007FF8FED60000 10.0.22000.1 profapi.dll
0x00007FF9011E0000 2001.12.10941.16384 clbcatq.dll
0x00007FF8F4F50000 10.0.22000.1 MMDevApi.dll
0x00007FF8FEB50000 10.0.22000.1 DEVOBJ.dll
0x00007FF8DFFA0000 10.0.22000.348 AUDIOSES.DLL
0x00007FF8FD850000 10.0.22000.1 powrprof.dll
0x00007FF8FD960000 10.0.22000.1 UMPDC.dll
0x00007FF900FF0000 10.0.22000.527 MSCTF.dll
0x00007FF8F9F50000 10.0.22000.469 AppXDeploymentClient.dll
0x00007FF8F9D40000 11.0.22000.527 urlmon.dll
0x00007FF8F9A30000 11.0.22000.593 iertutil.dll
0x00007FF8F9CF0000 10.0.22000.613 srvcli.dll
0x00007FF8FDC60000 10.0.22000.434 netutils.dll
0x00007FF83B320000 30.0.15.1215 nvoglv64.dll
0x00007FF8FB380000 10.0.22000.1 WTSAPI32.dll
0x00007FF8FE6B0000 10.0.22000.1 CRYPTBASE.DLL
0x00007FF8FE6F0000 10.0.22000.1 msasn1.dll
0x00007FF8F90C0000 10.0.22000.1 cryptnet.dll
0x00007FF8FEEA0000 10.0.22000.348 CRYPT32.dll
0x00007FF8F8E30000 10.0.22000.120 drvstore.dll
0x00007FF8FE760000 10.0.22000.120 wldp.dll
0x00007FF8FEE30000 10.0.22000.527 WINTRUST.dll
0x00007FF8FC6C0000 10.0.22000.1 ntmarta.dll
0x00007FF8FC920000 10.0.22000.41 dwmapi.dll
0x00007FF8FDBF0000 10.0.22000.1 WINSTA.dll
0x00007FF8CA970000 10.0.22000.1 dataexchange.dll
0x00007FF8F5CF0000 10.0.22000.593 twinapi.appcore.dll
0x00007FF8EAB00000 10.0.22000.282 textinputframework.dll
0x00007FF8FBF90000 10.0.22000.71 CoreMessaging.dll
0x00007FF8F9100000 10.0.22000.132 CoreUIComponents.dll
0x00007FF8F1130000 7.2.22000.1 Oleacc.dll
0x00007FF8CCFC0000 5.2.5.5 Pen_Tablet.dll
0x00007FF8C6D50000 10.0.22000.593 explorerframe.dll
0x00007FF8E95D0000 10.0.22000.527 MPR.dll
0x00007FF8E2890000 10.0.22000.1 p9np.dll
0x00007FF8E2880000 10.0.22000.1 drprov.dll
0x00007FF8E2860000 10.0.22000.527 ntlanman.dll
0x00007FF8E2840000 10.0.22000.1 davclnt.dll
0x00007FF8F96D0000 10.0.22000.613 wkscli.dll
0x00007FF8DF6C0000 10.0.22000.1 cscapi.dll
0x00007FF8FE690000 10.0.22000.1 CRYPTSP.dll
0x00007FF8FDF80000 10.0.22000.282 rsaenh.dll
0x000001653B280000 3.10.2150.1013 python3.DLL
0x00007FF8B67E0000 3.10.2150.1013 _bz2.pyd
0x00007FF8958F0000 3.10.2150.1013 _lzma.pyd
0x00007FF88ECF0000 3.10.2150.1013 _elementtree.pyd
0x00007FF867D10000 3.10.2150.1013 pyexpat.pyd
0x00007FF870BB0000 3.10.2150.1013 _ctypes.pyd
0x00007FF8CF780000 libffi-7.dll
0x00007FF83B020000 _multiarray_umath.cp310-win_amd64.pyd
0x00007FF867CE0000 _multiarray_tests.cp310-win_amd64.pyd
0x00007FF8B3AA0000 3.10.2150.1013 _socket.pyd
0x00007FF8FDAD0000 10.0.22000.282 IPHLPAPI.DLL
0x00007FF8CDF30000 3.10.2150.1013 select.pyd
0x00007FF831780000 _umath_linalg.cp310-win_amd64.pyd
0x00007FF88ECD0000 _pocketfft_internal.cp310-win_amd64.pyd
0x00007FF83AF80000 mtrand.cp310-win_amd64.pyd
0x00007FF864A50000 bit_generator.cp310-win_amd64.pyd
0x00007FF864A10000 _common.cp310-win_amd64.pyd
0x00007FF8C99E0000 3.10.2150.1013 _hashlib.pyd
0x00007FF823660000 1.1.1.13 libcrypto-1_1.dll
0x00007FF864490000 _bounded_integers.cp310-win_amd64.pyd
0x00007FF870960000 _mt19937.cp310-win_amd64.pyd
0x00007FF86D820000 _philox.cp310-win_amd64.pyd
0x00007FF867FF0000 _pcg64.cp310-win_amd64.pyd
0x00007FF8642B0000 _sfc64.cp310-win_amd64.pyd
0x00007FF8316D0000 _generator.cp310-win_amd64.pyd
0x00007FF8DC500000 30.0.15.1215 nvcuda.dll
0x00007FF8D8F20000 30.0.15.1215 nvcuda64.dll
0x00007FF8F6A30000 30.0.15.1215 nvapi64.dll
0x00007FF820D00000 7.4.1.0 nvoptix.dll

  • Python backtrace
The issue happens with all my blend files. I just started a project and added am image texture to the shader graph, because I can easily cause it to crash by adding a texture image through Windows Explorer file viewer. For the current Blender crash I changed the image texture interpolation from Linear to Closest and clicked open image, then crash to desktop. Added text below incase you have issues: [QuietSlopes-Town-Test.crash.txt](https://archive.blender.org/developer/F13013369/QuietSlopes-Town-Test.crash.txt) # Blender 3.2.0, Commit date: 2022-04-14 19:51, Hash 48ff456a4bda bpy.data.materials["Material.001"].node_tree.nodes["Image Texture"].interpolation = 'Linear' # Property bpy.data.materials["Material.001"].node_tree.nodes["Image Texture"].interpolation = 'Closest' # Property # backtrace Exception Record: ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF8315749A8 Exception Module : Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters- [x] : 0x0000000000000008 Parameters- [x] : 0x00007FF8315749A8 Stack trace: ``` :0x00007FF8315749A8 Symbols not available ``` Loaded Modules : 0x00007FF706D50000 3.2.0.0 blender.exe C:\Users\curri\Downloads\blender-3.2.0-alpha+master.48ff456a4bda-windows.amd64-release\blender-3.2.0-alpha+master.48ff456a4bda-windows.amd64-release\blender.pdb 0x00007FF901940000 10.0.22000.527 ntdll.dll 0x00007FF9000C0000 10.0.22000.613 KERNEL32.DLL 0x00007FF8FF280000 10.0.22000.613 KERNELBASE.dll 0x00007FF900990000 10.0.22000.1 WS2_32.dll 0x00007FF900BC0000 10.0.22000.613 RPCRT4.dll 0x00007FF8FFEF0000 10.0.22000.282 USER32.dll 0x00007FF8E0F80000 tbbmalloc.dll 0x00007FF8FF250000 10.0.22000.613 win32u.dll 0x00007FF8FFEC0000 10.0.22000.1 GDI32.dll 0x00007FF8E0FB0000 tbb.dll 0x00007FF8FF010000 10.0.22000.527 gdi32full.dll 0x00007FF8FF1B0000 10.0.22000.1 msvcp_win.dll 0x00007FF8FF600000 10.0.22000.1 ucrtbase.dll 0x00007FF901850000 10.0.22000.434 ADVAPI32.dll 0x00007FF901130000 7.0.22000.1 msvcrt.dll 0x00007FF8FF8A0000 10.0.22000.556 sechost.dll 0x00007FF8E0380000 14.29.30139.0 VCRUNTIME140.dll 0x00007FF900180000 10.0.22000.593 SHELL32.dll 0x00007FF8432C0000 14.29.30139.0 MSVCP140.dll 0x00007FF900FE0000 10.0.22000.1 PSAPI.DLL 0x00007FF900930000 10.0.22000.1 SHLWAPI.dll 0x00007FF8E0370000 14.29.30139.0 VCRUNTIME140_1.dll 0x00007FF8F2190000 10.0.22000.1 dbghelp.dll 0x00007FF900DE0000 10.0.22000.120 ole32.dll 0x00007FF840DE0000 8.0.1.0 openvdb.dll 0x00007FF901470000 10.0.22000.527 combase.dll 0x00007FF8431B0000 10.0.22000.41 OPENGL32.dll 0x00007FF840910000 3.10.2150.1013 python310.dll 0x00007FF900CE0000 10.0.22000.613 shcore.dll 0x00007FF8FF7E0000 10.0.22000.1 IMM32.dll 0x00007FF83ECA0000 58.134.100.0 avcodec-58.dll 0x00007FF83E940000 58.76.100.0 avformat-58.dll 0x00007FF8E0350000 58.13.100.0 avdevice-58.dll 0x00007FF83E670000 56.70.100.0 avutil-56.dll 0x00007FF901380000 10.0.22000.1 OLEAUT32.dll 0x00007FF83E5D0000 5.9.100.0 swscale-5.dll 0x0000000070440000 1.0.28.0 libsndfile-1.dll 0x00007FF83E480000 1.20.1.0 OpenAL32.dll 0x00007FF83E350000 2.0.12.0 SDL2.dll 0x000000006ACC0000 libgmp-10.dll 0x00007FF8E0340000 libgmpxx.dll 0x00007FF8CFCA0000 tbbmalloc_proxy.dll 0x00007FF8FF950000 10.0.22000.469 SETUPAPI.dll 0x00007FF8FEB00000 10.0.22000.1 CFGMGR32.dll 0x00007FF8F9470000 10.0.22000.1 VERSION.dll 0x00007FF8F3FC0000 6.10.22000.120 COMCTL32.dll 0x00007FF8BABD0000 10.0.22000.1 AVIFIL32.dll 0x00007FF896DC0000 10.0.22000.41 GLU32.dll 0x0000000070680000 libfftw3-3.dll 0x00007FF8959D0000 3.9.100.0 swresample-3.dll 0x00007FF8FE810000 10.0.22000.1 bcrypt.dll 0x00007FF8F44B0000 10.0.22000.1 Secur32.dll 0x00007FF8B6A70000 10.0.22000.1 AVICAP32.dll 0x00007FF8F2C50000 10.0.22000.1 WINMM.dll 0x00007FF8F2080000 10.0.22000.1 MSACM32.dll 0x00007FF8959A0000 10.0.22000.1 MSVFW32.dll 0x00007FF8FC680000 10.0.22000.1 dxcore.dll 0x00007FF8FE240000 10.0.22000.556 SSPICLI.DLL 0x00007FF8FE020000 10.0.22000.71 kernel.appcore.dll 0x00007FF8FCFA0000 10.0.22000.593 windows.storage.dll 0x00007FF8FCE30000 10.0.22000.527 wintypes.dll 0x00007FF8FC5A0000 10.0.22000.120 uxtheme.dll 0x00007FF8FF130000 10.0.22000.376 bcryptPrimitives.dll 0x00007FF8FED60000 10.0.22000.1 profapi.dll 0x00007FF9011E0000 2001.12.10941.16384 clbcatq.dll 0x00007FF8F4F50000 10.0.22000.1 MMDevApi.dll 0x00007FF8FEB50000 10.0.22000.1 DEVOBJ.dll 0x00007FF8DFFA0000 10.0.22000.348 AUDIOSES.DLL 0x00007FF8FD850000 10.0.22000.1 powrprof.dll 0x00007FF8FD960000 10.0.22000.1 UMPDC.dll 0x00007FF900FF0000 10.0.22000.527 MSCTF.dll 0x00007FF8F9F50000 10.0.22000.469 AppXDeploymentClient.dll 0x00007FF8F9D40000 11.0.22000.527 urlmon.dll 0x00007FF8F9A30000 11.0.22000.593 iertutil.dll 0x00007FF8F9CF0000 10.0.22000.613 srvcli.dll 0x00007FF8FDC60000 10.0.22000.434 netutils.dll 0x00007FF83B320000 30.0.15.1215 nvoglv64.dll 0x00007FF8FB380000 10.0.22000.1 WTSAPI32.dll 0x00007FF8FE6B0000 10.0.22000.1 CRYPTBASE.DLL 0x00007FF8FE6F0000 10.0.22000.1 msasn1.dll 0x00007FF8F90C0000 10.0.22000.1 cryptnet.dll 0x00007FF8FEEA0000 10.0.22000.348 CRYPT32.dll 0x00007FF8F8E30000 10.0.22000.120 drvstore.dll 0x00007FF8FE760000 10.0.22000.120 wldp.dll 0x00007FF8FEE30000 10.0.22000.527 WINTRUST.dll 0x00007FF8FC6C0000 10.0.22000.1 ntmarta.dll 0x00007FF8FC920000 10.0.22000.41 dwmapi.dll 0x00007FF8FDBF0000 10.0.22000.1 WINSTA.dll 0x00007FF8CA970000 10.0.22000.1 dataexchange.dll 0x00007FF8F5CF0000 10.0.22000.593 twinapi.appcore.dll 0x00007FF8EAB00000 10.0.22000.282 textinputframework.dll 0x00007FF8FBF90000 10.0.22000.71 CoreMessaging.dll 0x00007FF8F9100000 10.0.22000.132 CoreUIComponents.dll 0x00007FF8F1130000 7.2.22000.1 Oleacc.dll 0x00007FF8CCFC0000 5.2.5.5 Pen_Tablet.dll 0x00007FF8C6D50000 10.0.22000.593 explorerframe.dll 0x00007FF8E95D0000 10.0.22000.527 MPR.dll 0x00007FF8E2890000 10.0.22000.1 p9np.dll 0x00007FF8E2880000 10.0.22000.1 drprov.dll 0x00007FF8E2860000 10.0.22000.527 ntlanman.dll 0x00007FF8E2840000 10.0.22000.1 davclnt.dll 0x00007FF8F96D0000 10.0.22000.613 wkscli.dll 0x00007FF8DF6C0000 10.0.22000.1 cscapi.dll 0x00007FF8FE690000 10.0.22000.1 CRYPTSP.dll 0x00007FF8FDF80000 10.0.22000.282 rsaenh.dll 0x000001653B280000 3.10.2150.1013 python3.DLL 0x00007FF8B67E0000 3.10.2150.1013 _bz2.pyd 0x00007FF8958F0000 3.10.2150.1013 _lzma.pyd 0x00007FF88ECF0000 3.10.2150.1013 _elementtree.pyd 0x00007FF867D10000 3.10.2150.1013 pyexpat.pyd 0x00007FF870BB0000 3.10.2150.1013 _ctypes.pyd 0x00007FF8CF780000 libffi-7.dll 0x00007FF83B020000 _multiarray_umath.cp310-win_amd64.pyd 0x00007FF867CE0000 _multiarray_tests.cp310-win_amd64.pyd 0x00007FF8B3AA0000 3.10.2150.1013 _socket.pyd 0x00007FF8FDAD0000 10.0.22000.282 IPHLPAPI.DLL 0x00007FF8CDF30000 3.10.2150.1013 select.pyd 0x00007FF831780000 _umath_linalg.cp310-win_amd64.pyd 0x00007FF88ECD0000 _pocketfft_internal.cp310-win_amd64.pyd 0x00007FF83AF80000 mtrand.cp310-win_amd64.pyd 0x00007FF864A50000 bit_generator.cp310-win_amd64.pyd 0x00007FF864A10000 _common.cp310-win_amd64.pyd 0x00007FF8C99E0000 3.10.2150.1013 _hashlib.pyd 0x00007FF823660000 1.1.1.13 libcrypto-1_1.dll 0x00007FF864490000 _bounded_integers.cp310-win_amd64.pyd 0x00007FF870960000 _mt19937.cp310-win_amd64.pyd 0x00007FF86D820000 _philox.cp310-win_amd64.pyd 0x00007FF867FF0000 _pcg64.cp310-win_amd64.pyd 0x00007FF8642B0000 _sfc64.cp310-win_amd64.pyd 0x00007FF8316D0000 _generator.cp310-win_amd64.pyd 0x00007FF8DC500000 30.0.15.1215 nvcuda.dll 0x00007FF8D8F20000 30.0.15.1215 nvcuda64.dll 0x00007FF8F6A30000 30.0.15.1215 nvapi64.dll 0x00007FF820D00000 7.4.1.0 nvoptix.dll - Python backtrace

@NonSmallJohn Could you please download the .zip version of Blender from here, extract it, run blender.exe by double-clicking on it and test again. It seems you are using the Steam version without debug symbols.

@NonSmallJohn Could you please download the .zip version of Blender from [here](https://download.blender.org/release/Blender3.1/), extract it, run `blender.exe` by double-clicking on it and test again. It seems you are using the Steam version without debug symbols.
Author

Have never used a Steam version. Always download from website.

I see there are still no Symbols available following your steps above.

interior-test.crash.txt

Have never used a Steam version. Always download from website. I see there are still no Symbols available following your steps above. [interior-test.crash.txt](https://archive.blender.org/developer/F13015006/interior-test.crash.txt)

That's unfortunate, these symbols would provide clue at least.

One more thing that can cause issues is overclocked GPU. Can you check if your GPU is running at stock speed? Otherwise I think I am out of ideas.

That's unfortunate, these symbols would provide clue at least. One more thing that can cause issues is overclocked GPU. Can you check if your GPU is running at stock speed? Otherwise I think I am out of ideas.
Author

I've already tried turning off the GPU overclock and CPU overclock, but still the issue remains.

The only consistent evidence is Blender will cause the CPU to jump to 100% for seemingly mundane things. Such as: opening the shader editor, clicking on a node, changing any node setting. Also clicking on something such as the materials property menu will cause 100% CPU usage. Once the CPU goes to 100%, any actions that causes the Windows Explorer/File Viewer to open will crash the program.

I've already tried turning off the GPU overclock and CPU overclock, but still the issue remains. The only consistent evidence is Blender will cause the CPU to jump to 100% for seemingly mundane things. Such as: opening the shader editor, clicking on a node, changing any node setting. Also clicking on something such as the materials property menu will cause 100% CPU usage. Once the CPU goes to 100%, any actions that causes the Windows Explorer/File Viewer to open will crash the program.

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

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

Thanks for update.

Thanks for update.

@NonSmallJohn Just a guess, but do you have thumbnail display enabled?

@NonSmallJohn Just a guess, but do you have thumbnail display enabled?
Author

I do not.

I do not.
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

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

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

Hi, this might be related to #62651 (Dual monitor on separate graphics card driver error)
Do you have any external device (monitor, tablet) connected to your main system?

Had the default cube with the viewport set to Rendered view, switched to Cycles renderer, rotated the camera, clicked CTRL + S to save

Does this only happen when floating window is opened in render mode?

Hi, this might be related to #62651 (Dual monitor on separate graphics card driver error) Do you have any external device (monitor, tablet) connected to your main system? > Had the default cube with the viewport set to Rendered view, switched to Cycles renderer, rotated the camera, clicked CTRL + S to save Does this only happen when floating window is opened in render mode?
Member

Any news on this?

Any news on this?
Member

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

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

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
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
4 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#97369
No description provided.