>Take a look at the plugins your project is using - (the project with the pops and crackles and snorts and such).  It sound like you may be using one or more plugins during recording that were really meant to be used POST-recording (for mixing and mastering).  Some plugins are very CPU-intensive, and others have 'look-ahead' processing, and those 2 kinds of plugins are intended for mixing/mastering............ 
 
Bob Bone

Bob, I just wanted to say these are very wise words, sometimes we need to state the obvious just so we don’t forget it. 

aixmusique
Everything is in the title. If you have no pb with X2A patched, what is your configuration?
Thanks a lot!

Other than a hiccup this weekend, my rig does well.  Nice and responsive, even without cutting edge hardware capability.
  I'm pretty sure mine was a plug in issue (32 bit in 64 bit host)

No dropouts, very few problems at all.
PC spec as per sig.

Overall, things are getting better for me. I think that by completely axing all the 32-bit, crappy plugins from my arsenal and slightly increasing my buffer size did the trick. Of all the 32-bit plugins that I still do use, they come from reputable companies and seems to be coded well. Hence, I try to stay away from any SynthEdit or Synthmaker plugins unless they're from Variety of Sound, for example; they seem OK.
 
Also, most everyone's sigs omit their motherboards, and in my opinion, this is one of the most critical components in one's system, more so than listing several HDD/SSD's and/or their collection of dot-matrix printers. Not all motherboards are created equal. For example, I had to part ways with my beloved Gigabyte mobo (GA-EP45-UD3P) simply because it had inherent latency issues and was no-way compatible with anything related to music production. And since I run a slightly older system, Intel Core2Duo Quad Q9550 and had no intention to upgrade all components to an i7, I bought a new-old stock P5Q mobo and it made a world of difference. So in my opinion, someone that reports a great system based on their signature that doesn't list the mobo may only paint half the picture.
 

jb101
Like John, I use internal sound card for windows, etc.

Jb101, what does this mean exactly?  Do you somehow only run Sonar on your interface while Windows defaults to the internal? Maybe I should try this as some Windows apps force my interface from 48kHz to 44.1kHz, which results in silence and annoyance. This occurs despite the Windows default set at 48kHz, 24-bit.

2:43AM yes I do the same. Enable your Realtek or whatever in Windows as your default device. In Sonar, exclude it and only select the sound card and drivers you want SONAR to use. Works well. I keep a small set of PC speakers tied to my built in card just for windows sounds and for media player etc.

2:43AM
 
Also, most everyone's sigs omit their motherboards, and in my opinion, this is one of the most critical components in one's system, more so than listing several HDD/SSD's and/or their collection of dot-matrix printers. Not all motherboards are created equal. For example, I had to part ways with my beloved Gigabyte mobo (GA-EP45-UD3P) simply because it had inherent latency issues and was no-way compatible with anything related to music production. And since I run a slightly older system, Intel Core2Duo Quad Q9550 and had no intention to upgrade all components to an i7, I bought a new-old stock P5Q mobo and it made a world of difference. So in my opinion, someone that reports a great system based on their signature that doesn't list the mobo may only paint half the picture.
 

Interesting...  I'm running a Q9300 on a P5N mobo, which results in a very stable SONAR install.  I do use the occasional 32bit plugin but am mostly 64bit.  Is all of this coincidence?  Perhaps not.
 
 

Dude Ivey
Since i started using 64bit plugins only i havent had a single problem with X-2a.

this has been my experience as well. 

I had loud audio clicks at the first time. Now i'd disabled "use Multi processing engine" in audio settings and now it works very fine without clicks.
 
Cheers, Tomas

2:43AM
Overall, things are getting better for me. I think that by completely axing all the 32-bit, crappy plugins from my arsenal and slightly increasing my buffer size did the trick. Of all the 32-bit plugins that I still do use, they come from reputable companies and seems to be coded well. Hence, I try to stay away from any SynthEdit or Synthmaker plugins unless they're from Variety of Sound, for example; they seem OK.
 
Also, most everyone's sigs omit their motherboards, and in my opinion, this is one of the most critical components in one's system, more so than listing several HDD/SSD's and/or their collection of dot-matrix printers. Not all motherboards are created equal. For example, I had to part ways with my beloved Gigabyte mobo (GA-EP45-UD3P) simply because it had inherent latency issues and was no-way compatible with anything related to music production. And since I run a slightly older system, Intel Core2Duo Quad Q9550 and had no intention to upgrade all components to an i7, I bought a new-old stock P5Q mobo and it made a world of difference. So in my opinion, someone that reports a great system based on their signature that doesn't list the mobo may only paint half the picture.
 

jb101
Like John, I use internal sound card for windows, etc.

Jb101, what does this mean exactly?  Do you somehow only run Sonar on your interface while Windows defaults to the internal? Maybe I should try this as some Windows apps force my interface from 48kHz to 44.1kHz, which results in silence and annoyance. This occurs despite the Windows default set at 48kHz, 24-bit.

What John has done, and I have done recently, is to set the default sound device for Windows playback and recording to the on-board sound chip on the motherboard, and to tell Sonar and stand-alone music applications (Dim Pro, Reaktor, etc.) to use our audio interfaces for their sound devices.  This allows things like Windows Media player to cheerfully run at the same time as Sonar is up, and just means keeping an extra set of speakers plugged into the normal speaker output of the computer.
 
I have only recently done this, and only did it because I wanted to be able to run a program called The Amazing Slow Downer at the same time as Sonar, and by separating the audio devices used, it allows that to happen without any problems with ASIO.
But it does work nicely, and I also have the opportunity to play YouTube videos while also playing along using stand-alone music apps, like some of my soft-synths, so I have elected to use this now as my default configuration.  It does work either way, but without the on-board sound in addition to the audio interface I would only run Sonar by itself.
 
The 48k to 44.1k thing can still occur, however, depending on what each piece of software does.  For example, by default, the Dim Pro stand-alone version on my system was switching my interface settings back to 44.1, which was really pissing me off, until I figured out I could change the default sample rate that Dim Pro used, and once set that issue went away.  That would have occurred no matter what I did with the on-board sound, so it is still something you may need to look into.
 
Bob Bone
 

As with others posting here, using 32 bit plugins will cause a crash once in a while.