Pro 8.0 crashes on project

darg wrote on 11/2/2007, 11:51 AM
Hi Guys,

nice forum, I'm reading already a while here to find some answers. I hope I can find an answer in regard to my problem. I'm running Vegas 8.0a Pro on a new machine, the project will contain SD (in 16:9 from a Sony Camera captured with Vegas 7.0) as AVI and HDV (from a Canon HV10 via HDVSplitt Beta captured)as M2T material from two different cameras. Starting with my project I have added the material to the timeline and worked on it with envelopes and cuts and so. I figured out that I can only preview around 30 to 40 HDV scenes in the explorer and Vegas crashes with a failure message. I got the same message after I had reached a certain amount of scenes in the timeline. The overall project length is only 3 minutes, contains around 39 objects, so it can not be too big for the computer:

E6850 CPU on Asus P5K, 2GB RAM, GeForce 8800 GTS 640MB on Win XP (SP2) with all updates that you can get from MS and third party.

The error mesasage is:


Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module 'mcmpgvdec.dll' at Address 0x23000000 + 0x3B990
Thread: VideoRender ID=0xFAC Stack=0xAA7E000-0xAA80000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010206
EBX=00000000 SS=0023 ESP=0aa7ea5c EBP=0aa7ea74
ECX=0aa7ea38 DS=0023 ESI=00000010 FS=003b
EDX=7c90eb94 ES=0023 EDI=00002a14 GS=0000
Bytes at CS:EIP:
2303B990: 89 3B EB 95 8D B6 00 00 .;......
2303B998: 00 00 8D BF 00 00 00 00 ........
Stack Dump:
0AA7EA5C: 0AA7E9FC 0A980000 + FE9FC
0AA7EA60: 00000014
0AA7EA64: 0AA7E9C0 0A980000 + FE9C0
0AA7EA68: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EA6C: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EA70: 00005A00
0AA7EA74: 0AA7EB04 0A980000 + FEB04
0AA7EA78: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
0AA7EA7C: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EA80: 00000010
0AA7EA84: 21825870 21200000 + 625870
0AA7EA88: 21825850 21200000 + 625850
0AA7EA8C: 77C2C2E3 77C10000 + 1C2E3 (msvcrt.dll)
0AA7EA90: 217BB0C8 21200000 + 5BB0C8
0AA7EA94: 0AA7EB58 0A980000 + FEB58
0AA7EA98: 00000001
> 0AA7EAA8: 01204800 01150000 + B4800 (vegas80k.dll)
0AA7EAAC: 472A8FA0 46450000 + E58FA0
> 0AA7EAB0: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
0AA7EAB4: 0AA7EAC8 0A980000 + FEAC8
0AA7EAB8: 472A8FB0 46450000 + E58FB0
> 0AA7EAD8: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 0AA7EADC: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0AA7EAE0: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 0AA7EAE8: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 0AA7EB08: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 0AA7EB28: 0C2F0B4F 0C2E0000 + 10B4F (mcmpgdmux.dll)
0AA7EB2C: 67474E48 66700000 + D74E48
0AA7EB30: 674C0E48 66700000 + DC0E48
0AA7EB34: 0AA7EBBC 0A980000 + FEBBC
> 0AA7EB38: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0AA7EB70: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0AA7EB74: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 0AA7EB7C: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 0AA7EB88: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 0AA7EB98: 232135CA 23200000 + 135CA (mcmpegin.dll)
> 0AA7EBB8: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 0AA7EBD8: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 0AA7EC08: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 0AA7EC28: 23216DFD 23200000 + 16DFD (mcmpegin.dll)
> 0AA7EC68: 23218527 23200000 + 18527 (mcmpegin.dll)
> 0AA7EC98: 2323A5C2 23200000 + 3A5C2 (mcmpegin.dll)
> 0AA7ECAC: 7C931C41 7C900000 + 31C41 (ntdll.dll)
> 0AA7ECB0: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 0AA7ECF4: 01050104 00400000 + C50104 (vegas80.exe)
- - -
0AA7FFF0: 00000000
0AA7FFF4: 0059E390 00400000 + 19E390 (vegas80.exe)
0AA7FFF8: 0571BDB8 05570000 + 1ABDB8
0AA7FFFC: 00000000


I have tried everything, deinstalled Vegas 8.0, deinstalled .NET Framework 1.1 up to 3.0, Quick Time 7.2
The installation was flawless but still problems
It's not the SD, I could work with up 1 hour material, worked in a similar procedure. If I add HDV only, the same scenes like in my actual project, I get the message. I have tried the same material on Vegas 7.0 and it works fine, so I can exclude the material of the cameras. It's also not possible to render this project or a smaller version of this as MPEG

What the hell is going on with my system? Can someone help?


Thanks

Axel

Comments

CorTed wrote on 11/2/2007, 2:13 PM
I used to run into this a lot. It always seems to be Exception 0xC0000005 that shows up in the crashs info.
I am running Vista, I think it may be due to Vista. But I ended up splitting up my projects into smaller chunks and the problem went away. Don't ask me why, but try to downsize (less in physical memory) the project and see what happens.

Ted
darg wrote on 11/2/2007, 5:46 PM
Hi,

the project is not even 3 minutes long, how should someone work with this if he is more professional than I am and needs to get a video of an hour done? It can't be possible that I need a $499 Dollar software on a $1500 computer to make projects one for each scene :-)
I'm not using Vista, I have XP Pro and a more complex project is running on a smaller computer under Vegas 7.0 but the preview is not nice :-) That was the reason why I got a new one and now I'm getting nothing done!!!
How is Sony reacting to all these bugs? I was researching some other forums and even if my problems seems to be special there are a lot other bugs out there but never a solution to that.

Axel
darg wrote on 11/3/2007, 2:36 PM
It's getting better and better! After complete machine reinstallation with XP only and the needed Quick Time I got different events.

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module 'mcmpgvdec.dll' at Address 0x23000000 + 0x3B990
Thread: VideoCache ID=0xA8C Stack=0x3DDE000-0x3DE0000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010212
EBX=00000000 SS=0023 ESP=03ddeff4 EBP=03ddf00c
ECX=03ddefd0 DS=0023 ESI=00000010 FS=003b
EDX=7c90eb94 ES=0023 EDI=000023c8 GS=0000
Bytes at CS:EIP:
2303B990: 89 3B EB 95 8D B6 00 00 .;......
2303B998: 00 00 8D BF 00 00 00 00 ........
Stack Dump:
03DDEFF4: 03DDEF94 03CE0000 + FEF94
03DDEFF8: 00000014
03DDEFFC: 03DDEF58 03CE0000 + FEF58
03DDF000: 01204800 01150000 + B4800 (vegas80k.dll)
03DDF004: 01204800 01150000 + B4800 (vegas80k.dll)
03DDF008: 00005A00
03DDF00C: 03DDF09C 03CE0000 + FF09C
03DDF010: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
03DDF014: 01204800 01150000 + B4800 (vegas80k.dll)
03DDF018: 00000010
03DDF01C: 02959A20 02930000 + 29A20
03DDF020: 02959A00 02930000 + 29A00
03DDF024: 77C2C2E3 77C10000 + 1C2E3 (msvcrt.dll)
03DDF028: 3EE37B60 3E0C0000 + D77B60
03DDF02C: 03DDF0F0 03CE0000 + FF0F0
03DDF030: 00000001
> 03DDF040: 01204800 01150000 + B4800 (vegas80k.dll)
03DDF044: 02959C18 02930000 + 29C18
> 03DDF048: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
03DDF04C: 03DDF060 03CE0000 + FF060
03DDF050: 02959C28 02930000 + 29C28
> 03DDF070: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 03DDF074: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 03DDF078: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 03DDF080: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 03DDF0A0: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 03DDF0C0: 0BC10B4F 0BC00000 + 10B4F (mcmpgdmux.dll)
03DDF0C4: 3AB8D848 3A0C0000 + ACD848
03DDF0C8: 3ABD9848 3A0C0000 + B19848
03DDF0CC: 03DDF154 03CE0000 + FF154
> 03DDF0D0: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 03DDF0F8: 011B1DAC 01150000 + 61DAC (vegas80k.dll)
- - -
03DDFFF0: 00000000
03DDFFF4: 00598AE0 00400000 + 198AE0 (vegas80.exe)
03DDFFF8: 00ADA7FC 00400000 + 6DA7FC (vegas80.exe)
03DDFFFC: 00000000



Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) WRITE:0x1 IP:0x50002CA
Thread: GUI ID=0x4B0 Stack=0x12A000-0x130000
Registers:
EAX=00000001 CS=001b EIP=050002ca EFLGS=00010206
EBX=0012a104 SS=0023 ESP=0012a0dc EBP=0012a118
ECX=050002ca DS=0023 ESI=7d57aae8 FS=003b
EDX=474e5543 ES=0023 EDI=3f072480 GS=0000
Bytes at CS:EIP:
050002CA: 00 00 00 00 00 00 00 00 ........
050002D2: 00 00 00 00 00 00 00 00 ........
Stack Dump:
0012A0DC: 231C53DC 23000000 + 1C53DC (mcmpgvdec.dll)
0012A0E0: 00000001
0012A0E4: 00000001
0012A0E8: 432B2B00 42E20000 + 492B00
0012A0EC: 474E5543 47110000 + 3D5543
0012A0F0: 3F072480 3E0C0000 + FB2480
0012A0F4: 0012A104 00030000 + FA104
0012A0F8: 0012A10C 00030000 + FA10C
0012A0FC: 231C4CB0 23000000 + 1C4CB0 (mcmpgvdec.dll)
0012A100: 0012A0C0 00030000 + FA0C0
0012A104: 03DDF0F0 03CE0000 + FF0F0
0012A108: 0012A148 00030000 + FA148
0012A10C: 3F072480 3E0C0000 + FB2480
0012A110: 7D57AAE8 7D4A0000 + DAAE8
0012A114: 001C0000 00140000 + 80000
0012A118: 0012A128 00030000 + FA128
> 0012A11C: 231C47C5 23000000 + 1C47C5 (mcmpgvdec.dll)
> 0012A12C: 231C34B2 23000000 + 1C34B2 (mcmpgvdec.dll)
> 0012A134: 231D4C58 23000000 + 1D4C58 (mcmpgvdec.dll)
> 0012A138: 231C4DD0 23000000 + 1C4DD0 (mcmpgvdec.dll)
> 0012A160: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0012A164: 231C735C 23000000 + 1C735C (mcmpgvdec.dll)
> 0012A16C: 231C3450 23000000 + 1C3450 (mcmpgvdec.dll)
> 0012A18C: 231C350A 23000000 + 1C350A (mcmpgvdec.dll)
> 0012A19C: 0BC10B4F 0BC00000 + 10B4F (mcmpgdmux.dll)
0012A1A0: 3BB2EE48 3A0C0000 + 1A6EE48
0012A1A4: 7D57AF48 7D4A0000 + DAF48
0012A1A8: 0012A26C 00030000 + FA26C
0012A1AC: 00000001
> 0012A1C0: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0012A1C4: 231C7370 23000000 + 1C7370 (mcmpgvdec.dll)
> 0012A1CC: 231C3528 23000000 + 1C3528 (mcmpgvdec.dll)
> 0012A1EC: 23024BB9 23000000 + 24BB9 (mcmpgvdec.dll)
> 0012A214: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0012A21C: 2302D629 23000000 + 2D629 (mcmpgvdec.dll)
> 0012A24C: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 0012A284: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 0012A288: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 0012A290: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 0012A29C: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 0012A2CC: 23029B99 23000000 + 29B99 (mcmpgvdec.dll)
> 0012A2FC: 23027D9C 23000000 + 27D9C (mcmpgvdec.dll)
> 0012A31C: 2302612B 23000000 + 2612B (mcmpgvdec.dll)
> 0012A33C: 2322735F 23200000 + 2735F (mcmpegin.dll)
> 0012A36C: 2322C39C 23200000 + 2C39C (mcmpegin.dll)
> 0012A3CC: 33BBAF4B 33BB0000 + AF4B (mcplug.dll)
> 0012A3EC: 7C913E62 7C900000 + 13E62 (ntdll.dll)
> 0012A400: 003A0045 00360000 + 40045 (sfwbdmux.dll)
> 0012A404: 0054005C 00400000 + 14005C (vegas80.exe)
> 0012A408: 00650068 00400000 + 250068 (vegas80.exe)
> 0012A40C: 00520020 00400000 + 120020 (vegas80.exe)
> 0012A410: 0061006F 00400000 + 21006F (vegas80.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0083C9AB 00400000 + 43C9AB (vegas80.exe)
0012FFFC: 00000000


The latter one was coming after setting in Options/Video the render to 1 and dynamic RAM to 0. After that I changed both to nearly max but it jumped back to first.

Is there a known issue with the NVDIA 8800 GTS? The two latter ones sounded more like graphics problem?

Thanks

Axel
marts wrote on 11/3/2007, 2:50 PM
Did you try to run any other program beside Vegas on your computer just to test if perhaps something is not wrong with your hardware? Because it might be for example RAM problem. Microsoft has an useful tool called Windows Memory Diagnostic, you can download it here: http://oca.microsoft.com/en/windiag.asp
darg wrote on 11/3/2007, 5:51 PM
Hi,

yes, I tried Windiag and evertyhing is fine, because it looks like a hardware issue. I have tried to update the graphics BIOS but I don't have a floppy drive available which is recognized at startup. I have one at work and can do it in the evening. I will also get a backup graphics card from Frys for a couple of dollars just to make sure that Vegas can work with my 8800GTS.
I have tried already the test of NVidia but it was OK.
In regard to other software I have nothing which can work with HD because it's only triggert by HD material. With SD it's working fine. The thing is, I can render to HDV if I have m2t in the project but I can if it's SD only.
I double checked my m2t files, recaptured everything and tested for dropped frames - is OK. HDVSplitt worked without issues even with activated stop at dropped frames. Not even one was lost.

One very interesting thing is, that the update function of Quick Time is producing a Visual C++ failure message. Can this be related?

Regards

Axel
Laurence wrote on 11/3/2007, 7:02 PM
My guess is that one of your HDV clips is corrupted. Can you drag and test by previewing them (the HDV clips) to a fresh timeline in order to see which HDV clip might be causing the problem.
Laurence wrote on 11/3/2007, 7:03 PM
Another thing that will currently cause Vegas to crash is if you try to render HDV video with the 32 bit rather than 8 bit option.
darg wrote on 11/3/2007, 8:50 PM
I have never used the 32 bit, it's on 8 for sure.
In regard to pull clips in the timeline I tried several combinations including and excluding the affected clips:

30 to 50 clips fit in the timeline before it crashed. Same thing when I preview them in the explorer, 30 to 50 are OK, then it crashed.

To make sure that I have good material I captured my tapes again and will test them again.

I also have a new graphics card. I will see if it is driver dependent.

Thanks

Axel


darg wrote on 11/3/2007, 10:04 PM
OK, it's not the graphics adapter. Maybe the vendor? It's also a NVidia. Is there a known issue on Sonys site? Is here someone from Sony reading and posting?

Thanks

Axel
Laurence wrote on 11/4/2007, 12:26 AM
I'll bet it's not 30 to 50 clips but rather a corrupted m2t clip that is maybe among clips 50 to 60. Vegas can do lots and lots of m2t clips. Around Vegas 6 this was an issue but it hasn't been at all in 7 or 8. I still think you have a corrupted m2t clip. Once you figure out which clip it is you can use a program like MPEG VCR from womble.com to fix it, but you have to figure out which clip it is first.

Do a search of this forum and you'll see a lot of references to this.
Kevin Schmidt wrote on 12/12/2007, 6:50 AM
Have you discovered the problem causing the access violation? I am seeing a similar access violation in my project and it currently has no video clips, only pictures. (300+ sill images from a Sony Alpha SLR @ 10megapixels jpg)
I am trying to render using floating so I'll give the suggestion to try 8bit a go and see what happens.
My system has an ATI video card so that points to something other than video card vendor.
darg wrote on 12/12/2007, 1:04 PM
Hi Kevin,

my problem is solved since I recapture all my tapes directly with Vegas. I have used HDVSplitt before and have never tried Vegas since my verion 7 did not recognized my HV10.
I´m also using Vegas in 8Bit only since I have no idea if floating 32 is what I need :-) At the moment it works with 8Bit fine.

Regards

Axel