Crash with EXCEPTION_ACCESS_VIOLATION error #109469

New Issue

Julian Danilov · 2023-06-28T20:50:09+02:00

Julian Danilov commented

2023-06-28 20:50:09 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98

Blender Version
Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: c7fc78b81ecb
Worked: (3.5.1)

Short description of error

I am mentioning an addon but there's something telling me it might be a Blender problem considering the major changes done to CORE and the image buffer for in-viewport compositing to come.

There's this useful addon called Super Fast Render, it's freeware;

It benchmarks the frame to be rendered and sets the appropriate number of bounces depending on the materials in the scene, using a series of smaller rendered frames.

On completion of the benchmark, during rendering (F12), Blender crashes with

"Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF7A1011198
Module : blender.exe
Thread : 0000410c"

The weird thing is, benchmarking the frame leaves Blender in some kind of invalid state (not sure what to call it), because the render output seems to get 'stuck' (screenshot uploaded) on the size of the smaller renders SFR uses to determine number of lightpaths.

This makes me think it could be a Blender problem so I'm making this report.

To rule out driver issues, I've used DDU and reinstalled the Nvidia driver (tried a couple of them to see if it's not a driver issue), no luck.

Exact steps for others to reproduce the error

Install https://pidgeontools.gumroad.com/l/SuperFastRender
Open blend file attached.
Run benchmark.
F12 to render, and wait.

It crashes either during benchmarking or after benchmarking during rendering.
Might take more than a couple of tries doing this until it throws the access_violation error.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98 **Blender Version** Broken: version: 3.6.0, branch: blender-v3.6-release, commit date: 2023-06-27 08:08, hash: `c7fc78b81ecb` Worked: (3.5.1) **Short description of error** I am mentioning an addon but there's something telling me it might be a Blender problem considering the major changes done to CORE and the image buffer for in-viewport compositing to come. There's this useful addon called Super Fast Render, it's freeware; It benchmarks the frame to be rendered and sets the appropriate number of bounces depending on the materials in the scene, using a series of smaller rendered frames. On completion of the benchmark, during rendering (F12), Blender crashes with "Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF7A1011198 Module : blender.exe Thread : 0000410c" The weird thing is, benchmarking the frame leaves Blender in some kind of invalid state (not sure what to call it), because the render output seems to get 'stuck' (screenshot uploaded) on the size of the smaller renders SFR uses to determine number of lightpaths. This makes me think it could be a Blender problem so I'm making this report. To rule out driver issues, I've used DDU and reinstalled the Nvidia driver (tried a couple of them to see if it's not a driver issue), no luck. **Exact steps for others to reproduce the error** Install https://pidgeontools.gumroad.com/l/SuperFastRender Open blend file attached. Run benchmark. F12 to render, and wait. It crashes either during benchmarking or after benchmarking during rendering. Might take more than a couple of tries doing this until it throws the access_violation error.

Capture.PNG

93 KiB

report_blend.blend

5.4 MiB

blender_system_info.txt

25 KiB

blender_debug_output.txt

726 KiB