Just had my first major crash with X2... report crashes while browsing Dim Pro here

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.

@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.

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.

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've been having a lot of fun going through all the synths. This is some very powerful shiz.

It just happened again except Sonar didn't freeze this time. I just stopped getting sound. The Dim Pro track's volume meter was maxing out and unalterable Checked the task manager and I had WAY more than enough RAM. I tried removing the instance and reinserting it but no dice. I had to shut down Sonar and reopen it to get a signal again. So something weird is happening. This time I hadn't gone through nearly as many sounds. Oh well. If it gets in my way I'll get a hold of tech support... and thanks, scook. If I'm gonna just mess around I'll try it in standalone.

@stevec... How are, ya. I'll mess with it more another day and make detailed notes to send to support. I don't know enough to do any in depth troubleshooting for something like this and I don't want to make you guys chase your tails for something that really isn't a showstopper. It might just be a bug in X2 or the M-Audio thingy is screwing something up. It's not holding me back or anything at the moment. The only real problem I could see arising from this for myself is if the issue persists after closing and reopening a project. For the synth heavy folks I could see it being a major issue. Come to think of it I haven't done that quickfix update so maybe that has something to do with it. Cheers.

@sharke... X2? If so did this happen in X1 as well? Perhaps this thread should be a place to pool our reports of Dim Pro crashes while browsing.