Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
When you say you tried different VM sizes, how did you set it? Try setting the min and max sizes to be the same so that Windows won't dynamically manage the size. On my 32 GB system I've set it to 48 GB - and yes, you'll loose 48 GB of space on your SSD to the pagefile.
What I've found is that DS continues to allocate more memory as your session goes on, especially if you're changing things like materials or lighting. This allocation shows up in the "commited" memory, not the "in use" or "working set" memory that you see in Task Manager. Open the Resource Manager from within Task Manager to see this.
When the commited memory reaches the physical RAM amount Windows is supposed to dynamically allocate more pagefile space. It is at this point that I've seen DS drop to CPU. I have not experienced the drop to CPU since creating a fixed sized pagefile of 1.5x my physical RAM.
Of course, this doesn't explain why your 1070ti machine works fine. Still, I'd give this idea a try.
This one; no clue what happend to it.
(I can even use CUDA to render using CPU only, just by selecting it.)
Okay, so, I had it at minimum 48000 and max 62000.
I changed it now to 48000 and 48000
For now I'm rendering 50 mintues, no fails yet after the page file change and restart of PC.
Damn... I really hope this works!!!
Nope. After 1h40m it failed. And it kept failing same as before on next renders :/