3dsmax 2017 crash with Vray 3.6, Phoenix FD 3.04 and Backburner on z820 with 128 gb memory

[markus_s_cg]

Hi,

I'm experiencing some crashes when rendering a high res image 8000x4000px on a machine via backburner.
I'm not sure what is causing it. The file uses a lot of memory so I have to render on this machine which is set up as a rendernode only.

Any advice on what I should try?

I've rendered some earlier versions of the image successfully, but with less foam and splash particles. Then the render finished and VFB wrote the output files to disk, but max still crashed after writing the files and backburner would mark the job as failed and restart try to restart it several times. But now (with more foam in the sim), 3dsmax seems to crash in the middle the of rendering process.

[Zdravko.Keremidchiev]

Can you attach a 3ds max dump file?

[markus_s_cg]

Can you explain how/what dump file (and where do I find it)?

[markus_s_cg]

I tried rendering in lower resolution on my local workstation. The render finishes and writes the files, but also crashes after finishing.

I could also send you a max file with the sim (one frame) and the phoenixfd and render setup only.

[Zdravko.Keremidchiev]

The 3dsmax_minidump.dmp file can be found in the temp (%temp%) folder. But it will be best if you could send us the scene to support as well.

[markus_s_cg]

I couldn't find the dump file on the rendernode. I found one on my local machine (where I did the test in lower res due to only having 32 gig memory), however that dump was a day old, so probably not created from the crash I had today? I have sent an email to support with a stripped down version of the project.

[markus_s_cg]

I'm doing a test now where I reverted to vray 3.5003 instead of 3.6 just to see if that makes a difference (I just installed 3.6 yesterday, so I' want to check if that affected anything. I'll let you know if I find out anything.

[markus_s_cg]

After reverting the node to 3.5 it managed to finish the render at 8000x4000 and it did not crash at the end of rendering either. It seems to me like a new issue in 3.6 then?