Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums VEGAS Pro “An error ocurred during operation” — Sony shuts down!

  • “An error ocurred during operation” — Sony shuts down!

    Posted by Andre Anthonio on June 8, 2009 at 10:30 pm

    Hello, folks:

    Posting this at some risk because I haven’t first searched for answers outside of the forum because I’m feeling like this one may be a bit technically advanced. And, for sure, this one, like many others, is driving me crazy and I’m near the end of my roper. Watch the 11:00 news to find out if I offed myself (just joking).

    Problem: When editing in my project, I’m noticing that there are occasional drops in the video. In other words the video dips to black for a second or so. I first thought it was a bad tape but it’s a brand new first time use tape. Maybe it’s a bad capture?

    When I try to cut the dip out (splicing before and after the loss in video) this portion of video on the time line turns to red, and seems to affect other parts of the video further along in the same time line, same video source.

    Then, out of no where I get an error message and if I select “ok”, Sony shuts down immediately.

    This is the message:

    “An error ocurred during the current operation. An Exception has occured.”

    The rest of the message is as follows:

    Sony Vegas Pro 8.0
    Version 8.0a (Build 179)
    Exception 0xC0000005 (access violation) WRITE:0x20000 IP:0x20005
    Thread: VideoCache ID=0x4910 Stack=0x8C4F000-0x8C50000
    Registers:
    EAX=00020000 CS=0023 EIP=00020005 EFLGS=00010202
    EBX=00000000 SS=002b ESP=08c4f640 EBP=08c4f698
    ECX=2c9e0001 DS=002b ESI=08c4f744 FS=0053
    EDX=00021359 ES=002b EDI=08c4f774 GS=002b
    Bytes at CS:EIP:
    00020005: 00 00 00 01 00 00 00 60 …….`
    0002000D: 26 00 00 C4 00 00 00 00 &…….
    Stack Dump:
    08C4F640: 123906AC 12340000 + 506AC (m2tsplug.dll)
    08C4F644: 2C9E0000 2C9E0000 + 0
    08C4F648: 00021359 00020000 + 1359
    08C4F64C: 08C4F67C 08B50000 + FF67C
    08C4F650: 08C4F6B8 08B50000 + FF6B8
    08C4F654: 4A54F6B4
    08C4F658: 00000001
    08C4F65C: 281A7F70 28110000 + 97F70
    08C4F660: 00000000
    08C4F664: 119FEB70 11990000 + 6EB70
    08C4F668: 00000810
    08C4F66C: 2170B080 20F20000 + 7EB080
    08C4F670: 00000001
    08C4F674: 119AD270 11990000 + 1D270
    08C4F678: 2C020000 2C020000 + 0
    08C4F67C: 2C9E0000 2C9E0000 + 0
    > 08C4F68C: 124456A2 12340000 + 1056A2 (m2tsplug.dll)
    > 08C4F69C: 1239143C 12340000 + 5143C (m2tsplug.dll)
    > 08C4F72C: 75317344 75300000 + 17344 (MSVCR80.dll)
    > 08C4F894: 371E4507 37140000 + A4507 (sfpublish.dll)
    > 08C4F8A8: 74061BAB 74030000 + 31BAB (QuickTimeEssentials.qtx)
    > 08C4F8B4: 6F376A60 6E740000 + C36A60 (QuickTime.qts)
    > 08C4F8D4: 1244A819 12340000 + 10A819 (m2tsplug.dll)
    > 08C4F8DC: 12349DA8 12340000 + 9DA8 (m2tsplug.dll)
    > 08C4F934: 1234D74D 12340000 + D74D (m2tsplug.dll)
    > 08C4F984: 1234D12A 12340000 + D12A (m2tsplug.dll)
    > 08C4FA00: 006B1E3B 00400000 + 2B1E3B (vegas80.exe)
    08C4FA04: 00000000
    08C4FA08: 0000AAA6
    08C4FA0C: 00000000
    08C4FA10: 08C4FA40 08B50000 + FFA40
    > 08C4FAC4: 77B8238B 77B50000 + 3238B (ntdll.dll)
    > 08C4FAE4: 77C02926 77B50000 + B2926 (ntdll.dll)
    > 08C4FAF0: 77B83A0D 77B50000 + 33A0D (ntdll.dll)
    > 08C4FAF4: 77B83A5E 77B50000 + 33A5E (ntdll.dll)
    > 08C4FAF8: 77430000 77430000 + 0 (kernel32.dll)
    > 08C4FB10: 77441638 77430000 + 11638 (kernel32.dll)
    > 08C4FB18: 702EC2B0 70220000 + CC2B0 (QuickTimeVR.qtx)
    > 08C4FB20: 774415F9 77430000 + 115F9 (kernel32.dll)
    > 08C4FB2C: 702C2829 70220000 + A2829 (QuickTimeVR.qtx)
    > 08C4FB30: 702ED008 70220000 + CD008 (QuickTimeVR.qtx)
    > 08C4FB38: 702BB073 70220000 + 9B073 (QuickTimeVR.qtx)
    > 08C4FB40: 702BB06B 70220000 + 9B06B (QuickTimeVR.qtx)
    > 08C4FB50: 70220000 70220000 + 0 (QuickTimeVR.qtx)
    > 08C4FB54: 77430000 77430000 + 0 (kernel32.dll)
    > 08C4FB64: 702BCCD0 70220000 + 9CCD0 (QuickTimeVR.qtx)
    > 08C4FB68: 35EBA262 35E70000 + 4A262 (sfdsound.dll)
    > 08C4FB7C: 7577385E 75770000 + 385E (msdmo.dll)
    > 08C4FB80: 75770000 75770000 + 0 (msdmo.dll)
    > 08C4FB88: 757739C4 75770000 + 39C4 (msdmo.dll)
    > 08C4FBC4: 702BCCD0 70220000 + 9CCD0 (QuickTimeVR.qtx)
    > 08C4FBCC: 75773FDE 75770000 + 3FDE (msdmo.dll)
    > 08C4FBF0: 77B7F4B5 77B50000 + 2F4B5 (ntdll.dll)
    > 08C4FBF4: 77BB2C10 77B50000 + 62C10 (ntdll.dll)
    > 08C4FC0C: 77B867E6 77B50000 + 367E6 (ntdll.dll)
    > 08C4FC84: 77BC41B8 77B50000 + 741B8 (ntdll.dll)
    > 08C4FC90: 00800002 00400000 + 400002 (vegas80.exe)
    08C4FC94: 1AE8EBE8 19EC0000 + FCEBE8
    > 08C4FC98: 77B867E6 77B50000 + 367E6 (ntdll.dll)
    08C4FC9C: 1AE8EBE7 19EC0000 + FCEBE7
    08C4FCA0: 1AE8EBE2 19EC0000 + FCEBE2
    > 08C4FCC4: 77C02926 77B50000 + B2926 (ntdll.dll)
    > 08C4FCD0: 77BB2C10 77B50000 + 62C10 (ntdll.dll)
    > 08C4FCD4: 77B7F2B8 77B50000 + 2F2B8 (ntdll.dll)
    > 08C4FCF4: 77C02926 77B50000 + B2926 (ntdll.dll)
    > 08C4FD00: 77B70982 77B50000 + 20982 (ntdll.dll)
    > 08C4FD04: 77B86643 77B50000 + 36643 (ntdll.dll)
    > 08C4FD1C: 77B50000 77B50000 + 0 (ntdll.dll)
    > 08C4FD84: 77B82B3A 77B50000 + 32B3A (ntdll.dll)
    > 08C4FD94: 77B7FA88 77B50000 + 2FA88 (ntdll.dll)
    > 08C4FDC4: 77BA3081 77B50000 + 53081 (ntdll.dll)
    > 08C4FE00: 77BA3081 77B50000 + 53081 (ntdll.dll)
    > 08C4FE30: 77B7F26C 77B50000 + 2F26C (ntdll.dll)
    > 08C4FE44: 7744BA37 77430000 + 1BA37 (kernel32.dll)
    > 08C4FE50: 7744BA4D 77430000 + 1BA4D (kernel32.dll)
    > 08C4FE78: 75304EFE 75300000 + 4EFE (MSVCR80.dll)

    Boy, I’m glad I can copy and past this message because I was willing to type it verbatim.

    So glad I didn’t have to type but glad Dad made me take those typing courses. Love you Dad, RIP.

    Anything you can offer is MORE than appreciated.

    Andre

    Andre Antonio
    PHATeFX Panama

    Aaron Warnecke replied 17 years, 2 months ago 4 Members · 4 Replies
  • 4 Replies
  • Jeremy Rasnic

    June 9, 2009 at 1:14 am

    I had this problem when a veg file of mine became corrupt after a lighting strike. It progressively got worse and I had to recapture the footage and start from scratch on a new drive.

    I would give this a go- capture again and see what happens with a new veg file. You don’t have to capture the whole thing, just a portion of the tape that you know is having problems. This will rule out tape and/or capture if it is one of the two.

    j razz

    https://www.jrazzcreations.com

  • Andre Anthonio

    June 9, 2009 at 1:30 am

    Y’up. That’s what I’m doing now…managing hard drive space to make room for the recapture on another drive. Still got an hour or so to go to move the files. Losing a lot of production time here, but… Thanks for the come back. I’ll update again after I complete more steps. Thanks again.

    Andre Antonio
    PHATeFX Panama

  • Stephen Mann

    June 9, 2009 at 2:02 am

    “Sony Vegas Pro 8.0
    Version 8.0a (Build 179)
    Exception 0xC0000005 (access violation) WRITE:0x20000 IP:0x20005 ”

    Everything that follows is meaningless to everyone except the programmer, and then only in controlled circumstances.

    According to Microsoft:
    Fatal exception errors are codes that are returned by a program in the following cases:

    * Access to an illegal instruction has been encountered
    * Invalid data or code has been accessed
    * The privilege level of an operation is invalid

    When any of these cases occurs, the processor returns an exception to the operating system, which in turn is handled as a fatal exception error. In many cases the exception is non-recoverable and the system must either be restarted or shut down, depending upon the severity of the error.

    Steve Mann
    MannMade Digital Video
    http://www.mmdv.com

  • Aaron Warnecke

    July 1, 2009 at 12:13 am

    I have the same problem, except worse.

    I can open Vegas just fine, but any time I try and do anything, even as simple as importing a small video clip from the media manager, I get that error and it shuts down.

    Help?? I need to edit a video by thursday, and I don’t understand how I can fix this!

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