Are GTX 1080's having problems with 4.10
MegaP
Posts: 180
Hello,
I'm having problems rendering an animation.
It doesn't seem to get past the first render.
I'm still running 4.10 so it's not the new beta version.
The last few posts seem to be possibly having similar issues.
I'm sure I have enough memory,it keeps crashing or frozen on one frame.
Doesn't appear to be running hotter than normal either..temp looks ok
Ive updated Nividia drive and no change and no new Windows update I'm aware of.
Is this a bug and how do I fix it short of wiping it clean which I'm sacred of.
Thanks
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
Hi SickleYield,
Funny,I thought in the begining it may have been my render settings so i went to one of your tutorials and cut down samples etc.
I'll try and download an earlier version and fingers crossed hope it solves the problem
Make sure you do a full uninstall of your drivers with something like Nvidia Driver Cleaner!
Ahhh ok,I didn't do that and it looks like I still have the problem
Is it crashing on other scenes as well or just this particular one? Also, does the log file have anything useful after the crash to indicate where it's having problems? I have a 1080 as well running the latest Nvidia drivers and haven't any any rendering issues.
Hi JonnyRay.
Yes still having problems.
Seems to be crashing with any scene I load and as someone stated on another thread just posted it started a few days ago.
Attached I've included my log details and Daz report if that makes any difference.
Sorry,they're iPad screen shots as I'm giving the poor computer a break
That section of the log doesn't look likely to be relevant.
Incidentally, if you bring up the Windows menu and type Snipping you can access the Snipping Tool - click New, drag out a rectangle around the area you want, then click the disc icon to save; it will be much cleaner than a photo of the screen.
Hi, I have GTX 1070 and had this problem not long ago when I only had the one video card and found the fix, one thing I found out by a lot of searching on the web was that there is a conflict with the NVIDIA Telemetry Container conflicting with Iray renders in some machines, normally shows itself by way of Dcom errors in the windows system logs. Yes it sounds strange but the skinny of it is that somehow when this service is running while rendering it can crash. Although it is a service meant to support the Nvidia Experience, ie Control Panel the Experience panel which pushes updates.
I was crashing a hell of a lot and it started after a few updates ago from Nvidia. I followed the information on Nvidia's forums and disabled it, and have not had a crash since. Now, the thing to keep in mind is that once you disable this service you can no longer access the Nvidia Experience control panel unless you first turn it back on. DCom errors are when the active user account on the windows machine does not have the correct permissions to access a service etc and its a communication protocol. In the case of Nvidia the telemetry service uses this protocol to communicate with the Nvidia servers bla bla, boring tech stuff and then crash ;s Basically somewhere between Nvidia updates and windows updates there are driver conflicts or permission errors and its caused a mess with the telemetry service for some Nvidia users, especially when using Iray.
If you check your windows system information and look at the error logs you are most likely getting DCom errors which is hand in hand with the symptoms of the Telemetry service I have described, there is also information on the Microsoft Site which is what led me to the Nvidia site for the solution.
To correct this:
Press windows key and R to get the run command, enter: services.msc and press run or hit enter. Scroll down to Nvidia Telemetry Container and right click and select properties change it to disabled, then right click again and stop the service.
It will no longer start on its own, and just bear in mind that you will want to check from time to time the Nvidia site to see if you need drivers. Also, once you disable it you will stop the crashing, but this also would affect getting automatic updates from Nvidia or Notices for update via the user experience panel from Nvidia. The only other thing with this is if you start to notice that Iray is not working right it normally means there is a driver update, just do the reverse and enable it long enough to get the update installed and then disable it again.
Hope that helps, I did this 2 months ago and have not had an issue with crashing since.
This should be clearer Richard
Hi CgHipster,
Want to thank you for your detailed explanation.
I went through the procedure as described and have had no luck (It did however expand my knowledge computer wise,so thank you)
I actually followed this twice with re starting,disabling and a whole lot of rolling back etc
So glad you found a solution as its driving me crazy.
I'm now desperatly animating rendering one image at a time and slighty changing the frame position each time.
This is not going to be fun,wish I could get to the bottom of this asap
This is happening to a lot of people and it's not just on the 1080. In my case, disabling OptiX Acceleration solved the problem.
Happy to hear thats worked out in your situation.
It was one of the methods I tried to no avail,it also appears to brings Daz to it's knees if it infact does render anything
Roll back to the Nvidia 387.92 drivers, doing a Clean Install each time (option in GeForce Experience installer when you select Custom Install).
There's also Display Driver Uninstaller from TechPowerup.com that cleans everything out.
If it works fine there, start stepping the driver revisions up until it goes back to crashing. Then you'll know which drivers you can run safely.
It's a ton of work, and takes the fun out of life, but if it means a stable system and you're at least getting drivers that your card can benefit from, it's worth it. The 387.92 drivers work for older cards like the TitanZ, which doesn't get along with anything beyond that IME.
That sucks, this may be a stretch but... have you considered trying a new partition, loading in bare minimum drivers to run second windows install on your machine with just windows, video card and stock drivers, install daz and link it to your content library, don't update windows, then test a render session. Then incrementally you can start adding drivers until you find which is the conflict.
I would suggest downloading a free backup utility called Macrium before updating any drivers though so you can restore your new partition to first installation when you find the problem (ie install update that breaks daz) You could do this so you can test the nvidia drivers that work and rule out any bloat plugins or conflicts that you may have with anything already installed on your machine, including windows update.
This would eliminate any other drivers or software that could be installed from interfering with your testing. Only load essential hardware drivers and go for drivers that are from a period when you were not having this issue and then keep an image on standby in case a windows or nvidia update breaks your install.
Now, if this test doesn't turn up anything the other culprit could be hardware and I would first suspect power supply, these things don't always last but a failing power supply would take a serious draw from the GPU and could cause the GPU to fail and then crash daz if it is not getting enough power etc., bla bla more tech mumbo jumbo then crash.