Error : [MemoryManagerGpu::releaseUnmappedMemoryFromInstance] 700: Could not release device buffer

[zonda_visual]

Hi, I'm rendering in Vray GPU now, RTX. It's an animation of 400 frames, first, at frame 53 rendering stopped, and when trying to start again at any frame, the render automatically stop inmediately after "Building Light Cache" with the following error "Error : [MemoryManagerGpu::releaseUnmappedMemoryFromInstanc e] 700: Could not release device buffer"

I tried updating and changing drivers, once let me render until frame 239 but now even if I change drivers again it stays there with same mistake. Render with CPU works fine.

I have Intel Core i7 14700 - RTX 4080 SUPER - 64RAM. I think is a good setup, the scene is not complex. Pleaseee help I need to fix this ASAP.

[hermit.crab]

There was recent driver issues causing memory leaks, but they were resolved with the latest recommended driver - 572.16. Which driver have you installed? Also, don't forget to restart your PC after driver installation.

[zonda_visual]

Hi, thanks for answering. I actually have that driver, 572.16, restarted my computer lot of times and still that error not allowing to render. Again, is a very simple scene, render is done in 1 or 2 minutes, so it doesn't seem to be the GPU memory.

[hermit.crab]

In that case, send the scene so we can see if the issue is reproducible on our end.

[zonda_visual]

Sure, here the scene. If anything else is needed for analyze it better, tell me I can send it. The error started appearing in frame 239, and I could render perfectly the previous frames, so maybe it doesn't appear any error at the beginning, but yes later on. Also, I can render perfectly other files of other projects.

I tried another time, and a new error (maybe related) appeared: Error : Could not initialize the GPU for rendering!

Thanks a lot for helping,

https://we.tl/t-qxOxcG6hDV

[hermit.crab]

There seems to be an issue with the link.

Otherwise, Muhammed_Hamed just informed me that to get rid of the nasty memory leak issue from previous drivers, it's necessary to do a clean install (there's an option in the NVidia Installer called "Perform a clean installation") of the 572.16 driver (and of course restart the machine). Here's an article about doing exactly that. Could you try this first?

[zonda_visual]

So I tried step by step exactly like in the article, making a clean install of the driver 572.16 but "Error : [MemoryManagerGpu::releaseUnmappedMemoryFromInstanc e] 700: Could not release device buffer" still persists.

Here is another link for downloading the scene:
https://we.tl/t-CayPCh2E44

Thanks,

[hermit.crab]

So I tried step by step exactly like in the article, making a clean install of the driver 572.16 but "Error : [MemoryManagerGpu::releaseUnmappedMemoryFromInstanc e] 700: Could not release device buffer" still persists.

Here is another link for downloading the scene:
https://we.tl/t-CayPCh2E44

Thanks,

Thanks. The error is reproducible. I'll start debugging to determine the cause.

[zonda_visual]

Perfect thanks. Tell me anything you find, I will need to start rendering the animation today if possible.

Thanks,

[hermit.crab]

The crash (it's a crash) seems to occur with a very specific setup, so I doubt I'll find the culprit soon. However, I've noticed it doesn't occur when you render through Standalone (V-Ray > .vrscene exporter > Export and Render). You can use it as a workaround to render the sequence.

[zonda_visual]

Ok I tried with standalone and effectively yes, it renders normally. I can use standalone for test renders and test animations. Anyways, I will need eventually to render normally, so whenever you have news tell me.

Thanks a lot for help

[hermit.crab]

After further testing, I can deduce it's a memory issue. Most frames with the provided scene take about ~15GB of VRAM. I'm testing with a card similar to yours (4070Ti Super, which also has 16GB VRAM). If you adjust some settings for memory conservation, there's no crash. You can confirm this yourself by monitoring your GPU usage with f.e. GPU-Z. Here's a helpful article about optimizing GPU memory. What helps greatly is simply switching from Bucket to Progressive Image Sampler, using CPU memory for loading textures or rendering via Standalone (without 3ds GUI).

[zonda_visual]

Ok great thanks a lot, It strange this scene takes lot of memory, I've done more complex images and no memory crashes. Something strange in the model or in some texture must be there that takes lot of memory. Anyways, I will read the article to optimize it. Thanks again have a nice day!

[Alex_M]

We also have exactly the same issue and have been encountering it for a few years now. It happened when we had RTX 3090, and now the same happens with RTX 5090. It's extremely frustrating. It always happens when drawing a rectangular region a few times in VFB while IPR is running. How can we prevent this? It's really slowing down our work to the point that it's faster to just render on the slow CPU but not deal with these constant crashes. We don't use the recommended drivers since the new RTX 50-series cards have some issues with the older driver versions such as boost clocks getting stuck at 600mhz randomly after PC reboot and other issues. We would really appreciate a quick resolution to error 700.

[hermit.crab]

We also have exactly the same issue and have been encountering it for a few years now. It happened when we had RTX 3090, and now the same happens with RTX 5090. It's extremely frustrating. It always happens when drawing a rectangular region a few times in VFB while IPR is running. How can we prevent this? It's really slowing down our work to the point that it's faster to just render on the slow CPU but not deal with these constant crashes. We don't use the recommended drivers since the new RTX 50-series cards have some issues with the older driver versions such as boost clocks getting stuck at 600mhz randomly after PC reboot and other issues. We would really appreciate a quick resolution to error 700.

Just so you know, error 700 is, so to say, a general error - it may be a lot of things, but most often, it's related to memory issues. I'm not sure if this is the case on your end. Have you tried rendering the scene with the recommended drivers? Send the scene so we can troubleshoot.