Resolved - Dll exception error leads to crash on startup (every time)

Chronopunk

So as mentioned in another thread, I'm getting a QtScript4.dll exception every time I try to start up. I've submitted a ticket to the Help Desk (over a week ago, now, no reply - I know they're busy so I'm coming here as my backup).

When last attempting to simulate material in a scene, Daz locked up completly (wouldn't even reply to the task manager for several minutes), and when it finally accepted the force-quit, crashed out and gave me a QtScript4 exception.

Upon attempting to restart, that same exception was logged in the crash reporter. Every time since - including after removing Studio entirely via a clean uninstall/reinstall (since I know someone will ask) - I get the same error.

The error is as follows:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtScript4.dll" at 0033:0000000003F9E1BC, QScriptEngine::signalHandlerException()+18380 byte(s)

I'm at a loss, honestly.

I've backed up my library, plugins, etc, deleted Studio from my machine, done a clean reinstall, and nothing is working. This is still the error that I get and I can't figure out why.

(And yes, I have tried the menus/layout/etc rename/rebuild but that didn't work at all.)

I am open to thoughts and suggestions while I wait for the Help Desk to get back to me.

 

 

Chronopunk

So, this was resolved by doing the "Fifty Fifty Or Nothing" method - since the clean installs of the software were still returning the QtScript4.dll error, the next step was to remove the Content Library: if the install is clean and pure, then the issue must reside in the stuff that exists outside the application.

I was able to find the issue quickly - taking the content library out of the equation enabled Studio to launch, but it complained that my "last saved scene" script couldn't be found.

This told me that the issue might reside somewhere with the script.

I renamed my content library back from it's .bak disguise and then attempted a relaunch. QtScript4.dll error.

I renamed the script. Studio launched.

I attempted to open the last saved scene. QtScript4.dll error.

Thus the culprit was found.

Renamed the scene, put the script back, relaunched Studio. Script error, but no QtScript4.dll error.

The issue is the scene (not the script), which I now believe to have become fatally corrupted when Studio hung for the hour and change that caused this issue in the first place.

I created a new scene, with a clean figure, hair and clothing, dropped an HDRI into it and ran a simple simulation and render.

The issue did not repeat itself.

So, problem solved, but heck if it wasn't a bit of a hassle, there.