Now this is getting really, really annoying. Recently I find myself wasting some much time on troubleshooting troubles I never had before X3 came around.
 
And now again: new project, created in X3, only a few synth tracks plus a vocal line, which was modified with Melodyne and frozen, then saved. Coming back to open the project I just get crashes, unfortunately all auto-saved copies behave likewise!! But the version saved manually one hour earlier loads perfectly. The only differences really between the crashing version and the working earlier one is that a couple of clips were shifted by a few ticks and then one track was frozen.
 
Sonar again somehow corrupted our work.
 
I had the same problem in a bigger project just 3 weeks ago. Reported problem, got re-directed to support, whom I contacted but they never got back to me.
 
Now, I assume there'll be plenty of posts saying "go fix your system", but it ain't broken! I did soooo many checks in the recent 2 weeks (drivers, updates for 3rd party software, memory, disk integrity, power options, viruses, malware, ... the list goes on). I can't think of anything else to check. And now that it has happened in an extremely simple project, I'm even more convinced that it can only be X3 that's causing this!
 
I think I just forget about X3 until somebody from Cakewalk can tell what is wrong with those projects and why they work one day and are broken when coming back to continue working ...
 
 
<<for cakewalk reference: CWBRN-21497>>
 
Edit: opening the project in SAFE mode, also causes a crash! so it's none of the synths (which would be FabFilter) or plugs (which would be WAVES mostly)

I got one of those Corrupted Projects also..right after updating to X3c and opening a X3b Project, Doing some work, saving it, and then trying to open that again...it crashes the program....
 
But in today's effort to make my system tweaks complete...I went into the bios just to check on things....And I found CPU Speed step was enabled....Seeing as this may have been causing CPU Spikes to occur or interupts...could it be the culpret in corrupting data when being saved?
 
So perhaps this could be part of the issues some overlook in setup or tweaking?...
 
Also there are other things that may be causing hickups in the os...that may be bound to bios settings....So it would be prudent to double check , make a list,...and see what happens when....
 
Good luck.
 
Sir Les
 
 

64-bit double precision engine disabled? There are some issues with it in X3c, though I'm not sure if any of them can cause a crash.
 
 

FreeFlyBertl
Now this is getting really, really annoying. Recently I find myself wasting some much time on troubleshooting troubles I never had before X3 came around.
 
And now again: new project, created in X3, only a few synth tracks plus a vocal line, which was modified with Melodyne and frozen, then saved. Coming back to open the project I just get crashes, unfortunately all auto-saved copies behave likewise!! But the version saved manually one hour earlier loads perfectly. The only differences really between the crashing version and the working earlier one is that a couple of clips were shifted by a few ticks and then one track was frozen.
 
Sonar again somehow corrupted our work.
 
I had the same problem in a bigger project just 3 weeks ago. Reported problem, got re-directed to support, whom I contacted but they never got back to me.
 
Now, I assume there'll be plenty of posts saying "go fix your system", but it ain't broken! I did soooo many checks in the recent 2 weeks (drivers, updates for 3rd party software, memory, disk integrity, power options, viruses, malware, ... the list goes on). I can't think of anything else to check. And now that it has happened in an extremely simple project, I'm even more convinced that it can only be X3 that's causing this!
 
I think I just forget about X3 until somebody from Cakewalk can tell what is wrong with those projects and why they work one day and are broken when coming back to continue working ...
 
 
<<for cakewalk reference: CWBRN-21497>>
 
Edit: opening the project in SAFE mode, also causes a crash! so it's none of the synths (which would be FabFilter) or plugs (which would be WAVES mostly)

Could you please list all of the plugins this failing project has in it?  I want to try do do some digging into it.  Might be a wild goose chase, but who knows.  Worth a shot anyways.
 
Also, your signature lists X3b.  Have you tried the X3c update?  I looked through the fixes for X3c, and they apparently did do something to address compatibility issues with Waves plugins.
 
Here is the link to what they fixed in the X3c update:
 
http://cakewalk.com/Support/kb/reader.aspx/2007013331
 
 
Thanks, 
 
Bob Bone
 
 
 

Sir Les
But in today's effort to make my system tweaks complete...I went into the bios just to check on things....And I found CPU Speed step was enabled....Seeing as this may have been causing CPU Spikes to occur or interupts...could it be the culpret in corrupting data when being saved?
 
So perhaps this could be part of the issues some overlook in setup or tweaking?...
 
Also there are other things that may be causing hickups in the os...that may be bound to bios settings....So it would be prudent to double check , make a list,...and see what happens when....
 

Yeah, the BIOS is about the last thing that I haven't gone into ... and I'd rather not go there ...
 
From my specs you can see that my system is overclocked, but that was done by a professional about a year ago and tuned to a save level. Worked fine so far, never caused hickups and hence I'm reluctant to go fiddle with BIOS knobs I'm not familiar with, especially as it's just Sonar corrupting its own files, but no other application is behaving funny ...

64-bit double precision engine is disabled
 
@Bob: it's X3c (just updated my sig) - thanks for trying to help, but I assume someone will have to look at the mini-dumps and shed light on this ...
anyway, plugs in that project are only a few (VSTi: true piano, fab filter one, 2 instances of fab filter twin 2; VST: FF Pro-G, FF Pro-Q, WAVES Puig EQ, Amphex Aural, plus a few more in archived tracks) - but as I said it also crashes with all plugs disabled in SAFE mode.
 
The content of the project is not so relevant. It's just a scratch track of a vocal on top of a rough synth line ... but if I continue with X3c when is the next time this corruption problem will happen?
 
One more thing: I actually pulled in a template for drums (8 audio tracks plus 1 MIDI) to record some beats via the e-drums between the last functional saved version and the now crashing project, but I think I have done that 100 times with the same template in X2a ... I wonder if that is causing issues now - X2 templates pulled into X3??? Yet the template is dead simple, not even plugs that come with it, just I/O routing to the drums bus ...
 
bummer

Hi There -
I was just looking at your Windows 7 thread in software, and wondering if your backup changes may have reintroduced something.  If Sonar were looking for a saved copy through a backup app and now the app is disabled . . . . . .
 
Just thinkng.  Good Luck
 
Brian

 
The first thing that I noticed was that you're overclocked.  Sonar has seemed to me at times (and to others as well from what I read here) quite demanding of any system, perhaps because of the level at which Sonar interacts with it.  Any bug at a very low level (doesn't have to be in Sonar) could cause all sorts of corruption issues and overclocking just might bring you that much closer to trouble.
 
I'm not saying that your oc'ing is the source of anything, but it's something I'd disable as part of trying to find the cause.  I don't see the need for oc'ing in a DAW anyway.
 
 
 

OK - thanks for clarifying.  Perhaps it is something to do with the X3c update?  Have you tried rolling back to X3b?
 
I wish I was more help - maybe some more coffee, or more pain meds, would help.  I'll get right on that. :)
 
Bob Bone
 

When Sonar crashes with a corrupted project does it send a report to Cakewalk? Just curious....