Still got Cubase crash/freeze on closing the project using just Acustica Audio plugins. Doesn’t happen in Reaper so it’s deffo not plugin issue.
No crashdump in Steinberg folder when this happens.
Here’s the clip - YouTube
Hi,
Please use Microsoft Proc Dump to generate a DMP file.
Agree
Please, fix it
Hi,
Could you please provide a DMP file to know, what should be fixed?
In my case it doesn’t crash, but stops responding and doesn’t close for a really long time on quit. I usually have the same (large) template loaded and after 17 minutes it will sometimes close normally. Other times it hangs indefinitely (multiple hours).
I can watch Task Manager and see it very slowly freeing up memory. My guess is that it’s inefficient freeing up large amounts of memory. Fault could also lie with Kontakt or East West Play, as those are the plugins using all the memory.
Hi,
There were some tricks written, how to speed up Cubase quit. One of them is to close the project first and then quit Cubase.
Could you use Microsoft ProcDump utility to generate DMP file when Cubase freezes, please?
I’ve been having this issue since Cubase 9, and still having it now on 10.5 (Windows 10 as well).
Any particular command arguments needed with ProcDump execution? I’ll get one uploaded shortly.
I’m getting these freezing issues with the latest version of Elements 10.5 (as of today) on Windows 10. No plugins used, not rewire, no VST’s etc.
Just a few Midi tracks using my MODX.
Also noticed if i turn the MODX off while Cubase is open, i get a box come up telling me its lost connection to the sound device, and offers up others that it has detected. Thats understandable, but the box is totally un responsive and i have to force quit Cubase every time.
I’ve had 7 months of this same problem, and for me it only happens when there are Acustica plugins in the project, but there doesn’t need to be any open GUIs, and I’ve even switched off the plug-ins as a test. I have tickets open with Steinberg and AA. So far, lot’s dump files and system repair suggestions, but no luck.
I too have this same problem with Cubase 10.5.12. I didn’t have this issue with 10.5 when I was running on a windows 7 machine, but two months ago I got a new computer with windows 10 and now it happens when trying to close a big song or when trying to close cubase. I’ve been a die hard cubase user since 2002 and this is getting very frustrating. Steinberg fix this now please…its clearly not a plugin problem when so many people have the same issue with very different plugin sets. Thank you
Hi,
A *.dmp file would bring some light into it.
Win: Documents/Steinberg/Crash Dumps
The freeze doesn’t create a crash .DMP file, which I only realized after sending them to Steinberg already. You have to create a Cubase DMP in the Windows Task Manager when Cubase is not responding. This is what highlighted that the problem is related to:
BREAKPOINT_80000003_D3D10Warp.dll! Threadpool :: WaitWhileBusy
Which is the Direct3D 10 Rasterizer dll. I also highlighted to Steinberg that since Cubase 10.5 my Cubase GUI occasionally freezes for a few seconds. I believe the two issues may be somehow related. My GPU is Intel with no other known issues related to Cubase.
Just thought I’d mention that I’m also having this problem. Closing most projects results in a long hang time. I’m using lots of sample libraries from Spitfire, EastWest and others. I haven’t narrowed it down to any single factor, but it happens with most of my larger projects.
I have the same problem, for a long time now: Freeze on close. It is no crash, so no *.dmp-file available, Cubase is still using some CPU time in this frozen state and sometimes Cubase even finally closes, maybe after five or more minutes… Could be some sort of resource/memory release problem, maybe will try a live dump via task manager.
This happens with larger projects, many KONTAKT instances, … I am still clueless, but investigating occasionally. It is not a very serious problem, but annoying.
I’ve been told Steinberg are trying to work out the issue with Microsoft currently. The UI Direct3D 10 Rasterizer dll seems to go squiffy if it’s overloaded.
I’m pretty new to Cubase coming from using Reaper & logic… & Ableton & Renoise (a bit of a DAW Junkie) . Ive been really enjoying Cubase a lot & find it really great for midi. But this is very annoying, it hangs on closing a project or quitting especially if its been a long session. If i close after only a few minutes of work it closes just fine. I’m on macos so it’s not just affecting windows. There is no .crash file created because its not a crash.
I really hope there is a fix soon because I bought Cubase as I’m thinking of moving over to windows & want to use a pro DAW with amazing midi features & Cubase is that DAW. But this is a big problem right here that seems to affect both OS’s & since I’ve started using it I haven’t used Logic or Reaper so I really do hope it gets sorted soon.
Tale as old as time.
It’s not an external plugin because as has been metioned, it doesn’t happen with other DAWS.
Cubase takes an eternity to close… when it closes. And yes, as others have been pointing out, I think it depends more on the length of the session. If you’ve been working a few minutes, it’s going to close (and relatively fast!) but if you’re working on your project hours, chances are that it never closes.
In the dump file, they appear random plugins stuck.
In my case it only ever happens with Acustica Audio plugins & Cubase together. The size of the project makes no difference, small or large. It never happens if there aren’t any AA plugins in the project. The fault is focussed around the D3DWarp.dll.
Clearly you have a different problem to mine.
I recently installed the latest version of the Spire plugin 1.5.2 build 5090 to be exact and it works now without any problems …
Whelp, it’s got me too. Literally started happening out of nowhere. I trashed all my prefs and rebuilt everything from scratch. All plugins are up to date. Created a small template just now with only a few tracks to test and I have to force quit Cubase every single time. Frustrating beyond words. I moved from Logic thinking this was a better, more stable DAW and I’m slowly finding out that’s not necessarily the case. Just once I wish a company would focus on bug squashing and making programs more stable and reliable then adding a ton of new features. I can’t work, can’t save and have spent 2 days troubleshooting.