This won't help a lot, but I've worked out some of the crashes to be related to the type of footage on the timeline. AVCHD footage crashes the curve plug but avi seems NOT to crash the curve plug. Good luck.

Some of the simple things you might try:
1.Update to the latest video card driver
2.Turn off "User Account Control" in Windows 7
3.Put Windows in "Vista" compatibility mode.
4.Remove New Blue Titler
5.Put backuip files for V11 in separate folder from V10.
6.Update to latest Quicktine Pro
7.You want to have at least 8 gig of ram
8.Turn off GPU in video preferences.
9.Windows 7 doesn't like old hardware and old drivers so update everything you have.
JJK

Alot to turn off after you have just spent money to use these features isn't it?
You will wait forever for a reply from Sony as well. Last step is the refund.
Or start using avi or dv files again.

Rob, thanks for the response, but next time please keep your sarcasm to yourself, it's not appreciated here.

The reason I posted on the forum is I've noticed in the past that SCS tends to monitor the forums and sometimes we can get a response quicker here.

As for my system, let's see.... i7-2600K CPU @ 3.40GHz, windows 7 64-bit OS and 16 GB of Ram, 2 NVIDIA GeForce GTS 450 vido cards (with 192 CUDA cores and 1 GB of memory), 2-2 TB hard drive (internal) and 11 more TB over 6 more external hard drives. Also 1- 27inch 5ms monitor and 3-19inch 5ms monitors. So tell me Rob, is this system good enough for you?

To everyone else, I appologize, I don't mean to sound like a jerk I just am very discouraged with SV11 because I've been a long time customer/user and I just feel let down here.

Just an update to my earlier post, I have noticed most of the crashes are associated with using the NewBlueFX Titler Pro. It seems when importing .jpg files to the Titler, it crashes. I've also noticed if I have other programs opened that seems to promote crashes in SV11.

Clear Shot, I would think your system should be good for V11 with possible exception of the GTS 450's. I would defintely try turning GPU off (if it is not already disabled) in Vegas, not use NB Titler Pro., and if possible avoid using other applications when using Vegas.

/jerry

I agree Jerry, it seems turning off other programs (especially Adobe After Effects...LOL) seems to be helping.

This is why I came to the forum, to see what others have done to make this work for them too.

Thank you,
Steve

Have you got V10 and V11 on the same PC?

G

Yes I have both SV10 and SV11 on this computer. And I will add, when I went back to Titler Pro on SV10 it crashed. And I can't tell you the last time SV10 crashed.

Just humour me. How have got your Vegas temp folder setup? What is the Path?

G

Clear Shot said, "...2 NVIDIA GeForce GTS 450 vido cards (with 192 CUDA cores and 1 GB of memory), "

Vegas will only use one of those cards for CUDA. The other will not be of benefit when it comes to CUDA cores. The GTS 450 card is sub-par at best.

I am using the 560ti with the latest drivers and am getting good results.

Note: Your CPU may have enough power that CUDA may not be needed. So you might either get rid of the crashes or reduce them by not using the CUDA.

As for your original post, please do not do what I used to do and come here and post while you are all upset over Vegas crashing and leaving a post with a great big GROWL! LOL!!!

Take a while and calm down then leave a nice request for help with as much information as possible. There are plenty of users here who will be glad to help.

Sorry to hear all the trouble - but do not give up the hope.

Here I edit several hours every day using the V11 682 32 bit version (because of some 32 bit plug-ins) and I throw 17, 24 and 28 Mbps AVCHD 50i and 50p plus different mp4 from older cameras plus AVI from surveillance cameras plus small and huge jpg's plus huge png's plus mpeg-2 plus other strange media (i.e. from mobile phones) and, and, and - all onto the same timeline and V11 eats it all and renders it faithfully as I wish.

You may call me fanboi or whatever - but it does not change the fact that my V11 installation has not had one single hiccup for a very long time now.

Even my simple GTS450 hums along and GPU assists Vegas rendering and previewing. My machine is a 4 years old Apple MacPro running Windows 7 Ultimate natively (no Bootcamp etc) - and SCS support has even told me that they can/will not answer my technical questions because they do not support that machine... actually quite funny when that machine seems to fit Vegas so well.

Day before yesterday I even moved my C: drive to a new SSD and all my current input media to a new Seagate Barracuda 3 TB - and Voila: yesterday and today editing continued happily here.

Vegas 10e worked well here. The Upgrade to V11a was a real "surprise" (read: disaster) so I stayed with 10e until the current version of 11 came - and it has just done the job since that.

Dunno if it means anything for the stability, but I only seldom use any non-Vegas plugins (have only very few installed), have a 1 KW power supply and use ECC RAM memory on a Windows 7 Ultimate with all the latest updates and also the latest Nvidia (beta) drivers. I actually update whenever a Windows or a Nvidia or a Vegas update is available - thinking that there is a reason for the updates - not that I notice much change during the daily work - but it also does not spoil my machine (so far, anyway) :- )

No sarcasm intended. "Top of the line" is a very relative term. Your description here is a lot more informative. Otherwise your system could be the top of the BOXX line or the top of the HP consumer laptop line, and so on.

Regardless, the current favorite hardware culprits are graphics cards (and their drivers), PSUs (use something much bigger than you thought you'd need), and sound cards (ASIO drivers have a long history, but it looks like you don't have specialized audio hardware installed). Bad DIMMs are also high on the list of favorite culprits or scapegoats.

Grazie has suggested starting a brand new temp file folder for VP11. Some people have said it helped, others can't see why it would, but you might try that.

Compatibility mode helps with at least one possible bug, but not all. Turning off GPU acceleration is another itch to scratch and it's something I'd do to try to simplify the problem.

My computer at work is a C2D 8400 with 6GB of RAM. VP11-64 is stable on it even with a lot of applications running, but I'm not running AEFX. Vegas is the only app using video files so there's no chance of contention there. Still, I run a handful of other Adobe apps alongside Vegas with about 10GB less RAM than you. Vegas remains stable. Perhaps if both Vegas and AEFX are trying to use the GPU that could be a problem...

Rob

Yes six weeks seems to be about the going rate for responding to questions and then it is usually the re-install Sony cut and paste letter which has spectacularly failed to work for me ever. I have used Vegas since the very beginning, I used to love it so much now it is a flaky piece of software trying to catch up. I just bought CS6 and started the long haul to work with something else...

Grazie has suggested starting a brand new temp file folder for VP11.

More a "Version-dedicated" Temp Folder.

So instead of the default, that comes as part of the Factory Install, I've now chosen to do for each of the money-earning Vegas Installs I have:

F:\Sony Temp Folders\Version 9

F:\Sony Temp Folders\Version 10

F:\Sony Temp Folders\Version 11

I've also kept a MS Windows Explorer Pane open so I can VIEW the antics of Vegas as it goes about creating the Temp files it needs to work and I can see exactly what is going on. I see the UNDOs and REDOs and AutoSave and restore and bak files being produced. And MORE importantly, I can actually observe when and where these Temp files get removed on closure of Vegas. You will see AutoSave and restore going through an Alpha-Numeric naming process, I'm now thinking the unthinkable and that if these files get cross-referenced by my stupidity on NOT creating separate Folders, then all nonsense could (and maybe it does and that is where I was at with this) break loose.

Now, friends, ALL of this is predicated on this being the flaw. If it is as simple as this, then great. But we've all been here before, with searching an issue.

And yes, this activity of mine HAS been lodged with SCS and has been noted by their staff. So we'll see.

Cheers

Grazie

<<I have noticed most of the crashes are associated with using the NewBlueFX Titler Pro>>

Same here, so I stopped using it. A free update has been released but I haven't tried it. If you want to use this titling program I'd definitely install the update. FYI, though I've not used them extensively, the Boris FX and Magic Bullet Looks 2 plugins have both been 100% stable with VP11.

Vegas 11 still freezes occasionally when using Color Curves on AVCHD footage. This is a known bug, and it's been happening a lot less since I updated my nVidia drivers. In general, I have noticed increased stability with each new rev of V11 AND with each nVidia driver update; the last nVidia driver update was especially helpful.

As a last resort you may want to consider transcoding your footage to a more Vegas-friendly format - I've found that .mxf (HD Cam EX preset) works quite well. I shoot AVCHD with a Panasonic GH-2 and most of the time things work quite well. But occasionally I'll have a video clip that absolutely crashes Vegas; transcoding to mxf as described has fixed the issue 100% of the time.

Vegas 11 still freezes occasionally when using Color Curves on AVCHD footage. This is a known bug

Guy, I do have a similar bug when using the Color Curves FX over an event, sometimes the Color Curves settings (the curves) won't show up in the FX plug-in window and then you need to restart Vegas 11 because it crashed. Is your problem similar to what I have described?

Rob

We all know what it looks like even without the screen grab. All one can do before applying the curve plug to AVCHD files is save in case of the probable hang to crash.

So I thought I was the only one having this problem, for some reason I never read anything about it on this forum.
I also wrote to Sony over a month ago but never got any feedback yet.

Hope it gets fixed soon since that prevented me from working on V11, I just couln't live with it.

Rob

I have noticed most of the crashes are associated with using the NewBlueFX Titler Pro

All I can say is that with the latest NBTP build, I was never able to crash it even after intensive testing. Only, the Color Curves bug and V11 crashing unexpectedly preventing me from using it and went back to V10e because of tight deadlines.

Rob

I use it and let it crash and send the system reports to Sony, including all the extra information in the hopes that it helps make it better in the long run.

I understand that the Vegas crashes can cost you time and money, and so you should stay with Version 10 for now.

For me, CTRL + S is almost a reflex every 1 or two minutes, it is part of my editing rhythm now... when it does crash it only costs me a few moments, the most I lose is one or two editing moves.

Not an elegant solution, but for the good of Vegas I push on...

Your martyr,
Chap

Also I have had very good results running Vegas in "Compatibility Mode" with Vista Service Pack 2.

<<Is your problem similar to what I have described?>>

No, it is EXACTLY what you have described!

I like it, actually - it gives me a good excuse to curse ;)

Reading other threads I get the impression that it's related to AVCHD footage. It doesn't happen every time and was happening less with the latest software and driver updates - until I installed the GeForce 680 card. I've seen very little speed improvement with this card and Vegas seems less stable.