Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro Another Vegas crashing issue!

  • Another Vegas crashing issue!

    Posted by Mark Found on August 4, 2008 at 4:54 pm

    Hi there
    my Vegas pro keeps crashing – seems to be when I’m adding clips to the project. Have tried various suggestions on the forums but not getting anywhere at all.
    After many trials it doesn’t even appear to be crashing when one particular clip is imported into the project – sometimes it’ll be fine and then next time . . . !

    When the programme opens I get this error message:

    16 Bit Windows Subsystem
    C:\PROGRA~1|Symantec|S32EVNT1.DLL An installable Virtual Device Driver failed Dll initialization. Choose close to terminate the application

    I’m guessing this must be having an effect but what to do to correct it I’ve no idea!

    I’ve run several registry cleaners/bug fixers etc.

    I’m capturing from a JVC GY- HD111 and this has been problem free in the past – what seemed to happen rarely is now happening ALL the time! I can only edit for a short time before it crashes again.

    I’m saving after virtually every edit I make on the timeline but it’s no way to carry on.

    When Pro crashes this is the exception message:

    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: GUI ID=0x8DC Stack=0x133000-0x140000
    Registers:
    EAX=00000001 CS=001b EIP=2303b990 EFLGS=00210202
    EBX=00000000 SS=0023 ESP=00133c1c EBP=00133c34
    ECX=0000000a DS=0023 ESI=00000010 FS=003b
    EDX=7c90eb94 ES=0023 EDI=00002454 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:
    00133C1C: 00133BBC 00040000 + F3BBC
    00133C20: 02DD15A0 02DB0000 + 215A0
    00133C24: 00133C84 00040000 + F3C84
    00133C28: 00AA0000 00400000 + 6A0000 (vegas80.exe)
    00133C2C: 00AA0000 00400000 + 6A0000 (vegas80.exe)
    00133C30: 00005000
    00133C34: 00133CC4 00040000 + F3CC4
    00133C38: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
    00133C3C: 00AA0000 00400000 + 6A0000 (vegas80.exe)
    00133C40: 00000010
    00133C44: 02DD15A0 02DB0000 + 215A0
    00133C48: 02DD1580 02DB0000 + 21580
    00133C4C: 000002D0
    00133C50: 00000500
    00133C54: 00000006
    00133C58: 02DD15A0 02DB0000 + 215A0
    > 00133C68: 00AA0000 00400000 + 6A0000 (vegas80.exe)
    00133C6C: 5FA25BC8 5F350000 + 6D5BC8
    > 00133C70: 23030F82 23000000 + 30F82 (mcmpgvdec.dll)
    00133C74: 02DD15A0 02DB0000 + 215A0
    00133C78: 5FA25BD8 5F350000 + 6D5BD8
    > 00133C98: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
    > 00133C9C: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
    > 00133CA0: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
    > 00133CA8: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
    > 00133CC8: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
    > 00133CD8: 23028344 23000000 + 28344 (mcmpgvdec.dll)
    > 00133CF8: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
    > 00133D28: 01336DEF 01150000 + 1E6DEF (vegas80k.dll)
    00133D2C: 05751300 056B0000 + A1300
    > 00133D30: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
    > 00133D34: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
    00133D38: 00133D5C 00040000 + F3D5C
    > 00133D3C: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
    > 00133D48: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
    > 00133D78: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
    > 00133D98: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
    > 00133DC8: 23026179 23000000 + 26179 (mcmpgvdec.dll)
    > 00133DE8: 23216DFD 23200000 + 16DFD (mcmpegin.dll)
    > 00133E28: 23218527 23200000 + 18527 (mcmpegin.dll)
    > 00133E58: 2323A5C2 23200000 + 3A5C2 (mcmpegin.dll)
    > 00133E7C: 7E418B26 7E410000 + 8B26 (USER32.dll)
    > 00133E98: 7E4188D1 7E410000 + 88D1 (USER32.dll)
    > 00133EA4: 7E4188DA 7E410000 + 88DA (USER32.dll)
    > 00133EAC: 005AF480 00400000 + 1AF480 (vegas80.exe)
    – – –
    0013FFF0: 00000000
    0013FFF4: 00000000
    0013FFF8: 0083C9AB 00400000 + 43C9AB (vegas80.exe)
    0013FFFC: 00000000

    Any ideas? I’ve got Adobe Premiere Pro 3 but really don’t want to use it as Vegas has been great up until a couple of weeks ago and there’s been no conflict of interest for the last year when I’ve had both on the computer. Have done the old restore point thing too.

    Thanks, in advance, for any help
    Mark Found

    Steve Rhoden replied 18 years, 1 month ago 2 Members · 6 Replies
  • 6 Replies
  • Steve Rhoden

    August 4, 2008 at 6:30 pm

    C:PROGRA~1|Symantec|S32EVNT1.DLL An installable Virtual Device Driver failed Dll initialization

    This error report seems (maybe)to have something to do with a virtual drive installed on your computer…are you using daemon tools or any virtual drive emulator running on your system.

    Or, do you have Norton Antivirus installed on there? If so, is it causing some other problem?

    Steve Rhoden
    Creative Director
    TNX EFFECTS STUDIOS.
    http://www.youtube.com/hentys

  • Mark Found

    August 4, 2008 at 6:59 pm

    Well, Steve, this may well be the problem – but, unfortunately I don’t have the skills to know what virtual drives are and where they should be. I know I don’t have Norton Anti Virus – but that “Symantec” in the error message is screaming out at me!
    I’m not afraid to go into the system to investigate – but where should I go?
    Thanks, by the way, for the speedy response.

  • Steve Rhoden

    August 4, 2008 at 9:23 pm

    Well Mark,
    If you don’t know what is meant by a virtual drive, its likely you do not have it on your system (it is in fact the process of creating the illusion in your computer that it has extra drives, primarly for
    opening iso files among other features or run a programme directly from it
    ).

    Well i can then confidently tell you that something is conflicting
    with sony vegas. And no amount of reinstalling and configuring vegas
    is gonna solve the problem, you have to first rid your system of the
    offending file/files that i think is hidden in the registry that’s causing this conflict.

    Just in case there is a corrupt file there somewhere, try this:
    press start on your task bar….then run…type in: chkdsk c:/f
    then press ok….a prompt should come up telling you that check
    disc will run when the computer restarts or somthinge like that..
    type y then enter….Do this process twice just to make sure.
    Restart your computer and it should start its disk checking
    process….if it doesn’t…restart again until it does.

    BTW…..Where you once using Norton Antivirus?

    Steve Rhoden
    Creative Director
    TNX EFFECTS STUDIOS.
    http://www.youtube.com/hentys

  • Mark Found

    August 4, 2008 at 9:30 pm

    Just to update you I’ve fixed the driver problem:

    This error occurs if the registry value VDD located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers becomes corrupted. To fix this, simply delete the VDD value in the above key and replace it with another named VDD with of the type REG_MULTI_SZ.

    Windows XP instructions:

    1. Click Start->Run and type Regedit. Click OK
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers
    3. Delete the VDD value
    4. Click Edit->New->Multi-String Value
    5. Name the value VDD, press Enter

    Windows 2000 instructions:

    With Windows 2000 you must use regedt32.exe instead of regedit.exe. The regular regedit will not allow you to add REG_MULTI_SZ’s for some odd reason and a regular string value will not work in this instance.

    Aside from that, the instructions are the same.

    It also may be necessary to extract the original autoexec.nt and config.nt from your Windows CD, as they may be corrupted.

    1. Click Start->Run and type expand x:\I386\autoexec.nt_ %systemroot%\System32\autoexec.nt (Where x: is your CD-ROM drive)
    2. Click Start->Run and type expand x:\I386\config.nt_ %systemroot%\System32\config.nt
    3. Click Start->Run and type expand x:\I386\command.co_ %systemroot%\System32\command.com

    You should be up and running now.

    And many thanks to tweeksforgeeks.com for that. Vegas is still crashing on what appears to be random clips as I import them intoi the project. I’ll report back if and when I resolve for those with similar issues

  • Mark Found

    August 4, 2008 at 11:52 pm

    Okay, latest update – not ignoring you, Steve – and I’m trying what you’re suggesting. But, just before I restart yet again, and for the sake of anyone in the same boat – I’m having a lot more success at importing clips from my capture folder if I do it in “detail” mode. However, having importing loads, as soon as I switch to “thumbnails” the programme crashes. Could this be something to do with windows explorer? And if so, is there a way of disabling it?
    BTW, yes, Steve, I did once have Norton installed – it came with the computer. Have tried to get rid of it but it’s a pretty resilient fellow!

  • Steve Rhoden

    August 5, 2008 at 12:33 pm

    Well i would say get rid of all traces of Norton off your system, because it is still there…..and see how things behaves afterwards. Here is a link for the ‘Norton removal tool’:
    https://service1.symantec.com/Support/tsgeninfo.nsf/docid/2005033108162039

    Steve Rhoden
    Creative Director
    TNX EFFECTS STUDIOS.
    http://www.youtube.com/hentys

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