Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Sony Vegas Pro 8.0c keeps crashing – project due in 1 week

  • Sony Vegas Pro 8.0c keeps crashing – project due in 1 week

    Posted by Erik Martin on December 8, 2010 at 5:48 pm

    I desperately need help – I’ve been using Sony Vegas Pro 8.0c for a few weeks to create a Christmas video project for my grandparents, and since yesterday, the program keeps crashing due to an “exception” problem (pasted below). I’ve tried remvoing/reinstalling the program several times, installing the latest MS .Net framework 4.0/MS redistributable C++ package, Windows updates, etc., but it keeps crashing with the same “exception” error message. Any help is appreciated.

    My system is a Dell Inspiron 531s,2.6GHz AMD Athlon 64 X2 5000+ dual core processor, Windows 7 professional 64 bit (yes, I use Vegas with Win XP compatibility mode service pack 3 and run as “administrator”), 4 GB RAM, 256MB Nvidia GeForce 8600GT 3D card, 1 TB hard drive. Here is the error message 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=0xEBC Stack=0x6ACF000-0x6AD0000
    Registers:
    EAX=00000001 CS=0023 EIP=2303b990 EFLGS=00010202
    EBX=00000000 SS=002b ESP=06acf6dc EBP=06acf6f4
    ECX=48530000 DS=002b ESI=00000010 FS=0053
    EDX=05ece8b8 ES=002b EDI=0000345c GS=002b
    Bytes at CS:EIP:
    2303B990: 89 3B EB 95 8D B6 00 00 .;……
    2303B998: 00 00 8D BF 00 00 00 00 ……..
    Stack Dump:
    06ACF6DC: 06ACF67C 069D0000 + FF67C
    06ACF6E0: 04E4DCC0 04CC0000 + 18DCC0
    06ACF6E4: 06ACF744 069D0000 + FF744
    06ACF6E8: 003FFC00
    06ACF6EC: 003FFC00
    06ACF6F0: 00002D00
    06ACF6F4: 06ACF784 069D0000 + FF784
    06ACF6F8: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
    06ACF6FC: 003FFC00
    06ACF700: 00000010
    06ACF704: 04E4DCC0 04CC0000 + 18DCC0
    06ACF708: 58B92CA0 58B50000 + 42CA0
    06ACF70C: 00000030
    06ACF710: 76DAD0C5 76DA0000 + D0C5 (KERNELBASE.dll)
    06ACF714: 0000199C
    06ACF718: 00000000
    > 06ACF758: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
    > 06ACF75C: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
    > 06ACF760: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
    > 06ACF768: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
    > 06ACF788: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
    > 06ACF79C: 2302D06E 23000000 + 2D06E (mcmpgvdec.dll)
    > 06ACF7B8: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
    > 06ACF7BC: 047D1CFE 047C0000 + 11CFE (mcmpgdmux.dll)
    06ACF7C0: 00000100
    06ACF7C4: 66A50772 66A50000 + 772
    06ACF7C8: 04E4DCC0 04CC0000 + 18DCC0
    06ACF7CC: 58B92CA0 58B50000 + 42CA0
    > 06ACF7F0: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
    > 06ACF7F4: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
    > 06ACF7FC: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
    > 06ACF808: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
    > 06ACF81C: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
    > 06ACF838: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
    > 06ACF858: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
    > 06ACF888: 23026179 23000000 + 26179 (mcmpgvdec.dll)
    > 06ACF8A8: 232134FA 23200000 + 134FA (mcmpegin.dll)
    > 06ACF8CC: 23213AB9 23200000 + 13AB9 (mcmpegin.dll)
    > 06ACF8EC: 23234DCC 23200000 + 34DCC (mcmpegin.dll)
    > 06ACF918: 00E74800 00400000 + A74800 (vegas80.exe)
    06ACF91C: 00000000
    06ACF920: 00024000
    06ACF924: 00000000
    06ACF928: 00000000
    > 06ACF944: 33BB5C7F 33BB0000 + 5C7F (mcplug.dll)
    > 06ACF960: 33BB61C6 33BB0000 + 61C6 (mcplug.dll)
    > 06ACF9A8: 76DAE37D 76DA0000 + E37D (KERNELBASE.dll)
    > 06ACF9C4: 33BBAA5A 33BB0000 + AA5A (mcplug.dll)
    > 06ACFA00: 006B583B 00400000 + 2B583B (vegas80.exe)
    06ACFA04: 03EB3874 03D00000 + 1B3874
    06ACFA08: 00000371
    06ACFA0C: 00000000
    06ACFA10: 06ACFA40 069D0000 + FFA40
    > 06ACFA44: 7580A3BD 757E0000 + 2A3BD (kernel32.dll)
    > 06ACFA74: 0147B664 013C0000 + BB664 (vegas80k.dll)
    06ACFA78: 7821B340 77C90000 + 58B340
    06ACFA7C: 06ACFA98 069D0000 + FFA98
    06ACFA80: 00000028
    06ACFA84: 6544C768 64790000 + CBC768
    > 06ACFAD8: 77B3E592 77B10000 + 2E592 (ntdll.dll)
    > 06ACFAE8: 003C1A6C 003B0000 + 11A6C (ADvdDiscHlp.dll)
    > 06ACFAEC: 77B3E5C5 77B10000 + 2E5C5 (ntdll.dll)
    > 06ACFAF0: 707602FB 6FBE0000 + B802FB (System.Windows.Forms.ni.dll)
    > 06ACFB04: 77B3DE63 77B10000 + 2DE63 (ntdll.dll)
    > 06ACFB08: 757E0000 757E0000 + 0 (kernel32.dll)
    > 06ACFB10: 003B0000 003B0000 + 0 (ADvdDiscHlp.dll)
    – – –
    06ACFFF0: 00000000
    06ACFFF4: 0059B990 00400000 + 19B990 (vegas80.exe)
    06ACFFF8: 00AE9C84 00400000 + 6E9C84 (vegas80.exe)
    06ACFFFC: 00000000

    Sebastien Gravel replied 15 years, 4 months ago 4 Members · 6 Replies
  • 6 Replies
  • Mike Kujbida

    December 8, 2010 at 6:35 pm

    Sony are the only folks who can truly understand those error messages so you’d have to send it to them for analysis.

    Have you installed ANY other software recently besides the ones you mentioned?

    If it crashes at the same place each time, I’d suspect a bad piece of media.
    Try replacing it with something else (like Color Bars so it stands out) and see what happens.

    Is this for a DVD?
    Try rendering out to an AVI file first and then bring that back into Vegas for rendering to DVD.

  • Erik Martin

    December 8, 2010 at 7:03 pm

    Thanks for your quick reply. Vegas had been working fine for several days until yesterday; yes, it could be the last MPEG 2 clip I added that is causing my project to crash; but every time I try to re-open the project file (or even the .bak file, for that matter), I immediately get the exception error once it fully loads, with no option to remove that last clip, render video or edit further. I suspect that the entire project file is damaged/corrupted/non-repairable. Luckily, I outputted my project to AVI 2 days ago and can edit from that, but that means I lost the last 6 hours of work.

    Do I need to change any settings under “preferences”, by the way, to decrease chances of crashing?

    Lastly, I do remember seeing a separate Windows error message after rebooting 2 days ago (before the Vegas crashing problem started) indicating some kind of fault/exception with MS .NET Framework (I think it was 3.5). I’ve since upgraded to .NET 4.0.

  • Mike Kujbida

    December 8, 2010 at 7:27 pm

    “it could be the last MPEG 2 clip I added that is causing my project to crash”

    What I would try first is to load the problem clip only into a new instance of Vegas.
    If it still crashes, then it’s definitely the cause.
    If it doesn’t, render it out to another format (DV-AVI if it’s SD format).
    Move the problem clip from it’s current location to a new one, start Vegas and load the project.
    When it can’t find the missing MPEG-2 clip, it’ll give you a few options.
    Point it to the newly rendered DV-AVI file and it should continue to load properly.
    Re-save the project under a new name and continue editing.

    “Do I need to change any settings under “preferences”, by the way, to decrease chances of crashing?”

    I stand to be corrected but there’s nothing specific that I’m aware of.

  • Erik Martin

    December 8, 2010 at 7:33 pm

    Good suggestions–I’ll try them. Thanks so much!

    But if anyone else can suggest a reason/solution for why my Vegas keeps crashing, based on the symptoms I posted above, please post. I would greatly appreciate it.

  • Dave Haynie

    December 9, 2010 at 9:41 am

    If it’s related to that newly added clip, there’s a good chance the clip is mal-formed in some way. Again, as Mike said, only Sony software engineers are going to make much out of the stack dump you provided.

    Vegas is not very good at dealing with file corruption. I suspect that’s intentional — when you assume a file might be bad, you need all sorts of checks that slow down the processing of normal files.

    If this was a DV or HDV capture, you can try to re-acquire it from the camera… capture glitches are as common as they used to be, but they sill occur. There are tools for filtering out glitches, too, if there’s a problem with the tape. Some places to look:

    https://www.videohelp.com/tools/sections/video-repair-fix
    https://home.roadrunner.com/~mwilczyn/mpeg2repair/

    -Dave

  • Sebastien Gravel

    December 14, 2010 at 3:19 am

    You could also delete/move the “supposed” offending file from it’s current location. Then start Vegas. It will give an error message of missing media, but at least you’ll be able to open the project.

    You can then try to convert the malformed media using another instance of Vegas or some other conversion tool.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy