Freezing Issues during render with the 4.12
jcalebdesign
Posts: 31
4.12 seems to "lock up" on me during the render process. By that I mean, it locks up up my entire PC and I have to do a hard reset. If I turn on another app, say let an Audible book play during it, I can usually get to a point where I can save it. Its really weird and I've never had to do that. I was thinking of uninstalling and reinstalling it to see if that clears up the issue. Would I do that through the DIM? I don't want to lose my content, just want to reinstall the program. Or if anyone has any other suggestions that'd be great.
Jake
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
I have this exact problem and literally came in to make the same comment. I have a BEAST of a system too. In my case, everything is frozen, including the cursor however.
Yes! Same here, its not the specs on my machine that's causing the issue. I do think it may be a driver issue, I'm looking into that now but I got nothing man.
In Windows open up the Task Manager, find the Daz Studio .exe program, right click on it and set it to Set Priority to Bellow Normal and/or Set Affinity to all but one or two cores and see if that helps. You have to do this every time you close and start Daz Studio though. Also check your paging file and make sure it is at least twice the size, or even more, of the RAM on the machine.
I tried both of those and still it freezes the entire PC about few minutes into the render. I've tried on both 4.12 and the Beta, same thing. It happens on multiple scenes. I've attached the last chunk of the log, if that may help.
Jake
2019-10-31 13:43:58.493 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : Light hierarchy initialization took 0.081s
2019-10-31 13:43:58.493 Iray [VERBOSE] - IRAY:RENDER :: 1.14 IRAY rend stat : Lights memory consumption: 1.709 MiB (device 0)
2019-10-31 13:43:58.509 Iray [VERBOSE] - IRAY:RENDER :: 1.14 IRAY rend stat : Material measurement memory consumption: 0.000 B (GPU)
2019-10-31 13:43:58.634 Iray [VERBOSE] - IRAY:RENDER :: 1.14 IRAY rend stat : Materials memory consumption: 611.164 KiB (GPU)
2019-10-31 13:43:58.634 Iray [VERBOSE] - IRAY:RENDER :: 1.14 IRAY rend stat : PTX code (198.975 KiB) for SM 7.5 generated in 0.135s
2019-10-31 13:43:58.728 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : JIT-linking wavefront kernel in 0.035s
2019-10-31 13:43:58.728 Iray [INFO] - IRAY:RENDER :: 1.14 IRAY rend info : JIT-linking mega kernel in 0.002s
2019-10-31 13:43:58.728 Iray [INFO] - IRAY:RENDER :: 1.16 IRAY rend info : CUDA device 0 (GeForce RTX 2080): Scene processed in 8.311s
2019-10-31 13:43:58.743 Iray [INFO] - IRAY:RENDER :: 1.16 IRAY rend info : CUDA device 0 (GeForce RTX 2080): Allocated 494.385 MiB for frame buffer
2019-10-31 13:43:58.743 Iray [INFO] - IRAY:RENDER :: 1.16 IRAY rend info : CUDA device 0 (GeForce RTX 2080): Allocated 1.097 GiB of work space (1331k active samples in 0.000s)
2019-10-31 13:43:58.743 Iray [INFO] - IRAY:RENDER :: 1.16 IRAY rend info : CUDA device 0 (GeForce RTX 2080): Used for display, optimizing for interactive usage (performance could be sacrificed)
2019-10-31 13:44:02.539 Iray [INFO] - IRAY:RENDER :: 1.16 IRAY rend info : Allocating 1-layer frame buffer
2019-10-31 13:44:03.070 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00001 iterations after 12.649s.
2019-10-31 13:44:06.773 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00002 iterations after 16.347s.
2019-10-31 13:44:12.115 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00003 iterations after 21.701s.
2019-10-31 13:44:13.912 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
2019-10-31 13:44:14.552 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00004 iterations after 24.128s.
2019-10-31 13:44:19.082 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00005 iterations after 28.666s.
2019-10-31 13:44:22.331 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00006 iterations after 31.916s.
2019-10-31 13:44:26.487 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00007 iterations after 36.070s.
2019-10-31 13:44:30.127 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00008 iterations after 39.712s.
2019-10-31 13:44:34.126 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00009 iterations after 43.703s.
2019-10-31 13:44:37.937 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00010 iterations after 47.513s.
2019-10-31 13:44:41.936 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00011 iterations after 51.513s.
2019-10-31 13:44:45.732 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00012 iterations after 55.306s.
2019-10-31 13:44:53.293 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00013 iterations after 62.871s.
2019-10-31 13:44:53.527 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00014 iterations after 63.111s.
2019-10-31 13:44:57.401 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00015 iterations after 66.973s.
2019-10-31 13:45:01.400 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00016 iterations after 70.977s.
2019-10-31 13:45:05.196 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00017 iterations after 74.769s.
2019-10-31 13:45:10.336 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00018 iterations after 79.913s.
2019-10-31 13:45:17.350 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00020 iterations after 86.932s.
2019-10-31 13:45:28.175 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00022 iterations after 97.756s.
2019-10-31 13:45:32.175 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00024 iterations after 101.756s.
2019-10-31 13:45:39.938 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00026 iterations after 109.512s.
2019-10-31 13:45:45.390 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
2019-10-31 13:45:58.887 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00028 iterations after 128.465s.
2019-10-31 13:46:00.277 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00031 iterations after 129.855s.
2019-10-31 13:46:17.726 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00034 iterations after 147.304s.
2019-10-31 13:46:21.975 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00037 iterations after 151.554s.
2019-10-31 13:46:34.207 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00040 iterations after 163.787s.
2019-10-31 13:46:49.188 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00044 iterations after 178.770s.
2019-10-31 13:47:12.307 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00048 iterations after 201.882s.
2019-10-31 13:47:23.445 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00053 iterations after 213.020s.
2019-10-31 13:47:36.567 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
2019-10-31 13:47:45.331 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00058 iterations after 234.915s.
2019-10-31 13:48:06.467 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00064 iterations after 256.045s.
2019-10-31 13:48:28.352 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00070 iterations after 277.925s.
2019-10-31 13:48:58.876 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00077 iterations after 308.452s.
2019-10-31 13:49:22.308 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00084 iterations after 331.886s.
2019-10-31 13:49:49.646 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): peer performed orderly shutdown errno=0
2019-10-31 13:49:53.129 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00092 iterations after 362.716s.
2019-10-31 13:50:29.136 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00101 iterations after 398.720s.
2019-10-31 13:51:06.393 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Received update to 00111 iterations after 435.976s.
I have the similar problem, that my computer freezes.
Although it doesn't happen during render, but afterwards when I click on a render.
Initially I thought it might be a driver problem and updated the driver, but the problem remains.
And it happens with both 4.12 and 4.12 beta.
Quick question... Are you rendering something which Daz is pulling from the "Cloud"? I have never seen that error in my logs. (I don't use the cloud)
Could it just be an internet issue, as Daz is waiting for ??? from the cloud-storage transfer. (I know it says "peer performed orderly shutdown", but obviously you are not killing or shutting down the rendering, mid-way through a render. Seems more like Daz failing, and an inappropriately labeled log-error, when it should say, "program performed orderly shutdown". The lack of an actual error number "0", indicates it is just an unhandled error, internally, which shouldn't be labeled as a "peer" action. {Though, I am sure it is "Peer", as opposed to "Server", which is somewhat appropriate, although misleading.)
I get occasional DPC_Watchdog violations and my system will blue screen. Sometimes it runs fine fior days, and sometimes I can't render a dmaned thing. Never happened with 4.11.
Daz Studio does not pull content from the cloud (unless the end user has set their content directory to be on a remote server).
The "peer" in
is in reference to how DAZ Studio communicates with the DAZ CMS (via a localized TCP port connection between DS peer -> CMS PostgreSQL server.) This log file line reappearing over and over again during a short span of time is an indication that there is constant traffic going on between your running instance of Daz Studio and the CMS. Which very well could be the source of your problems (constant background activity over a system communication bus sounds very much like the slowdowns you are experiencing.)
As to a fix, I'd say first try reinstalling Daz Studio AND Install Manager and seeing if things improve. The CMS installs/uninstalls as part of Install Manager.
Have the same problem here. I had a scene that worked fine with 4.11, but after updating to 4.12 (also updating my graphics driver), rendering the scene would freeze my entire computer in about 20 seconds after clicking "render". I have no other programs open. The only thing that seem to work from time to time is when I change the render dimension to something around 1920x1080, anything bigger my computer would freeze.
If you have a good GPU card, something to try is in Rendering settings, go to Advanced tab and under Photoreal Devices to uncheck the CPU option.
Could also uncheck the CPU option under Interactive Devices. It might work to help resolve the issue depending on the computer and hardware.
However, there's another option that I found works good for me, and I can leave both CPU and GPU options checked, is to use a nifty free utility that can limit the CPU load of a selected running program; BES – Battle Encoder Shirasé http://mion.faireal.net/BES/
Run it with Administrator level privilagess, from the Process list, find DAZStudio, click on "Limit This" and confirm. Then there's a slider that can be controlled. So, for example, I may typically set the slider at -30% , so the CPU load for DAZ Studio will be limited to using 70% (of course one can experiment with what percentage seems to work good, giving a balance of having DAZ doing a render while not hogging the CPU to the point that it basically makes the computer unusable for anything else).
When finished using DAZ, simply close the BES CPU Limiter program as well.
I am also having the same issue now. I installed 4.12 about a month ago and had no problems until 2 days ago. Now I cannot render. I didn't see a solution in the thread above.
Exactly same problem here. Why there is not any solution yet? I mean, c'mon DAZ!
I was having the same problem a few weeks ago. Then it stopped. NOW it started freezing during the render. I thought it was just the laptop getting too hot. But no I have a cooling table underneath it with fans going but that's not it.
Yeah I tried both ways too and it still froze up on me.
Neither of those worked.
I just let my computer sit there froze. Then I went to go do a 30 minute workout in the garage. I come back and it's already started on 20 Iray Iterations. one hour later it's at 1000.
You need to find out what is really going on to solve this problem. Daz taking over the whole system could be just CPU rendering so you have to make absolutely sure that the GPU is being used and not the CPU.
That involves verifying that the CPU is not selected in the advanced render settings and checking that the GPU CUDA is in use by opening Task Manager -> Performance -> your gpu -> select a graph -> click the title of the graph-> select CUDA. Then Options -> Always on Top. Now start a render.
If all that is correct then Daz, or iRay is crashing or having a resource conflict with something else in the system.
First make 100% sure that you have the most recent driver from Nvidia installed.
Then if things are still FUBAR uninstall DS, shut down and restart, reinstall DS. Try a render.
If it is still happening then you need to start figuring out where the conflict is. AV software is teh most common culprit.
I have the exect same issue now. No idea what has changed but rendering worked fine and since a couple of days my PC freezes while rendering. Sometimes it seems like it somewhat recovers after an hour or so but more often I have to hard reset. I have CPU fall-back disabled, Graphics-card is an RTX2070 with 8GB.
In the cases DAZ recovers, CPU is not that busy and RAM is used as expected but rendering is awfully slow.
Grab a copy of GPU-Z.The next time this happens - while the freezing/generally really slow computer situation is still ongoing, open GPU-Z and switch it to the Sensors tab for your 2070 (2070 is selected from the bottom dropdown list.) Take a look at the Bus Interface Load graph and see if it is trending above or below around 3%. If it is going above that, the source of your problem is probably having other apps open that also use video memory (eg. Chrome) while rendering. Meaning that the solution would be to not run other vram intensive tasks on your machine at the same time as rendering.
Thx for the quick response. Updated the nvidia drivers in the meantime. No freezes since than but a quit small sample size. Therefore I have a different problem showing up about ever second or third render. It starts to render propperly but after the "Iray (Statistics) : Geometry memory consumption:" it stops by stating "Render finished" and the render window is stil empty (of course it is). Still investigating.
I have the same problem, any solution guys?
Unfortunately it didn't work for me. It keep freezing for 10 or 20 minutes, even if I set the slider at -50% :(
What did you do in order to it worked for you?
What did you do in order to it worked for you?
Having the same problem since a few days, after the last update I think... feeling kind of desperate, I cannot work anymore.
On my machine there is a distinct lag prior to rendering an animation frame that was not there before and the window showing the rendering progression will say "not responding" on occassion.
How come there is NO" Daz Studio Tech's Here to answer any questions or help solove this problem?
I don't know if any one over looked this in Daz under advanced to rendering where it list you CPU and GPU scroll down check change the CPU Load Limit thread core settings to lower then whats listed, thats taking less stress off your CPU load for Multi core processing. (set mine to 8 Logical processors from 16 Logical processors) Due to I have a 8 core ThreadRipper..
that could help I am trying it now my self.
I am also using this too Battle Encoder Shirasé, at 25%...
I am trying to render Moshi Toon Fury Kitty in a Sit down pose No shadow on ground.
almost done at 99% and No freeze yet or lock out ofr Entire system.
and my Entire sytem froze during this same process for Moshi Toon Kitty same pose and everything, just changed the resoulation size to 1080P.
Well it finished the render without freezing up for 8 Logical processors and Resolution Winodw size of 1080P x 1080P and using Battle Encoder Shirasé at 25%.
I am going to try a new render using the same Character but set the resolution window size to 2560x2560P and keep CPU Load Limit to 8 Threads and use Battle Encoder Shirasé for 25% again and see what happends.