-
Specific .veg file causes Vegas to Crash
Here’s my situation. I was editing many, many clips. Everything was working seamlessly, until I was about to drag in a file, when everything froze, and crashed. It was about 30 minutes of footage, taking me about 70 hours to edit; so I’m pretty desperate.
Now when I open the file again, it begins to load. Once it finishes loading, it crashes seconds later. Other files work perfectly.
In an attempt to solve the problem, I open 2 vegas windows, go to my explorer, and click and drag the file I want onto the other vegas window. It is now able to load, and but it still receives constant freezes and crashes. When I try to render the file, it either just crashes, or stays at 0%. It again only happens on these two files. For some reason, some clips have a red or green thumbnail on the timeline.
Here is the error I get:
Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module ‘mcmpgvdec.dll’ at Address 0x23000000 + 0x3B990
Thread: VideoCache ID=0x1698 Stack=0x67FF000-0x6800000
Registers:
EAX=00000001 CS=001b EIP=2303b990 EFLGS=00010202
EBX=00000000 SS=0023 ESP=067ff6dc EBP=067ff6f4
ECX=067ff6b4 DS=0023 ESI=00000010 FS=003b
EDX=776f9a94 ES=0023 EDI=00001bec 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:
067FF6DC: 067FF67C 06700000 + FF67C
067FF6E0: 04EB2C00 04E70000 + 42C00
067FF6E4: 067FF744 06700000 + FF744
067FF6E8: 003FFC00
067FF6EC: 003FFC00
067FF6F0: 00002D00
067FF6F4: 067FF784 06700000 + FF784
067FF6F8: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
067FF6FC: 003FFC00
067FF700: 00000010
067FF704: 04EB2C00 04E70000 + 42C00
067FF708: 0224B7A8 02160000 + EB7A8
067FF70C: 0224B7A8 02160000 + EB7A8
067FF710: 00000000
067FF714: 00000001
067FF718: 00000001
> 067FF758: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 067FF75C: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 067FF760: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 067FF768: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 067FF788: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 067FF79C: 2302D06E 23000000 + 2D06E (mcmpgvdec.dll)
> 067FF7B8: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 067FF7BC: 03AC1CFE 03AB0000 + 11CFE (mcmpgdmux.dll)
067FF7C0: 00000100
067FF7C4: 7156006C 71560000 + 6C
067FF7C8: 04EB2C00 04E70000 + 42C00
067FF7CC: 0224B7A8 02160000 + EB7A8
> 067FF7F0: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 067FF7F4: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 067FF7FC: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 067FF808: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 067FF81C: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 067FF838: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 067FF858: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 067FF888: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 067FF8A8: 232134FA 23200000 + 134FA (mcmpegin.dll)
> 067FF8CC: 23213AB9 23200000 + 13AB9 (mcmpegin.dll)
> 067FF8EC: 23234DCC 23200000 + 34DCC (mcmpegin.dll)
> 067FF920: 776A9834 776A0000 + 9834 (ntdll.dll)
> 067FF92C: 77708B2C 776A0000 + 68B2C (ntdll.dll)
> 067FF930: 77708752 776A0000 + 68752 (ntdll.dll)
> 067FF944: 33BB5C7F 33BB0000 + 5C7F (mcplug.dll)
> 067FF960: 33BB61C6 33BB0000 + 61C6 (mcplug.dll)
> 067FF9A8: 76D3B887 76CF0000 + 4B887 (kernel32.dll)
> 067FF9C4: 33BBAA5A 33BB0000 + AA5A (mcplug.dll)
> 067FFA00: 006B583B 00400000 + 2B583B (vegas80.exe)
067FFA04: 1A4132B4 1A3B0000 + 632B4
067FFA08: 00002913
067FFA0C: 00000000
067FFA10: 067FFA40 06700000 + FFA40
> 067FFA44: 76D39F78 76CF0000 + 49F78 (kernel32.dll)
> 067FFA74: 0191B664 01860000 + BB664 (vegas80k.dll)
067FFA78: 592BB280 588D0000 + 9EB280
067FFA7C: 067FFA98 06700000 + FFA98
067FFA80: 00000028
067FFA84: 7E0D1FA8 7D370000 + D61FA8
> 067FFAE4: 776A9834 776A0000 + 9834 (ntdll.dll)
> 067FFAEC: 04B599E3 04AF0000 + 699E3 (CFHD.dll)
067FFAF0: 00000000
067FFAF4: 00000003
> 067FFAF8: 04AF1038 04AF0000 + 1038 (CFHD.dll)
067FFAFC: 00000003
067FFB00: 00009FC0
> 067FFB14: 04B4EB01 04AF0000 + 5EB01 (CFHD.dll)
– – –
067FFFF0: 00000000
067FFFF4: 0059B990 00400000 + 19B990 (vegas80.exe)
067FFFF8: 00AE9C84 00400000 + 6E9C84 (vegas80.exe)
067FFFFC: 00000000 -
14 Replies
-
Did you try to open the automatic backup file from Vegas? That one might be created before something happened to your veg-file.
(I suppose you didn’t make back-ups with different cversions?)Theo
-
What’s an automatic backup file? And no, I didn’t make backups unfortunately 🙁
-
Look in the folder where you store your veg file. Probably you will find there another file withe the same name ending with .veg.bak
rename this file to something ending with .veg and try to open it in Vegas. This backup file could be still fine.Theo
-
It still crashed :/.
I had enough time to copy the timeline, copy and paste it onto another timeline. This one doesn’t freeze after it loads. I would like to render it just so I don’t have to worry anymore, but it stays at 0% when rendering. I am rendering at HD settings, to a MPEG1.
Is it the settings? I tried the same settings to a 5 second clip, and it took like 2-4 minutes to render.
-
Sorry to hear that it didn’t work out well.
I don’t know what you would like to make (DVD, Blueray), but MPEG1 files are used for (low quality) videoCDs. That is certainly not what you should use.
Theo
-
Should i try .wmv?
Why do I keep crashing/freezing? -
I upgraded to vegas 9.0.
No more freezing. I can open it, but I can’t render :/
It stays at 0%
I am using .wmv format now -
Good that you can open your project in Vegas 9. But are the red and green thumbnails gone?
I would be very much worried that you are dealing with a hardware problem (memory defect?). Probably John Rofrano can tell you more about this.Theo
-
Yes, the red and green thumbnails are gone. Why is the rendering process not working though? It just stays at 0. What can I do?
-
I am a total newbie to Vegas, and don’t know much, but until John Rofrano can get here, try running a scan on your memory modules, to make sure they are OK.
Norman Willis
http://www.nazareneisrael.org
servant@nazareneisrael.org
Reply to this Discussion! Login or Sign Up