what does this crash error mean? Content Gatherer question.
WillowRaven
Posts: 3,787
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\dzcore.dll" at 0033:0000000060E61893, DzObject::modifierIterator()+35 byte(s)
Post edited by WillowRaven on
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Usually, it means that your system RAM wasn't sufficient to run everything. It can be caused by a too large scene, or running too many programs/things at the same time, or a render going from GPU to CPU.
Hmm... I have plenty of ram and space ... so how would I prevent the last part?
All I know is I had no problem opening the scene before ... accidentally, I deleted my entire runtime folder. So I painstakingly tracked down every single missing file and reinstalled everything. Daz opens fine, but when I try to open the scene it crashes.
? reboot the computer
? all drivers up-to-date
? tell D/S to relocate all its files or one of the other options {from the Content Pane's hamburger menu}
It "might" mean that you need to reinstall D/S. However if D/S is otherwise working, if it were I, I would go with resetting up the scene and saving it again with a new name. Clear all, then see if it can open the new scene.
So completely start the scene fresh ... just start over? I wouldn't know where to begin because I no longer have the list, lol. Didn't think I'd need it anymore.
Or do I use the log file after it crashes just to load stuff into a generic scene then save, then try to open the crashing file?
Unless you have some scene subsets to help compile it, yes.
............
Sure, you could try from the log file to discover the items, but first see if the new scene file will load. If it won't then there's something wrong with one of the ingrediants.
I've re-installed Daz studio via install manager, but I'm getting a new error message when I open Daz (sans scene):
A valid PostgreSQL CMS connection could not be established. Several Daz Studio features that require a valid PostgreSQL CMS connection, such as context aware content views and loading content installed using the Daz Connect service, will not be available. Check your network, anti-virus, and firewall settings for conflicts.
Soooo ... translation?
I hope this is all the problem is 'cause it's the easiest solution. Check that the pathway is correct. For some silly reason I have found that yes, with installation [actually for me it was using DIM] had this setting mis-matched.
This is the default position as D/S is installed on the computer [i.e. not an external hard-drive].
And the AppData is a hidden folder, so this is how to get it to be visible.
DIM keeps telling me it's installed it, but it won't show me where it installs it, then I close DIM and there it sits squatting in the ready to install tab again.
So I went to the folder, but what am I supposed to do once there?
Years ago I found DIM could not install D/S on my system ... possibly because W10 guards the computer and wants a person response as to whether or not to allow that type of a download/installation.
So I go to my Product Library and manually download D/S and the Postgre etc., and then run those manually from the Desktop. They install to the default installation places as per the OS protocols.
One of the (many) reasons, why I usually do not install anything with the default paths, especially to any folders Microsoft is trying to force people to use (=any and all premade whatever "My Scribbles" etc.)
The main one I've had to look out for were attempts to install things to "the cloud" ... no want programs on their clouds lol ...
OK ...after re-installing Daz several times ... it now opens correctly again, but the scene still crashes and I can't figure out why. Here is the error file if it helps anyone tell me why.
You have 16GB's of RAM and 6GB's of VRAM, my guess is that you are running out of both.
Another thing that jumped out from your log, was having special characters on folder names - Even though one could.,, doesn't mean one should use any other characters than A to Z, numbers 0 to 9, the underscore and dash to ensure compatibility between different programs in different context
I don't think this would cause a crash but did notice that there is a missing texture:
Can it open other scenes okay?
Making several subset scenes instead of one super large scene tends to work out better. They can all be loaded 'as needed' then and if one file gets corrupted all is not lost.
It's not that big a scene ... five figures in clothes and a bus ... nothing more ... and before I accidentally deleted my runtime folder and had to reinstall all the 'lost' files, it opened just fine, so why would I suddenly not have enough ram?
ok ... since my characters were custom dialed, how do I go about rebuilding the scene EXACTLY ... I don't see how the log can help me. How do I see everything in the scene?
If it is that the file is corrupted, it could be giving D/S all kinds of weird messages which "do not compute" so D/S crashes. We seldom know why a scene file becomes inoperable but it happens. Over the years for different people, cause was a shader, or cause was a script, or cause was a .tiff, or cause was ....
If it were I, I would consider setting up a scene subset, one each for all 5 characters, and then one for the bus as well.
Remember too that D/S isn't the only program working on the computer. There's the AV and there's Microsoft forever updating stuff and all the other programs that love to call home to update files.
.... from your own memory. From previous renders or notes written down. After custom dialing the characters, did you make any shape presets?
--
Your log says when opening DS that you have just 8.2GB's of RAM available, which is very little and that is before attempting to open any scenes.
There has been plenty of posts of users with too little RAM having problems and crashing being one of those problems, apparently DS does not like using the drives for virtual memory.
What do you have running on the background that eats half of your RAM?
Looking at the Task Manager, Chrome takes up a lot, but again, it always has, so I can't imagine that being the problem all of a sudden. On the off chance that it is, I turned off all chrome instances and tried again.
Here is the latest crash message:
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\dzcore.dll" at 0033:00000000CF8E1893, DzObject::modifierIterator()+35 byte(s)
What does that mean?
Oh, and this attempt was an earlier version of the scene.
...DzObject::modifierIterator()+35 byte(s). Problem with some modifier. The last lines from the log file before the Daz Studio crashed:
2022-06-02 23:00:22.543 [INFO] :: Preparing modifiers... 2022-06-02 23:00:22.625 [WARNING] :: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(5962): Parent for modifier not found: FBMStrandsThicker. 2022-06-02 23:00:22.625 [WARNING] :: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1712): Modifier not prepared: FBMStrandsThicker! 2022-06-02 23:00:22.656 [INFO] :: Creating modifiers... 2022-06-02 23:00:22.952 [WARNING] :: ..\..\..\..\..\src\sdksource\fileinput\dzassetdaz.cpp(1729): Modifier not created: FBMStrandsThicker!I would venture to suggest that this is a DzMorph modifier and it's trying to apply a morph to an object that does not exist. It's probably hair. For example hair from the "Stylized Matt Figure and Hair for Genesis 3 Male(s)"
OK ... so how do I remedy that? Is there any way to go into the code of the file and remove just that?
I didn't have to experiment with .duf files. It seems to me that it would be better to reinstall the missing product. If not, then it is possible to rename or temporarily move the FBMStrandsThicker.dsf morph file from the folder where it is located (it is data\ folder in daz library) Perhaps the studio will ignore the erroneous operation if it does not find this file. But maybe it will crash again. By the way, if you can find the location of this file, you can determine the product to which it belongs.
Sorry. I have to leave the forum for a few hours.
And many thanks to Catherine3678ab for the hint on PostgreSQL. Actually, I got to this topic by request "postgre cms" in a forum search trying to get rid of the curse at the start of the Daz Studio, that is called...
"A valid PostgreSQL CMS connection could not be established. Several Daz Studio features that require a valid PostgreSQL CMS connection, such as context aware content views and loading content installed using the Daz Connect service, will not be available. Check your network, anti-virus, and firewall settings for conflicts."
You're welcome :-)
IMHO they could add that info to their warning.
They probably did not expect that there will be such fools who will believe that the "network, antivirus, and firewall settings" are to blame for this
and will patiently press the OK button every time the Daz Studio starts ;-)