I have had this problem - it really does exist, comes up at the most inopportune time... 1010 always, everyday -  on vista 64 bit.  828MKII never.. It happened most frequently when I was recording midi using dimension pro, but it did happen with audio from time to time too. Thats all I know about it.  From my chair,  MARKYZNO is right, it happens, and others are right in that it could very well be the driver / hardware. 

Best Regards,

L

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.

hockeyjx

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.

......and I'll garauntee that if it had a MIDIsport attached it wouldn't. The problem is real, it's just a dodgy driver though. I can unplug my MIDIsport and have no problem with closing X1, plug it back in again and it can hang.

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.

One way to find out if it is an M Audio driver is when X1 hangs after a crash is to disconnect the M Audio device if at all possible. If it is a PCIe card than it may be difficult to do so. We that are saying that its a driver issue have either had the problem with an M Audio device or have noted it in many other posts for many years.

No one can be 100% sure on this yet it follows from the collective wisdom of this forum.

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. 

I have the same problem.  You can't kill the process!  You have to reboot.  Huge PITA.

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.

I purchased Sonar X1 back in January and have yet to experience a crash of any kind.  Now I...on the other hand...have crashed several times trying to learn the program.  But I'm getting more comfortable with it every day.  

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.