Can anybody replicate this?  I'm using Dorchester and whenever I try to bounce an audio clip that has clip automation, the engine stops working and won't restart until I close Sonar completely and reopen it.  Steps:
 
1) create an audio clip with some clip automation (e.g., volume envelopes)
2) Highlight the clip and select Clips > Bounce to Clips
 
The clip bounces in place, but I get the "engine stopped working" notification every time, and neither run/stop the audio engine or reset the audio/MIDI engine does anything. Sonar won't play back until I close and reopen Sonar.  If I try to close and open the project without exiting Sonar, I get the white screen/Sonar has stopped working blah blah blah.
 
Update: see Grandcross' advice below. It turns out that I had set my buffer size too high (1024) and forget to decrease it before bouncing to clips.  Doh.

I cannot replicate on my laptop. It works as it should here. Will check again when I am at my studio pc.

I have no problems with the Dorchester (Platinum) 64 bit version and clip bouncing with automation.
 

Sounds like some sort interoperability issue with the interface driver; SONAR closes ports and shuts down the engine while doing any offline audio processing which is probably what's triggering the problem. Are you sure it only affects clip automation? If so, what are you automating?
 
Do you still have X3, and is it also affected? If so, have you recently changed interfaces or updated drivers?  Do you have "Always Open All Devices" checked in Preferences > Audio Playback and Recording? You might try toggling that and/or other possibly relevant settings like Always Stream Audio Through FX to see if they're implicated.

Do you set the buffer size to big?
If your buffer size is too small ,Sonar is stopped by share the memory's debug.
You must check your surface that has audio's buffer size.
And then you try to wide of buffer.
It's a simple issue. 

Grandcross
Do you set the buffer size to big?
If your buffer size is too small ,Sonar is stopped by share the memory's debug.
You must check your surface that has audio's buffer size.
And then you try to wide of buffer.
It's a simple issue. 

Ya know, that might be the problem.  I was running my buffer at 1024 at the time.  I'll check it when I get home this evening.
 
edit: yup, that was it.  I turned it up because Melodyne was giving me some strange artifacts at smaller buffer sizes and forgot to decrease it.  Decreasing the buffer size to 512 or less solved it.  Good call, Grandcross!  Thanks to everybody else for checking it out.