Not really a big deal but thought I'd mention it. I was noodling around with my new Oxygen 25 (first time using it) and Dim Pro. I was testing out all the different sounds for about an hour just having a great ole time. I went into the Expansion Pack 1 folder > Dimensions. I got to one called Sing for the Cows and it made a loud crackling noise after I keyed a few notes. It did that a couple of times and then seemed to be fine. I switched to another sound (Mysterious Side or something... I forget) and it stop producing sound and X2 became unresponsive. I had to close it. Opened it back up again and everything is running smoothly. Is it possible that because I was going through all those patches it was keeping them in the RAM somehow and I maxed it out? I seem to recall that being talked about on here before. Like I said no biggie. BTW it didn't give me the crash reporter. Maybe it wasn't a full crash. Cheers.

ive just tried those 2 pre sets, work fine here

@Chregg... Yeah, they're working fine here now too. I'm really thinking that I just maxed out my RAM. Can someone confirm that when moving around patches the old ones stayed loaded? That would make sense. I've got 16 GB and I had probably gone through almost 100 sounds.

If you're unsure, you can always leave Task Manager open next time around and track how much memory SONAR is using in the Processes tab.
 

Good idea. I installed the ASUS monitoring software but it sucked and the darned thing refuses to uninstall. Gotta find another resource monitor. This system is a powerhouse though so I normally don't have to worry about this kind of thing with the type of stuff I do. That may change though now that I'm in the worderful world of soft synths.

Right. Press ctrl alt del and the TASK MANAGER can be chosen. 

What OS are you on BEEPSTER. With that amount of RAM it probably is W7 64 bit. Do you have all patches?

Win7 Pro 64 bit. Windows was up to date about a month or so ago but the system was working fine and a round of updates from that time seemed to be causing people grief so I've let the updates slide. Haven't seen any issues reported on here lately though so maybe it's safe to allow Windows to do it's think. I am indeed familiar with the task manager but just closing Sonar fixed it. Still I figured I'd let the forum know and see what you guys said. I gotta tell ya I've been passively looking for problems with X2 and I'm really not finding much. I'll also say that any crashes I had with X1 would take a lot longer to resolve. X2 seems to just move on from them very quickly. With this one I just hit the close button and immediately the Save/Close program warning came up, I clicked close and it closed instantly and I was able to restart Sonar seconds after the fact. No hanging or lagging so even when failing X2 is better IMO. Cheers.

I used to get a crash if I browsed too many patches in Dim Pro. I've probably had crashes for the same reason with Zeta and Rapture as well in the past.
The new PC with 8 GB of ram has not crashed (so far) due to patch browsing....actually, thinking about it there was a crash the other day when the browser from Dim Pro disappeared - I think Sonar realised something was odd and bailed. That's not quite the same thing though.

I just live for the moments when everything runs smoothly and I'm hearing groovy sounds from my monitors .

Grum.

I've been having a lot of fun going through all the synths. This is some very powerful shiz.

DimPro and Rapture have standalone modes like Guitar Rig, so you do not have to run them in SONAR just to play around. The exes are in the Vstplugins folder for each synth. Any of the other CW or other VSTis without a standalone hosts can use http://www.hermannseib.com/english/savihost.htm to run standalone.