Loading...
> >

HELP - FATAL ERROR

mlolyamlolya Posts: 36
in Technical Help (nuts n bolts)

Lately whenever I try to render even a slightly complex scene DAZ encounters a fatal error and shuts down. I'm getting the following message:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\libs\iray\libneuray.dll" at 0033:00000000AB9AC0CE, mi_neuray_factory()+4039486 byte(s)

can anyone help!

Comments

  • Richard HaseltineRichard Haseltine Posts: 108,072

    That's an Iray error. What GPU do you have, and what driver version are you using?

  • mlolyamlolya Posts: 36

    I have a GeForce GTX 1050 with 4 Gig, but it's what I've been using for a while and this problem is something new. I just downloaded the latest GeForce driver and made sure that both the GPU and the CPU are checked in the advanced render settings and the problem is still there!

  • Richard HaseltineRichard Haseltine Posts: 108,072

    It may be worth trying to uninstall the driver, then reinstall.

  • mlolyamlolya Posts: 36

    Okay, here's what I learned for others who may run into this issue. As I mentioned above the crashes just seemed to begin recently and I had't changed anything that I cosuld think of. So I went over what was different about the scene that I was trying to render. It was happening with several differnt scenes and not with others. Then I realized that the scenes that crashed had one thing in common. A new Gen 8 hair that I purchased. 

    I replaced the hair with a differnt hair and the crashes stopped. I'm not sure why that hair crahes my renders, but I won't be using it anymore.

  • nonesuch00nonesuch00 Posts: 18,729
    mlolya said:

    Okay, here's what I learned for others who may run into this issue. As I mentioned above the crashes just seemed to begin recently and I had't changed anything that I cosuld think of. So I went over what was different about the scene that I was trying to render. It was happening with several differnt scenes and not with others. Then I realized that the scenes that crashed had one thing in common. A new Gen 8 hair that I purchased. 

    I replaced the hair with a differnt hair and the crashes stopped. I'm not sure why that hair crahes my renders, but I won't be using it anymore.

    The hair likely cused you to run out of memory, particularly if it was Fibre Mesh har. You can get around the out of memory problem most rtimes by setting optimize to Memory instead of Speed.

  • Richard HaseltineRichard Haseltine Posts: 108,072
    nonesuch00 said:
    mlolya said:

    Okay, here's what I learned for others who may run into this issue. As I mentioned above the crashes just seemed to begin recently and I had't changed anything that I cosuld think of. So I went over what was different about the scene that I was trying to render. It was happening with several differnt scenes and not with others. Then I realized that the scenes that crashed had one thing in common. A new Gen 8 hair that I purchased. 

    I replaced the hair with a differnt hair and the crashes stopped. I'm not sure why that hair crahes my renders, but I won't be using it anymore.

    The hair likely cused you to run out of memory, particularly if it was Fibre Mesh har. You can get around the out of memory problem most rtimes by setting optimize to Memory instead of Speed.

    The optimisation you are referring to is for instances, it doesn't have anything to do with non-instanced items.

  • nonesuch00nonesuch00 Posts: 18,729
    Richard Haseltine said:
    nonesuch00 said:
    mlolya said:

    Okay, here's what I learned for others who may run into this issue. As I mentioned above the crashes just seemed to begin recently and I had't changed anything that I cosuld think of. So I went over what was different about the scene that I was trying to render. It was happening with several differnt scenes and not with others. Then I realized that the scenes that crashed had one thing in common. A new Gen 8 hair that I purchased. 

    I replaced the hair with a differnt hair and the crashes stopped. I'm not sure why that hair crahes my renders, but I won't be using it anymore.

    The hair likely cused you to run out of memory, particularly if it was Fibre Mesh har. You can get around the out of memory problem most rtimes by setting optimize to Memory instead of Speed.

    The optimisation you are referring to is for instances, it doesn't have anything to do with non-instanced items.

    Most people instance without realizing it - 2 G8F or 2 G8M characters in the same scene involves instancing. The OP states nothing about the details of the scene they are rendering and switching Optimization for the crashing scene from Speed to Memory definately will not cause DAZ Studio to crash because of the switch. If it's still happening they know why already but it won't be because of the optimization type chosen..

  • Richard HaseltineRichard Haseltine Posts: 108,072
    nonesuch00 said:
    Richard Haseltine said:
    nonesuch00 said:
    mlolya said:

    Okay, here's what I learned for others who may run into this issue. As I mentioned above the crashes just seemed to begin recently and I had't changed anything that I cosuld think of. So I went over what was different about the scene that I was trying to render. It was happening with several differnt scenes and not with others. Then I realized that the scenes that crashed had one thing in common. A new Gen 8 hair that I purchased. 

    I replaced the hair with a differnt hair and the crashes stopped. I'm not sure why that hair crahes my renders, but I won't be using it anymore.

    The hair likely cused you to run out of memory, particularly if it was Fibre Mesh har. You can get around the out of memory problem most rtimes by setting optimize to Memory instead of Speed.

    The optimisation you are referring to is for instances, it doesn't have anything to do with non-instanced items.

    Most people instance without realizing it - 2 G8F or 2 G8M characters in the same scene involves instancing. The OP states nothing about the details of the scene they are rendering and switching Optimization for the crashing scene from Speed to Memory definately will not cause DAZ Studio to crash because of the switch. If it's still happening they know why already but it won't be because of the optimization type chosen..

    Not, as far as I am aware, if they differ (in shape or pose). DS has only one copy of any particular base shape in memory, which is why you can't do different Geometry Editor changes (if I understand), but then they get various modifiers added on top and are not, to the best of my knowledge, passed to Iray as instances.

Sign In or Register to comment.