POLL: Is C6 hanging on exit for you?

I just recently began having a hanging issue in projects with BFD Eco 64bit. Posted this in another thread…maybe it can be of help:

Just to update here: I tested all last night and this morning. Fresh Cubase install, Eco install, registry cleaning and all sorts of other things.

Microsoft Runtime C++ 2005 Redistributable version 8.0.56336

It was installed with the m-audio usb/midi driver for my controller. I tried uninstalling the m-audio driver and the Cubase project did not hang. Tried to reinstall the driver, but it would not reinstall without this version of C++. Got it installed and project hangs again. So:

(1) Removed just the driver, leaving the C++ version there = Project hangs
(2) Reinstalled driver, uninstalled the C++ version = Project closes properly

So as far as the project hanging, for whatever reason, Eco + Cubase 6 + this version of C++ cannot coexist. What I don’t understand is that Eco would not hang every project it was instantiated in. Only 75% of them…

Also, I’m not sure that this explains why Eco would not pass the initial Cubase vst scan and gets blacklisted. In any case, looks like I’m back in business…

As told, since 6.5 I am having the hanging on exit problem again on some projects.

I’ve found out that the problem (for me) must be plugin releated but the plugin itself is not problem.

For example in one project there is an instance of Massive as the 1st vst-instrument with 5 other instruments as vst-instrument, but Massive is the plugin which is have having the problem and prevents cubase from shutting down correctly (Every other instruments I can remove from vst-instruments, but if I remove massive the project and cubase his hanging). So I thought massive must be the problem - deleted the dll so that cubase can’t load the plugin and massive is marked as not found in vst. If Massive itself is the problem it should be no problem the remove that vst-instrument, but even if massive is not loaded the project and cubase is hanging if I want to remove that 1st vst-instrument.
Any ideas how to solve this?

I’ve been toying a little with C6.5 64 but it is too unpredictable, too fragile to use.
It crashes for no obvious reasons and sometimes I have to CTRL+Esc it to get it to exit, and then restart it.
I’ve not seen any clear repeatable patterns but I don’t want to trust it too much.

I just keep using C6.5 32 for the time being :sunglasses:

[edit]

I should probably adjust my radar a little …
then it would have detected that I mainly used 32bit plugins.
so the jury is still out.
later after some projects I’ll try again with 64/64

I’ve been using Cubase 6 x64 (didn’t even install the 32-bit version) since its release and the main thing I think is essential is to delete (“trash”) the preferences folder on each upgrade. I think this forces a re-scan of all VSTs and perhaps with each new version, the handling, particularly of 32-bit VSTs in a 64-bit host, is improving – I don’t know, it just seems that way.

A recent update to HALion 4 has removed one source of crashes on 64-bit systems, however that might be a bit off-topic as this is about Cubase hanging (as opposed to crashing) on exit. I found two utilities which may offer some clues, BlueScreenView and WhoCrashed, and have enabled crash dumps, but of course, since then, my system has been rock solid … :unamused: (or maybe: :smiley: ).

My specific use case is very simple though, I have about 5 third-party VSTis, all but one of which are 64-bit, I don’t work with video (much) or have an exotic setup. If I try out a VST, when I’m done with testing I remove it … I’ve seen people with 100’s of VSTs, most of which they tried once, but never use … and unless I really, really want or need a particular VST, if it doesn’t come in a 64-bit version, I move on.

I still have a feeling the problem has something to do with closing ASIO or MIDI devices, and this is why the symptoms are so varied, because everyone has a different audio/MIDI interface. It may be compounded by the fact that some VSTis have MIDI inputs and outputs, but that’s just my gut feeling.

You could be on to something here, well spotted! I have no less than five versions of this thing installed, and I don’t know any way to determine whether it’s safe to uninstall (via Control Panel) any of them. This is a complete Microsoft mess.

I dont think the log file gets created if Cubase freezes completely (since its not able to save the log anymore), only when Cubase is aware that something went wrong.

Just a recap: 333 posts here and STILL no single reaction from Steinberg?!?!?! SHAME ON YOU!!! :angry:

this is normal, as explained here:

http://social.technet.microsoft.com/Forums/en-US/w7itproappcompat/thread/e55213da-c158-4d6f-9977-d56ac2a848fc

I think Steinberg doesnt care cause they know this is not a single problem, its more dependent on various configurations we all have. In their test labs everything probably runs well.

This is why it would at least be useful if they gave us a way of finding out what’s causing the problem…to see what Cubase is doing on shutdown. like:

unloading Halion sonic
unloading Battery
unloading Kontakt (freeze)…AHA!!!

Nonsense. On page 1 there already is one, and page 9, maybe more. But probably you weren’t interested in facts but needed to shout in frustration. Hope it helped.

cubase crashes on exit for me,even if i just start cubase and dont load any projects. just shut down after startup,and i get the crash. in last 2 updates .0.6 and .0.7 64bit windows.

Not very helpful responses, unfortunately. We’re supposed to deactivate all VSTs before closing a project? Other sequencers don’t have this problem. Seems like a Cubase issue to me.

Hello
I’ve many crashes on audio mixdown not on exit
Ganax

I am having a problem with Cubase 6 crashing on exit but only if somepoint during the session I use an external controller. It is as if when closing Cubase it is trying to save the current controller settings and failing.
I want to upgrade to Cubase 6.5 but do not want to do this until I have resolved the current problem.
The blue screen crash error is: Page Fault In Non Paged Area
Examples of actions that cause this problem (nb Cubase only crashes on exit well after I have made the controller change)

  • Use of learn mode on Novation Zero SLMkII
    Using any control on Novation Zero SLMKII
    Changing anything setting through ASIO control panel for M-Audio FastTrack Pro
    Changing the volume for the M-Audio FastTrack Pro in Windows (rather than via cubase)
    Using Learn function or moving any midi controller button/pot/slider on MAudio Keystation Pro 88

Note that everything else works fine as long as I save before exit I don’t lose anything and I have produced 48 track compositions with no other issues.

What I have tried so far:

  • Originally searching KBs highlighted blue screen error as being hardware related. I swapped out memory, then mother board and memory but error persists.
    Cubase forums suggested run as Administrator but error persists.
    Strip down Cubase to a blank project with 1 track problem persists.

Noted that immediately before each crash the following are events are always logged in the event log in the following sequence:

1. INFORMATION LEVEL EVENT FOR SOURCE - USB MIDI SERIES AUDIODEVMON
The description for Event ID 0 from source USB MIDI Series AudioDevMon cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Replacing class driver for Vid: 0x00000A4D Pid: 0x0000008E using INF C:\Program Files\M-Audio\USB MIDI Series\Streaming\MAudioUSBMIDI.inf

2. ERROR LEVEL EVENT FOR DRIVERREPLACER
The description for Event ID 0 from source DriverReplacer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ExecuteDriverReplacement error (9) calling SetupDiCallClassInstaller

3. ERROR EVENT FOR DRIVERREPLACER
The description for Event ID 0 from source DriverReplacer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Error: 0x00000000 - The operation completed successfully.

OK, cubase crashes on exit for me,even if i just launch cubase,dont open any project.just close it down,and it still crashes. i get the"cubase has stopped working " message.
it is happenning in last few updates.

Now I am crashing not only on exit but also if I try to add an output bus!

Not sure if this helps. Attached MiniDump File (.dmp renamed to .txt). This seems to indicate Cubase Problem.
042712-24663-01.txt (281 KB)

Even the demo version of 6.5.0 hangs on exit. Had it happen when closing a simple project with 2 midi tracks, and no plugins of any kind (opened quickly just to check a feature).

After force quitting, Cubase wouldn’t restart. Restarted Windows, and now it also couldn’t find the elicenser key. I had to unplug it and plug it back in after rebooting the system for the second time. The fact that it lost track of the key has me concerned about Cubase/Steinberg’s copy protection reliability as well now.

Steinberg might want to address issues like this very quickly. Stability is paramount in a pro environment.

I score film/ads for a living and have been considering moving some work back to Cubase from ProTools. However, issues like this will send me right back to ProTools, despite it’s more limited midi capabilities. PT hasn’t crashed in over a year of working 5-7 days a week. I’ve been running the Cubase 6.5 demo for a grand total of 3 days, and it hangs on close about 50% of the time. This system is rock solid, so that isn’t it, and I’m just demoing Cubase with very small projects.

The last one had no plugins of any kind, so it isn’t a 32/64 bit plugin issue either.

If this were a recent issue, it would be one thing. This has been going on across three versions, over three years. If it hasn’t beed fixed yet, it’s because SB haven’t yet hired anyone who knows how.

Ouch. That long? Not very confidence-inducing.

As for the proposed “solutions” of reinstalling USB/interface drivers, midi drivers, etc. These should NOT be a problem - esp. when there are no “inexpensive” devices or suspect drivers or 3rd party plugins on the system.

No other DAW on this system I’m using to demo C6.5 has a problem - PT9/10, Sequoia, etc all open and close (and run) without a single issue, and always have. Same audio/midi drivers, midi controllers, updated Syncro drivers, MS C++ installs, etc.

No matter, I’ll head back to PT and maybe give Digital Performer 8 a go when it’s released. After all these years of giving Steinberg the benefit of the doubt, nothing has changed. Feature additions continue to trump stability. Too bad really. They have some great ideas in there. But it’s their responsibility to take reports like this seriously without requiring users to find a the problem for them.