Loading...
> >

DAZ 4.12 has Fatal Error crash when opening (fixed)

geoduck42_9c16d169b0geoduck42_9c16d169b0 Posts: 11
edited November 2020 in Daz Studio Discussion

On my Win 10 PC, my copy of DAZ 4.12 has abruptly started throwing up a Fatal Error message when trying to load, when it reaches "building interface":

DAZStudio.exe caused INT_DIVIDE_BY_ZERO in module "C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_2cec8fd58a80e6ea\igdrcl64.dll" at 0033:00000000FF6C93B9, clReleaseGlSharedEventINTEL()+252969 byte(s)

That .DLL file appears to be associated with my Intel graphics card. I updated the Intel driver, no luck. None of my other programs seem to be having any problems. I have Malwarebytes security. I did submit an offical help request, but thought I'd ask here too, maybe someone has a brilliant suggestion.
 

Post edited by geoduck42_9c16d169b0 on

Comments

  • Richard HaseltineRichard Haseltine Posts: 102,273

    Is that the only GPU on your system or do you also have a separate nVidia or AMD GPU?

  • geoduck42_9c16d169b0geoduck42_9c16d169b0 Posts: 11

    Just the Intel Graphics 360.

  • geoduck42_9c16d169b0geoduck42_9c16d169b0 Posts: 11

    The DAZ folks got back to me with gratifying speed, and gave me this set of instructions:

    Rename the plugins folder in the Daz Studio install directory (C:/Program Files/DAZ 3D/DAZStudio4) and launch Daz Studio. If it runs please let me know. You can rename the plugins folder back to the original name and then move "dzdynamics.dll" out of there and launch again.

    No idea why that worked, but it did, at least for now..

     

     

  • premierart_2340fada0fpremierart_2340fada0f Posts: 38

    Is there anything in particular I need to name the folder as, cause I've had the same problem, renamed the folder "old plugings", but it didn't solve my problem. Thanks

  • geoduck42_9c16d169b0geoduck42_9c16d169b0 Posts: 11
    edited November 2020

    I didn't hear anything about specific names, sorry. And for anyone else who comes along with this problem, be aware that "dzdynamics.dll" is what controls dForce in DAZ, and as long as it's out of position, dForce will not be available to use.

    EDIT: ..which means, I can attest, if you go to the tab where dForce should be listed as an option, you get a blank box.

    Post edited by geoduck42_9c16d169b0 on
  • fernfairy73_bb8ec3d37cfernfairy73_bb8ec3d37c Posts: 82

    is it just me or has been since they up dated everything in the store as well as daz

  • fernfairy73_bb8ec3d37cfernfairy73_bb8ec3d37c Posts: 82

    this is why i hate updates

  • Richard HaseltineRichard Haseltine Posts: 102,273

    The store update has had no effect on DS, other than Connect possibly.

  • pluplu Posts: 0

    I noticed on my Windows 10 that there had been an update of the onboard Intel graphics.

    I looked at the dates of the folders in C:\Windows\System32\DriverStore\FileRepository which started with igdlh64.inf_amd64.  In my case also igdlh64.inf_amd64_2cec8fd58a80e6ea.

    Now open the Registry Editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors

    On my PC, I had two entries there pointing to the new and the previeous version of the Intel FileRepository folder.

    First right click the Vendors key and export it as a safe copy (remember where you put it!).

    Then delete the line which does NOT point to that most recent Intel FileRepository folder.  So you'll keep only one entry there pointing to the C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_2cec8fd58a80e6ea\igdrcl64.dll

    Now try again.  For me it worked.

Sign In or Register to comment.