DAZ constantly crashing during render
Geminii23
Posts: 1,328
Anyone know why this happens? It often feels like a crap shoot of whether or not my renders will finish. So today, I finished a render and didn't like the final lighting, so I adjusted the lights and try to render again. Half-way through DAZ crashes. Really frustrating consdering I am on a 2013 Mac Pro 8-Core. Dual AMD, 64 Gb ram. Not a cheap machine at all.
Thanks
Post edited by Geminii23 on
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
It started getting this way the the latest version of studio. Even though I have the memory I think the large textures are causing it, especially when hdris are used. It seems like studio does not optimize memory and runs out hanging and causing a freeze. If I use scene optimizer it crashes less.
I think I have that add-on but haven't yet used it. Will it also speed up my renders on Mac with AMDs?
There's already a big thread on the studio crashing, you may want to find it and surf through for ideas. Should be in the first couple pages of Commons somewhere. Welcome to the Crashing Club.
Here it is. (Way back on page 6, so no surprise you didn't see it. )
Are you using any dForce items? I find that the VAST majority of the crashes I get are when I have something dForce in my scene.
Thanks I will check that out. Meanwhile, my latest render has taken over 4 hours so far. 3Delight. Single character. Three lights using Fantasty backdrop and preset. This is ridiculous. I have rendered with this same background and a single character and never took this long. Ugh.
It does for me, also allows me to render more content in the scene. Test it on one of your crashing scenes and see how it works for you.
Sounds reasonable, I haven't used dForce at all and no crashes when rendering here, even if I push everything to the limits.
I noticed that when a render goes to switch from GPU to CPU is when my DS will usually crash.
I would have thought dForce items would only be likely to cause a crash during an actual simulation. During rendering, it is just a mesh with textures along with everything else.
Yes, for me as well. I actually started the thread on crashing as its very very frustrating. I do promo's (usually fairly simply scenes, character, lights, clothing and maybe a prop or two (sometimes, not even a prop, just a stand or whatever) I render with no background so it doesn't even have to render the backgrounds. I do 1 to 2 renders a day at least 6 days a week. I can't afford to have it crash all the time.
I agree. Daz never crashes on me unless it's analyzing for rendering and runs out of memory during the process. That's when I know the scene's too big for GPU so I either break the scene down and render in sections or let it render CPU. I do feel for those who keep having the issues though, but no matter if it's GPU, CPU, dForce, non-dForce, Daz rarely ever crashes for me except in the one instance I mentioned. I've rendered several scenes with the outfits almost entirely dForce items or converted to dForce and not one time has it ever crashed...during a rendering or not.
It shouldn't crash due to lack of RAM; you're system should be set up to manage what happens when RAM gets low.
Have you (or anyone else) disabled Swap RAM?
Crashes when RAM is low might suggest an issue with RAM, of course it could also suggest many other issues.
Troubleshooting is about seperating out the problem from what is causing us a problem; to put it another way, make sure symptoms are not diagnosed as the problem.
And yet I don't crash. Not in any of the situations mentioned including after dForce simulation. Machine is good but 4-5 years old and not state of the art.
Win 7 64 bit. 32GB Ram, I7 4770K, GTX 980TI.
Video RAM usage drops to base after all render windows closed. Studio frees CPU RAM to base w/i a minute after Studio closes. For this sytem, Studio behavior hasn't changed since 4.6.
Occasionally it starts swapping here, a couple of times it has taken an hour or so before it started rendering because of that, but no crashes.
When it occasionally crashes which is rare its usually when I'm doing something unusual like closing an open canceled render window while it is starting on another render and things like that. It's often those kinds of unexpected user actions which takes a program down.
So I tried using the basic setting for Scene Optimizer and it does seem like it improved things slightly. Not sure how much. Have been able to get through several renders without crashing. I don't think any of the clothing on these characters was specifically dForce. Also, I know most of the shaders applied are iRay defaults but I am rendering with 3DL instead. Not sure if that makes a difference.
I think texture sizes add up and the new daz software seems unable to allocate memory like it used to.
In my testing today I did three renders back to back of the same scene without crashing. So I do think the Scene Optimizer is definitly helping. These tests also show why I don't care to use iRay. On my Mac, the iRay version took 15 minutes to render, the 3DL was done in 5. I know I would have to spend more time on the iRay to adjust the lights and surfaces, etc. but for what I am wanting to do (graphic novel artwork) the 3DL looks fine to me. The third image is a test run of sorts. I am trying to figure out an efficient but nice art style for my graphic novel. Something I can do really quickly. Thoughts?
scene with two figures, clothed, no lights no backgrounds- optimises images then crashes without even giving any warning message- at least previously I was able to render every second time before it crashed- this sucks big time- thank gods I am still running good old stable studio3 on my really old windows 7 machine- at least that will still actually render most of the time as long as I don't get too ambitious (y'know it tends to fall short after 7 fully clothed figures lifghts, background and assorted props- not bad for a programme which sodding DAZ no longer support!)
4.10 sucks sucks sucks. Anyone got any suggestions on optimising a render so it actually WILL render? without spending lots of money which I don;t have? I don;t think asking it to render 2 dressed figures is exactly pushing the boat out!
So this is a 3Delight render?
Actually, right now I cannot even render a primative in iRay without an access violation.
Looks pretty good to me @geminii23 except for the hair on the arms might be a bit too messy. You could check on these threads where a lot of people give good advice related to graphic novel type rendering/post-working etc:
https://www.daz3d.com/forums/discussion/227541/more-non-photorealisitic-renders-npr-ii#latest
https://www.daz3d.com/forums/discussion/228061/3d-comic-book-tips-and-pictures#latest
Which nVidia driver are you using?
GeForce GT 1030
Version 430.39
As I understand it GeForce Experience keeps my drivers up to date.
I have seen a few people reporting odd issues with 430.x, you might want to try a slightly older version (I am using 419.35 with success).
Thank you. 419.35 seems to be better. I'll have to do some more testing, but at least it's not bombing right away. I'll have to be careful not to let it update.
BTW could this be why Unreal engine continually bombed? (I eventually removed it)