Constant save crashes stifle all work
stephan.verleysdonk
Posts: 8
Minimum 50% of the time DAZ 4.23 crashes during a save attempt with DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll" at 0033:000000005A8FEA30, inflateMark()+4768 byte(s). OK, the software is free, but still.
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
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
What are your system specifications? What security software are you runing? What nVidia driver vesion (if you have an nVida GPU)?
MS Windows 11 Pro, Version 10.0.26100 Build 26100
64 GB of RAM
NVIDIA GeForce RTX 4090 Driver version 32.0.15.6094
I'm only running Window's build-in security software, no 3rd party solutions.
I have to say that the crashes are related to me working on a very high poly model composed from very many 3D objects. However, that same model handles flawlessly in Blender. Granted, there are some issues with non-manifold geometry which is too tedious to fix, but it's no problem in Blender.
I'm not sure how to read that driver version number - but the minimum required is 537.13, if yours is much newer than that it may be the root of your problems - try rolling back to something closer to the minimum required version, which was known to be good.
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\dzcore.dll" at 0033:00000000A1A4929B, DzOrientedBox3::includeLocal()+155 byte(s)
Try increasing windows vertual memory firstly ... as well as check if you ever enabled XMP in BIOS, If you did, disable it and try again to see if the crash persists ~~
My understanding about Nvidia driver numbers (based on a recent installation) is that the long-form and short-form version numbers share the same last five digits in the same sequence, but the dot is in a different place.
For example: version 32.0.15.6094 (long form) corresponds to version 560.94 (short form).
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_0afec3f2050014a0\nvoglv64.dll" at 0033:0000000088AFFB67, DrvPresentBuffers()+1893783 byte(s)
This program is completely unsuitable for anything except dabbling.
C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_0afec3f2050014a0\nvoglv64.dll is the openGL part of the nVidia driver, so quite possibly a driver bug rather thana DS bug (especially as we don't see a lot of reports of similar errors).
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll" at 0033:000000006458EA30, inflateMark()+4768 byte(s)
A save crash after installing the latest nVidia studio driver.
Saving also uses OpenGL, for the thumbnail, unless you have turned tumbnail generation off. Quite a few people have found that the latest nVidia driver is not the best, though I think the most obvious issues have related to Iray.
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll" at 0033:000000006458EA30, inflateMark()+4768 byte(s)
The % into the save when the crash occurs is between a few like 2% to 74%. Until now, I never had a crash when it passed the 74% mark. Should that rule out a problem with thumbnail generation?
It certainly doesn't sound like an OpenGL issue, I would suspect it is connected to compressing the file or its thumbnail - if it was the thumbnail it might be triggered by an issue with the OpenGL rendering, though I wouldn't want to bet on that. I don't know why your system would be having these issues - they do not seem general or even common.