Page MenuHome

Crashing while rendering to openEXR sequence on Windows only.
Closed, InvalidPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.12

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-13 16:25, hash: rB9bd0d8b5505a
Worked: (optional)

Short description of error
Rendering out an image sequence of OpenEXR files causes Blender to crash, giving the error "Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF70FCD7EB4"

Rendering using exactly the same settings on macOS or Linux works without a problem.

Crash occurs with both CPU and GPU rendering. Have only tried Cycles.

We've tried this on two Windows 10 computers, both crash with the same error message.

Exact steps for others to reproduce the error

  • Open Blender on Windows (these crashes have been happening on Windows 10, can't test other versions).
  • This should work on any blend file, so default scene will do.
  • Change file format to 'OpenEXR'.
  • Change Codec to 'DWAA (lossy)'
  • Render animation

The render will either eventually freeze or outright crash. The project I'm currently working on crashes Blender after two frames and gives the "Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF70FCD7EB4" error. Testing the default scene, the render froze on frame 88.

Event Timeline

Dalai Felinto (dfelinto) lowered the priority of this task from 90 to 30.Nov 18 2019, 8:36 PM

Hi, thanks for the report.

Could you please test rendering with EEVEE and smaller render sizes? (and when able to reproduce please save the file and upload it here).
Render 88 frames on Cycles only to reproduce a bug that may be happening only in your system is a hard issue to debug.

Also please test with the official stable 2.80 release for comparison.

Hi Dalai,

That's fair enough, yes, happy to do that, but it'll take a bit of time as I usually work in Linux and have a lot on right now.

I'm finding it hard to replicate the bug with a shareable file unfortunately, the default cube render must have been a different issue. It's probably best to just close this bug report.

Dalai Felinto (dfelinto) claimed this task.

Thanks for the original report anyways :)