Sonar X1 Prod. EX. Crashing on loading a large project

This is the second time this has happened to me: I get near completion on a large symphonic movie cue (20-30 samples loaded / 2-3 minute cue) and I can no longer load the project because Sonar crashes.  After googling this problem, I was actually surprised to find out about the "Safe Mode" method of loading a project.  

So, I loaded said project in safe mode, and OK'd one track at a time until Sonar crashed - it was on something similar to "LRS track bus GroovePlayer" (I don't remember adding anything with this label to my project).  So, next time, I load the same project in safe mode and choose "NO" for loading this item and Sonar *still* crashes after my choice. 

Any further ideas?  Since this happened last time on a large project, I've gotten into the habit of keeping 50+ backup saves.  So, I've also tried renaming one of the earlier saves to see if it will load and the exact same thing happens.  


Current setup:
Windows 7 x64 on an i7 920 with 6GB of Ram, std IDE drives
Multiple sample libraries (EWSO Gold, Komplete7, Omnisphere,EW Pianos, RA, Stormdrum, MOR, etc)
Tascam FW-1884 interface


I've tried loading the project with "No to All" under safe load, and it will load.  Does this mean, worst case scenario, I have to reload each sample library one at a time, then copy/past the midi data to the new tracks?

When you load in safe mode, say no to everything starting with that 1st track that crashed SONAR. If it loads, then startup again and say no to the 1st track that crashed SONAR and then say no to the 2nd track you said crashed SONAR. Then say yes to the next one and so on, and see if SONAR crashes upon loading another track.

The point is when ever a track crashes SONAR, next time say no to that track.

Your problem sounds like a plug in of some sort is causing the crash.
Does the tracks you say yes to and then see SONAR crash, have a plug in on them?

Try to isolate the tracks that are starting SONAR to crash.
 
My understanding is that if this crashing is because you have run out of RAM, SONAR will give an error message that says that. Do you get such a message?

Hope this helps.

I've seen the message before, "Memory is running low, do you really want to continue loading."  I've always continued and been able to work fine.  However, that isn't happening in this case.  I've been working on this cue for several days, adding more and more each day (music and samples).  Then, today, I loaded Sonar and chose to open last project, as I always do, and it started crashing.

It always crashes right after the grooveplayer loading notice.  I will have more time tomorrow to expand my attempts to load some of the samples and skip the rest, but, It still is crashing after I say "NO" to the file that causes the crash.

I too have had projects corrupt on me, which is what it sounds like is happening with your project.  In the three times this has happened it was a plugin that was working fine for weeks and then one day crashes Sonar.  To fix it I had to load my project in safemode without any plugins whatsoever and redo my entire mix.

More recently Sonar displayed the "RESET BUTTON" error and would no longer load my project without crashing.  Needless to say I was not happy, but I had saved a different version just before which loaded without error and continues to work to this day.

I too keep 50+ backup versions as it seems to be necessary to not loose work.

Excellent suggestions, I'll give them a try this evening.  The project will load...up to the metronome file, even if I choose "no" to loading it.  So, I'm going to try "no to all" right before the culprit, then maybe I only have to recreate half of my orchestration.

I'll also leave out the huge files.... (Steinway D from Pianos Gold is absolutely huge!).  Maybe that will make a difference and I'll grab 24gb of ram then.

Ok, just about cried again.  After hitting 'freeze' on the first track available, Sonar crashed with a report about something like 'k-lite codec.....' so I thought I was finished.  But, I tried again, and started freezing completely different tracks and it worked.  I had task manager open, and without the piano sample loaded, I was at 58% ram.  As I started freezing tracks, I watched it reduce to 51%.

Now, to get to work rebuilding the cue.

I believe it did - at least once or twice.  I keep the task manager on a 2nd monitor now and watch available memory on large projects. 

I've read that my motherboard can support up to 24gb of ram, so I'm planning on buying the max (up from 6gb) as soon as I can.  That should help a bit.