Audio Engine suddenly stops for no apparent reason all the time on export

        Hi, everyone. It's been a long time since I've been on the forum. Let me give a shout out to Planetearth, Jimbo 88, and Large Style. Thanks, you guys, for helping me out in the past. As you can see from my signature, I now have a monster system which I recently built and am running SONAR Platinum. At present I have a project with basically a rock band setup (multiple vocals, three guitar tracks, bass, drums, B3 organ), which has about 25 different tracks. This really should not be taxing my system at all. I have been having a great deal of trouble with audio engine just simply cutting out, all the time, at unexpected times. I have started tracking the usual suspects, and made some progress. I can now get my project to play through without a problem, but I cannot export anything. I went into BIOS and deactivated hyperthreading, all enhanced power saving options, C-states, and other options which might be a culprit. I've gone into task scheduler and deleted every unnecessary program there. The ones I left I am pretty sure are not a problem. I tried to alter the audio buffers in ASIO and tried them from 16 all the way to 1024 without any effect. I tried altering my playback and record I/O buffer sizes as well, again without any effect. I've tried looking at computer events and aside from deleting Apple's Bonjour did not find anything else of note. I downloaded LatencyMon and checked the system with this app, but it could find nothing wrong. In fact my delays were never any more than 250 µs, both DPC and ISR.
        So now I am stuck. I am trying to export the individual tracks as wave files, but every time I try it, the audio engine suddenly cuts at various times, sometimes as little as a second, sometimes as long as a minute or two. I've yet to get one completed wav file out. I've tried looking at the Task Monitor and cannot see any unusual I/O problems occurring with the disk drives or the CPU. I don't know where to go with this problem now. I hope one of you guys out there could help out. Thanks in advance.

If "Fast Bounce" is not enabled on the export dialog, try enabling the feature.

have you tried unchecking 64 bit engine ?

 
As a test you might want to delete the VB3 tracks just to see if its something within that which may be causing a problem.
Use the Process and elimination formula.

When you say you had no sound in the files exported using fast bounce. Did you try "select none" found under edit  ( or CTRL/SHIFT/A )  i had the same issue from time to time when using "select all" and someone here advised to use select none and since then never had an issue with export. I always use the fast bounce. 
What are you exporting at, 44.1 or? 
 
You certainly sound like you've looked into every rabbit hole as far as background interference which can be common on an un optimized machine. Latency Monitor usually sorts that out. 250 is not ideal but within a safe area. But I've heard people talking about little spikes that don't get picked up. 
For me it's always been disable the internet adaptors and on laptops battery management. Video cards are another source of grief and most folks will disable the HDMI audio. 

I don't think he meant the preset 'none' as you will want a lot of the stuff that selecting it will deselect, FX, Automation etc etc, as you have found. I think he is referring to track selection, which is why CTRL/SHIFT/A was mentioned, as it will deselect all tracks and buss's, kind of sounds a bit funny having none selected, but . . .  that's how it is.

Sounds like a very frustrating problem.  But whenever I had the audio engine stop when rendering the entire project to a wav or mp3 file, (by using "Render as" in the dropdown menu) even though I get the audio engine stop message, Sonar actually continues on to render the whole project. 
And I agree with the previous comment about always selecting "None" before attempting to render.
Several times I had one clip or track selected, and it only rendered what was selected.  So I always click on "None" first.

        Thank you Matron, I see what you mean now. As I individually selected the choice myself, the result was the same. But now I know what you meant as it's another method of doing it. To Soens. I actually tried to do that, which is to drag the clip to the desktop and it wouldn't do it. I don't know why, but I'm sure it's something I'm not doing right. I'll work with it and see if I can figure that out. To Leee, what I am finding is that on the slow bounce, whenever the audio engine cuts off, the rendering stops and I am asked if I want to save the partial file up to that point, which I don't. On fast bounce, I never know what happens as SONAR does complete the rendition regardless, as you have said (although I never see an audio engine cut out popup), but I suspect that if there was an audio engine cut out, the resulting file is blank without any sound. That is what happened to me, I believe.
        I think that the measures I have taken up to this point have solved my problem in respect to being able to do a fast bounce without problems, as my fast bounce problems happened before I tried the measures in my original post. At this point, things are better, but still I shouldn't have a problem with an audible bounce either. I didn't have any problem with it before I built this particular machine. To Cactus Music, and all you guys, thanks again, now I know to select "none" in the render box. Hopefully in the future, I'll figure the rest of this problem out.

As I've recently learned "fast bounce" is a lot more stable, as it does not require the instruments to be playing and active during the bounce.  And also the term "fast bounce" can be deceiving, because it sometimes takes LONGER than a regular bounce.  It should be more accurately be labeled "variable speed bounce" because it goes as fast (or as slow) as your system can handle.  By using the normal bounce, you're actually forcing Sonar to bounce at a fixed speed, which can cause memory and ram issues.  

I always thought "fast bounce" used more system resources and could create a wav or mp3 file with errors.
But as I said, someone set me straight about this, and with the rare exception of certain synths, the fast bounce is much more stable and reliable. Just make sure to select "None" which unselects any specific tracks or clips.