Loading...
> >

[SOLVED] Lots of random crashes, have tried many things... Any idea?

boubakeurjohnboubakeurjohn Posts: 36
edited 11:14AM in Technical Help (nuts n bolts)

Hi everyone,

So for a few weeks now Daz has been crashing a lot on my PC, to the point of making it nearly unusable. Sometimes the program throws an error message, sometimes it just disappears...

Things that can make it crash include: loading a scene, loading a figure saved as a preset, saving a scene, running a simulation, switching the viewport from textures to iray, rotating a bone on a character, dialing a morph...

So far I've tried installing the latest Daz version, uninstalling Daz and reinstalling it on a different Windows profile, running the program from different drives (one NVMe, one SATA SSD), re-installing Windows, dialing down my i9 power limits (PL1/PLC2/ICC)...

Nothing's made a difference... Can't work for long on scenes, can't render them with the render queue... You can guess it's getting extremely frustrating!

Does anyone have any idea what I could check?

The logs contain lots of warnings about formulas, but there is no error whatsever logged when Daz goes down (confirmed by support).

My configuration: Z790 Aorus Elite AX, i9 13900K, 32Gb DDR5, RTX 4090, Windows 11 and nvidia drivers both up to date (unless they changed today).

Ever since I built this PC, Daz has always been a bit buggy, in that I could get crashes when adjusting the pose of my characters, usually when working on heavy scenes and/or after a lot of work in the application.

But it's never been this crazy, now I'm happy if I can work on a scene for more than half an hour or if the render queue processes more than 2 or 3 scenes.

For what it's worth, there hasn't been any indication about hardware faults in the many other programs and games this PC also runs.

So, being kinda lost, any help would be very appreciated!

 

Post edited by boubakeurjohn at

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,759

    Duplicate Formula warning are figue-specific, usually indicating that two characters/morph sets use the same name. They wouldn't be causing crashing.

    Using the latest nVidia driver is not always best - try rolling back to soemthing closer to the minimum required version, but note that older nVidia drivers have a potentially serious security issue so - unless you work offline in that machine - you hae a tricky balancing act.

    32 GB is not a lot of system RAM, and is likely to run out before you fully use the memory of the 4090 (the rough rule of thimb is you need two to three times as much RAM as scene data on the GPU, so a 24GB card would need 48GB to 64GB while 32 GB would handle scenes up to 12 to 16 GB of data) - running out of memory could be a factor in the crashing, at least if the Viewport is using the Iray Drawstyle.

  • crosswindcrosswind Posts: 8,083

    DS log usually won't help with trouble-shooting for crash issues. If you see the fatal error dialogue, yon can save the dump files and attach them in here. We may help to check.

    For the time being, you can try increasing virtual memory of your system 1st of all, see if that'll help.

  • boubakeurjohnboubakeurjohn Posts: 36

    Thank you Richard, but I doubt these are the cause of my issues: I've gotten plenty of crashes where Iray hadn't been used at all since the program started, viewport stayed in texture shaded mode. 

    A common scenario is open program -> load scene -> Daz crash while loading. Happens like 1 out of 3 times when I open a scene manually or the render queue does it.

    I am tempted to buy another 32Gb of RAM anyhow, but I don't know if it'll be of help in regards to Daz.

     

  • boubakeurjohnboubakeurjohn Posts: 36

    crosswind said:

    DS log usually won't help with trouble-shooting for crash issues. If you see the fatal error dialogue, yon can save the dump files and attach them in here. We may help to check.

    For the time being, you can try increasing virtual memory of your system 1st of all, see if that'll help.

    I attached some dumps I collected in a few different crash scenarios.

    Regarding your suggestion about virtual memory, thank you, I'll look into that. I've seen crashes with more than 10Gb of free RAM available, so I don't know if it'll help, but it won't hurt either.

     

    zip
    zip
    Daz Dumps.zip
    1017K
  • crosswindcrosswind Posts: 8,083
    edited February 24

    Four of dumps point to DzCore.dll with the issue of invalid pointers. In my experience, the culprit might 1stly come from lacking of RAM. Try increasing virtual memomry 1stly, see if it'll help... Check this post:  https://forum.daz3d.com/forums/discussion/comment/9000496/#Comment_9000496

    The dump related to NVIDIA Iray preview points to libneuray.dll... I'm not sure what caused it for the time being, it may be related to RAM or VRAM, or related to asset issue. Anyway, 1st thing's 1st, try the point one ~~

     

    SNAG-2025-2-25-001.png
    1539 x 948 - 124K
    Post edited by crosswind on
  • boubakeurjohnboubakeurjohn Posts: 36

    Just changed virtual memory size to 120Gb (min and max), restarted my computer, and still got two dzcore.dll crashes...

    First one happened while running a dforce simulation, the other while hiding parts of a character in preparation of a simulation in the same scene, but with different clothes (wanted to make sure it wasn't a specific item that caused the first crash).

  • crosswindcrosswind Posts: 8,083

    I have no idea why dForce simulation still brings you DS crash. You may name the product you used...

  • boubakeurjohnboubakeurjohn Posts: 36
    edited 11:19AM

    Turns out it won't be necessary ;)

    After my last message I checked several error reports and saw this appear several time: DzShellGeomGraftObject::~DzShellGeomGraftObject

    Considering my character has several grafts and shells, I tried running the simulation I told you was making Daz crash with different combinations of grafts/shells, however the results made no sense at all to me, there was no "faulty" thing as far as I could tell.

    So I checked again this stuff about the i9 power settings (PL1/PL2/ICC things I mentionned in my original message), and I saw that Gigabyte had released a new BIOS with the Intel recommended settings at the end of last year.

    I was hesitant at first, didn't want to screw with my RAID array, but I decided to do it anyway and lo and behold: I haven't had a single crash since I flashed the BIOS! 

    I tried many things yesterday, worked with heavy scenes, and everything works flawlessly. And as a bonus it didn't screw with my RAID settings.

    Conclusion:

    - Thank you for trying to help me with my issues, I really appreciate it!

    - If you ever see someone else running an 13th Gen i9 complaining about instability issues, ask them if their MOBO BIOS is up to date.

     

    Post edited by boubakeurjohn at
  • crosswindcrosswind Posts: 8,083

    Ah, you had a pretty unique case but it was nice that you fixed it. I'll certainly mark it as a reference case.

  • boubakeurjohnboubakeurjohn Posts: 36
    edited 5:11PM

    Don't know if these links are allowed are not, but I think they could be useful:

    For anyone interested, here is the Reddit post that helped me figure out this is the issue I was facing: https://www.reddit.com/r/overclocking/comments/1axepvu/optimizing_stability_for_intel_13900k_and_14900k/

    It also might not be that unique of a case, I saw on DeviantArt that other people with Intel i9s are having stability issues: https://www.deviantart.com/edheldil3d/journal/I-m-sorry-DAZ-1056301332 (check the post and comments)

    Post edited by boubakeurjohn at
Sign In or Register to comment.