After update Daz now won't open

Everything was working fine until I updated from 4.22 to 4.23.
Now every time I have tried to open DAZ nothing happens, it loads as if it is starting up then crashes.

The fatal error information just says; DAZStudio.exe caused ACCESS_VIOLATION in module "F:\Program Files (x86)\DAZ 3D\DAZStudio4\plugins\dzshaderbuilder.dll" at 0033:000000004C6BEF7B

What is the best way to fix this or would it be best just to submit a ticket to DAZ support?

«1

Comments

  • Richard HaseltineRichard Haseltine Posts: 101,408

    Is DS set to load a scene when it starts?

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    Is DS set to load a scene when it starts?

    I don't think so, I have never had this issue in the past it's only been since the update. Is there a way I could check this to make sure this isn't the case?

  • I've had the same issue updating from 4.22 to 4.23 on Mac where the plugins have crashed the program upon launch.

  • Richard HaseltineRichard Haseltine Posts: 101,408

    Yes, therev is a plug-in issue with 4.23.0.1 on Macs - sorry, I should have asked which OS you were using.

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    Yes, therev is a plug-in issue with 4.23.0.1 on Macs - sorry, I should have asked which OS you were using.

    I'm using Windows

  • ArtbyGemArtbyGem Posts: 16

    pastafarian720 said:

    I've had the same issue updating from 4.22 to 4.23 on Mac where the plugins have crashed the program upon launch.

    It's so annoying, isn't it? I did used to have it on Mac and I just found it was so broken for Mac users in general I feel like they get left out when it comes to the Mac version.

  • ArtbyGem said:

    pastafarian720 said:

    I've had the same issue updating from 4.22 to 4.23 on Mac where the plugins have crashed the program upon launch.

    It's so annoying, isn't it? I did used to have it on Mac and I just found it was so broken for Mac users in general I feel like they get left out when it comes to the Mac version.

    Yeah, I find it tedious since I really only use Daz on the Mac as a hobbyist thing compare to using it for various stuff on Windows. I do hope for more improvements for Mac users since they seem to be pushing to do more for the Mac version.

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    Mac users might want to try the Public Build http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_23_0_2

    What is the best course of action for the issue I am facing? Is there a fix?

  • ArtbyGemArtbyGem Posts: 16

    pastafarian720 said:

    ArtbyGem said:

    pastafarian720 said:

    I've had the same issue updating from 4.22 to 4.23 on Mac where the plugins have crashed the program upon launch.

    It's so annoying, isn't it? I did used to have it on Mac and I just found it was so broken for Mac users in general I feel like they get left out when it comes to the Mac version.

    Yeah, I find it tedious since I really only use Daz on the Mac as a hobbyist thing compare to using it for various stuff on Windows. I do hope for more improvements for Mac users since they seem to be pushing to do more for the Mac version.

    Yeah I pretty much use it for the same.I am glad you got to solve your issue though!

  • Richard HaseltineRichard Haseltine Posts: 101,408

    ArtbyGem said:

    Richard Haseltine said:

    Mac users might want to try the Public Build http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_23_0_2

    What is the best course of action for the issue I am facing? Is there a fix?

    a test maybe.

    1. Create a new shortcut to Daz Studio (find the application itself, right-click and drag to a convenient spot - just on the desktop will do - and from the menu that opens select the create Shortcut option.
    2. right-click on the hortcut and select Properties
    3. In the "Target" text box you should see the full path to Daz Studio, in quotes. Click to put the cursor after the closing quote, type a space, then paste in
    4.  -instanceName testUI -copySessionUI 0
    5. Click OK
    6. Double-click the shortcut to launch Daz Studio, without any of your customisation settings (so it won't be useful, but it will confirm that some setting is the issue)
  • Richard HaseltineRichard Haseltine Posts: 101,408

    Grr, ignore the 4. in from of the bit I want you to paste - just copy the first hyphen on.

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    ArtbyGem said:

    Richard Haseltine said:

    Mac users might want to try the Public Build http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_23_0_2

    What is the best course of action for the issue I am facing? Is there a fix?

    a test maybe.

    1. Create a new shortcut to Daz Studio (find the application itself, right-click and drag to a convenient spot - just on the desktop will do - and from the menu that opens select the create Shortcut option.
    2. right-click on the hortcut and select Properties
    3. In the "Target" text box you should see the full path to Daz Studio, in quotes. Click to put the cursor after the closing quote, type a space, then paste in
    4.  -instanceName testUI -copySessionUI 0
    5. Click OK
    6. Double-click the shortcut to launch Daz Studio, without any of your customisation settings (so it won't be useful, but it will confirm that some setting is the issue)

    This didn't do anything for me. If I delete the dzshaderbuilder.dll file, would that cause damage in the long run?

  • Richard HaseltineRichard Haseltine Posts: 101,408

    Same error? It isn't often the fdix but it may be worth reinstalling Daz Studio.

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    Same error? It isn't often the fdix but it may be worth reinstalling Daz Studio.

    I deleted that file which seems to fix it but I have reinstalled it several times and every time comes up with the same error - DAZStudio.exe caused ACCESS_VIOLATION in module "F:\Program Files (x86)\DAZ 3D\DAZStudio4\plugins\dzshaderbuilder.dll" at 0033:000000004AC1EF7B

    I've generally never had this issue and very frustrating now, though I do appreciate your help and taking the time to help me. Is there a way to install an older version?

  • ArtbyGemArtbyGem Posts: 16

    I've attached the error report file. Maybe yourself can make better sense of it?

    zip
    zip
    DAZStudio_error_report_241014-162837.zip
    40K
  • Richard HaseltineRichard Haseltine Posts: 101,408
    edited October 16

    Ah, so you are using the 32 bit version of Daz Studio. Sorry, I had missed that.

    Post edited by Richard Haseltine on
  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:


    Ah, so you are using the 32 bit version of Daz Studio. Sorry, I had missed that.

    I shouldn't be as my computer is a 64bit and I have downloaded the 64bit version of Daz Studio

  • Richard HaseltineRichard Haseltine Posts: 101,408
    edited October 17

    The entries in the crash report all refer to the 32 bit vesion - Program Files (x86) rather than Program Files.

    Post edited by Richard Haseltine on
  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    The entries in the crash report all refer to the 32 bit vesion - Program Files (x86) rather than Program Files.

    Is there a way to fix that and is that what is causing DS not to start?

  • Richard HaseltineRichard Haseltine Posts: 101,408

    Try running the 64 biot version directly - go to C:Program Files/daz 3D/Studio4/

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    Try running the 64 biot version directly - go to C:Program Files/daz 3D/Studio4/

    There is nothing in that folder even though the 64-bit is downloaded. I'm reinstalling it again after making sure all the folders and files have been removed. I'm also double checking the drivers again. Otherwise is there anyway of getting like a patch update, in hopes it would fix my issue?

  • Richard HaseltineRichard Haseltine Posts: 101,408
    edited October 17

    In Install manager go to Advanced settings ands in the Installation tab check that the paths for 32 bit and 64 bit software are correct - I suspect they are the same and you are installing one over the other.

    Application paths.jpg
    512 x 127 - 14K
    Post edited by Richard Haseltine on
  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    In Install manager go to Advanced settings ands in the Installation tab check that the paths for 32 bit and 64 bit software are correct - I suspect they are the same and you are installing one over the other.

    Reinstalled, double checked all drivers. Nothing is being flagged as the issue yet I am still getting a fatal error message with the same issue with that same plugin.
    "plugins\dzshaderbuilder.dll" at 0033:000000004422EF7B" 
    Though I have found that if I remove that file from the folder, my Daz opens as normal but if I put it back in the application won't open again. Is the dzshaderbuilder.dll file needed?

  • Richard HaseltineRichard Haseltine Posts: 101,408

    What are you installation paths, the equivalent to those in my screenshot?

  • ArtbyGemArtbyGem Posts: 16

    Richard Haseltine said:

    What are you installation paths, the equivalent to those in my screenshot?

    The same as yours, UPDATE: I have got it to load now but every time I go to load a scene in from my saved scenes, DS crashes and says this: "DAZStudio.exe caused UNKNOWN_ERROR in module "C:\WINDOWS\System32\KERNELBASE.dll" at 0033:00000000FD71B699, RaiseException()+105 byte(s)" 
    My Windows is all up to date even with the optional updates.

  • Richard HaseltineRichard Haseltine Posts: 101,408

    Any scene or a specific scene? Will it load content into a new scene? If it will, and you save it, will it reload? If you mean the Saved Scenes category, what happens if instead you use File>Open?

  • artxtapartxtap Posts: 158
    edited October 19

    maybe the scene you saved was created with the 32bit version?

    Post edited by artxtap on
  • ArtbyGemArtbyGem Posts: 16

    UPDATE: All issues are now fixed, I have reinstalled Windows and installed all the updates again including optional driver ones. All is working now. The fresh install of Windows seemed to have fixed everything!

    Thank you to all who gave me their advice and help!

Sign In or Register to comment.