Hi
 
There are a lot of positive threads about a great X3b version, yet I don't seem to get the same stability I used to have with X2a (same system, just x3b installed).
 
I wonder if anybody else is in the same boat?
 
Yesterday I had 5 crashes in 4 hrs (!!!): one after 3 minutes when just working heavily on the jog and Cursors on the VS-700, then none for 3 hours, then 4 in 30 minutes (@ save after comping, @ clone track, @ changing audio card settings i.e. increasing ASIO buffer, @ disabling all FX globally from button in navigation bar right after reloading project) ...
 
None of the crashes lost me any work due to auto-save, neither required a reboot; however, still pretty "wild" and I'm glad this was a lonesome editing session ... and no, my system is not the problem, I did have about 5 crashes in the entire past 9 months (since using X2a and staying away from 32bit plugs)
 
Now I just had another crash: finished comping vocals, wanted to clone and archive track (in case I have to go back) before I delete muted clips ... but after cloing all my track labels were gone (???) so I tried UNDO and then Sonar left me handing there ...
 
 

You might want to try and reinstall X3 over your current X3 installation.  Perhaps some file is corrupted.  And/or try running scandisk for disk errors in files / sectors.  Then reinstall X3. Other than that it would be a mystery, X3 is pretty rock solid.

Has your computer been updated by Microsoft? Anything is possible.

Thanks for trying to help.
 
Further info ...

• No Microsoft updates (DAW is off the net, so no auto-updates)
• the project that I work with is using Kontakt 5 samples, which take about 3.4 GB RAM (out of 32 GB); K5 is updated to the latest availabe version
• X3b was the 2nd last installed program (additive drums came after)
• Audio drivers are same as before (were not reinstalled)

 

Sound Rehab, you might check with support and see what they can advise.
 
I'll say that when I'm getting repeated crashes in a project I'm usually bumping my head on the same issue repeatedly. If the issue can be identified, than the problem usually goes away.
 
For me, I'm not having any trouble with X3 (I know YMMV).
 
This is why I'm suggesting going to support to see if they can put their finger on it. Identifying the issue early could save you a lot of headaches.

Have you checked Reliability Monitor or Event Viewer to see what they report?

Sorry about that. Most users of X3 have reported vastly improved stability so this is likely some corner case. Have you submitted bug reports? Please list the CWBRN numbers and I can look at the crashes.
Some combination of workflow and hardware could be leading to these crashes but until I see the dumps I won't know. It could also be plugin related. Do you have any waves plugins in your project for example?
 

Just for experimentation's sake, do these crashes occur if you open a project in 'safe' mode, with no plugins loaded?
 
Many of the X2a and prior release crashes occur due to plugin issues, and within those, many of those are due to problems with some 32-bit plugins being loaded into projects in a 64-bit Sonar.  
 
BitBridge and some of the 32-bit plugins just do not seem to play nice together, and while folks have reported greater stability using 32-bit plugins with another bridging piece of software called JBridge, some 32-bit plugins can still fail in 64-bit Sonar.
 
IF this ends up being the culprit for you with X3b, then you might consider either swapping those 32-bit plugins out for 64-bit ones, or checking for 64-bit plugin availability for the ones you do have in 32-bit, or you could install a 32-bit version of X3b and use that one for projects that fail using 32-bit plugins in 64-bit Sonar, as 32-bit plugins will be more stable in a 32-bit Sonar.
 
Bob Bone
 

I'm probably not going to like the answer, but...
 
Does X3b have a syslog or debug function, with the ability to enable and use it locally?? I'm genuinely asking for input here. Although I'm not currently having trouble with X3, not having this function in X2 was 50% of the reason I cursed X2 daily. I could have saved myself considerable frustration had I had this ability to review a Syslog. It's so backward to think that Support can resolve the occasional intermittent crash at the time of the incident. Crash reports don't go to Support (correct me if I'm wrong), so those don't help the user, especially if the issue isn't Sonar.

brconflict
I'm going to bust a vein if the answer it No, but...
 
Does X3b have a syslog or debug function, with the ability to enable and use it locally?? I'm genuinely asking for input here. Although I'm not currently having trouble with X3, not having this function in X2 was 50% of the reason I cursed X2 daily. I could have saved myself considerable frustration had I had this ability to review a Syslog. It's so backward to think that Support can resolve the occasional intermittent crash at the time of the incident. Crash reports don't go to Support (correct me if I'm wrong), so those don't help the user, especially if the issue isn't Sonar.

Brian,
 
I can't tell you how much I would appreciate this! This is a key feature for any power user of professional software, especially if it interfaces with 3rd party plugins and hence makes almost every system unique in some respect.
 
@ gswitz: I do agree that these crashes (although they seem rather random) probably have one common reason (and a user-readable log file would be killer in that respect!) ...
 
@ noel and bob: I had these random crashes in heavy duty projects first with X2a until I eliminated (almost) all 32bit plugs (and labelled the remaining ones with 32bit) - so there's definitely nothing 32bit used here ... but I do suspect that it might be coming from either WAVES (only a few plugs involved here, mostly S1), FabFilter (heavily used) or Kontakt 5 (2 instances) ...
 
I'll try to narrow down the potential troublemakers and hopefully can provide more info soon. I also need to go searching for crash dumps as Sonar just hung / froze but did not seem to write anything ...