What CJ say's is what I would do. 
Open the Project
Delete all but the part you want and perform a "save As" to a Normal-CWP file,,,
direct this to a new folder and use "copy audio with project" 
If you save it into the same original folder it won't delete the other audio files, just tags them. 
 
Don't use bundles, there are post after post of issues with bundles, they are hit and miss for dependability. Only use they seem have is stripping away audio snap. Use a zip file if your wishing to compact the file, Bun is not for compressing. It's original selling feature is only the fact you have one little icon instead of a folder with an icon (CWP) and the audio folder inside. 

gbowling, there must be a reason that what Kalle suggests doesn't work. And as CJ suggest, it's very simple.
 
However, try this;
Split the clips before and after the 3 min part. Then select all the clips in the 3 min part, right click and select "Apply Trimming"
 
Now once that is done, do as Kalle and CJ suggest, 'Save As' to a different name.
 
If that doesn't work, I suggest you give us the exact steps you are taking. We can go over them and figure this out.
 
Let us know

Cactus Music
 
Don't use bundles, there are post after post of issues with bundles, they are hit and miss for dependability. Only use they seem have is stripping away audio snap. Use a zip file if your wishing to compact the file, Bun is not for compressing. It's original selling feature is only the fact you have one little icon instead of a folder with an icon (CWP) and the audio folder inside. 

The bun file was used back in the day when CW stored ALL audio in one folder, it's default folder. You would then use bun files to save all associated files for the .wrk file and have it all in one place. IOW, it saved you from having to find all associated audio files with your .wrk (project), then you could transfer that .wrk file (project) to another computer or person.
 
You can still use bun files. Just make sure that when you create it, that you can open it back up before you delete anything.

The step that is important when you use CWP files, is to do the "save as" to a new location! 
If you just do a save as and re name, it will still use the original audio folder. it's still associated with that audio folder. Saving to a new location will only copy the 3 minutes in the new audio folder.
 
Sure a bun file should strip this away but with so many people finding them corrupted for no explained reason, why use them at all.. 
 
They seem to be a left over from the days before we had the "per Project' option. 

Aside from the occasional report on the forum, do you have an idea of what the failure rate is? It would seem a little fear mongering without a handle on the figures. Project files get corrupted too with no explanation. Zip files get corrupted with no explanation. Rather then suggesting to avoid using cwb files entirely, a better approach may be to suggest verifying the bundle after creation.

scook
Aside from the occasional report on the forum, do you have an idea of what the failure rate is? It would seem a little fear mongering without a handle on the figures. Project files get corrupted too with no explanation. Zip files get corrupted with no explanation. Rather then suggesting to avoid using cwb files entirely, a better approach may be to suggest verifying the bundle after creation.

I asked in another thread whether anyone had tested a bun file immediately after saving to see if it opened or not. If it opened correctly, that would indicate the BUN process is fine but the corruption happens after the fact due to other factors. However, I saw no responses.
 
I decompress important zip files after compressing just to make sure everything was compressed properly. I have had instances where everything was okay when I tested it, but the file was corrupted when I tried to send it over the net or open it a few years later. I suspect something similar could happen with bun files.

Craig, I haven't had the occasion where "after" I tested a bun file, that at a later time it wouldn't open.

To OP, Cactus makes an very important point. You HAVE to save the new file to a DIFFERENT location for what is suggested to work properly.

Grem

To OP, Cactus makes an very important point. You HAVE to save the new file to a DIFFERENT location for what is suggested to work properly.

 
 "Per Project Audio Folder" method sort of includes that, doesn't it?  If you change the name of the project and use Per Project Folder there's no other option than to save to a new location, ie. a new folder. 

Kalle Rantaaho
 
 "Per Project Audio Folder" method sort of includes that, doesn't it?  If you change the name of the project and use Per Project Folder there's no other option than to save to a new location, ie. a new folder. 

I thought so too. But upon looking into this, I remembered that when you "Save As" you have to specify or create a new folder. If not it will dump into the default "Global Audio Folder" and that is set in Preferanc/File/Audio Data.
 
So to OP, be sure that when you use "Save As' to also choose the location of where you want the new project to be created. I would suggest creating a new folder with the name of folder being the same as the song.

Sure it might only be 1 in a 100 bun files that go south but I'd hate to be that person. It will never happen to most of us because we save and double save our work. 
Given a choice file formats,  would you use the one that always works or one that has a small history of failure. 
Besides if a CWP files goes south you still have your audio. A smart person would also have saved the project as a mid. file too. 
I too asked if the "Burnt Bun" issue was caused upon creation and so far nobody seems to know anything. I find it hard to swallow that any file format becomes corrupt if saved to a normal hard drive. Over the internet of course that's different. These people have all saved their work as a bundle on a hard drive, CD/DVD ROM or USB stick only to find they cannot open it latter down the road or at their friends house. Why? 
It is most likely that it is a certain situation within a Sonar project that corrupts the file and it would be nice if someone figured that out so it could be avoided. We know about Audio snap that's all. 
For now I will continue to warn people.