Daz crashes very often - memory issue?
bleybourne_772d5802c5
Posts: 67
Hi,
Daz often crashes on any remotely complicated render.
I get an error like this:
DAZStudio.exe caused IN_PAGE_ERROR in module "C:\Program Files\DAZ 3D\DAZStudio4\dz3delight.dll" at 0033:000000000913A848, Dz3DelightDll::DSlo_DetailtoStr()+2522056 byte(s)
Does anyone know what this kind of error means? Does in_Page_error mean the issue is when it's trying to page RAM? I have 16gb of RAM and system managed page file (which I just checked, and the system appears to have allocated about 3gb, I would have expected more. Should I override it and make the page file (a lot) larger? Usually you hear about physical RAM plus 50%, so I would have expected my page file to be 24gb or so? Could this be the problem?)
Often, to get a render I have to break my image up into "slicces" and render each part separately and then layer them together in photoshop, butr I'm sure there must be some trick to it.
Can anyone help?
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
You are using the 64-bit version of DS?
IN_PAGE_ERROR can be caused by hardware problems...RAM and hard drive errors being high in the possibilities.
Hi,
Yes, I am using the 64 bit version of DS.
RAM or HDD errors? Hmm, that would suck. I guess I can download memtest86 and see what that thinks of my RAM, and do a disk check for the hDD. I'll try those, thank you.
I was having a lot of errors...and it was my RAM. One stick won't run at full speed so I had to lock it at a lower speed in the BIOS. With it locked the errors disappeared, but left to auto, it would error out very often.
Do you mind if I ask how you worked that out? Is that something memtest86 can tell you, or did you work it out another way?
Are you using an older version of an Intel HD Graphics GPU? They use shared system RAM and a complex scene may make you run out of video RAM. I actually get video driver crashes from my Intel HD Graphics 3000 when browsing and at unexpected times. The key is I start running out of RAM. The most likely culprit in Windows 10 will be Microsoft Edge.
It was pretty easy to see, when Memtest said I only had half the RAM I was supposed to...the test was running at full speed. When I set the speed to a lower one in the BIOS, Memtest showed the full amount. But if I set it to auto in BIOS, the BIOS would run it at the speed both sticks would work, but Memtest wanted to bump it up to full speed for testing...
No, I have an nvidia 970 in there. But I'm rendering with 3delight, so I don;t think it uses my video card anyway...?
Bugger. I ran it for several hours, and it did report the full amount of RAM (16gb) and no errors.I was kind of hoping it was going to be that easy :-/
Well if you were using an Inel HD Graphics video card it would be using system RAM but as you said you are using a nVidia card and 3DDelight which wouldn't use nVidea RAM or Intel HD Graphics shared system RAM anyway. And I'm not an expert on 3DDelight but you seem to say it's a SW only rendering solution with no assist from the video card so it would be using a system RAM cache, potentially a very large one. I do know know that with Blender or Unity the most probable chance for a HW failure is to render or lightmap because of the CPU/CPU cyces and heat that get generated.
The system page-file memory needs to be more. When something asks for ~3GB, and there is less available, it allocates more... if something asks for >3GB, it crashes, because there isn't 3GB available. (At the least, you should have 2x your RAM. Windows will use it all, if it is available to use.)
EG, A scene has 1GB needed, beyond your RAM... it could allocate that, because it has reserved up to 3GB, even if 48GB is in use now. If you ask for 4GB beyond RAM, it crashes, because it has only reserved an additional 3GB, and DAZ is not handling the callback that says, "insufficient memory", and instead, is just relaying the error message, then crashing.
I have mine set to 128GB minimum, because my scenes often hit close to that size, beyond my 16GB of ram. (Part of this is due to using the HD settings and using the full sub-division for models, clothes and hair. Not to mention that I render in large formats of 6000x6000 often.)
To get an idea of how much a scene requires, you can go to the task-manager and render-out individual components. Then just add. Where possible, I try to do layer rendering. Background, Distant, Far, Near and close-up or HD. Stacking layers in photoshop, after rendering, or directly in DAZ with the built-in layer image-editor tool.
Do you have only two sticks of RAM? Are they setup in the "Even" slots? Some mobo's demand that, for parity. (If you have every other slot colored with two colors, you need to do that. If not, and speeds do not match, or memory is not the same exact specs... then it is common to put one on one chanel and one on the other. "Even/Odd" using the first two slots closer to the CPU. Best to have both the same speed anyways. Has to do with timing and the fact that the CPU now handles the memory, not an external memory-contoller. Thus, the speed is actually in sync with the CPU speed.)
https://www.microsoftpressstore.com/articles/article.aspx?p=2224043
"Bank 0 includes slots 1 and 3 and these two slots are normally blue. Bank 1 includes slots 2 and 4 and these slots are normally black."
"On most motherboards, the slots are color-coded to identify the banks. Slots of the same color indicate the same bank, and matched pairs should be installed in these slots." (Eg, can't often run safely with unmatched chips or specs or speeds. Both have to be exactly the same, in every aspect. Otherwise you have to reduce both to the values of the lowest speed that both can "pair-up" to, in sync.)
Honestly Guys,
shouldn't a proper application catch those exceptions, show up a qualified message and return to the status before the render (workspace of DAZ)?
That's what I expect of a professionaly programmed application. And this is what each programmer learns at his professional education.
Sorry, AndyS, but a lot of those kinds of errors are WAY below the application level. Those are in motherboard firmware at best. The application has no idea what is going on down there. It takes special code to interface with the BIOS and query things like that, and that code is NOT uniform across all motherboards. Different DIMMs also support different mechanisms, though there are some hardware protocol standards they all support for the BIOS to interface with.