daz crashes ntdll.dll

Comments

• vectorinus Posts: 138

  April 2

  However, before loading this single G8, according to the log file, you had a scene with two hairy fully clothed G9 characters. I wonder how much RAM the textures of all these objects took up? I read somewhere that Daz Studio does not free up memory completely after closing the previous scene (maybe I'm wrong). However, if this is true, then maybe this post will help you: https://www.daz3d.com/forums/discussion/686936/cannot-open-daz-studio-scene-file-not-enough-memory-resources-are-available-to-process-this-command?srsltid=AfmBOopvNFtELf10LgJlKFpcXyHalq64VUYfoXWXrGW5OTEs92xrRgTk
• frank0314 Posts: 14,713

  April 2

  It does eventually release the RAM a short time later after the app is closed.
• yevhenjohn Posts: 11

  April 2 edited April 2

  vectorinus said:

  However, before loading this single G8, according to the log file, you had a scene with two hairy fully clothed G9 characters. I wonder how much RAM the textures of all these objects took up? I read somewhere that Daz Studio does not free up memory completely after closing the previous scene (maybe I'm wrong). However, if this is true, then maybe this post will help you: https://www.daz3d.com/forums/discussion/686936/cannot-open-daz-studio-scene-file-not-enough-memory-resources-are-available-to-process-this-command?srsltid=AfmBOopvNFtELf10LgJlKFpcXyHalq64VUYfoXWXrGW5OTEs92xrRgTk

  Thanks for the hint. Actually, it not that much of RAM as I was playing around with a scene with only g3 alone. And after a while it was the same issue. Sometime it is even start after PC restart. 

  Post edited by Richard Haseltine on April 2
• vectorinus Posts: 138

  April 3

  An unpleasant problem. I have encountered something similar. But in that case I ruined Daz Studio myself. If you work with log files, you could collect information from them after each crash of the program. The very last lines before the crash. Is it always caused by attempts to create materials, as shown in your presented log? Or are the causes different? If they are similar, then you could move on in your investigation.
• yevhenjohn Posts: 11

  April 3 edited April 3

  vectorinus said:

  An unpleasant problem. I have encountered something similar. But in that case I ruined Daz Studio myself. If you work with log files, you could collect information from them after each crash of the program. The very last lines before the crash. Is it always caused by attempts to create materials, as shown in your presented log? Or are the causes different? If they are similar, then you could move on in your investigation.

  It is really hard to say, as sometimes it give that error message and sometimes doesn't. Furthermore, log files do not specify anything specific. Sometimes it just says shutdown and that it is. Currently, I am reinstalling windows and try again from the scratch, as the same scenes work well on my laptop although that has only 16 GB ram. 

  Post edited by Richard Haseltine on April 3
• Richard Haseltine Posts: 108,091

  April 3

  If the log file lists a Daz Studio Exited message then it didn't crash.
• vectorinus Posts: 138

  April 3

  Yes, usually when Daz Studio performs an unsuccessful operation and crashes, it does not have time to make a record in the log, and the next time we start we see in the log only the last successful operation. The message about the spontaneous closure of the program is something new for me.
• Imago Posts: 5,663

  April 3

  yevhenjohn said:

  Once scene is load - it works fine. But it really makes it impossible to do render queue as it just crashes at random loading.

  I'm having a similar problem in 4.23. The crashes doesn't happen in 4.21 and I can use batch rendering with no issues. Which release are you using?
• yevhenjohn Posts: 11

  April 3 edited April 3

  Imago said:

  yevhenjohn said:

  Once scene is load - it works fine. But it really makes it impossible to do render queue as it just crashes at random loading.

  I'm having a similar problem in 4.23. The crashes doesn't happen in 4.21 and I can use batch rendering with no issues. Which release are you using?

  I am using 4.23.  Did you have also the issues with loading scenes? Because rendering is fine. It just when it tries to load something to a scene or load a new scene it is only then it crashes. Or it simply closes. 

  Post edited by Richard Haseltine on April 3
• Imago Posts: 5,663

  April 3

  yevhenjohn said:

  I am using 4.23.  Did you have also the issues with loading scenes? Because rendering is fine. It just when it tries to load something to a scene or load a new scene it is only then it crashes. Or it simply closes. 

  As I said, when I use 4.23 the scenes often crashes with no obvious reason. For a while I thought it was Mesh Grabber 3's fault but I discovered it was quite unrelated.

  The same scenes loads correctly in 4.21, I do animations so my scenes are always really heavy and under that "old" release all works fine and I can batch render my scenes with nbo crashes.

  I suggest you to try those scenes in 4.21 (4.22 gives me the same crashes as .23 but perhaps it won't happen to you too) and see if there they work fine.
• vectorinus Posts: 138

  April 4

  I think this thread's issue is resolved. I really like Daz Studio 4.22 and will happily continue using it. Thank you, dear friends, for your information! (Although I don't do animation ;--)
• yevhenjohn Posts: 11

  April 5

  vectorinus said:

  I think this thread's issue is resolved. I really like Daz Studio 4.22 and will happily continue using it. Thank you, dear friends, for your information! (Although I don't do animation ;--)

  Nothing is resolved.   I can repport that in 4.21 it was only a single crash compare 4.23 but I need more time to see how it works.  when i had that crash it was the same error as before. 
• vectorinus Posts: 138

  April 5

  If you're receiving Faulting module name: ntdll.dll message, one possible cause could be a bad memory module in your system. Testing your memory will either identify a problem or clear your RAM of any responsibility. Maybe DS 4.21 is forcing memory less than the newer versions.
• Imago Posts: 5,663

  April 5

  vectorinus said:

  If you're receiving Faulting module name: ntdll.dll message, one possible cause could be a bad memory module in your system. Testing your memory will either identify a problem or clear your RAM of any responsibility. Maybe DS 4.21 is forcing memory less than the newer versions.

  Nope. I had the same thought and installed a whole different set of RAM in my PC. Same results, crashes on ntdll.dll, TBB.dll and Dzcore.dll.

  Same crashes on my second machine too, with a totally different hardware.

  It's DAZ Studio itself, sadly.
• vectorinus Posts: 138

  April 5

  I don't make big scenes on DAZ, preferring to montage a full image from several renders of different objects of the scene in Photoshop or Krita. However, sometimes I experiment a little with my own plugins in DAZ Studio. And it is very useful for me to know about the stability of DS 4.21. I have it. Thank you for your information, @Imago!
• Richard Haseltine Posts: 108,091

  April 6

  Imago said:

  vectorinus said:

  If you're receiving Faulting module name: ntdll.dll message, one possible cause could be a bad memory module in your system. Testing your memory will either identify a problem or clear your RAM of any responsibility. Maybe DS 4.21 is forcing memory less than the newer versions.

  Nope. I had the same thought and installed a whole different set of RAM in my PC. Same results, crashes on ntdll.dll, TBB.dll and Dzcore.dll.

  Same crashes on my second machine too, with a totally different hardware.

  It's DAZ Studio itself, sadly.

  If it was Daz studio itself then everyone would have the same issue, which is not the case. It could be an add-on (most likely a plug-in), an obscure content issue, or possibly soime external software or hardware issue common to both systems.
• yevhenjohn Posts: 11

  April 20

  So, the problem seems to be resolved. The issue was related to an imported library. Although there was nothing wrong with the library itself, the way Daz handles it is strange—but that’s just how it is. It wasn’t too complicated: the library was originally created and saved on an external SSD labeled E. On the new PC, that same external SSD was labeled F, and this mismatch caused all the problems.

  Furthermore, Daz behaves in a weird way. Even when I reset the metadata and excluded my library—leaving only the default assets like G8 or G9—it still crashed occasionally. It’s as if once the old library is imported, Daz gets "corrupted," even if I disconnect the library afterward and reset everything. Maybe there’s some guideline somewhere that says the library should stay in the same location when transferring to a new PC, but the fact that it only crashes occasionally and often gives misleading or no error messages at all is really frustrating.

  So far, after I changed the drive label back to what it was on the old PC, Daz has been running without crashes for three days—just as it should.