Vegas Pro 10d Crashes Constantly

[Nigel O’neill]

Tom

I would also try a project without Boris FX and see if the problem persists. If it does and you are able to obtain crash reports, you need to report your problem to Sony and submit the reports for analysis.

You might want to check if there is an update for Boris FX and if not, report the problem with them, too. It’s not always Vegas that’s at fault.

Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6

[Tom Zeller]

Thanks Neill, I will definitely give your advice a shot…meanwhile I will also definitely take any other ideas or solutions from those with similar problems.

thanks again, everyone.

[John Rofrano]

I must have sent half a dozen crash reports to Sony yesterday and all I was doing is straight cut editing a Camtasia tutorial that I’m working on. It’s odd because I can work with RED or BCC7 for a 1/2 hr with no crash but yesterday, I would just click on the timeline after making a pan/crop adjustment and the whole thing would crash. 10d is not as stable as I would have hoped for. Of course none of these are reproducible so it makes it very hard to report to Sony. I am constant using Ctrl+S to save after very two or three edits.

I must say that RED and BCC7 work better in 10d than 10c so I really don’t want to go back. I just wanted to let you know that you’re not alone. 10d is crashing a lot for me too. 🙁

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Jim Greene]

For me, 10d is so much more stable than the previous v10 revisions. However, once in a while I do get a crash, and is usually due to copy/paste from multiple projects, and also from audio filter changes. It seems that audio editing & playback is worse than other releases, which is odd considering this is Vegas.

-Jim.

[Stephen Crye]

Hi; I feel your pain also. 10d is NOT more stable. Here is a typical crash:

Faulting application name: vegas100.exe, version: 10.0.0.670, time stamp: 0x4dc30003
Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c8f9
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x103c
Faulting application start time: 0x01cc1ed7f5c0ed81
Faulting application path: C:\Program Files\Sony\Vegas Pro 10.0\vegas100.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: bc5b5be4-8acb-11e0-9a50-0022192138a7

I’ve taken to hitting ctrl-S about 3 times a minute, and alternating between multiple versions of .veg files so that I always have a recent version of a saved project.

Fun, eh?

Steve

[Jim Cates]

64 bit version of 10d will not run….it will open, then almost immediately “stop responding”. Posted this issue in a separate topic.
No help from the Vegas forum yet….

[Tom Zeller]

Thanks for letting me know I’m not alone you guys…that does help, but how about people with information on the issue…such as the Sony people. Come on Sony, we are trying to make a living here, which is tough when your product constantly crashes. I know new versions have new features, but the greatest new feature you’ve added to your software seems to be its ability to crash without fail constantly.

[Tom Zeller]

…and I now can safely mention that this is definitely the combination of Sony Vegas Pro 10d and Boris FX. I edited a new project flawlessly without a single crash (working on it about 7 total hours) when I did not add any Boris FX to it.

However, I have got a really incredible project I need to finish and it is loaded with Boris, so I can’t really get rid of the Boris plugins….any ideas? I don’t want to start this project over and also have to learn a new plugin product to attain the same effects I already know how to do.

Thanks again!