Joining the nvcuda64.dll Access Violation club

rames44

Running 4.15 on Windows 10.  Things have been solid as a rock for quite a while.  Suddenly, 3-4 weeks ago, I'm starting to get nvcuda64.dll access violations.  No hardware changes, no changes to Daz Studio.  (Of course, there WERE Microsoft updates.)

Figuring it MIGHT have been an NVidia bug, I've tried a couple of different versions of their drivers with no success.

The thing I notice is that I'm fine if I batch render a series of images.  It's animations that are causing the crash - when it moves from one frame to another and gets ready to render the next frame, that's always when it crashes.  I wondered if one of my GPU's was going flaky (I have dual 1080's) so I tried with just one enabled and just the other enabled - didn't change anything.  (Other than render slower.)

Don't know if anybody has chased down the source of this, or has any suggestions.  I did upload a couple of the crashes to support, but, of course, I don't ever expect to hear anything from them.

Catherine3678ab

I realize that it may take longer for tech support to reply over what it normally takes sales support to reply, but they normally do.

And they tend to appreciate a video showing how to replicate the problem. Log files too of course.

To get an appropriate length of a log file, I tend to open the log file and delete everything on it, save it. Then redo whatever it is that is failing, then copy that log file to a text file for tech support.

 

Spacious

Are you trying to render animation to a movie file?  Maybe try rendering to an image sequence instead, and then using other software to create the movie.  There's lots of software that can do this.  Blender is great for turning an image sequence into a movie, just a few clicks, plenty of easy tutorials for that subject, and it's free.

rames44

Catherine3678ab said:

I realize that it may take longer for tech support to reply over what it normally takes sales support to reply, but they normally do.

And they tend to appreciate a video showing how to replicate the problem. Log files too of course.

To get an appropriate length of a log file, I tend to open the log file and delete everything on it, save it. Then redo whatever it is that is failing, then copy that log file to a text file for tech support.

I've submitted the crash report.  The log shows nothing - probably because the interesting part never makes it out to disk as Daz Studio dies.

rames44

Spacious said:

Are you trying to render animation to a movie file?  Maybe try rendering to an image sequence instead, and then using other software to create the movie.  There's lots of software that can do this.  Blender is great for turning an image sequence into a movie, just a few clicks, plenty of easy tutorials for that subject, and it's free.

No - I always render to an image sequence.  So, yes, I can pick up where I left off, but it's annoying when you only get 2-3 frames, crash, restart, reload the file, reset the first frame, lather, rinse, repeat.