Fatal error while rendering.

Kat_KatKat_Kat Posts: 169
edited June 2015 in New Users

I hav e no idea what is going on, created a new scene, I am getting a fatal error as soon as it stops compiling the shaders and begins rendering, the odd thing, if I do not close the fatal error window, the render chugs along and will finish by the looks of it if I let it anyway.

A couple days ago everything was working perfectly, quick Iray renders, worked perfect, reloaded the same scene, it now nearly locks my computer it lags it out so badly and the same scene I rendered perfectly fine, now also gives me the same fatal error, which will also complete perfectly fine behind the fatal error message if I do not close it.

I can provide some of theeorror calls if that will help.

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\libs\iray\libiray.dll" at 0033:00000000C9B2DF63, mi_plugin_factory()+371363 byte(s)

Edit: As an oddity, once the fatal error occurs, the render speed goes right up again, barely any system lag.

Post edited by Kat_Kat on

Comments

  • atticanneatticanne Posts: 3,009
    edited December 1969

    Please file a report on it with the Zen desk. Click on Help above to get there.

  • ChoholeChohole Posts: 33,604
    edited December 1969

    talas said:
    I hav e no idea what is going on, created a new scene, I am getting a fatal error as soon as it stops compiling the shaders and begins rendering, the odd thing, if I do not close the fatal error window, the render chugs along and will finish by the looks of it if I let it anyway.

    A couple days ago everything was working perfectly, quick Iray renders, worked perfect, reloaded the same scene, it now nearly locks my computer it lags it out so badly and the same scene I rendered perfectly fine, now also gives me the same fatal error, which will also complete perfectly fine behind the fatal error message if I do not close it.

    I can provide some of theeorror calls if that will help.

    DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\libs\iray\libiray.dll" at 0033:00000000C9B2DF63, mi_plugin_factory()+371363 byte(s)

    Edit: As an oddity, once the fatal error occurs, the render speed goes right up again, barely any system lag.

    which devices are checked in the Advanced tab of render Settings, and is OptiX acceleration on

  • Kat_KatKat_Kat Posts: 169
    edited December 1969

    I have tried it with both cpu on and off and both my GeForce cards are selected, as well as optix acceleration is on (Sli is disabled, discovered that early it increases render times, may be anecdotal but it seems to keep from splitting the memory?). They are unchanged from several days ago when it ran fine. I reloaded a scene I did that rendered complete, with the same render settings still saved and it now keeps encountering a fatal error (Those settings are Cpu, x2 gpu, optix.), I have uninstalled and reinstalled only daz 4.8. I do not know if uninstalling my entire library would help, but I am willing to try that.

    I have submitted a technical support ticket but thought if someone has encountered this in the community....many hands make light work after all.

  • ChoholeChohole Posts: 33,604
    edited December 1969

    There's no need to uninstall content. Have drivers been updated since it was working?

  • Kat_KatKat_Kat Posts: 169
    edited December 1969

    No, I keep NVidia set so I have to approve it, I don't trust my computer >.>. No new drivers, no new software. At least none I can think of. My first thought is something is corrupt, but beyond that. I cannot understand it. It will render a base figure V7 with hair and iray mats, albeit it slows my computer to unusable levels. When it shouldn't.

  • ChoholeChohole Posts: 33,604
    edited December 1969

    try deleting half the stuff in the scene and see it if renders, if it does undo and delete the other half and test. That should enable you to find the bad item, if it is due to a single item.

  • mjc1016mjc1016 Posts: 15,001
    edited June 2015

    This is the same problem as

    http://www.daz3d.com/forums/discussion/58432/

    (And there are a couple of others like this floating around)

    The Access_Violation errors are always in the renderer, either Iray or 3Delight and can be with any scene on any hardware…so it is a real bug, not just something in the scene.

    It’s also NOT limited to amount of memory used.

    Access_violations are somewhat tricky to track down and may not always be caused by what is showing in the error. The full crash log files are needed to see what’s going on…and many times this error can be a permissions related one…or even indicative of bad RAM.

    File a support ticket.

    I've been trying to track down the actual source of this problem for a month now...it first showed up for me in the last build of 4.7, but on my main computer only, which is about as non-standard a configuration Studio can run on (and unsupported). It IS NOT...scene related, I can get it to happen with any size scene, with any content...under certain conditions. It can happen with any lights/shaders. It doesn't happen using the REYES hider in 3Delight, and only certain cached modes of the raytrace hider. It seems to be related to a cache/permissions problem and not with the render engine. But possibly something else in Studio itself.

    But I have not completely ruled out bad RAM...but the latest build of 4.8 (4.8.0.59) has cut it down to occasionally, as opposed to regularly.

    Post edited by mjc1016 on
  • Kat_KatKat_Kat Posts: 169
    edited June 2015

    I will have to agree, as a scene that rendered out perfect 4 days ago. Was saved. I now reload, touch nothing, not even render settings as those save with the scene as well, now throws the fatal error and access violation.

    The other thing that is perplexing, is the massive slowdown I now experience running a render that does not happen to throw a fatal error. When I ran the render I speak of 4 days ago. I could play elder scrolls online, with max setting while it ran, albeit a little choppy. Then watched a movie with a tiny bit of lag. Now even just a naked v7 with iray mats and hair, nearly locks my computer in lag. Even without a fatal error.

    I have also submitted a support ticket, with the full error log.

    Post edited by Kat_Kat on
  • alan bard newcomeralan bard newcomer Posts: 2,248
    edited June 2015

    don't have fatals.. .but I Iet the install manager update everything last night...
    my renders are blazing fast 2 seconds, but then it's an empty screen when finished...
    the viewport etc have all changed... colors etc
    ---
    any suggestions... and how do I get the older version back...
    ---
    so i went to the software page to redownload the studio file and again it cross references the order from Feb but doesn't name the version....
    the version in my installed folder is
    4.8.0.55
    but apparently there is now a 4.8.0.59 which may fix the problem.
    the manual download says dazstudio 4.8.0.59 but the one in the download managers folder is not ided... just 48win64bit and dated the 20th... but if all of them in the manager have the same name how does it know to update again?
    ---
    install manager now wants to install daz so I cancelled the manual download...
    just a note to the IM programmer...
    you flashed a message that said please wait while we download 4.8 and the genesis 3 content... fine...
    but you bypassed the logic in IM so it doesn't have a progress bar, doesn't show a speed ... so I really have no clue that it is actually doing the download...
    ---
    and now an hour later I return to my computer... there are no messages about new software downloaded or installed...
    ---
    so how do I even know if anything has happened? Well checking the exe file in the DAZ 4 folder does show4,.8.0.59 so I guess it's done...
    ---
    even more delightful is the fact that it is now rendering... now to make a deadline or two...

    Post edited by alan bard newcomer on
  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    DIM keeps track of that internally...don't ask...it's better not to know...

    But you can always check by going to Help > About in Studio.

  • alan bard newcomeralan bard newcomer Posts: 2,248
    edited December 1969

    once it had installed the 4.8 zip from last week, when I cranked up the installer this evening it read the installed version and realized it need to be updated but I don't think it knew before because there was also a hot fix that was realeased between the one it installed yesterday and the one today.
    ---
    As it is I'm working, it's rendering and that will keep us happy for now.

  • fixmypcmikefixmypcmike Posts: 19,613
    edited December 1969

    alanbard said:
    once it had installed the 4.8 zip from last week, when I cranked up the installer this evening it read the installed version and realized it need to be updated but I don't think it knew before because there was also a hot fix that was realeased between the one it installed yesterday and the one today.
    ---
    As it is I'm working, it's rendering and that will keep us happy for now.

    That's right, it doesn't connect to the server until you tell it to.

  • alan bard newcomeralan bard newcomer Posts: 2,248
    edited December 1969

    last night it downloaded new products and updates...but it didn't download a new 4.8 because there was one in the install folder.
    but until it installed the daz in the zip ... I don't think it knew it had an old zip rather than a new one....
    the version it installed last night was .55 because that's what the exe said when I checked
    tonight, but tonight it downloaded and installed .59
    but even though the zip was sitting in my install folder... it didn't check in and add the .58 from the 19th
    I think it downloaded the zip on the 15th...
    ---
    any way I'm pleased, but paranoid about doing updates until I hear good feed back because losing the ability to render and not being able to reinstall the working version of the day before was scary.
    I am now also going to download the manual installer for .59 --- so if the next install of .6 blows something out I don't have to wait for a fix....

  • Kat_KatKat_Kat Posts: 169
    edited July 2015

    Ok, two things, running my laptop on a 1500 watt inverter in my truck, realized one of the wires was a touch loose so the inverter was not giving out full power, so my laptop was possibly not getting the power it needed. Second, it seems some shaders and some lights really, really, REALLY do not get along well. Distant light and the granite shader being two in particular. Especially where the granite may want to reflect back at itself. Third, it seems somewhere along the line my SLI was re-enabled. I may have done it as a test and forgot to turn it off, I have also noticed the odd time SLI will enable and disable itself for no apparent reason. With it disabled, my power stable, I am rendering the scene that before made me have to perform a hard shutdown because it lagged my machine out so hard I could do nothing, with no fatal error and minimal lag.

    I will not consider this solved, because I have no idea which if any of these things solved this, as my first render that threw fatal errors the second time around had neither granite nor a distant light...

    If I had to put money, I would say it was SLI combined with a power shortage. Though why it would give a fatal software call is a little beyond me.

    Post edited by Kat_Kat on
  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    talas said:
    Ok, two things, running my laptop on a 1500 watt inverter in my truck, realized one of the wires was a touch loose so the inverter was not giving out full power, so my laptop was possibly not getting the power it needed. Second, it seems some shaders and some lights really, really, REALLY do not get along well. Distant light and the granite shader being two in particular. Especially where the granite may want to reflect back at itself. Third, it seems somewhere along the line my SLI was re-enabled. I may have done it as a test and forgot to turn it off, I have also noticed the odd time SLI will enable and disable itself for no apparent reason. With it disabled, my power stable, I am rendering the scene that before made me have to perform a hard shutdown because it lagged my machine out so hard I could do nothing, with no fatal error and minimal lag.

    I will not consider this solved, because I have no idea which if any of these things solved this, as my first render that threw fatal errors the second time around had neither granite nor a distant light...

    If I had to put money, I would say it was SLI combined with a power shortage. Though why it would give a fatal software call is a little beyond me.

    Iray + SLI = not nice things.

    Crappy power + anything = not nice things.

  • Kat_KatKat_Kat Posts: 169
    edited December 1969

    combined with a light with no falloff and reflective materials+SLI+crappy power= Fatal errors and hard restarts due to computer locks I assume. Now onto....HDR lighting headaches lol....

Sign In or Register to comment.