64 bit Vegas still a crasher

Comments

Sunflux wrote on 10/24/2011, 10:34 PM
In days gone by, Vegas has had rather severe memory management issues - at least on the projects I worked with. For example, when I was working with SD .AVI files, I routinely had problems rendering where the software slowly ate up all available memory and then crashed. At a certain point, I could no longer even edit on the timeline due to crashes. Then I switched to editing HD .AVI Cineform files and the exact same problems continued. I traced it down to having too many .AVI files on the timeline: around the 80-100 mark, things would break.

When I finally built a brand new high-end PC, I started editing native HD .M2T files and almost magically my memory issues vanished. I could recreate the exact same issue if I swapped in .AVI versions, but with .M2T it would happy render a project with 150 source files without a single issue.

I'm certainly not saying that is the problem here... just that Vegas does potentially do things differently than other programs. It is also far more intensive on CPU and memory than the majority of other software, and in different ways.

Memory issues may also only be exposed under extreme conditions, perhaps when v-reg "droop" comes into effect. With the memory corruption issues I describe earlier, I could install Windows 7, browse the internet, use Office and any other number of daily tasks without suffering ill effects, but if I played a demanding game or tried to edit video then the crashes and BSODs would pop up.

I have not seen one single BSOD on the system I'm using now (at least not since I fixed the memory timing problem), and I've been doing a heck of a lot of work in Vegas. Now 32-bit Acid Pro, on the other hand, crashes like a $!%@$ and it's doing so little compared to Vegas.

To test your system, I would download a copy of Prime 95, set it for the memory-intensive test, and have it run overnight. If you can pass that with flying colors (ie. no rounding errors), then you might be able rule out memory as your culprit.
ReceptorDeceptor wrote on 10/25/2011, 9:23 AM
Huge crashing issues here as well. Vegas Pro 11 is a big flop - why can't Sony fix the damn bugs in their software before releasing yet another "update" that we have to pay for? I'm seriously considering moving to a different video editing software.

One of the most ridiculous examples of the quality of Vegas 11 Pro came up when I tried this:

- Opened up a new project
- Imported a 2 min clip shot with Sony HD Blogger (.MP4, 1080p)
- Tried to stabilize it, maybe 10-15 times -> the program crashed EVERY SINGLE TIME. I don't know how but I managed to stabilize the clip in the end, and the end result was that Vegas crashed during playback. This is beyond my comprehension, really! How can anyone put out "professional" software with a price tag like this ???

I found out that the new GPU assisted preview/rendering is also nothing more than a pile of bugs stacked on top of an already buggy software. I've had a bit less crashes in some of my old projects after I've disabled it altogether.

So, I can only say as a tip to all that:

1. MAKE SURE YOU HAVE ALL THE LATEST DRIVERS! Vegas 11 used to cause BSOD's for me right from the first time I tried it, and it was because it completely messed up my AMD/ATI Radeon video card drivers. The new Catalyst drivers (which are about a week old) have a new security feature which prevents Vegas (or any other software) from crashing the whole computer.

2. My suggestion is that you should disable the whole GPU acceleration altogether from Preferences -> Video, until Sony fixes those f***ing bugs. Which sadly isn't going to happen anytime soon, if ever. Or if it does, we'll probably have to pay for it.
JHendrix wrote on 10/25/2011, 9:49 AM
to the OP...I too have been getting (as of this week) many Unmanaged Exception (0xc0000005) crashes. no logic as to why.

i don't have time to wonder anymore though, since i need a new box anyway, I am going to buy a new machine, install only vegas on it and never have it connected to the web. if this type of thing keeps up after that I will know for sure its vegas (even though I am 99% already know it is I am being a gambler and betting on that 1% chance)

i will post back and let you know.
Sebaz wrote on 10/25/2011, 10:16 AM
To determine if my computer actually has a problem, I downloaded the newest 64 bit Prime 95 along with CoreTemp last night and left them running all night long, and I chose the Prime test that says "Lots of Memory Tested" since some suggested memory might be the issue here.

Now it's over 9 hours later and not a single worker has crashed (to those who don't know Prime, it starts a "worker" for each core the CPU has), and temperature is 37C. So it's a stable system, but tonight I'm going to let it run the Windows Memory Diagnostic just in case.
rmack350 wrote on 10/25/2011, 11:14 AM
I was just hunting around for information on (0xc0000005). I wanted an explanation of what it was. The following page had quite a lot of information, some of it along the same lines as my guesswork above.

http://www.updatexp.com/0xC0000005.html

In general it's a memory access violation that could be caused by a pretty broad number of things.

The parts about DEP were interesting. I've had suspicions about this in the past. Keep in mind that Vegas has been around longer than 64-bit windows, and longer than DEP. It's quite possible that there's legacy code in there or in some of the DLLs, or in some codecs, that doesn't play well with DEP.

Rob
Sebaz wrote on 10/25/2011, 3:32 PM
That's interesting, but if the problem was that Vegas doesn't work well with DEP enabled, wouldn't it crash for everybody just the same? I'm betting the ranch in that it's still Vegas' fault for having part of the code that doesn't work well with a range of systems as wide as the other software, because if my system was flaky, Prime95 would crash at least one worker in 9 hours of running at 100%, and all my other software would crash often as well.
Steve Mann wrote on 10/25/2011, 3:48 PM
Prime95 is not a system tester, it is a system stresser. Its only function is to run the processor cores flat out. It does this by calculating prime numbers, which is prcessor intensive. It doesn't test anything else. Not the device drivers, not the bus controllers, not the interrupt controller, and any other hardware.
Sebaz wrote on 10/25/2011, 5:36 PM
Steve, which program do you recommend as a complete solution to test the hardware for errors, CPU, memory, all the motherboard components, etc?
ReceptorDeceptor wrote on 10/25/2011, 6:35 PM
To be honest: I've used numerous video transcoding tools from other software vendors than Sony that have GPU assisted rendering and more. I've always had good results (one example is TMPGEnc's Video Mastering Works 5). Only program that's ever crashed, and in some cases brought down the entire computer along by causing a BSOD, has been Sony Vegas Pro, version 10 or newer.

The ugly truth is: Even in Sony Vegas Pro 10, the introduction of the widely-marketed "GPU assisted rendering"-feature was a huge joke. For instance, I couldn't get the CUDA feature to work in my desktop PC at all. I've tried also tried the GPU rendering on my other workstation, a relatively new Sony Vaio i7 laptop (bought last year). It was one of the flagship models at the time of purchase and it even had CUDA-promo stickers on it, and, surprise surprise - NOTHING WORKED! Crashed every single time!

Calling these issues "probably a memory error in your computer's RAM", "you're doing it wrong" and so on, is just ridiculous.

As for Vegas Pro 11, I consider the whole update virtually unusable as for now. It's absolutely devastated my workflow when I try to work with projects left unfinished in v10.

Instead of being in awe with the new features, I've pretty much experienced only BSOD's or at least critical program terminations if you're using AMD/ATI Radeon video cards and have the latest drivers. In addition to that, there's constant crashes (coming from who knows where, probably not even Sony software developers), hang-ups and what have you. Having any kind of GPU boosts enabled will only cause more instability than what I've ever experienced before during years of Vegas Pro usage.

I am a VERY disappointed customer, to say the least. Seriously - why do paying customers have to be beta-testers of Sony's poorly coded software? Version after version !??! What kind of persons do they have running the software department anyway? This is like a bad joke IMHO. I think we should start voting with our wallets and move to other video editing programs if Sony doesn't feel like it should address any of the known bugs in its own software. Just my opinion.
rmack350 wrote on 10/25/2011, 7:16 PM
...but if the problem was that Vegas doesn't work well with DEP enabled, wouldn't it crash for everybody just the same?

First off, I'm just really making guesses. Forming hypotheses to test. The more I read the more I think it's not DEP because it would give error messages that mention it. However, DEP is mandatory on 64-bit windows, for "essential Windows programs and services". By default it wouldn't be on for Vegas unless perhaps you were running security software that turned it on "for all programs" without your knowing it.

The question of "wouldn't it crash for everyone just the same" is an important one. Since it doesn't crash for everyone then the question might be "why not? To me this suggests that it's several factors of A+B+C+D+E=Crash. So the way to track it down is the way you always track these things down, by subtraction. This can be more work than you want to deal with, especially when Edius works just fine. Why bother? Curiosity, maybe. Stubbornness, maybe.

Rob
John McGrath wrote on 10/25/2011, 8:10 PM
if you used that many cards you may have ghost registry remaining in your sys, run DriverSweeper
John McGrath wrote on 10/25/2011, 8:13 PM
listen to steve mann he knows his stuff,
hes a vegas guru!!
SStone wrote on 10/25/2011, 8:24 PM
Well I will add to the mix.... I have been using Vegas 9 64bit without any issues (love it). I skipped getting Vegas 10 but wanted to get the latest version so I downloaded the trial version of Vegas 11 a couple days ago. It has crashed on me & locked my system up numerous times. I contacted support & was referenced to some info that basically tells me to unload programs that are running in the background. I tried that and it still crashes when I am editing things. Remember this same PC had no issues with version 9! So I don't know whats going on. Support seems to just pass the buck. I may try downloading the 32 bit version just to try. Sony if your listening, You do have an issue somewhere!
Steve Mann wrote on 10/25/2011, 10:35 PM
Sony generally does not monitor these forums. This is a place for peer assistance.

"Crash" is a very broad term. What are you trying to do and how does the crash present itself?

Hint: "Unmanaged Exception" errors are almost always driver issues.
Do NOT overclock until you are comfortable that Version 11 is working for you.

Version 11 uses computer resources that Version 9 never did, so if there's a problem in the PC, I am not surprised by the number of people suddenly having errors. Vegas 10 saw changes to the AVCHD processing and probably involved a lot of changes to the CODEC. Version 11 is likely a huge rewrite to utilize the GPU Cuda cores. Again, some PC resources are being tapped for the first time.
Steve Mann wrote on 10/25/2011, 10:36 PM
"listen to steve mann he knows his stuff, "

Thanks for the thought, but I am a mental midget (or mental case depending on the forum) compared to some of the long-time users who hang out here.
John McGrath wrote on 10/25/2011, 11:04 PM
Well Steve I think ya know your stuff and you usually always point me in the right direction :)
SStone wrote on 10/26/2011, 9:34 AM
When I say crashes I mean Vedas locks up. I can usually close the screen without having to reboot. I am in the event FX edit mode: I get an error window that says "Vegas Pro has stopped working" "A problem caused Vegas Pro to stop working correctly" . It doesn't go into any detail at all.
rmack350 wrote on 10/26/2011, 11:28 AM
Your system specs say you're still running Windows XP and using a GeForce 8400. This is probably out of date.

So this happens when you're working with Event FX? Any particular FX or is it all of them?

You might start a new thread since this one is about 64-bit Vegas being unstable across multiple versions.

Rob
SStone wrote on 10/26/2011, 8:05 PM
That's old stuff. Sorry I will update.

I have:

AMD Athlon IIx4 630 Processor 2.80 GHz
8Gig memory
64 bit Windows 7 Pro
Graphics card is GeForce GT 440 w/1 gig memory

Steve Mann wrote on 10/26/2011, 10:23 PM
"Vegas Pro has stopped working" "A problem caused Vegas Pro to stop working correctly" . It doesn't go into any detail at all."

Those are from Windows. Not necessarily anything that Vegas did, but you were running Vegas when Windows couldn't do something as planned.

When an error occurs, go look at the event viewer to hopefully find a clue as to what caused the error:


Sebaz wrote on 10/27/2011, 2:04 AM
Just an update, I ran the Windows Memory Diagnostic, 2 passes on the extended test. It came back with no errors. Which along with Prime95 not crashing in 9 straight hours tells me that my machine is perfectly fine.
farss wrote on 10/27/2011, 4:48 AM
"Which along with Prime95 not crashing in 9 straight hours tells me that my machine is perfectly fine. "

Which leaves either:

1) The type of media you're working with.
2) The way in which you use Vegas.

as being the factors which differentiate your experience with Vegas from the majority of other users. I have had some issues related to 1), in fact that media caused both Vegas and Ppro to go wobbly. As I've mentioed before I've also had issues that were related to the order and speed with which I did things in Vegas.
If you want to get the bug that's causing your issue fixed you have to do a bit of work to define the exact sequence of actions and speed of doing them to invoke the problem. I cannot say SCS will fix the problem once you get that level of detail to them. I can say they'll very likely not fix it intentionally until you do. The ball is kind of in your court.

Bob.
Sebaz wrote on 10/27/2011, 8:36 AM
No, I think the ball is in their court. My footage is AVCHD from a Sony HDR-AX2000 camcorder, sometimes a Panasonic HMC-AG40, I can't remember the exact profile and all that, but it's the highest quality type that is 21 Mbps variable. Meaning, my footage is not some kind of weird file format that is unpopular or untested. But still, I remember this happening from when I had an HDV camera, same thing. I would hit play and crash.

My editing is rather normal, it's not like I press J and L fifty times a second or go back and forth like crazy in the timeline with the mouse. If just by positioning the mouse at a certain point in the timeline and then hitting the space bar crashes the program, that makes obvious to me that it's flimsy program. It may work with certain hardware configurations, but it doesn't play well with all configurations, and my machine is rather high quality, as evidenced by all other software running perfectly fine and passing the tests I mentioned, although if someone wants to suggest other tests, feel free to do so and I will run them. Tests can be left running overnight, so I don't mind running them. But dedicating hours to beta test Vegas 64 for SCS for free is not something I'm willing to do. After all, Edius is far better for almost everything and I can go weeks without a single crash.
China wrote on 10/27/2011, 8:54 AM
...for the life of me, I can't seem to locate it just now, but I seem to recall reading sometime in the last week, that somebody had major issues from having CS5 and Vegas on the same machine.

Apparently resolved by having Vegas installed AFTER the CS suit. I've Googled and can't seem to find it any more, (that might be due to the red wine!) , but at this stage, it may be something to try to see if your dramas can be resolved.

I hope you find success.

My Vegas11 seems to behave for me.