Why is it that every time Sonar X1 Producer Expanded crashes on a win 7 64 bit machine that after the crash it takes 20 mins for the Sonar.exe to kill so stopping you from restarting Sonar?

It doesn't matter what you are using when it crashes, why its crashed, whether its via Jbridge or Bit Bridge...

This has been seriously messing my workflow ever since I changed to X1....

FWIW,

If it were me I find the source of the crashes.
That seems far more important to me.

For me SONAR crashes once about every 1000 hours and I attribute it to the fact that I hardly ever shut down my DAW. But, when SONAR does crash I simply open the Task Manager and if SONARPDR.exe is running I manually kill it. I'm up in less than a minute.

I *never* blame SONAR for a crash out of the gate. I *always* assume it environmental first.

FWIW,

If it were me I find the source of the crashes.
That seems far more important to me.

For me SONAR crashes once about every 1000 hours and I attribute it to the fact that I hardly ever shut down my DAW. But, when SONAR does crash I simply open the Task Manager and if SONARPDR.exe is running I manually kill it. I'm up in less than a minute.

I *never* blame SONAR for a crash out of the gate. I *always* assume it environmental first.

The crash could be anything, any number of reasons, could be using NI Komplete, or something In house like Dimension Pro, crash report is different every time but what remains constant is that I cant manually kill the Sonar process, it just stays there while it dumps for 20 mins then I can restart Sonar. Even a reboot will take 20 mins while Windows tries to kill Sonar itself. Its incredibly frustrating and has been going on ever since I bought X1 (never happened in Sonar 8.x)

Ya know ... the same thing used to happen to me.

Long story short ... I had to move my studio in to the basement for reasons beyond my control.

I've spent about 25 - 30 hours mixing, mastering, and mastering a CD last week.

Sonar crashed twice, which I think is great because I gave it one hell of a workout. Funny thing though, it crashed a lot more than that upstairs, and I saw the same problem of it sitting in memory after that crash for a very long time. I used to just reboot.

Now ... since I moved in the basement ... when Sonar crashed those two times, I was able to immediately restart it. The only time that ever happened previously was with X1 Original Release.

The only changes I made were, I moved my system to different outlets, my Yammy's are running through a high end line filter now, and my sound card is plugged in to a different USB port.

Try one of those things maybe?

I'll be scratching my head over this one for a very long time.

Good luck.

After reading markyzno's post, I remember now that both crashes I experienced were Dimension Pro related. So I guess 'technically' Sonar didn't crash, DimPro did.

For those following my saga ... moving to different outlets, filter on the Yammy's, and different USB port didn't help my Pro Channel on/off problem. God I hope X2 fixes that, but then again, how will I know? ;)

*bUb StRuTs AwAy SiNgInG THIS (not a plug -- sorry Baps)*

I'm looking in to my crystal ball and I'll bet you have some m-audio drivers somewhere...... they don't release properly.

FastBikerBoy

I'm looking in to my crystal ball and I'll bet you have some m-audio drivers somewhere...... they don't release properly.

Hey man ... nobody wants to hear about your prosthetic genitalia.

It's usually a peripheral device that won't close down, hence the m-audio driver mention. M-audio keyboard?, Midi router?, controller of some sort?

I'd think it's either what Craig said or dumping/error reporting. Run task manager and if you see a process called dumprep, kill it.

This isn't a problem I've had, but I do remember hearing others had success with unplugging MIDI devices when the sonar.exe would hang.
 

Mr FastBikerBoy......

Yes, dreaded M-Audio....Thats probably it. I used to have an Emu 1820m with my old Sonar and a year ago it died after many years of good service and bought a Delta 1010.....

Aggghhh, this has got to be it.

I've tried rolling back to different drivers due to other M-Audio bugs (not being able to work in different sample rates and other nasties) but this problem persists....

So it leads on to another question/problem which I fear is unresolvable.

Is there a 64 bit win 7 M-Audio driver that actually works for the Delta series?

Will Sonar X2 help with this at all? (Which I will upgrade to anyway as its looking tasty)