Sonar X1 Shutting Down Upon Opening Project

Not sure what the issue is, but you might be able to open the project in SONAR's "safe mode" by holding down Shift while you open the project.

You will then be able to choose which plug-ins get loaded...

Scott

--
Scott R. Garrigus - Author of the Cakewalk Sonar and Sony Sound Forge Power book series. Get Sonar X1 Power - Today! Go to: http://www.garrigus.com/

Publisher of DigiFreq - free music technology newsletter. Win a free SoundTech Vocal Trainer Package, go to: http://www.digifreq.com/digifreq/

Publisher of NewTechReview - free consumer technology newsletter. Win a free i2i Stream Wireless Music Pack, go to: http://www.newtechreview.com/newtechreview/

Edit: Never mind! Scott had a better suggestion than where I was heading :)

Thanks for all the replies:-) hmmm very odd, still crashed even with safe mode, heres the crash report, means nothing to me lol


Faulting application name: SONARPDR.exe, version: 18.0.1.197, time stamp: 0x4d0900d5
Faulting module name: SONARPDR.exe, version: 18.0.1.197, time stamp: 0x4d0900d5
Exception code: 0xc0000005
Fault offset: 0x0000000000097b09
Faulting process id: 0x85c
Faulting application start time: 0x01cbba52ca1b0839
Faulting application path: C:\Program Files\Cakewalk\SONAR X1 Producer\SONARPDR.exe
Faulting module path: C:\Program Files\Cakewalk\SONAR X1 Producer\SONARPDR.exe
Report Id: 63e2ee0b-2647-11e0-bb4a-00196678a3cd

Funny.  I'm getting the same thing.  I hoped the patch would fix it.  No dice.  I've been running 8.5 producer on this machine, dual quad running 12 gig of memory and dual hd monitors ever since 8.5 came out (64 Bit). Windows 7, Onyx 1640 Firewire, cause I know someone will ask. I NEVER had a single solitary issue. 

I thought the problem was V-Vocal, the first crash occurred when I tried re-opening a saved session in which I used V-Vocal.  I'm now pretty sure it's the pro-channel.  Left unused I have no problems.  As soon as I turn it on, in any channel or bus and then save the project, Sonar refuses to re-open the project once closed.

I tried safe mode, unplugged every plug in.  Same error message.  I plan to uninstall x1 tomorrow and request a refund.  This upgrade is retrograde and, as my son would say an "Epic Fail."

I'm sure that I'll be thrown under the bus by a bunch of folks that know more about computers than I do.  I'm a musician, not a computer guy.  Cakewalk should work for the average person, out of the box, period.  If it doesn't it just isn't ready to be sold.  I've used it for years, purchased every version since 6 I think.  They're into me for a lot of money, and they've now cost me a whole day's worth of tracking. 

Where's the love Cakewalk?  This program is infected with salmonella.  Issue a recall before someone gets really sick!

I checked the event viewer.  I had 19 of these in the last hour...I'm sort of stubborn:

Faulting application name: SONARPDR.exe, version: 18.0.1.197, time stamp: 0x4d0900d5
Faulting module name: SONARPDR.exe, version: 18.0.1.197, time stamp: 0x4d0900d5
Exception code: 0xc0000005
Fault offset: 0x0000000000097b09
Faulting process id: 0x534
Faulting application start time: 0x01cbaef34e2676be
Faulting application path: C:\Program Files\Cakewalk\SONAR X1 Producer\SONARPDR.exe
Faulting module path: C:\Program Files\Cakewalk\SONAR X1 Producer\SONARPDR.exe
Report Id: 98d69baf-1ae6-11e0-9eeb-0024e80d142f

I wonder if there is some plug-in that needed to be upgraded/activated within a time period expiring and has now lapsed that time and is creating a conflict within the software. I think I stated on another thread that I noticed after one of the crashes today that Session Drummer 2 had disappeared but 3 was still there. In the end, I still get a similar crash Popup window when launching a certian project and get knocked all the way out of X1 consistantly.

Actually, in 8.5 or X1, there are 4 options, yes, yes to all, no to all, cancel.
 
Yes allows you to load one plug in at a time until the program fails which will lead you to know where the problem resides.

Thanks Jre-
 I did delete some busses that were accidentilly created about the time this started.  Gonna fiddle with that idea for awhile and see what I can do or come up with.

OK, got around to adding buses to a project this morning, even added pro channel across the bus.  That project opens fine.  I actually tried to duplicate everything I had done on a different take of the same song.  Yet, for some reason, no effect.  I can't duplicate it.

I was able to recover SOME of the tracks by importing them in to a new project from the fouled up project that was really important.  For some reason, the drum overhead tracks aren't even in the folder???  It was something akin to recovering a lost wallet without the money, drivers license or credit cards in it.  Oh well at least I got the lint back.

Looking on to a refund today.  I'll probably purchase x1 again, after everyone else works the bugs out for Cakewalk.

Windows reported my memory fine, just don't understand why adding and playing around with both multibands would shut it down. Cant even load project at all safe mode or other wise, it was fine until I did that

Since it was initially done in X1 cant go back to 8.5.3 to save it. Grrrrrrrrrrrrrr not a happy bunny right now

I just don't understand why there are all these issues with X1, what the hell are Cakewalk playing at. Even earlier releases of Sonar version had bugs but you could live with most or work around them, X1 is just unreliable to use as a main DAW at this moment in time.

I realize this is a long-dead thread, but I've started experiencing what I think is the same issue lately. If I open a project immediately after launching Sonar I get an 0xc0000005 error. Interestingly, if I let Sonar sit for a minute or two and then open a project it's fine.

I ran a memory check and my RAM's good. I even reinstalled Windows recently and that didn't have any effect on it.

Has anybody else had this problem and resolved it without some sort of workaround? I'd rather get down to the root of the issue. Any insight is greatly appreciated.

benjaminfrog


I think I found the culprit, though I wish I knew more, specifically, about what was causing the issue.
 
I recently purchased a 2TB WD My Passport external hard drive. If it's plugged in when I launch Sonar and I open up a project right away, it crashes 99% of the time. If I unplug it before launching Sonar, I can open a project immediately without issue.

Additionally, I've discovered that having it plugged in when I turn my computer on, significantly slows down my boot time.

Anyone have thoughts about why this might be happening? I have other external drives and they've never caused either of these issues.

Thanks.

I just got a 3TB drive for holding samples, and figured hey, I'll just plug it in, copy over my samples and rock on! 
 
So I plug it in and Windows shows 740GB or something like that. Ooops. I turned to the troubleshooting section of the Seagate manual, and it says "if you're getting the '740GB' error message..."

This then meant a trip to the Intel web site, where it queried my computer and said "you need stuff, click here." Long story short: Nothing really worked the way Seagate said it would, and the Intel site was like a Chinese puzzle, but somehow it ended up working. You may need a driver update too...or not...who knows.