Not Ready to Say Good-bye to Vegas! No Getting Close.

[Ken Bennett]

I haven’t really tried that yet. I guess I could bring over the media files for the project in-works on to a single drive and edit from that data.

Thanks for that tip Phil.

Ken Bennett
Video Adventures
Capturing Your Life’s Adventures!

[Ken Bennett]

My system:
MOBO: Intel P9X79 WS w/6X PCIe 3.0
CPU: Intel i7 3930K 6-core, 3.2GHz
RAM: 32GB DDR3
1 LG Blu-ray burner
1 LG DVD/CD burner
WIN 7 64bit
Quadro 4000 card
RocketRAID card
BlackMagic DeckLink card
5 Seagate 3TB HDDs
2 external 9TB RAID-5 boxes
2 22″ Dell monitors
Logitech keyboard & mouse

The crashes:
1. During playback, video freezes, audio continues to lay, Vegas interface goes ghostly white and then final the Vegas has stopped work message comes up.

2. The entire Vegas interface simply vanishes. No warning. “Poof” gone.

3. Sometimes just during editing the interface will lockup. The everything in #1 takes place.

I will try all those other suggestions. This is a custom built system and I have know the builder for over 20 years so replacing/fixing components is no big issue. Just a slight cost if any.

Crashes started back in Vegas 10-11 on another system, but it was an old computer.

I’ll let you know what I find after your suggestions.

Thanks Stephen

Ken Bennett
Video Adventures
Capturing Your Life’s Adventures!

[Ken Bennett]

I do have a script that will autosave every 60 seconds.

Ken Bennett
Video Adventures
Capturing Your Life’s Adventures!

[Ken Bennett]

BTW I have a 1200w PS in this system.

Ken Bennett
Video Adventures
Capturing Your Life’s Adventures!

[John Rofrano]

[Ken Bennett] “I haven’t really tried that yet. I guess I could bring over the media files for the project in-works on to a single drive and edit from that data.”

I’m not sure if it matters but I only use my RAID 5 for archiving. I edit everything on internal SATA drives or Non-RAID eSATA drives and I don’t have a lot of crashes. So I agree to copy one project to an internal hard drive and see if the crashes are less just to get the RAID out of the equation.

~jr

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

[Stephen Mann]

If a program freezes up and the screen goes “gray”, often followed by a message like: “Program has stopped responding”.
OK, why has it stopped responding? The usual suspect is that a process required by the program has itself stopped or failed.
You can use the Windows Resource Monitor to try to determine what process has caused the problem.
Go to Start, Run, and enter resmon
In the Overview tab, look for the program in the image column.
Right-click on the program image name and select “Analyze Wait Chain”
If a process is the problem, you can try to simply end the process. More often than not (in my experience) this usually fixes the immediate problem and the program can continue running. Back up your work and Google the offending process to see if there may be a fix. (It’s a long shot, though.)

Steve Mann
MannMade Digital Video
http://www.mmdv.com