Unable to open scene. HELP!
jobie187_81b9583f0a
Posts: 8
I recieve the following error message
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\DzCore.dll" at 0033:00000000E7CBC1CE, DzObject::modifierIterator()+30 byte(s)
when trying to open a particular scene. Worried cause I put quite a bit of work into that scene last night and want to keep the workflow going! Aaaaah!! Can anyone tell me how I can fix the problem? Im running dazstudio 4.8 on win 7 64
Thanks in advance
Comments
Ive tried merging the problematic scene with a new blank scene but still have the same error. I have other similar scenes (same actors props etc) and they load up fine, and havnt found any trouble with any other scenes so far. I've tried reinstalling daz 4.8 and made sure to delete the leftover program files first. Is there any other way around this tricky DzCore.dll problem?
Any LAMH items in the scene? somebody in a German forum was able to track down a very similar message to the LAMH preset for the MilDog ...
Unfortunately even Daz Support was not able to help her rescue the scene ...
Is it a file you are willing to put up for others to try opening? If you open the log file before causing a crash, then reload the log after the crash and scroll to the end is there any information on what DS was doing?
Thanks for the responses guys. No LAMH objects are active in the scene. Dont think I have the plugin installed at the moment anyway.
Oh, and here's the log!
Crashed with the same error code here using the latest DAZ Studio.
I feel your pain man. Not experienced this bug before. Hope it doesn't happen often cause it's worrying. No one likesbeing caught out like this
Well, it isn't file corruption due to compression - it unzips and looks clean, but still crashes.
If it's crashing for you Richard, I'm scared. You're the guy that gets things working! Any advice or ideas about what may cause the issue. If I have to start over I don't want to make the same error again. Thanks for giving it a go though.
I'm not an expert at reading crash logs, and since there isn't any obvious file corruption (as sometimes happens) I don't get a clue from that. Looking at the crash report I think it was working on modifiers, but I may be wrong or that may be misleading. I would suggest opening a support ticket and ataching the file with a note of the content used - a crash is a bug, whatever the underlying cause.