Since installing 6.5 I’ve only used native Cubas vst’s and nearly every time I have to do a force shut down. Yesterday I tried to find a pattern and though it had to do with a high number of vst’s in one project. Then I started a new project (empty) with only one Spector and one Mystic, and still it required a force shut down in the end. Really annoying.
Could you save your project?
Meanwhile I have purchased the 6.5 version. I also have to force shut down, a regular shut down never works
though fortunately I don’t have any data loss.
The most annoying thing is I can’t open my UAD SPL Vitalizer!
As soon as I try to activate it, a black window pops up in a split second and then vanishes again.
The other UAD plug-ins do fine as far as I can see.
This may be relevant for some:
I recently switched from an internal card to an external usb interface. On the first day I turned off the interface before I quit Cubase and got a violation error. This doesn’t happen if I remember to not turn the interface off first.
Hard to work out exactly how that information impinges on all your systems out there but I’m hoping a lightbulb may go on somewhere.
On exiting Cubase something in some systems (one of the Services?) is turning off before Cubase has finished finalising it’s shut down.
Try opening Taskmanager before shutting down Cubase and see if anything stands out immediately.
I’ll look around and see if there are any apps to see “what happened on X computer in the last two minutes” and see if the shutdown of Cubase can be tracked and logged by anything.
For those who don’t know how to power cycle, you need to turn ON all of your computer periferals (including audio interface and MIDI controllers) before you turn your computer ON. When finished working, turn the cumputer OFF first, then the periferals. This way you’ll avoid a lot of problems, possibly including the one described in this thread (no guarantees).
HTH
Altiverb is definitely the problem for me. Take it out of a project and it closes fine.
Yes, I can save my project. The problem occurs only when shutting down.
For me the problem occurred with C6.5 (64bit) again.
It started with 6.0, after research and trying out something, I found out that the problem was related to a bug in the access virus control, which was fixed half a year ago. So the last half year I don’t have the shutdown problem and was really happy that it was resolved for me.
But now I have a project, started with 6.05 with no shutdown problems in the first versions, has in later versions (edited with 6.5) problems with shutting down Cubase. So I have versions of the project with no shutdown problems (also edited in 6.5) and newer versions (also edited with 6.5) with problems shutting down Cubase. But other projects – also started in 6.05 and edited with 6.5 don’t have the shutdown problem.
So it seems that the shutdown problem is project related.
Any suggestions how to find out the problem in that project, which prevents Cubase from shutting down?
Hey - has anyone tried my suggestion on the previous page?
Anyway, here ladies and gents, is living proof that the shutdown issue in NOT plug-in related, Virtual Inst/VST related, project related, peripheral related, external synth related, video engine related, USB/FW issue related, jBridge related, VSTBridge related, 32bit vs. 64bit related, and on and on and on.
Oh? How come mine was? How come I fixed it by remembering to turn my usb soundcard on first?
OMG! I didn’t do it right did I?
OK it won’t work everywhere but I wouldn’t make sweeping and final statements that the big I am had found the problem.
Unspotted ironies and jokes aside. 
I’ve read the posts and I’ve trashed all my preferences but the that special project has a problem that prevents cubase from shutdown correctly.
The other projects work fine so it has nothing to do with the peripherals.
I also have a hang on exit and recorded the process-events with procmon.
It hangs right at the last line, when Cubase6.exe accesses synsoacc.dll.
I have attached the last rows of the procmon output:
Maybe anyone could confirm that it hangs always on the same row?
Here you can get procmon
Just add a filter for process name Cubase6.exe and you only get the events from Cubase.
Since updating to 6.5, it crashes on exit about 70% of the time for me. It never crashes during a session, so I don’t lose any work…but it’s mildly concerning nonetheless.
In the meantime Steinberg’s support has suggested a procedure to me that should help to identify all plug-ins not working properly with the current version. They say their UAD plug-ins run without problems.
Although I didn’t have the time yet to try out their proposal, I wonder why that particular plug-in worked trouble-free with v. 6.0 …
Not a plug in. Mine does it every time. Open. Start new project. Close. Crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Cubase6.exe
Application Version: 6.5.0.102
Application Timestamp: 4f23141b
Fault Module Name: Cubase6.exe
Fault Module Version: 6.5.0.102
Fault Module Timestamp: 4f23141b
Exception Code: c0000005
Exception Offset: 000000000101f4dc
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 2089
Additional Information 2: 2089248258d142380b2cc6826f8bf2ac
Additional Information 3: 7ddd
Additional Information 4: 7dddee0f5429b9997c8522638a00b76a
I’m working on a project in 6.5 and I get bsod when I exit it. I’m treading lightly and so far it only effects this project and the asio meter is is running at 85% but I’ve never ever ever had crashes like that with Cubase. 
Same here: fresh Win7 sp1 64bit, cubase 6.5 freezes almost all the times. x86 or x64, no differences.
I’ve had a freeze also without opening a project, but only editing some preferences and then closing cubase.
It’s really annoying.
Just had a 6 hour session, multiple projects, importing tracks, a zillion plugins (VSTi’s and FX) – and it didn’t crash on exit. Previously it had crashed on exit after 15 minutes with 1-2 plugins. So it’s random as far as I can tell…
No matter the plugin or device that causes the hang, Cubase ‘SHOULD’ compensate for this and have some kind of error catching system. Other programs I use do not crash when using the same hardware and vst’s. Cubase is just implementing the hardware, vsts and error checking poorly.
My Cubase hangs when a vst crashes or a piece of hardware isn’t working correctly. The same situation in other programs, the program lets me know and closes it safely.
It’s just ‘safe programming’
Yes when working with old projects from SX3 and C5 with tempo maps and audio warp! Ifixed the tempo map problem by deleting the tempo map track and creating new MIDI tracks and just copying the note data to the new tracks then deleting the old tracks and no more hanging or crashing! On the audio warp files I deleted the audio tracks and removed the audio from the pool then recreated everything from scratch including resaving the audio files in wavelab now no more crashes with audiowarp or hanging at close. 
couldnt steinberg implement a way to help troubleshoot these kind of problems?
maybe an option to see what cubase is doing during shut down, which would give idea of how far it gets.