Daz 4.9 has just gone RAM crazy, and the Help Desk is a 500 page
goose_chase
Posts: 84
Has anyone else ever encountered the latest model of Daz3D suddenly deciding it is going to flood the RAM to over-capacity during a render?
I haven't touched anything. I haven't changed anything. I'm hoping it's a computer fault. Yet no other programme is doing this at all.
Any workarounds?
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
Iray or 3Delight?
Mine does that all the time and so I've taken to keeping Task Manager open during DAZ renders and it tells me that despite having 8GB of memory and no other interactive user programs running that I of 8GB available I have less than 4GB free and DAZ seems to crash when I get just over 3GB in use. It gets upp to 2.7GB often without a problem. Probably that magic 3.2GB number although Windows 10 is 64bit and DAZ Studio 4.9.1.30 is 64 bit.
Iray. It's getting a bit better, and actually getting to the rendering now.
But these stats are obscene. It doesn't usually do this.
I haven't changed anything in the Render Settings.
Hmm. Here's what appears to be happening: despite the settings telling it to only use the Nvidia Card, Daz4.9 is shunting the entire scene into the RAM, and then squeezing it back out through the CPU to perform the Iray render.
The graphic card itself is in fact whirring into action as it ususally does. It takes off like a jet engine during rendering. So...? Hmm. It's... getting clogged up, somehow, and backing up into the RAM? Is that even feasible?
Is there a crazy setting in Daz that says "shunt everything into the RAM?" Is there a way to turn that off, if so? I've crashed to full reset during tiny, teeny renders today.
It may well be the Nvidia card, which I'll investigate further. That's not too likely, given I can read this text as I am typing (the card handles the monitor) but hopefully that's all it is.
Last post, sorry to keep bumping this.
It's not the Nvidia card. It's behaving normally, processing this scene that is well below the VRAM capacity, as you can see. Normally the RAM usage wouldn't pass 60% tops. The CPU usually spikes to 90% at the very start of an Iray render, and then goes back done to idle 0-1%. Now however, it appears.... to be trying to render in tandem? That's not right, is it?
Hmm. I'm going to... shut it down and do something else. Maybe it'll fix itself. That usually works with these sorts of thing.
It shouldn't crash; that is what swap memory is for, although it will certainly slow down once it has used or RAM.
Have you or someone else disabled swap memory?
You know... I bet it's... Yeah, It's probably that oh-so-chipper Win 10 Defender. It's possibly trying to scan the bits and pieces collecting on the SSD during render in realtime and murdering the machine.
I turned it off because it was doing similar to another programme, but now I discover it periodically turns itself back on, presumambly to send its creepy little report to the NSA.
Naturally, I had this genius lightbulb just as the massive nuke uninstall deleted everything for a clean start. Ah well, I was thinking of going all-Conect anyway, and had to do it sooner or later.
I'm fairly confident this was a Win 10 issue. I guess I'll find out tomorrow. Yeah, yeah, I derserved it because of Windows, I know, I know. Sorry to waste your time, thanks for the interest..
Hopefully it'll be alright now. Bad Cortana! Off! OFF!
It was Win 10 Defender. It was trying to scan all of the developing Iray data for viruses/user data to collect and sell on to spammers.
So essentially, if you're using Windows 10, switch off Windows Defender before rendering Daz3d in Iray.
Also be aware it turns itself back on from time to time, all by itself, to send all of your documents and website clicks to the Department Of Correct Thought And Action.
Going all-Connect is awesome, btw. Downloading your stuff as and when you want to use it rather than a giant wave, that's a neat approach.
I'm on Win7/64 and this happens to me from time to time as well, except that the GPU isn't doing the work, just the CPU. I'm thinking that at some point (canceled render?) VRAM isn't being released (or DAZ/Iray doesn't think it's been released?) causing the scene to be rendered on CPU. But I have 16GB ofr RAM and still get the flooding on scenes that easily fit in 4GB of VRAM. A reboot of my PC is what it takes to resolve it; then renders happen normally again.
The last few days Ive started getting GPU TDR ( Timeout Detection and Recovery.) errors and crashing my display driver during rendering daz in Iray. This error only happens when I'm rendering Iray in Daz 4.9. and not with any of my 3d games. or my 3d vision .. I have win 7 pro 24 gigs of system ram and 2 NVIDIA 980 cards. with a combined gpu of 8 gigs. running on a i7 3.333 cpu so according to NIVIDA Technical data log, TDR errors are caused by Daz using all my GPU.. and drawing off my system ram . now I've been working with NVIDIA developers guide ever since i installed my 2 graphic cards to get the most out them.. this is how NVIDIA describe the errors I am getting. http://http.developer.nvidia.com/NsightVisualStudio/2.2/Documentation/UserGuide/HTML/Content/Timeout_Detection_Recovery.htm they even give you trouble shooting techniques which was no help. and MS site was not much help either https://msdn.microsoft.com/en-us/library/windows/hardware/ff570087%28v=vs.85%29.aspx At first I thought it was because of a new Driiver update i got from NVIDIA last Friday.. so I tried rolling back the driver. but i still get this error. what is bugging me is this happens in daz 4.9 and not 4.8 it happens with just one character & using any type HDRi map.rendring at 1920 x 1080 . and the frustrating issue is its intermitting so I have not been able to trace down what using all my GPU and system ram. Daz log file is no help because once i get the TDR error message it clears my daz log file for some reason. and my windows log file stops recording because of the lack of ram at the moment of the crash, showing that all my system resources were being used.... which I feel is impossible with what I have for gpu and ram. so its become very frustrating rendering with daz 4.9 so I'v gone completely back to daz 4.8 anyone else getting TDR errors. and do you have a fix other than what NVIDIA suggest?
I'm wondering if this
https://technet.microsoft.com/en-us/library/security/ms16-034
may be contributing to the Nvidia driver/Iray problems.
Hi Mjc .. I read that document over I'm not sure But why do you think this KB 3143145 maybe the isue because if thats the case I have no problem uninstalling it
After checking my win update history I guess this would not apply to me MJ .. I check my windows update histories it was one of them Kb's I hide and was not installed.
it also pointed to this update as well of Kb 3136082 which I also did not install. https://technet.microsoft.com/library/security/MS16-018
as you can see by my install history so I guess that rules that out for me,.
Because the Nvidia drivers have kernel mode components...
And specifically....
That threw up warning flags for me...
But since I'm not running on Windows and am not affected I can't actually check any deeper.
I see well that may have been a possiable issue accept I don;t have those updates installed either ..so back to square one
Okay MJ I went into my control panal and then went to programs and features located this update (3139852) and unistalled it . reloaded daz and the scene I was working on and bingo no more TDR errors .
Good call MJC
Windows 7 for x64-based Systems Service Pack 1
(3139852)
Important
Elevation of Privilege
Important
Elevation of Privilege
Important
Elevation of Privilege
Important
Elevation of Privilege
3134214 in MS16-018
Check if you have "Purge Memory" script in your library under DS formats - Scripts - Utilities. It might help.
I do; I'll give that a try - thanks!