I've been using it on this computer since I got it-- maybe a three months or so.

I have a project that will use 204 videos shot with a Sony handicam. Earlier, I could only bring in about 150 files. As I brought in more, it would crash. So I started small and started bringing in files in groups. I have about that many now. It just randomly crashes.

So I started on the generated media-- there is one for each video which is a description of the video. I got through about half of them and it just crashed again. It's like I have too much video. It's about 4 hours of raw footage, but it's currently edited to about 30 minutes.

Sometimes it crashes when I edit the media text or just size it. Sometimes when I rbing in a new video. Sometimes when I trim the video. Nothing in particular causes it.

No third part plug-ins. I do have the Veggie toolkit, but I haven't installed any of the tools or anything. I haven't even used it in awhile.

Thanks

Another crash. This time I pulled in about 15 more files and edited them. When the 16th was pulled in, only the video outline was shown before it was dropped. The audio was not being shown. I dropped it and nothing happened. I tried to drop it again, and it gave me the "Ghostbusters logo" ;). Then it crashed.



Sony Vegas 7.0
Version 7.0d (Build 192)
Exception 0xC0000005 (access violation) READ:0x7FE4001F IP:0x7C931C6B
In Module 'ntdll.dll' at Address 0x7C900000 + 0x31C6B
Thread: GUI ID=0xB50 Stack=0x12A000-0x130000
Registers:
EAX=0012a364 CS=001b EIP=7c931c6b EFLGS=00210206
EBX=00000000 SS=0023 ESP=0012a2b8 EBP=0012a374
ECX=01820048 DS=0023 ESI=7fe40020 FS=003b
EDX=6680d168 ES=0023 EDI=003b0000 GS=0000
Bytes at CS:EIP:
7C931C6B: 80 7E FF FF 0F 82 08 E8 .~......
7C931C73: FD FF 8B D6 E8 B2 04 00 ........
Stack Dump:
0012A2B8: 668C8C48 66560000 + 368C48
0012A2BC: 7FE40020
0012A2C0: 6680D21C 66560000 + 2AD21C
0012A2C4: 00000000
0012A2C8: 00000000
0012A2CC: 00000000
0012A2D0: 00000000
0012A2D4: 00000000
0012A2D8: 0012A318 00030000 + FA318
0012A2DC: 6B208200 6A720000 + AE8200
0012A2E0: 7C9321C2 7C900000 + 321C2 (ntdll.dll)
0012A2E4: 0012A2FC 00030000 + FA2FC
0012A2E8: 6B4D2CF8 6A720000 + DB2CF8
0012A2EC: 00000000
0012A2F0: 00140000 00140000 + 0
0012A2F4: 01A00002 01920000 + E0002
> 0012A31C: 7C91056D 7C900000 + 1056D (ntdll.dll)
> 0012A324: 7C91043D 7C900000 + 1043D (ntdll.dll)
> 0012A368: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0012A36C: 7C910570 7C900000 + 10570 (ntdll.dll)
> 0012A378: 78134B9F 78130000 + 4B9F (MSVCR80.dll)
> 0012A390: 78134AD2 78130000 + 4AD2 (MSVCR80.dll)
> 0012A398: 7C9133CE 7C900000 + 133CE (ntdll.dll)
> 0012A3B4: 78138AD1 78130000 + 8AD1 (MSVCR80.dll)
> 0012A3C4: 0CD1482F 0CC60000 + B482F (mcmpgdec.dll)
0012A3C8: 7FE40020
0012A3CC: 0012C860 00030000 + FC860
> 0012A3D0: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0012A3D4: 7C910570 7C900000 + 10570 (ntdll.dll)
> 0012A3E4: 0CA09960 0C9E0000 + 29960 (mcmpegin.dll)
0012A3E8: 6680D168 66560000 + 2AD168
0012A3EC: 00000000
0012A3F0: 0012A4B0 00030000 + FA4B0
> 0012A3F4: 7C90E288 7C900000 + E288 (ntdll.dll)
> 0012A3F8: 7C801875 7C800000 + 1875 (kernel32.dll)
> 0012A404: 0CA0A892 0C9E0000 + 2A892 (mcmpegin.dll)
0012A408: 668C8C48 66560000 + 368C48
0012A40C: 668FCB16 66560000 + 39CB16
> 0012A410: 0CA0B5A0 0C9E0000 + 2B5A0 (mcmpegin.dll)
0012A414: 00000001
0012A418: 668DBAA0 66560000 + 37BAA0
0012A41C: 668C8C48 66560000 + 368C48
0012A420: 0012A480 00030000 + FA480
> 0012A424: 0CA0A217 0C9E0000 + 2A217 (mcmpegin.dll)
0012A428: 668C8C48 66560000 + 368C48
0012A42C: 00000000
0012A430: 00000000
0012A434: 00000000
> 0012A43C: 021A0070 02100000 + A0070 (vfplugs.dll)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 009302DB 00400000 + 5302DB (vegas70.exe)
0012FFFC: 00000000

I'm afraid I don't know for sure. A stab in the dark would be some sort of issue with the video files. Are they HD or SD? I know there used to be a problem with too many HD m2t files, but I thought that got fixed. Can't tell you right off the top of my head what it would be, but this might be something you want to go to tech support with by phone. I think it costs a little money, but I don't know, I've never needed it.

Dave

450gb hard drive space? on one drive, two?

leslie

"When the 16th was pulled in, only the video outline was shown before it was dropped"

That tells me it is possibly a memory problem. You are obviously pushing some limits somewhere.

I would get a copy of Sysoft Sandra (hardware testing/diagnostic tool) and run some tests to make sure the hardware is solid.

SD videos

3 150 GB hard drives as a RAID



I'm so close to finishing. All of the files are in and edited, but it keeps crashing. Sooooo frustrating.

Can't do anything now. I tried to render it to make one file to bring into another file so I wouldn't be accessing so much video (10 GB), but it just crashes.

My hard drive is pretty fragmented, so I'm running a defrag.

In the meantime, I'm copying all the files to another monster computer to try.

Couldn't find Sisoft Sandra to download in English. I'm just frazzled becasue this video is due tonight.

The other computer, a duplicate of this one, also crashed as soon as the file was completely open. I find it hard to believe I've reached the limitations of Vegas.

I don't think you've reached the limitations.
I've brought that much in even on an amd dual-core 4400+ with 2 gigs ram (non-raid however - just a couple 320g sata's).

What format are the files you're bringing in?
Was the project created on an earlier vers of vegas (.veg)?
Toss out all plug-ins and try - if you have them in your project (new/fresh project).

Does the "other monster system" have the same/similar raid setup...same controllers for raid as the other crashing sys?
Same/simiar mobo and ctrlrs (or chipset)?

Have you tried on a non-raid setup by chance?

I still think there is few/little benefits to a raid setup imo.
To add, i still don't read about better stability of 7 vs. vegas 6d as well. I'd like to move to it, but there's too many random "crashing" cases out there.

>>>The other computer, a duplicate of this one, also crashed as soon as the file was completely open. I find it hard to believe I've reached the limitations of Vegas.<<<

Ooop, missed that.
Hmmm, I'd be suspect of the raid setup or ctrlrs used (since it's a dupe of the other sys). Nothing wrong with having 3 separate HD's non-raid, I'd try it when/if you get the time.
drivers for your ctrlr (or ctrlrs themselves) might be suspect - research it.
latest and greatest is nice, but it comes with the "unknown factor" too.

OK, first of all, don't bother with the defrag. It is a complete and total waste of time no matter what, and even if it did speed up your computer (which it won't), it will have zero impact on stability.

Since we all know that Vegas is a stable application, and it has (I presume) been running pretty well for you prior to this, I think we need to look at a few other things in order to solve your problem.

For one brief period of time several years ago, I had stability problems with Vegas. I actually wrote to Sony tech support, and they got to the root of the problem very quickly. What was it?

A third-party plugin.

Therefore, you should go to the plugin manager (View menu) and report back here on all non-Sony plugins you have installed, both audio and video. As you go through the various plugin menus, the non-Sony plugins will be shown with a yellow (rather than green) icon in front of the name.

In my case, the problem plugin was an earlier version of Mike Crash's excellent denoiser plugin. I removed it, and Vegas became stable.

Also, I have heard of other people crashing Vegas by messing with the hidden "internal" dialog. If you don't know what that is, then you won't have changed it, so there is no problem. If you have changed it, then you'll need to set all of Vegas' preferences back to default. I can give you the simple steps to do that, if you wish.

There have been a few problems in the past, especially with certain Vegas 6 versions, of crashing when large numbers of still photos were put on the timeline.

I believe he said the project was plug-in free though ("No third part plug-ins")...
If it's not and he is using a plug somewhere - do follow that and report back as that's good advice.
Tell people what plug and vers it is too so they know.

>>.Since we all know that Vegas is a stable application<<
Well, ... to a degree. 7 is still suspect to me.

Hmm, sumpin tells me it's a V7 issue or related to that mobo/ctrlrs/raid (if it's an exact dupe that is).

believe he said the project was plug-in free though

Ah, I missed that post.

well, let's see what "3rd party" means to him first - you could be right, it could a straggling plug somewhere in there.

Format of the files coming in and .veg version info would be nice too.

I think I'm having a similar problem. Got a project with about 4 hours of m2t in it. Vegas was locking up at random, what was really driving it nuts was adding more clips. I thought it was part of a system problem and I was able to nuke some of the m2t out of the project and go ahead o.k. - Your problem sounds very similar though...

One of the symptoms I had before a crash was it would tell me such and such clip was missing and do I want to look for it. Also thumbnails would turn into those little generic icons, like a bunch of media was missing. On a couple of cases it locked my system up hard and I had to hit the reset button. My error messages also mention the "Thread: VideoRender".

I've tried it with the project on a few different drives (raid and single SATA) and it doesn't seem to solve the problem.

System specs:

Asus a8n sli
AMD X2 4800
Raptor OS drive
4 drive Raptor Riad 0
2 Nvidia PCI express 6800 vid cards
Echo Gina 24

First, don't waste time posting the whole error dump - except for the third line, the rest means nothing except to the original programmer.

Access Error means that the program is trying to access memory that it does not have rights to. Some other task may still be using it.

Try increasing the number of pagefiles and make the swap area static. (In Control Panel, system, advanced, performance, virtual memory, advanced - they don't make it easy to find), set the minimum and maximum RAM allocation to the same value.

Steve Mann

The videos brought into the project are MPEG-2 files shot with a Sony Handicam. 720x480x32. 1.2121 pixel aspect ratio (NTSC DV widescreen.)

The project was not created in an earlier version.

I am not using any 3rd party plugins. I do have the Veggie Toolkit installed, but I've never tried to use any plugins-- not even sure how yet ;). I checked the plug-in manager and none appear in yellow.

The other computer is the same setup. Both part of 4 computers bought at the same time and all configured the same way.

I've not tried a non-RAID setup since my last computer. I would like to try that eventually. I have an older computer still available that just needs to be upgraded to Vegas 7.

No idea what the hidden internal dialog is. :)

Vegas version is the latest and greatest. 7.0d build 192

The virtual memory is configured as follows:

Space available: 235835 MB
Custom size: yes
Initial size (MB): 2046
Max size (MB): 4092

Total paging file size for all drives
Min allowed: 2 MB
Recommended: 3835 MB
Currently allocated: 2046 MB


Thanks everyone!
I don't see anything about swap area.

>>The videos brought into the project are MPEG-2 files shot with a Sony Handicam<<

Hmmm, another piece to look into. Have you tried completely uninstalling 7d and all prev versions of vegas and reinstalling?

Just for kicks, i wonder what would happen if you batch cvrtd these to uncompressed .avi and then rebuilt the proj. Will it crash?

i'm surprised nobody saw vegas was loading the mainconcept mpeg .dll in his second error dump!

Open a new project & bring in the mpeg's one file at a time. I've had a similar error in V4 & 6 where a mpeg file was bad. Took forever to figure it out. Could very well be one of your files is bad (but might still play in media player).

Or you could even try previewing each file inside vegas: make sure auto-preview is enabled & go through each one in the project media/explore window. If the file's ok vegas SHOULD tell you the file info & play it.

I too have been experiencing the same problems. Based on some of the earlier posts, I did a little investigating and found that both DivX and Mozilla Firefox installed a different version of the MSVCR80.dll file. Removed the DivX bundle and Firefox and so far so good.

It has been stable for me for the last couple of days, but....

Just something to try!

Vegas has - at least in my experience - been very bad at memory management. Back in Vegas 4 days I would routinely run upon "maximum number of open clips"-related crashes. I found it hard to believe that a 5-minute video with 80 clips would be pushing some sort of limit, but it was. I could watch its memory usage grow and grow as each new clip was loaded, until it hit the Windows' maximum amount of memory a single program can use.

Vegas 5 was better - I was at least able to edit my work to completion, although I still had to break the projects up into chunks for rendering elsewise it would crash at random points. Vegas 6 was a complete wash for me - I couldn't even do what I could in 5, so after playing with the demo I stuck with the old version.

Vegas 7 was a pleasant surprise - not only could I edit to completion but it would even render in one shot as well. Memory management is certainly better. However I am currently stuck at using v7.0b due to a horrible crashing problem I had with v7.0d and CIneform clips. Although Cineform thinks it was just a random installation issue, I so far haven't tried reinstalling "d" since I've been too busy and haven't wanted the hassle (especially if I have to end up going back to "b").

I only mention this since I'd suggest - if you have it - possibly trying out 7.0b (maybe on that duplicate PC) since some of your errors are quite similar to what I received with 7.0d.

My computer is starting to crash like crazy again too using 7d and CFDI files...
Had it lock up tight, had to hit the off button to close and start again.
Add files to timeline and the program disappears completely, no clue why.

On one occassion got the "Dr Watson DeBugger, etc...." report and looks like a memory dump. ( I have 4GB installed)
Doing a render of CFDI files my CPU useage is above 90% on an
AMD 4400+ Dual Core system

Thought my crashing had stopped with the "d" version but its back again.....

Teaktart