Access Violation Crashes

Limosisv2

Hi Folks.

So I've been getting an access violation crash, which happens most frequently when trying a progressive render in the viewport, but not all the time. Maybe 1 of every 6 renders crashes.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\dz3delight.dll" at 0033:00000000140A89C7, Dz3DelightDll::DSlo_DetailtoStr()+286023 byte(s)

I'm aware that Daz no longer supports 3delight, butt i have tried a couple of different versions of Daz3d with 3delights plugin as part of the install, all with the same frustrating result.

Note:: This crash rarely ever happens to a non-progressive render, directly to file.

Richard Haseltine

What about a non-progressive render to a new  window, or a progressive render to a file? Which versions of Daz Studio are you using?

Limosisv2

Currently using v4.21, but have tried v4.24 also.

I've done some testing over the day and I've worked out a few things:

• Crashing happens whenever I am not rendering to file. It doesn't happen every attempt, but 1/5 attempts at rendering in viewport or to window will crash, Progressive or not progressive.
• Rendering to a file crashing in this way nearly never happens. I render to file quite regularly and only recall 1 time in the last 6 months where it happened.
• CPU usage will spike to 99% percent duing all renders, but will yo-yo between 99% and 39% constantly when rendering to a window or viewport
• CPU usage is far more stable when rendering to file, with an initial spike to 99%, but constant 37% for the rest of the render (which could take an hour or more)
• GPU usage seems nearly non-existant, with my Geforce rarely registering above 2% during a render. Maybe some brief moments when it spikes to 11% for less than a second.

Is it normal for the CPU to be spiking to 99%? My PC isn't brand new, but it is powerful enough to not struggle with any other software/game.

 

Edit: I've just noticed that the CPU sitting on 99% correlates to the software window being maximised and visible on the monitor, and drops below 40% when the window is minimised... strange...

Richard Haseltine

3Delight should use all of the CPU cores by default. It iis a puely CPU render engine, so any GPU activity is not part of the render process - and the extent to which the CPU is used should not depend on the render target, unless the writing to disc is imposing a severe bottleneck. I do wonder if there is a heat-related issue with your CPU.

Limosisv2

Thanks Richard.

Can confirm it looks like my PC is overheating/throttling and shutting down Daz. It appears to work fine when i put Daz in efficiency mode, even progressive rendering in viewport.

I will have to address what is causing the heat buildup.