Daz Studio "ACCESS_VIOLATION" Error
Up until now Daz Studio has worked pretty flawlessly, but the last day or so I have been experiencing pretty consistent crashing. The error is: DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Daz 3D\Applications\64-bit\DAZ 3D\DAZStudio4\dzcore.dll" at 0033:0000000020D5D9E0, DzPropertyGroup::getTree().
These crashes seem to occur when auto-fitting certain items -- though the rhyme or reason to it is inconsistent so I have been having trouble avoiding it. Google research has told me Access Violation errors tend to occur with GPU driver issues, but mine is currently up to date and not confused with an integrated Intel one. Also, the "DzPropertyGroup::getTree()" seems to be more unique without many people encountering it.
Would appreciate some help/advice before I do any full re-installations. This error has made Daz nearly unusable and with the sales going on this weekend, I am pretty disappointed.
Comments
Well one does not have to shop through the program. There is the 30 day return policy if it's a total no-go. However, some have had to roll back to a previous driver, some had to update drivers, if using Nvidia - get the Studio drivers from Nvidia [M$ updates sometimes replaces them with generic drivers, so I've read somewhere in the forums].
I'm not an expert log file reader - looks to me like you've got the program trying to access files online which it can't so you might want to check those Daz Connect links, etc. I don't use Daz Connect. AFAIK most have content stored in either their C, D or eternal # drive, not in the clouds.
egaads ... now I'm getting weird log messages too! Something looking for cloud, customer, content, whathaveyou on clouds or something. Totally out of line. Something we're installing may be causing this. I had just installed some 3rd party and Daz3D content. Sorting through it and hopefully I can find the culprit.
..............................
Confirmed, drivers had been replaced yet again so updating from NVidia seems to have solved the rendering problem for now.
Still wondering who Nick is and why D/S log file was looking for him and customers and so forth geez.