Vegas kept crashing from 'minor' edits. Felt hopeless. Until I checked the Knowledge base link. Made my Vegas pro 11 compatible with Win 7 and poof, problem solved.
Thought it might help someone struggling as I did.
Thanks for the replies. I was hoping that by changing my compatibility setting to Windows 7 that it would clear up some issues I'm having.
I recently switched over from XP32bit to Win&64bit. Everything went fine until I started editing and I hate to say it but Vegas 9.0e actually edited better on my old XP machine! In fact I can make reliably make Vegas crash now by simple doing the following:
Select a clip on my timeline (granted its a long timeline with lots of clips but nothing not fully supported, no fx or transitions of any kind) and quickly split it in several places randomly. Then just as quickly hit Ctrl-Z several times to undo those and CRASH! This certainly wouldn't have been the case on my XP system.
The ironic thing is that I should have a much more powerful system now. Running Win7Pro with 32gb of RAM with a brand new Nvidia Quadro 4000 card. This is all inside my HPxw8600 workstation with dual quad 3.2mhz processors.
This is all on a new HD with a fresh install and very minimum of software installed. I won't even take email on this machine. I was really hoping the compatibility setting would help.
Compatibility mode has had mixed success; I tried it and it made no difference. In my case, my problems had nothing to do with any third party FX, they were simply routine editing tasks that I've done uncounted numbers of times in earlier versions of Vegas.
I'm glad to hear that this has been helpful in your situation.
I think running VP11 in compatibility mode only helps with a subset of people's problems. Specifically, if you find Vegas crashing as you muck about with FX then running in compatibility mode can help.
From my perspective, this was a very big discussion a month ago and it's kind of disappointing that people missed it.
Running Vegas in Compatibility mode is a workaround, not a fix. I fully expect SCS to figure this out and fix it in another point release somewhere down the road.