Thanks for the help you guys.  Just Ad Aware.. but that was also running under X2.  I did see the first response about trying a new project with X3D which I will do tonight and post the results.  Who knows, X3d could fix the whole thing.  It just shocked me that the bounce took over 14 hours.  

> Just Ad Aware
 
Are you sure you aren't running any other antivirus software? Never install 2 at the same.
 
I would consider another antivirus product other than ad-aware, I don't want to start a large conversation on what antivirus to use (this thread will explode), so let me just point you to this thread:
http://forum.cakewalk.com/Microsoft-Securtiy-Essentials-m2947912.aspx
 
Anyways enough to go on for the moment, just the beginning I suspect...
Please can you go through this thread from the beginning and keep us updated to what you have done, plenty of points here to take heed. Thanks..

OMG... yes, *please* install the X3d patch and let us know. I personally would be significantly more than "shocked" on a 14 hour bounce.

I just bounce a Dim Pro track, (a Pad) about 1:54 in length and it took about 10 seconds, including drawing the waveform on the bounced track

Hopefully the X3d patch will help, but I've done plenty of Kontakt bounces using all versions of X3 without problems. Having never had to find a workaround, I don't really have any suggestions other than grasping at straws. Background processes, e.g. a hard drive scan from an anti-virus program, is indeed an option. But I was also wondering if you're running out of RAM or hard drive space. RAM would be particularly problematic because of the size of many Kontakt libraries. Also, both of these could be affect with no changes other than using X3 instead of X2 due to other factors, like programs that decide to take up more of a RAM footprint running concurrently with Sonar.
 
This is definitely not normal behavior so there should be a fix.

Hi Marc2109
 
I would check a few things coming from X2. Seems that the configuration file has not read your audio device correctly. At least the basic settings. Usually the new install will read the audio settings and use them since X2 is assumed to be working.
 
If X2 is still installed and running on your computer go and check the following areas that I have noted below and write them down so you can use them as a comparison reference between X2 & X3.
 
Go to preferences and pay attention to the following areas.
#1 : File>Audio Data

• >Bit Depth
• >Render Bit Depth

#2 : Audio>Driver Settings

• Audio Bit depth
• Sampling Rate

All the bit depths have to be correct before any of the rendering and bouncing can operate correctly. I have also removed most of the options in the bounce to drop down list because I only use three mix down procedures.
 
I don't know if this will do the trick for you but it can't hurt to check these settings. I use these a lot and they are one of the best time savers that digital audio has to offer.
 
Good luck Marc!
 

Try deleting or renaming your existing aud.ini file.
 
Sonar will build a new one the next time it's opened.
 
You can find it here:
 
C:\Users\Username\AppData\Roaming\Cakewalk\SONAR X3 Producer
 
AppData is a hidden folder so you will have to switch on the option to view hidden files in Windows Explorer

Some things to try:
-export to a different hard drive
-make sure realtime bounce isn't checked
-look at the performance tab in task manager and see if you are running low on memory during the bounce
-bouncing another project and see if it exhibits the same problem
-uncheck the option to include fx in the bounce and see if it speeds up. if so some plugin may be causing the issue
-check if the project contains audio snap.
-reset your audio configuration (preferences | configuration | reset configuration )

-look at the performance tab in task manager
 
or process explorer which is nicer rer :) #4...
 
Cheers...

Thanks for all the suggestions...I'm working through them.  Here are the results from tonight's tests:
 
I installed X3D, then created a 2 minutes Kontakt 5 Midi file in a new project.  It rendered in about 15 seconds.  I went back to the project i was working on with the 14 hour render, and picked a shorter midi track and started rendering it.  After 10 minutes it was about 5% done.  I made no audio settings changes from the new project to the old one.
 
I reset the audio configuration and tried again with the same results.
 
I tried a different project and a midi file about the same length as the troubled project track and it rendered in less that 30 seconds.
 
Help me think this through...if audio settings or the aud.ini file are the culprit, wouldn't i  have the slow render problem with both projects not just the old one?  I will still go back and make a careful comparison and delete the aud.ini.  
 
So far it looks like the problem is in the project itself.  Two different softsynth tracks with the same extremely slow render.  I still have over 80GB hd space on the drive.  The memory looks like its only taking about 25%.  If its an issue with this particular project, then I am in for an immense amount of work to fix it, since it contains over 30 softsynth tracks.
 
So trying to think ahead if this project can't be rendered to audio,  is there an easier way that writing down all the synths and patches used and copying the midi tracks into a new project and re-inserting all of the softsynths?  I bet I would still loose all my automation.