[Nigel O’neill]

Jamie, if you have the option to use a 64 bit version of Vegas (assuming you have 64 bit Windows), you will not see this error.

[Nigel O’neill]

I use a Sony HDR CX110 as a backup camera, but with memory card will be about $400. It can shoot full HD at 24 mbps, and you can reduce that to 17 or 9 or even 5 mbps via the menu. It is tiny and unobtrusive and runs off SD HC cards.

I use it when I do stage work and mount it on my main camera offset slightly to the right using a bracket that connects to my hotshoe. I operate my main camera and occasionally adjust the framing to get a two shot on the CX 110 whilst I go in for the tighter one shot with the primary camera. You can get some really nice dissolves or superimpose two shots.

The same principle applies to an interview situation where I can lock both off with different framing. That way I can keep an eye on both cameras and only use 1 tripod.

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

[Nigel O’neill]

Thanks Steve and Jeff. I have something similar to a StarTech USB 2.0 video card, but I came across posts on the Internet suggesting that having 2 video drivers loaded can cause system instability issues. I did try it, albeit not with 3 monitors (just 2) and Windows 7 blue screened after a driver update, my first ever on Windows 7. Once I rolled it back, it was OK.

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

[Nigel O’neill]

You will probably notice that if you do not shutdown your PC or mount/dismount drives, your project will not have this problem. Saving them as different version veg files made no difference in my case.

I had this issue in version 10c onwards and don’t restart my PC or swap in/out drives until the project is done. A silly workaround, but it works.

[Nigel O’neill]

It was the card reader. Got one that was USB 2.0. Still takes 9 minutes to copy 2GB, but that is better than 1 hour.

[Nigel O’neill]

Thanks John

Unfortunately the CF card is in a DN60 Datavideo recorder hooked up by firewire to the Z1P which has a dead tape transport mechanism. It was cheaper to buy the DN60 from B&H photo with international postage than to fix the tape mechanism!

I tried hooking the DN60 by firewire to my PC, but it does not access it as a drive. I might buy a more modern card reader as I don’t recall when I got it. It could be USB 1.1, but I have no way of telling on my readers.

[Nigel O’neill]

Jeff, did you say you were running 2 x GTX 460 in SLI? The reason I ask is our office call centre wants to run a 3 monitor setup. We are kind of restricted in terms of case size (standard desktop case), and I am wondering what sort of card dimensions we are talk of here for your setup.

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

[Nigel O’neill]

George, that screen shot was actually very helpful. I don’t think Vegas is the culprit.

Stop 0xoA errors are generally caused by a hardware fault or something interfering with the driver.

One typical cause is memory. You could try reseating the memory (remove and reinsert) to see if that helps.

As computers get switched on and off, they heat and cool, and the expansion and contraction causes minor movements, enough for parts such as memory modules, to pop up. If you don’t feel comfortable with reseating your memory, you could just try firmly pressing it down. You may hear a small click or creak at the memory gets reseated into the slots.

Make sure you switch your PC off. If the blue screens continue, your memory could be faulty and in need of replacement. You can run a utility called memtest to check.

Some other forums suggest the fault could be caused by malware in the form of a rootkit that has infected one of your drivers, which can be removed. For more information about TDSKILLER, go to:

https://support.kaspersky.com/viruses/solutions?qid=208280684

[Nigel O’neill]

I have to admit (quite sheepishly) that when I first started using Vegas (SVP10) I installed the K-lite CODEC pack and did not have one issue. I was using it so I could import this AVI file that would not import or play in Vegas unless I installed K-lite. I then rendered out to the DVDA template. Having said that, when I rebuilt my computer (as part of my 3 yearly refresh), I did not reinstall K-lite.

For Vegas to blue screen your computer at ANY time, it has to be pretty serious. The only time I have ever had blue screen issues with Windows 7 was when I was using a USB video card on my backup system whilst the primary system was being upgraded. I deduced the problem was related to a video driver update, and once I rolled it back to the version that shipped with Windows 7, the blue screens stopped.

Unless you post some information about what the blue screen error is saying, it is going to be hard to work out what the actual problem is. Most likely you have unknowingly downloaded a suggested Windows 7 update which has caused this issue.

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

[Nigel O’neill]

Gilles, I have seen similar ‘sliver’ problems with jpegs when doing my weddings.

This is what I do:

Drop the jpeg on the time line, right click it, select properties and confirm that PAR = 1.000 on the media tab. I then go to Event Pan/Crop and select the Pre-set titled 16:9 Widescreen TV aspect ratio, and voila!, the slivers disappear.