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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Okay that is weird. Size of render should not be an issue and with that I don't think this is related to the iray render server connection. Hmmm. I will have to cogitate upon this riddle.
Did you unistall DS Beat and put back DS public? Did do all the uninstall and reinstall others recommended for Nvidia drivers, which I can confirm I have done in the past?
Hi,
No I'm sticking with the beta as it performs better than the previous version.
I did the full uninstall of the NVIDIA drivers in Safe Mode (what a pain to do that in Windows 11, found an easy solution on REDDIT to invoke MSCONFIG, pin that to the task bar, Select the boot into safe mode and then when your done reverse that and boot back into regular Windows. I then installed the Studio NVIDIA drivers. I'm just back from all that so haven't had an opportunity to try a render yet.
Not sure why you think that the system wouldn't balk at the extra pixels being drawn (1000X1000 VS 1600X1600) but maybe you know more than I do about such things, I was able to render fine with the lower pixel output but when I went up to the recommended promo size I would get DS crashes and even BSOD. To me there is a correlation! Perhaps I'm wrong but seems that way to me.
OK. After all that hassle to get a really clean install of NVIDIA drivers tried to render and got a BSOD pretty quickly. NO OTHER PROGRAM causes this for me. NONE! So something is up with DAZ Studio!
I agree this does seem to be a DS problem, but still it was a good idea to scrub the Nvidia drivers to eliminate that possibility.
"Not sure why you think that the system wouldn't balk at the extra pixels being drawn (1000X1000 VS 1600X1600) but maybe you know more than I do about such things, I was able to render fine with the lower pixel output but when I went up to the recommended promo size I would get DS crashes and even BSOD. To me there is a correlation! Perhaps I'm wrong but seems that way to me. "
I agree there seems to be a relationship, but there should not be. As an example, I am rendering Old Jeb in a tuxedo in Urban Future 7 on my RTX 4060Ti 16GB with i7 4790K and 32GB RAM. The unoptimized scene is rendering at 5000 x 5000 and uses 10167 MB VRAM. It has been runinng for over 9 hours and DS has not crashed.
I am not certain what is causing the problem on your system. Hopefully, the DAZ Tech Minions will come up with a solution.
I remember years back there was an issue similar to this and I think Richard Haseltine hinted about some hidden folders that I might try moving and letting DS recreate or something like that and iirc that worked. I don't think it's the folder under the AppData/Roaming area but another area. Can't remember off hand.
Well I stopped the render at 1% after 12 hours and again no crash, so in this case SIZE doesn't matter ... per se.
However, you will notice when I started the render at 2000x2000 the VRAM used dropped to 7214 MB from 10167MB. Of course, greater resolution of the render increases VRAM used, but still I don't think size in itself is the issue, you still have lots of head room with 16GB VRAM. I should also mention that computer is accessed through Splashtop remote desktop, which is additonal overhead on the video card and another point for DS render failure.
BTW: GPU-Z is a good way to monitor your video card while your system renders. https://www.techpowerup.com/download/techpowerup-gpu-z/?J4jiq5=2LYeh56T7i
If you do find out the problem, please share with the group. :-)
Yes, I have GPUZ. I didn't know about the log option while rendering. I've pinned it to my taskbar and will bring that up and enable it when I try to render next. I've also just moved my directory to a different hard drive to see if that will help. You never know when things are going sideways like this what all in play to cause the issues and errors. So from E to D drive, it's my Beta library so not huge and took just about 10 minutes.
i only update once a while and it doesn't seem to affect the performance much.
I compared both video cards idle VRAM usage. Both cards are 16GB and on Win 10 64 idle VRAM is less than 500 MB, BUT on Win 11 64 it is over 1000 MB. I knew about this before, but it is a cold reminder and has nothing to do with DS. It is a Windows helpful "feature".
I think 256GB VRAM cards would be nice.
I stopped the render after 7 hours on the 2000x2000. It reach 98% complete at 93% convergence within 40 minutes and just sat there for the balance of the time. It did not crash but it did not finish. Not sure what that is about. Any ideas?
So did moving the library make any difference? Also if you don't use DAZ Connect, you may want to make sure the path is correct in the content library and the folder is empty.
I found updates make a difference when the card is a newer model. When installed my 40xx series cards I was running an older version of DS. I updated to the latest version and saw content load times improve and and some improvement in render speed. In my personal opinion, I think DAZ has taken DS 4 as far as they can and now it is more about compatibility and stability. My personal impression is the underlying software based is too old to really take advantage of newer Windows O/S and Nvidia cards.
Not checked it out as of yet if changing hard drives worked in preventing a crash. I really don't think it would but again you never know. I had a busy day today and not sure I'll get to testing things until tomorrow. I did hear back from Devon from the DAZ3D tech team and he gave me some instructions on how to better zero in on what's going on but I did tell him the same thing; I'll get to it tomorrow. Pretty tired now.
Good luck. Let us know how it goes.
Will do, I linked the report to this thread in case they can get any additional info from here!
Does the issue persist if you turn off CPU rendering?
Not sure how to turn that off to test it. Also not sure if my GPU will have enough memory to render a scene that size.
please see attached for CPU GPU hardware choices.
If I remember correctly you have 16GB VRAM. If you are rendeing the scene you showed here earlier then it should fit in your VRAM. This is where GPU-Z is your friend. You can know how much VRAM is used by your computer and your DAZ scene by waiting for the DS render to start showing percentage rendered. When it starts showing percentages then it has loaded everything and now it is doing render iterations.
I think your scene only uses 2 GB of VRAM plus 1 to 2 GB of VRAM for Win 11, therefore max total 4 GB VRAM.
FROM YOUR LOG:
2025-03-07 07:29:23.910 Iray [INFO] - IRAY:RENDER :: 1.12 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 4060 Ti): Allocated 22.888 MiB for frame buffer
2025-03-07 07:29:23.911 Iray [INFO] - IRAY:RENDER :: 1.12 IRAY rend info : CUDA device 0 (NVIDIA GeForce RTX 4060 Ti): Allocated 2.094 GiB of work space (2048k active samples in 0.000s)
Cool, thanks for being so so helpful!
BTW, an app I use for reviewing the DS log file is Notepad++ ( https://notepad-plus-plus.org/downloads/ ). It is an amazing text file editor.
I have that but always go back to EditPad Pro!
Well, I'll be. Turning off the CPU access to the engine seems to have fixed this. It took a little over 9 minutes to render the 1600X1600 but no crash or BSOD!
In that case a few thoughts.
Could be CPU temperature related as rendering on the CPU is quite a heavy workload.
Could be that your PSU doesn't like running the CPU and GPU flat out at the same time.
If you have a 13th or 14th gen Intel chip there have been issues with stability and degradation on some of the chips which can manifest in odd ways, even GPU driver problems.
Intel have a processor diagnostic tool which may highlight issues but it doesn't always.
There have been motherboard bios updates rolled out with less aggressive Intel default settings that may be more stable at the cost of a little performance.
Turning off any auto overclocking features in the bios and brand specific tweaks like multi core enhancement may help. Failing that Intel have extended the warranty period for the chips.
Thanks. The computer is over 2 years old so I'm pretty sure I don't have coverage for that and if it were a repair issue I don't have the ways and means to pack it up and send it back to CyberPower PC to have that looked at. I'm just relieved that turning off the CPU useage seems to have cleared up the issue for now. I just want to get the promo's done and then I'll get more serious about looking into that possible issue when I have the time and energy. As stated above I don't have an issue with any other workhorse program like Photoshop, ZBrush or Poser.
oddbob's recommendations are good.
1. Make sure you have turned off all overclocking in the computer BIOS and video card. You prefer stability over performance because overclocking is really aimed at gaming which is intermitant power boosts and even a short render can be 30 minutes long. Unless you have 4 RTX A6000 with water cooling, which every home should have.
2. What is the power supply of that computer? My computer is custom so software will not tell me. I have to open the case. You can try these methods: https://robots.net/tech/how-to-tell-psu-without-opening-the-case/
My PC with the RTX 4060Ti is using a Corsair CS750M (750 watts). But I never want to default to CPU because it would increase render times to a ridiculous amount. Better to have the render fail and then optimize the scene.
I also have lots of fans on my computers (at low speed) to ensure no heat dwells in the computer case.
You're welcome. Sounds like you have a solid plan. If you do have one of the affected CPUs then the warranty with the extension should be five years.
I would guess the two drivers are exactly the same, except the game ready drivers come with a custom profile setting for the Daz Studio executable. Which should be found in the Nvidia control panel under Manage 3D Settings. Which basically says, "apply these settings to the Daz Studio executable when it runs". Turn this feature on, or turn this feature off, etc... I have this set to use my own global settings, so I doubt it makes any difference if I install either one.
But, if you think something driver-specific is your crashing app, then I would just go into "Manage 3D Settings", and start turning things off, one by one.
I never have overclocking turned on, I've always had unwanted effects from that making my system unstable. So that wasn't the issue. I have the same video card as you so you know how all that works. I've not done another render yet as I had to go out and do some exercising and more errands so home now. I will run another scene file and see how it does with the CPU options turned off.