Access Violation nvcuda64.dll

ebergerlyebergerly Posts: 3,255

Okay, this has gotten annoying enough that I've decided to try to find the culprit. I've seen other posts in the forums this year with a few folks having apparently the identical problem, but no clear resolution. 

So I'm on Windows 10, with an AMD CPU, and it seems to happen when I'm running D|S 4.15.0.2, the last non-beta released in January. And it seems to happen when I've got a scene loaded (it's happened with various different scenes) and I'm moving stuff around. And I *think* that moving stuff while in Iray preview mode is most likely to cause the crash, though it probably happened before in just OpenGL preview since I don't make a habit of moving stuff whle in Iray preview. Running out of RAM or VRAM isn't an issue, since I've got 64GB of RAM and this happened most recently in a scene that uses only 4GB of my 8GB GPU VRAM in Iray preview mode. 

The D|S crash windows that pops up is shown below, and it basically says there was an access violation with the nvcuda64.dll, so clearly it's somewhat related to Iray. I checked, and that DLL does exist at that location, so it's there, but apparently it can't be accessed. And I'm signed in as an administrator. 

Now this has happened with some older NVIDIA drivers, and also with the latest Studio drivers I just downloaded yesterday. And it's been happening for months, though only occasionally, and there's no reproducible steps to replicate the problem. And I've had no problems with any other software in recent years, and I use a lot of software. I'm rendering with an RTX-2070 Super plus a GTX-1080ti. 

And here's the relevant piece of the log file, which tells me nothing other than it was going along rendering the Iray preview and then just stopped, and then I restarted D|S a while later. And W10 Reliability History has no entries for the crash. 

2021-06-07 12:02:46.658 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating lights.
2021-06-07 12:02:46.658 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating object flags.
2021-06-07 12:02:46.658 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating caustic portals.
2021-06-07 12:02:46.658 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Updating decals.
2021-06-07 12:02:46.661 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Allocating 1-layer frame buffer
2021-06-07 12:02:46.667 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Using interactive scheduling, caustic sampler disabled
2021-06-07 12:02:46.682 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX Prime for CUDA device 1
2021-06-07 12:02:46.689 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Initializing OptiX for CUDA device 0
2021-06-07 12:02:46.793 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering with 2 device(s):
2021-06-07 12:02:46.793 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 1 (GeForce GTX 1080 Ti)
2021-06-07 12:02:46.794 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : CUDA device 0 (GeForce RTX 2070 SUPER)
2021-06-07 12:02:46.794 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend info : Rendering...
2021-06-07 12:02:46.794 Iray [INFO] - IRAY:RENDER ::   1.4   IRAY   rend progr: CUDA device 1 (GeForce GTX 1080 Ti): Processing scene...
2021-06-07 12:02:46.794 Iray [INFO] - IRAY:RENDER ::   1.5   IRAY   rend progr: CUDA device 0 (GeForce RTX 2070 SUPER): Processing scene...
2021-06-07 12:02:46.795 Iray [VERBOSE] - IRAY:RENDER ::   1.15  IRAY   rend stat : Geometry memory consumption: 892.352 KiB (device 0), 0.000 B (host)

2021-06-07 12:20:35.282 +++++++++++++++ DAZ Studio 4.15.0.2 starting +++++++++++++++++
2021-06-07 12:20:35.282 Performing cleanup...
2021-06-07 12:20:35.292 Release Cycle: General Release
2021-06-07 12:20:35.292 Platform bits: 64
2021-06-07 12:20:35.292 Qt Version: 4.8.7
2021-06-07 12:20:35.292 OpenSubdiv Version: 3.0.0

 

Does this ring a bell with anyone? I'm wondering if one of the newer D|S betas may have fixed an issue?

Thanks. 

Error.PNG
533 x 511 - 28K
Post edited by ebergerly on

Comments

  • barbultbarbult Posts: 16,753

    One card is RTX and the other isn't. Could that be an issue?

  • ebergerlyebergerly Posts: 3,255

    Okay, well I think it's safe to say that this happens when the view is set to Iray preview and you adjust stuff. Either directly by manipulating the move/rotation/scale in the Iray preview window, or maybe while adjusting those things in the UI while Iray preview is enabled. I have a simple scene with just an office desk and chair, very low mesh, and I add a G8 into the scene, and if I do stuff like scale an overhead emisslve light plane enough times (using the manipulator) I can get it to crash. So I think somethings going on with Iray preview updating. And if it takes a long time to update due to scene contents it seems more likely to crash.  

    I'm wondering if the Iray preview update gets laggy then maybe Iray can't update fast enough and just gives up. 

  • ebergerlyebergerly Posts: 3,255

    barbult said:

    One card is RTX and the other isn't. Could that be an issue?

    That's a good point...they both show up and do the render, and they both show up in the NVIDIA control panel, and both use the same driver according to the NVIDIA website, but maybe they don't play nice together with Iray. That would sure give me a frowny face laugh 

  • ebergerlyebergerly Posts: 3,255

    OK, well I got it to crash with just the RTX card enabled, so that kinda points to it being a generic problem I think. 

  • ebergerlyebergerly Posts: 3,255

    And I just downloaded the latest beta 4.15.0.14 and the same thing happens. In fact it was easier to get DAZ to crash. Just opened the scene, went into Iray preview, scaled an emissive plane in one direction, and BAM, D|S crashed. 

  • ebergerlyebergerly Posts: 3,255

    FWIW, it occurred to me that since this DAZ Studio crash can be often repeated by adjusting scene objects while in Iray preview (specifically I can reproduce it by adjusting the length & width of an emissive light plane enough times) that seems to possibly implicate the PCI bus, since adjusting stuff in Iray preview requires PCI communication between the GPU doing the real time rendering and the DAZ Studio UI using the main memory and CPU to allow the user to adjust stuff. So it occurred to me that maybe I should try to update the AMD chipset drivers on my MB, since they include drivers for PCI communications.

    So I went ahead and updated the chipset drivers (something I haven't done in years) and then loaded the scene I've been using and started adjusting the emissive light plane. Well, unfortunately, it crashed again with the same NVCUDA64.DLL error. 

    I dunno, it sure seems like this is starting to point more and more to a DAZ Studio issue rather than a hardware issue or NVIDIA driver issue. As I mentioned before, I've tested all the hardware I can think of, tried 3 different NVIDIA drivers, 2 versions of DAZ Studio, updated chipset drivers, disabled my older GTX-1080ti card, and nothing seems to help. 

    Strange. This is the first time in years I can recall having a nagging crashing issue with DAZ Studio.  

Sign In or Register to comment.