Daz 4.16 Crash on Render

jim_doria

I finally set up a dedicated PC to do Daz renders, but every time I try to render a scene it crashes

Both machines (the production & the render PCs) running idential Daz 4.16.0.3 64 bit. Similar GPUs on both (GeForce GTX 1050 2GB on production, GTX 1060 3GB on render). Latest drivers on both (Studio version. I've also tried Game Ready).

Environment, library, etc mirrored on both machines. Scenes LOAD fine on the renderer. They render fine in the viewport.

I press Render on the render box and it crashes nearly every time. I attached the latest crash report. Same scene renders just fine on the production PC.

How do I even start to troubleshoot this? I'm tearing my hair out!

Richard Haseltine

It appeards not to like the geometry:

<process>

<name>DAZStudio.exe</name>

<id>8356</id>

</process>

<module>C:\Program Files\DAZ 3D\DAZStudio4\dzcore.dll</module>

<address>0033:00000000FEF10399</address>

<function>

<name>DzFacetVertexDelta::operator=</name>

<offset>1129</offset>

</function>

<file/>

<line>

<number/>

<offset/>

</line>

</error>

 

AgitatedRiot

Richard Haseltine said:

It appeards not to like the geometry:

<process>

<name>DAZStudio.exe</name>

<id>8356</id>

</process>

<module>C:\Program Files\DAZ 3D\DAZStudio4\dzcore.dll</module>

<address>0033:00000000FEF10399</address>

<function>

<name>DzFacetVertexDelta::operator=</name>

<offset>1129</offset>

</function>

<file/>

<line>

<number/>

<offset/>

</line>

</error>

 

Looks like it also interrupted other processes. "This thread has been interrupted " causing an error with serval core windows processes. Points back to the what, Richard's first assessment concluded.DzFacetVertexDelta::operator tiggered this.

 

jim_doria

If there was a book on how you intepret these things, I'd pay good money for it. Blood, maybe.

So is there a way for me to figure out which vertex of the many millions in this scene is the bad guy?

i'm not sure where or how such an error even gets introduced. I'm not doing anything crazy or exporting internal objects.

Also doesn't really explain why it works on prod box but not on render.

As far as Windows interferenece with processes, I'm trying to keep the render machine as lean as possible to avoid such conflicts. I thought Windows threads were fairy safe from one another? Or is the "other processes" just error-speak for "Iray engine / Nvidia drivers"?

Richard Haseltine

My suspicion would be that it's a driver issue, or much less likely an actual bug in the chip doing the work.

jim_doria

I was able to get some traction on my previous problem by reducing the render subdivision. Not ideal but...

Now I'm getting a different issue:

2022-04-22 19:48:37.393 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(359): Iray [WARNING] - API:DATABASE ::   1.0   API    db   warn : Transaction is released without being committed or aborted. Automatically aborting.

Pops up on multiple scene files I've tried, even with subdivision reduced. What does it mean?