Please fix this
beyonder2k9
Posts: 117
DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Windows\system32\nvcuda.dll" at 0033:00000000CB82B9AA, cuDevicePrimaryCtxGetState()+3202413 byte(s)
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
Have you filed a help request? https://www.daz3d.com/help/help-contact-us
That is a component of the nVidia driver, the CUDA support. Were you rendering in Iray at the time? What is your system specification? Have you tried updating yor video drivers (using nVidia drivers), or if current have you tried using a slightly older version?
I spent two hours making a scene and went to hit the iray preview for lighting and I got that error. I was so pissed at the time. This only happens when I am rendering more than one character. This is a resource sharing issue. My system isn't the issue.
If that were the case it would be far more widespread. However, without more information it is impossible to offer even a tentative suggestion of what is going on or work around the issue.
Yeah, what Richard said. It sounds like CUDA was trying to access your GPU (or something about your GPU) and couldn't. I *believe* a "cuDevicePrimaryCtxGetState()" represents a CUDA function to access the present state ("ctx" or "context") of an individual device/GPU.
So yeah, it's quite likely your system IS the issue, either the hardware or the drivers.
Normally, I get that error message when my graphic card VRAM can't hold the scene, and falls back to CPU. In some cases, if the system RAM can't hold the scene, DAZ crashes with that error message.
So, as Richard said... unfortunately, without further information, it is not possible to offer a suggestion what might have triggered the message. As for "fixing", you'd have to put in a support ticket. Otherwise, the information will not reach the programmers properly.
Sorry, but for first rule of tech support; do NOT make assumptions.
I would expect at least a number of other reports of similar issues if it was not something on your system; having said that, first rule is to not make assumptions. So please provide more info as already requested by Richard.
Have you got SWAP disabled? That is supposed to be the purpose of SWAP, to stop crashes when RAM is used up; it starts dumping 'stuff' to the SWAP space on Disk.
First rule of tech support is to expect to hear someone say "did you check everything but our product?"
Just sayin'.
I wanted to offer that this observation helped me out greatly: a scene with many object instances (i.e., trees in a forest) and growing numbers of actual objects (e.g., leaves) was causing decreasing stability in trying to render with the Octane Daz plugin as it grew in size, to the point where it would get "stuck" trying to render and Daz would eventually crash with the nvcuda.dll - related message quoted by the original poster. Very similar message, but a different renderer within Daz.
I have some NVidia GPU cards with the smallest being 4G VRAM and an Octane setting to extend into system RAM as needed, so tried turning off the 4G cards and using only the 12GB card that was in my system for rendering (i.e., a different card was being used for display purposes.) Lo and behold Daz stopped crashing after attempted Octane renders and the Octane pluging no longer became stalled on render attempts.
So I would like to emphasize that ability to contain a scene when rendering with Iray (or other) can be a very real issue and cause unexpected issues in Daz when those limits are reached, from my experience.