I have an update.  Not a complete fix but I found that the Breverb2 was enabled in the Pro Channel and that was causing the short sound artifact to be added at the beginning of the track.  I now do not think Pro Channel is the issue.

Also, if I import audio, do whatever I want to do such as adding Ozone5, export it works OK.  However, if I then delete the audio in the track and then import another one, when I export the second one then Sonar will crash.  If, after importing, doing what I want to do, exporting and then closing the project, then open a new project it will work OK.

Please send us the crash dump via the problem reporter. If you choose to be notified you will get a tracking number. List the CWBRN number here.

I sent a crash dump, along with the description of what happened and my e-mail but I never got a response.
 
As this is repeatable, I'll cause another crash and send another report.

I created and generated the crash report.  CWBRN-13706

I was able to recreate the exact same problems on Windows 8 this morning.

I had a crash and sent the report.  CWBRN13760.

Both issues that I have on Win 7 are also on Win 8.  (1) the crashes.  (2) Audio artifact added to start of track if Breverb2 is enabled in the Pro Channel.

firebird: is it possible that there are no updated chipset drivers ?

No, not the issue.  I have the latest Intel motherboard chipset drivers.  In fact all drivers for both Win 7 and Win 8 are up to date. Both Win 7 and Win 8 have both been completely reinstalled (clean installs) within the last two weeks.  All drivers installed were the latest for Win 7 and/or Win 8 as applicable (I'm a PC Tech). 

This problem would probably never occur for most and probably wasn't considered in Sonar's program testing.  If I just wanted to import a wav file, do whatever and export it, the crash will never happen.   However, as I had 10 songs from a CD project that I wanted to run through Ozone 5 and after a couple of import/exports, Sonar will crash.  I don't have the original project files as this particular CD project was done on a Fostex VF160 hard drive recorder and mixed down from the recorder to wav files on the PC.   I had to do it with the mixdown wav files. 

The scenario.  I can import to an audio track in an existing project or an audio track on a new project - it makes no difference.  I import a song (standard 16bit 44.1Khz stereo wav file) into the track. I don't have to do anything to it, just export it (for testing).  Then delete the audio in the track and then import a new audio file to the same track, do whatever or nothing and then export it.  The crash can happen at any point, sometimes I've had it happen on the second export, sometimes it will happen on the third or fourth. 

If you are using the full version of breverb it should autoupdate to the latest version or go to their site.

I'm wondering what cakewalks strategy is here in updating bundled overloud products for bug fixes.

does it happen when you drag the audio to/from the browser or just with the import/export file commands?

I'm just using the version of Breverb2 that was supplied with X2 Producer.  

There is no problem importing.  Just when exporting after using the same track for import/export "x" number of times.