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

[Alex_M]

I haven't used the recommended driver due to the problems with this and other older drivers and the new RTX 50-series cards, as I mentioned above. On reboots the GPU boost clock is randomly stuck at 600mhz instead of boosting to 2900mhz. So we can't really use this driver or our work will be extremely slow. Either way, we've had this problem in the past even with the recommended drivers and it only happens when drawing regions in the VFB while IPR is running.

I've submitted a ticket (#363013) with the scene. Do let me know if you find something. Thanks in advance!

[hermit.crab]

I haven't used the recommended driver due to the problems with this and other older drivers and the new RTX 50-series cards, as I mentioned above. On reboots the GPU boost clock is randomly stuck at 600mhz instead of boosting to 2900mhz. So we can't really use this driver or our work will be extremely slow. Either way, we've had this problem in the past even with the recommended drivers and it only happens when drawing regions in the VFB while IPR is running.

I've submitted a ticket (#363013) with the scene. Do let me know if you find something. Thanks in advance!

Thanks. Just so you know, the error is reproducible. I'll start debugging.

[hermit.crab]

Whatever it is, it does not seem to occur in the latest stable build. Could you try it out?

[Alex_M]

Whatever it is, it does not seem to occur in the latest stable build. Could you try it out?

Thanks! I did as you suggested and I can't make it crash now. It seems that it's fixed in this version. I will keep testing and let you know how it goes. Thanks again for your help!

[zonda_visual]

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.

I tell you my experience. The first crash is a VRAM memory issue, in my case I had VrayEnvironmentFog in the scene, and when I put the Fog with a high distance, it required a big ammount of VRAM memory so it crashed. Now, without closing the scene, deleting the fog and trying again, it was kind of a bug that was remaining in the scene and the render will crash again. So once the fog was deleted, I had to close the file, open it again and then render with lower fog distance or either without fog. I had to do this too many times in order to reach to discover that the fog was the issue, and also the maximum distance thatn my VRAM memory can support. I finally decided to get rid of the fog.

In your case, you can start making test renders deleting heavy assets in the render until the crash disspears so you can discover which thing of the file is causing the crash.

Hope this helps!

[Alex_M]

Thanks for sharing your troubleshooting experience. My scene is actually pretty simple. It's literally two walls, a shower and a wash basin, all lit by a dome light with an HDRI. No heavy assets or complex effects. Besides, I'm using an RTX 5090 with 32GB of VRAM which should be more than enough even on very complex scenes. So the bug seems to be caused by something else. Whatever it was though, it seems to have been resolved in the latest stable release, as suggested by hermit.crab .