Sonar X2 crashes when exporting audio in both Win 7 and Win 8

I wanted to import some older sound files (stereo) so I could run them through Ozone5 and then export them back out.  However, every time I imported one there was a sound artifact added to the front of the track and when I tried export the file, Sonar would crash with Exception code c0000005. 
 
I had never tried this before so I started eliminating things.  It was not Ozone5 as I tried exporting plain, no added Effects and it still crashed.  By accident I noticed the Pro Channel was enabled and the Concrete Limiter was also enabled.  I disabled the Pro Channel and the sound artifact added to the front of the track was gone as was the crashes. 
 
The Pro Channel is not causing any problems within a project (I use it all the time), just for some reason with this particular function of importing/exporting.
 
EDIT/UPDATE:  I changed the subject since Pro Channel is not causing the crashes. 

Quick fix is installed.  I did a dump report to Cakewalk, along with my e-mail address on one of the crashes.  So they should have all the info on what happened. 

That case its not the OS or Sonar. It is the setup you have with Win 7, drivers or plugins or missing latest update or antivirus probably. Clean install is the way to go though...

This is a new install  I did a complete, clean, reinstall less than two weeks ago.  I use the Microsoft Security Essentials.  It has not caused any problems in the last several years I've used it. 

The Pro Channel does not cause any problems with other projects.  Just this one import/export function - importing a 16bit/44.1 standard stereo wav file (for the purpose of adding Ozone 5) and then exporting it as a standard 16bit/44.1 wav file.  Its not Ozone5 as it does it without any added effect if the Pro Channel is enabled. 

I'm going to reinstall Sonar and see what happens.  Nothing else that I have installed (and not that much) would affect this.  BTW, I'm a computer tech and do computer support (the reason I have Win 8 installed as I have clients with Win 8).

Noel, I used one of the built in projects for this.  It was a "new" project in that I had never tried this particular function before import/export standard 16bit/44.1 stereo wav files.  

I filled out the crash report and sent that with the info and my e-mail address after one of the crashes.  I've never gotten any response from Cakewalk from the crash report. 

I suspect the problem may be just a bad install of Sonar as I did a complete, clean (reformat hard drive) install of Win 7 64bit less than two weeks ago.  I did a complete install of Sonar X2, including addons such as Concrete Limiter and other 3rd party software such as Ozone 5.   As I can't duplicate the problem in Win 8, that leads me to believe that a uninstall (restart PC) and then reinstall should correct the problem.

I'm a computer tech and keep a "very clean" PC.  Minimal in the Notification area (used to be Systray) and in startup.
 
I wouldn't have marked this as solved until I do the reinstall and confirm its fixed.  It still could be some type of issue with Sonar and Win 7.

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.

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 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.

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. 

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

Jack, are you using Fast Bounce for your Export?

If so, try a real time bounce and see if it works

Thanks for sending in the bug report. This issue has been fixed. The crash actually only occurs if you happen to explicitly or implicitly select a silent area on the track before export, which is why you don't typically run into this issue.