Did the memory hack already and got the same results.

I did monitor VMS on the task manager and it never exceeded more that 997k of memory utilization, so that led me to believe that it wasn't a memory issue.

Is the memory issue due to the number of clips or lenght of the project? I worked on another project that had about 34 clips lasting about 2:15 and it didnt have the crashing issue I am having with this one.

Ok, try Vegas Pro 10 trial and see if the bug is fixed there. If it is, then maybe VMS11 or VMS10.x (if there's a free update coming) will fix the issue.

Out of curiosity, I just put 376 1920x1080i AVCHD clips, totaling almost 10 GB, on the VMS 10 HD Platinum time line with out a problem, other than it was pretty sluggish while it built the audio peaks. It even appeared to be stuck at one point and Win 7 put the "(Not responding)" message in the title bar after the VMS program name. But then it continued building the rest of the peaks and the "Not Responding" message went away. The total length of these clips was 1 hr. 20 minutes.

To get it over the 2:15 length you were using, I added a few hundred more clips at the end of the first 376, but added them about 100 at a time, so the peak building went faster (very fast in fact - no sluggishness at all). VMS added these additional clips without incident. The additional clips made the total length 2:20. I did a couple quick edits and played the time line starting from a couple different spots -- still no problems.

I started a render using Sony AVC 1920x1080 AVCHD. I canceled the render after 10-15 seconds because I didn't really want the rendered file. I just wanted to make sure it would at least start rendering without crashing.

So it does appear to be possible to add at least 600 or 700 clips with over 2 hours total length.

I have not applied the memory hack to VMS 10. I needed it on VMS 9 because AVCHD renders would crash without it, but have not needed it on VMS 10.

>>>My specs are: Win 7 64bit, i7-920, 12Gb RAM, VMS 10, Canon HF11.<<<

Mine are similar: Win 7 64bit, i7-920, 6 GB RAM, VMS 10 HD Platinum, some clips were from my Sony XR500; others were from my previous camcorder, a Sony SR11. Both record at 1920x1080i AVCHD.

OK, I found what the issue is, and it is not related to the number of AVCHD clips I have as part of a project. I added over 4 hours of video with 225 plus clips and the program didn’t hiccup until I added TWO files.

By trial and error, I isolated the only two clips that were previously edited with Pixela, the software that came with my Canon camera. I only removed maybe a second out of each clip towards the end, and it looks like VMS doesn’t like the modified AVCHD file. The interesting thing is that I can play both files using Windows Media Player on my PC, and the Playstation 3 plays them fine via my Twonky server.

But the moment I insert one of them into the timeline, VMS goes kaput.

Is there something I can do to determine what is wrong with these files? I don’t have the original anymore and don’t want to delete them from my project.

You will never find what exactly is wrong. It might be a Vegas bug not implementing AVCHD perfectly, or it might be Pixela screwing up the format. Always use the files out of your camera directly on Vegas.

You can try opening up a new project and seeing if you can drag the clip to the timeline and then chop a few frames off the beginning or end and then re-render.
If that doesn't work, try a free video editing program that can edit AVCHD and do the same. One way or another, I would imagine that you will be able to get the file into Vegas for use in your larger project.