It's SONAR on *your* system that does it.

And there you have it. Not to say the lad isn't having problems, but I don't have a problem loading or running X1.


I guarantee if I built and configured a machine for this OP - it would work.

My home studio PC runs SONAR X1 Expanded with an Edirol UA 101, a Delta Audiophile 2496 (M Audio) and a KORG MS 20 MIDI USB controller which was part of the original KORG Legacy bundle. I have the issue with SONAR crashing and not being able to kill the exe in task manager or being able to restart the program for 20 minutes. If I power down the UA 101 after a crash and then disconnect the KORG via Device Manager I can then kill the process and restart the program. On my work PC I have SONAR X1 Studio and an Echo MIA MIDI. When SONAR crashes on that machine I have no issues restarting at all. Bottom line in my experience it is a driver issue not a SONAR issue and M Audio is just one of the culprits. PS SONAR rarely crashes on me unless I do something stupid.

I've had some random behaviour in this regard; I used to have similar sounding crash-no-way-to-restart hangs on 8 and 8.5 actually. I found at one point that it was leaving garbage in memory that was not getting cleared, and had a shortcut to a kind of force-clear-all-unused-memory command (I forget what it was exactly) on the desktop. That would work, though sometimes I had to do the task-manager kill process thing as well to get rolling again. Maybe helpful? (This is all on XP mind you, with an E-mu 1616m sound card).

Since X1 I have had none of that, very occasional crashes that require the task-manager trick but nothing worse. I have found it pretty solid. This is a relatively old machine (2007 I think) and has had a lot of heavy use, and it still ploughs along pretty well under XP/X1. I don't know if it will run X2 yet, might need to finally move up to Win7 (or 8?). 

I have had issues on my Win7 laptop, the worst was using Asio4all with onboard sound (in a pinch, on a plane), I had constant crashing that was driving me crazy until I figured out it was a particular *patch* in a particular Reaktor ensemble - not the ensemble, which would run other patches just fine, it was literally only that snapshot that was killing Sonar. I froze the track and suddenly, smooth sailing. Weird. 

Quite some time back, I had a problem whose circumstance resembles the OP.
Despite lots of help from SONAR forum members... nothing worked.
The Cakewalk folks dug into the problem reports, sent me forms, fixes, etc and finally... somewhere in Germany, a Roland staffer got a computer to do exactly what mine did...
every time.

The Cakewalk folks sent me so much help, I will never forget the customer service.
And the forum folks did the same...

I would send more details but the computer that held all the information blew up.
YEP.. the computer was the problem...luckily for me the problem was something that could have caused others the same problem, so I got lucky.

Cakewalk staffers have always been tops in customer service.
Since I realise I'm one of millions of people, I had to follow up a lot and that is to be expected.

The problem isn't "SONAR" exactly.... rather SONAR is involved with other issues...
I make a living with SONAR ...every day.

You'll remedy your problem... keep a good attitude and continue challenging the situation...
and remember... some of these boys lending assistance have helped hundreds of others...

Thanks to all y'all and here's a cheer to getting your problem fixed.

What did CW report to you when you sent them the crash dump?

When SONAR hangs like that, it is either a driver issue or a hardware failure (the audio interface, a firewire adapter, or in rare cases a power supply, disk drive or controller). SONARPDR.EXE is hung because it's waiting on some external event, e.g. waiting for a call to a driver to return, but the driver has either crashed or gone into an infinite loop waiting for hardware to respond. IOW, it's not something Cakewalk can fix.

In my situation it only happens when using one of my USB interfaces - Roland Quad Capture and Cakewalk UA-25EX.  It doesn't happen when using my Echo Audiofire 8Pre.

It IS a driver issue but Sonar is the ONLY audio application I have seen be such an ungraceful piece of @$#% about it. I once read a post (I think from Noel) defending Cakewalk's grandiose position that it wasn't their fault even though other applications can deal with this reality without being an utter piece of crap. Why do things right when you can hide behind standards and blaming the other guy? This issue has pissed me off for a long time. Of course droves of folks around here will tell you Cakewalk can do no wrong and that its all your fault. Doesn't help Sonar get any better when valid criticism is drowned out.

Part of the confusion: The event viewer only shows what has been reported.

So, Sonar has stopped working. And it reported itself.

What stopped Sonar is the real question. Driver, plugin, OC, mem voltage,...

Get BlueScreenview
http://www.nirsoft.net/utils/blue_screen_view.html
And appcrashview
http://www.nirsoft.net/utils/app_crash_view.html

Delta 1010...

Legacy item...

Emu...legacy item...

The OP has given very little real details...driver versions, hardware versions, etc...

I am actually surprised Delta even has Win 7 drivers for the 1010...

Its a little hard to take this post serious when we have so little serious information to go on...

I feel for the OP...but not a lot.

Well - it seems to boil down to only one question then. Does Sonar have to take in account rotten drivers and make weird work-arounds, or do the hardware makers have make drivers that work good in the first place. I think I go for the last option. Oh - and by the way.. Korg also made some terrible drivers for their micro controller series. If this is still the case I don't know, because I do not have any Korg hardware anymore.

I have no doubt its something Delta 1010 MAudio related....

MAudio cant write drivers for toffee.....

I'm using the 5.10.0.5076 drivers as the latest Win 7 Drivers wont let me change Sample rate from 44.1 no matter what!

For reference the latest Win 7 Drivers and Sonar still crashed anyway....

I did try all the usual things guys, like when Sonar crashes, kill all the Maudio processes, Windows Audio Service, everything Audio related basically but still SonarPR.exe wont free itself up.

But guys, Sonar is the only bit of software I have ever used that behaves like this after a crash.....

yes, that driver proved to be quite hellish....Also it lies! After installing it you can clearly see that the MAudio proc is still running under *32 bit when the site clearly states its a 64 bit Win 7 SP 1 driver....

*sighs*

daveny5


In your defense, I've been having a lot of white screen crashes of Sonar. I just went out to the M-Audio site and got the latest driver for my Delta44. Apparently there is a newer one for Windows 7 64-bit SP1. I'll see if that helps. You should check for a newer one for the 1010. 

EDIT: Its 6.0.8