Panick! Studio won't open my files anymore...

SylvanSylvan Posts: 2,711
edited October 2014 in The Commons

When working in Studio, I called Reality 2.5 and nothing happened.
So I figured Reality or Lux had crashed and I closed down and restarted Studio.
When I tried to re-open my files, Studio crashes :(
Now it won't load any of my files any more...I am panicking a bit here ><<br /> I'm getting this error:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\DzCore.dll" at 0033:00000000E59793CE, DzObject::modifierIterator()+30 byte(s)

Post edited by Sylvan on

Comments

  • SylvanSylvan Posts: 2,711
    edited December 1969

    I reinstalled DAZ and even installed the beta version in the hope that it would work, but it didn't work :(

  • pcicconepciccone Posts: 661
    edited December 1969

    Hi Esther.
    That is a crash in one of the Studio DLLs.

  • NovicaNovica Posts: 23,887
    edited December 1969

    Soooooo...for us non-technical folks, what does that mean and how does she fix it if a re-install didn't work?

  • pcicconepciccone Posts: 661
    edited December 1969

    I wouldn't know how to fix it. You need to be there with the computer and to know why it happened. These are not normal things. It's not like this is the expected behavior of the program.
    What it means is that a part of the program, the DzCore.dll has caused the crash, possibly because of an unexpected situation.
    This is unusual and not common but, with so many things that can be done to a computer, it can happen.
    I would suggest to completely delete Studio, re-install it and avoid installing any other plugin. Then try again. If the problem is continuing then there is something else that causes the issue. Try to remember what you have installed and/or changed in the last few hours. For example, installing an update of the OS can cause this.

  • SylvanSylvan Posts: 2,711
    edited December 1969

    Pret-A-3D said:
    I wouldn't know how to fix it. You need to be there with the computer and to know why it happened. These are not normal things. It's not like this is the expected behavior of the program.
    What it means is that a part of the program, the DzCore.dll has caused the crash, possibly because of an unexpected situation.
    This is unusual and not common but, with so many things that can be done to a computer, it can happen.
    I would suggest to completely delete Studio, re-install it and avoid installing any other plugin. Then try again. If the problem is continuing then there is something else that causes the issue. Try to remember what you have installed and/or changed in the last few hours. For example, installing an update of the OS can cause this.

    Thanks paolo!
    I tried it but still the same error.
    I am really worried that a good portion of my files are tainted :(
    Will write a ticket now to DAZ...fingers crossed!

  • MistaraMistara Posts: 38,675
    edited October 2014

    i had some trouble with DS last year. running install doesn't truly clean up the existing files.
    first i moved my content lib to a bak folder
    then ran the DS uninstaller.
    Deleted the studio program files from hard drive
    rebooted just to be sure
    then ran the install.
    moved content to original folder path.
    had to re-install all the plugins.


    (was trying to make genesis work with carrara, clean DS install seemed to solve the problem)

    Post edited by Mistara on
  • SylvanSylvan Posts: 2,711
    edited December 1969

    i had some trouble with DS last year. running install doesn't truly clean up the existing files.
    first i moved my content lib to a bak folder
    then ran the DS uninstaller.
    Deleted the studio program files from hard drive
    rebooted just to be sure
    then ran the install.
    moved content to original folder path.
    had to re-install all the plugins.


    (was trying to make genesis work with carrara, clean DS install seemed to solve the problem)

    Indeed there are some files that linger around somewhere!
    After I fully uninstalled Studio and also uninstalled every plugin I could find and went through every folder to make sure I had deleted every trace.
    When I reinstalled DAZ, it still knew my recently used files and also opened up the last content folder I had used >>
    What is a bak folder by the way?
    Did you mean back folder?

  • MistaraMistara Posts: 38,675
    edited October 2014

    i mean a backup folder that isn't in the programfiles path.

    there is an user, app subdirectory that holds your prefs and layout. don't usually need to delete those,


    so you manually deleted all the program files with dlls before re-install? still didn't solve?


    underneath everything is the Visual Studio ++ files. maybe you need a fresh install of the VS++?

    Post edited by Mistara on
  • nightwolf1982nightwolf1982 Posts: 1,160
    edited December 1969

    Are you able to open and run DAZ Studio normally, without trying to load a file?

  • SlimerJSpudSlimerJSpud Posts: 1,453
    edited December 1969

    You never mentioned what OS you are running. If Win7 or 8, you might want to read this article:

    http://www.thewindowsclub.com/winsxs-folder-windows-7-8

    If for some reason, Windoze cached a corrupted dll, the application could be running the cached, corrupted version of the dll, even though you thought you uninstalled and did a clean install. The article shows how to use Disk Cleanup to flush the dll cache in the WinSxS folder. It's worth a try.

  • SylvanSylvan Posts: 2,711
    edited November 2014

    i mean a backup folder that isn't in the programfiles path.

    there is an user, app subdirectory that holds your prefs and layout. don't usually need to delete those,


    so you manually deleted all the program files with dlls before re-install? still didn't solve?


    underneath everything is the Visual Studio ++ files. maybe you need a fresh install of the VS++?

    Oh! I tried looking into that, but I have no idea what it is, or what I am looking for.
    Can you point me in the right direction?
    I tried finding all my files, but I am not sure where Windows 7 puts all the dll files though/

    I will try and "flush"!
    (I am using Win7 64 bit by the way)

    And yes, I can still open Studio, but not all my saved scenes will load anymore.

    Thank you so much for thinking with me, it is greatly appreciated !!!

    Post edited by Sylvan on
  • NovicaNovica Posts: 23,887
    edited December 1969

    Are you still stuck? Worried about you.

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,204
    edited December 1969

    is there something in common with the saved scenes you cannot load?

  • WendyLuvsCatzWendyLuvsCatz Posts: 38,204
    edited December 1969

    I ask because if you were to share the scene .duf say on Skype anyone can open it in studio they will just get grey blocks for content they do not have
    it may help problem solve your issue

  • nightwolf1982nightwolf1982 Posts: 1,160
    edited December 1969

    I think we're on the wrong track here. The dll crash was the result of DAZ Studio trying to read from or write to the same part of memory at the same time another program was doing the same. If you can open DAZ Studio and load objects into the scene, this issue is fixed.

    You mentioned that the Reality plugin wasn't responding. Have you tried deleting and re-installing Reality? If any of your scenes were saved with settings specific to the Reality plugin, and that plugin is having problems, it could be causing DAZ Studio to crash when it attempts to load those scenes.

  • SylvanSylvan Posts: 2,711
    edited December 1969

    Novica said:
    Are you still stuck? Worried about you.

    Aww, I am fine Novica ^^
    I am really impressed by all the concerns I hear from people here and there, I feel much loved ^^

    GOOD NEWS
    Skiriki took my file and hassled with it and TADAAA, it worked!
    Some things were deleted from the scene but I got to keep my pose, which was so very important to me!
    Thanks everyone for being awesome!
    Lucky to be part of this community <3</p>

Sign In or Register to comment.