Loading...
> >

DAZ Studio won't start [SOLVED]

marblemarble Posts: 7,500
edited May 2016 in The Commons

I have just been to the NVidia download site and installed the latest GeForce drivers. Now DAZ Studio crashes on start-up. Nothing in the log. I have reinstalled DS just in case but that didn't help either.

Any ideas? Can I back-out these drivers?

Post edited by marble on

Comments

  • marblemarble Posts: 7,500

    Here's the Windows event log:

    Faulting application name: DAZStudio.exe, version: 4.9.1.30, time stamp: 0x56d4a509
    Faulting module name: libirt.dll, version: 24.6000.9999.0, time stamp: 0x5666b227
    Exception code: 0xc0000409
    Fault offset: 0x00000000002a56ec
    Faulting process ID: 0x12b0
    Faulting application start time: 0x01d1a4866c81d401
    Faulting application path: C:\Program Files\DAZ 3D\DAZStudio4\DAZStudio.exe
    Faulting module path: C:\Program Files\DAZ 3D\DAZStudio4\libs\iray\libirt.dll
    Report ID: a594c944-3a26-4477-8843-a30f1c60be16
    Faulting package full name: 
    Faulting package-relative application ID: 

  • mjc1016mjc1016 Posts: 15,001

    Roll back the video drivers and see if that helps...

    That error message is about as helpful as 90% of the rest of them in Windows...in other words, not very.  But my guess is it is driver related.

  • marblemarble Posts: 7,500

    Yes - I'll try to uninstall the new GeForce drivers and reinstall from the Driver CD that came with the PC. I thought it might be because I was running the Display from the Intel i7 but changing over to the GPU didn't help.

  • marblemarble Posts: 7,500

    Well, that's a bit of a concern. Re-installing the old drivers has worked but I wonder whether DS has been tested with the latest drivers? The version I downlaoded was dated April 2016 - very new.

  • mjc1016mjc1016 Posts: 15,001

    The problem is on Nvidia's end...the last several Windows drivers versions have had problems...

  • marblemarble Posts: 7,500

    In that case, I hope this thread serves as a caution to others thinking of updating.

  • mjc1016mjc1016 Posts: 15,001

    It's been the 364 series, mostly...the older series are fine and some of the 'beta' ones are good, too.   Part of it is that most of the recent updates have been tweaked for specific games and not really tested for 'everyday' use.  And part of the problem seems to be Windows 10 itself...it's more a moving target for driver support than anything else.  It makes it harder to come up with a stable driver package, because some of the recent updates have changed system files that the drivers rely upon...and what may have been stable before the update could very well be unstable after.

    At this point, if it's working leave it be...unless there is a compelling feature/fix.

  • marblemarble Posts: 7,500

    Well, "working" is not an absolute term. I've had the PC just over a week and DAZ Studio has crashed at least once a day. In the 3 years I had the Mac I probably had half a dozen crashes in total. But there's a downside to the Apple control-freakery too - if something is broken it is almost impossible to get them to fix it (OpenCL, for example). The crashing of the Windows versions of DAZ Studio was always a problem before I moved to a Mac so I'm disappointed it is still with us.

    By the way, the crashing at the moment seems to be related to IRay preview ... I mean having IRay enabled in a Viewport (usually Interactive). MEC4D highlighted this in another thread but the symptoms can be different. For me, Interactive works but if I move or change things too quickly, it crashes. Also, it seems to have a problem releasing memory when things are deleted from the scene or shaders are changed. For example, If I keep trying on different clothing on a figure (even if I delete the items before trying another), Iray will eventually refuse to render. The log file reports that I don't have a capable GPU available which I assume means that it ran out of VRAM but I don't have the CPU ticked as a render device. 

  • mjc1016mjc1016 Posts: 15,001
    marble said:

    For example, If I keep trying on different clothing on a figure (even if I delete the items before trying another), Iray will eventually refuse to render. The log file reports that I don't have a capable GPU available which I assume means that it ran out of VRAM but I don't have the CPU ticked as a render device. 

    Yes, video memory running out will cause what you are seeing in the log...

    One thing to remember, if you are rendering to a new window (renders not viewport) then Studio will hold the scene in memory (video if it was being used) until you close the window.  So you will run out of memory sooner if you have both the viewport running and leave any render windows open. Closing them and switching the viewport to some other mode should free up the held memory.

  • marblemarble Posts: 7,500

    Well. I do close render windows but this was happening just with Viewport rendering on Interactive. I think you might be right about switching to another mode - I'll have to monitor that.

Sign In or Register to comment.