Loading...
> >

Daz Studio 4.6 Pro crashes at launch (NVidea GeForce 770)

elusivealbumselusivealbums Posts: 0
edited January 2014 in Technical Help (nuts n bolts)

I've been using Daz Studio mostly problem free for several months now and have hundreds of successful renders. However, just tonight Daz Studio crashed. But now every time I try and start it up to an empty scene, it loads up about a third of the way and crashes!

The Exception reason stated is this:

DAZStudio.exe caused INT_DIVIDE_BY_ZERO in module "C:\Program Files\DAZ 3D\DAZStudio4\QtGui4.dll" at 0033:0000000062C1E5AF, QPixmap::grabWindow()+4719 byte(s)

I'm running this on a Nvidea GeForce GTX 770 which is no weak little card. I am launching 4.6 Pro 64-bit on Windows 8. Restarting my computer did nothing, and this happened after already having the program open for several hours so it is unlikely a windows update suddenly applied itself.

I did not add any content recently and no previous installed content has caused it crash before. As mentioned before, I'm just loading it up to an empty, fresh scene, so it's not when trying to load any particular asset.

Has anyone encountered something like this? I will attempt the usual things--update drivers, reinstall, etc, and have submitted a bug report--but if anyone else has encountered this and has advice I'd love to hear it. Thanks!

Edit: Uninstalling and reinstalling Daz did not fix anything.

error.png
547 x 523 - 29K
Post edited by elusivealbums on

Comments

  • Richard HaseltineRichard Haseltine Posts: 100,941
    edited December 1969

    If it is suddenly doing it I would suspect a driver update - nVidia do, I think, update without prompting by default.

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    Richard Haseltine said:
    If it is suddenly doing it I would suspect a driver update - nVidia do, I think, update without prompting by default.

    I did a little looking around, last night, and it seems this particular error is pretty common in gaming circles and many times does indicate driver problems...but NOT video drivers. It is many times caused by AUDIO driver problems.

    Depending on your computer...especially if it is an 'off the shelf' machine from a big name label, it can have all sorts of 'auto updaters', some of which can/will update drivers...so start checking to see if there have been any updated drivers, recently. Also, AV updates and OS updates can cause problems...

  • elusivealbumselusivealbums Posts: 0
    edited January 2014

    This is what tech support has had to say so far--the suggestions are along a bit of a different line, stating that it may be a database issue. I'm unable to test at the moment, likely not until later tonight or in a few days.

    ---------------------------------

    Hi,

    Thanks for the error log. It looks like you have a corrupt database. There is an involved process to fix that. However, before you do that, let's try something easy. I'd like you to clear out the DSON Cache folder, if possible. Normally, you could launch Studio and go to EDIT --> Preferences --> General --> DSON Cache Files. This would give you the path to the DSON Cache Folder. Since you probably cannot get DAZ Studio to launch and stay stable for that long, you should look for the default folder.

    The default folder for the DSON Cache folder is here:
    C:/Users/[your user account]/AppData/Roaming/DAZ 3D/dson/cache

    Find the cache folder and delete all the files and folders (if any) inside of it. Then try to launch Studio. If that works, it should be good.

    However, based upon the message of the log you sent me, I believe the real cause is a corrupt database. If doing the above doesn't resolve this, then you need to trash the database and re-launch Studio.

    Scroll down to REBUILD THE METADATA DATABASE. Please following these instructions carefully. If you have questions about what they mean, please ask before doing them.
    https://helpdaz.zendesk.com/entries/22523891-Trouble-shooting-the-Smart-Content-Pane

    Please let me know the status of this issue.

    ---------------------------

    Is there a way to use or another way to collapse all that?

    Also, my machine is prebuilt from IBuyPower and is indeed a gaming machine. I will also check out if drivers have been updated recently.. The crash literally happened while loading one scene from another one.

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

    elusivealbums said:
    This is what tech support has had to say so far--the suggestions are along a bit of a different line, stating that it may be a database issue. I'm unable to test at the moment, likely not until later tonight or in a few days.

    Also, my machine is prebuilt from IBuyPower and is indeed a gaming machine. I will also check out if drivers have been updated recently.. The crash literally happened while loading one scene from another one.

    That was another area it seems to occur...but driver issues outweighed database ones by a considerable margin, when I was looking up the error. So that seems to be the logical one to look at, first.

  • elusivealbumselusivealbums Posts: 0
    edited December 1969

    What tech support suggested did not work.

    In addition, I've gone to my View update history in Windows 8.1, and there is no listed updated newer that one from the 14th. I've rendered dozens of images since then.

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    What tech support suggested did not work.

    In addition, I've gone to my View update history in Windows 8.1, and there is no listed updated newer that one from the 14th. I've rendered dozens of images since then.[/quote

    The last and least common cause I found...hard drive failure. Basically, a bad sector that has corrupted a small part of the program or driver's code...

  • frank0314frank0314 Posts: 14,056
    edited December 1969

    Did you check Nvidia's website to see if you have a driver update? There have been several updates to mine in the last couple months

  • elusivealbumselusivealbums Posts: 0
    edited December 1969

    The last update for my graphics card, the Nvidia GeForce 770 on Windows 8 64 bit, looks like it came out on November 27.

  • elusivealbumselusivealbums Posts: 0
    edited December 1969

    So as it turns out the culprit in my scenario was actually a particular plugin, dzrenderlibrary.dll . Removing it from my plugins folder allows Daz to load and--as far as I'm aware--operate as normal.

    Anyone know what dzrenderlibrary.dll is responsible for? It sounds somewhat important, but I've not--yet--encountered any problems running Daz Studio without it.

  • Richard HaseltineRichard Haseltine Posts: 100,941
    edited December 1969

    That's the render library - a pane which shows thumbnail views of the images in the folder it is pointing to, and automatically generates images even if the image was not originally a render. I imagine there was either a bad file in there that caused it to crash when DS tried to generate the thumbnail or something about the folder being pointed to.

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    Richard Haseltine said:
    That's the render library - a pane which shows thumbnail views of the images in the folder it is pointing to, and automatically generates images even if the image was not originally a render. I imagine there was either a bad file in there that caused it to crash when DS tried to generate the thumbnail or something about the folder being pointed to.

    I wonder what it would do if the folder it was pointing to had a permissions problem or wasn't writeable?

  • Richard HaseltineRichard Haseltine Posts: 100,941
    edited December 1969

    mjc1016 said:
    Richard Haseltine said:
    That's the render library - a pane which shows thumbnail views of the images in the folder it is pointing to, and automatically generates images even if the image was not originally a render. I imagine there was either a bad file in there that caused it to crash when DS tried to generate the thumbnail or something about the folder being pointed to.

    I wonder what it would do if the folder it was pointing to had a permissions problem or wasn't writeable?

    Quite, but I can't immediately see where the path is stored to allow it to be recovered for checking.

Sign In or Register to comment.