Nuendo 15.0.30 64bit2026.8.13 0.47.44.663.dmp (2.1 MB)
Can someone help me figure out what the problem is? It’s been bothering me for months. Whenever I export or render locally, this situation happens when I go back to working in Nuendo.
If Nuendo freezes after an export or rendering process (such as Render in Place)—often while the timecode continues to run or at 100% progress—this is usually due to conflicts with video tracks, graphics card drivers, cloud services running in the background, or specific plug-ins.
This is a curious one. The failure is an access violation in the Windows Component Object Model. It means it’s trying to access memory that it’s not allowed to, likely due to a bad address. What’s curious is that I see several references in the dump to a web address for dev.azure.com.
Are you running on a standalone machine?
Yes, it’s running on a standalone machine, and apart from Windows updates, graphics card driver updates, and Nuendo upgrades, there haven’t been any other software installations or updates. I searched for errors related to combase.dll, and many people reported that it was caused by NV drivers, but I’ve already tried many different driver versions and it’s still the same.