error message please help!

L8R wrote on 4/9/2009, 8:56 AM

I went to open up a wedding project that I had been working on and it gets to 100 % then pops up with the window:
An error occurred during the current operation.
An Exception has occurred.

If anyone knows what this all translates to, where the error occured and maybe a way to get around this, it would save me hours of work, as this was a finished project that I have yet to render.

Details:

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) READ:0x190 IP:0x518478
In Module 'vegas80.exe' at Address 0x400000 + 0x118478
Thread: GUI ID=0xCCC Stack=0x12C000-0x130000
Registers:
EAX=000000af CS=001b EIP=00518478 EFLGS=00010202
EBX=00000003 SS=0023 ESP=0012cd00 EBP=00000002
ECX=05ab0618 DS=0023 ESI=097baf80 FS=003b
EDX=00000000 ES=0023 EDI=000000ef GS=0000
Bytes at CS:EIP:
00518478: 8B 92 90 01 00 00 3B FA ......;.
00518480: 7F 02 8B FA 3B 7C 24 20 ....;|
Stack Dump:
0012CD00: D4041011
0012CD04: B2010F69
0012CD08: 77F17AA0 77F10000 + 7AA0 (GDI32.dll)
0012CD0C: 097BAF80 09720000 + 9AF80
0012CD10: 0000000E
0012CD14: 000000EF
0012CD18: 00000113
0012CD1C: 0A76EBE0 0A700000 + 6EBE0
0012CD20: 0000002F
0012CD24: 00000000
0012CD28: 00000002
0012CD2C: 00000002
0012CD30: 000000F0
0012CD34: 00000119
0012CD38: 0000012E
0012CD3C: 00000000
> 0012CD4C: 00519097 00400000 + 119097 (vegas80.exe)
0012CD50: 00000004
0012CD54: B2010F69
0012CD58: 00000000
0012CD5C: B2010F69
> 0012CD64: 77F16A56 77F10000 + 6A56 (GDI32.dll)
> 0012CD98: 0125897D 01160000 + F897D (vegas80k.dll)
> 0012CD9C: 014670F0 01160000 + 3070F0 (vegas80k.dll)
0012CDA0: B2010F69
0012CDA4: 0012CE58 00030000 + FCE58
> 0012CDA8: 00FFFFFF 00400000 + BFFFFF (vegas80.exe)
0012CDAC: 00000000
0012CDB0: 00000000
0012CDB4: 00000000
0012CDB8: 00000000
> 0012CDDC: 00610052 00400000 + 210052 (vegas80.exe)
> 0012CDE0: 00650074 00400000 + 250074 (vegas80.exe)
- - -
0012FFF0: 00000000
0012FFF4: 00000000
0012FFF8: 0084963B 00400000 + 44963B (vegas80.exe)
0012FFFC: 00000000

After I click ok another window pops up saying:

The instruction at "0x0290595b" referenced memory at "0x02741fdc". The memory could not be "read".
Click OK to terminate the program

Comments

musicvid10 wrote on 4/9/2009, 8:59 AM

See if you can open the project backup. (Change the .bak extension to .veg)

L8R wrote on 4/9/2009, 9:19 AM

I tried that... it does the same thing. In the folder there is one that reads the same name that is a .veg file and then one that is a .veg.bak
when I cange the .veg.bak to just "filename.veg" it opens to 100% then fails the same.
Is one of the file corrupt?
the version before the backup works but I know that this is not the final version because I can see all the chapter marks that were added after the backup took place.

musicvid10 wrote on 4/9/2009, 9:27 AM

If the most recent backup does not work, then you can go back to one that does work and retrace your steps, or you can send the corrupted .veg file to Sony support and see if they can fix it.

These are the only two options I know of.

L8R wrote on 4/9/2009, 9:46 AM

Ok, great advice... I did manage to find a restored file in the restore folder. It looks to be somewhere inbetween the file that would open and the file that wouldn't.
I don't know why this has done this. Anytime I get a program error and open it back up I always resave the file to the newest filename. I don't know why this didn't save properly.
Thanks for your help, I hope this is the most current version of it. This is why I hate when clients take their time getting back to me about changes.... This was from Feb.

musicvid10 wrote on 4/9/2009, 10:41 AM

If your system memory is loaded to the max when you save the .veg, sometimes errors occur.

Best practice is to make incremental backups, close Vegas, and reopen periodically as you work.

gpsmikey wrote on 4/9/2009, 1:20 PM

Something I have used for a number of projects (both here and Photodex Producer slideshow software) is to save a copy of the .veg (or .psh) file to a different name or extension ( .veg_works1 ) to that the auto-backup process doesn't roll that one off the edge when I am going in and out a number of times. Gives me a good reference point doing it that way.

mikey

ushere wrote on 4/9/2009, 4:02 PM

http://www.jetdv.com/vegas/forum/viewtopic.php?t=2661

great - dependable and i can edit with a clear mind!

L8R wrote on 4/9/2009, 7:36 PM

Does this work with Vegas 8 pro?
I notice the thread is from 2004.

TheHappyFriar wrote on 4/9/2009, 8:00 PM

gdi32.dll has to do with the display drivers... you update something lately?

ushere wrote on 4/9/2009, 9:06 PM

l8r

running on 8c perfectly......

craftech wrote on 4/10/2009, 3:48 AM

Exception 0xC0000005 (access violation) is a "memory access violation" that is pretty common in Windows XP Service Pack 2 especially.

Because Windows was designed to benefit Microsoft it is inherently prone to security attacks that never end. One of the bandaids that Microsoft included in Service pack 2 was Data Execution Prevention that added some new memory checks to attempt to prevent hacker code exploits. It affects both the software and the hardware. Sometimes a slight change in software can trigger this. It is possible to turn of DEP by editing the Boot.ini file if nothing else works for you. There is more information here.

The problem can also be the result of bad RAM. I don't know what your configuration is, but you can try removing part of your RAM if that is possible and or switching sticks. Example: 4G of memory. Try 2G of memory alternating the sticks.

If you updated drivers for hardware this violation can also happen. That would be video card updates in particular. You can roll back to a previous driver to troubleshoot that.

musicvid10 wrote on 4/10/2009, 5:20 AM

Since the OP is having problems with only one project, a hardware or system fault seems a less likely cause. Sometimes projects get corrupted on save. This is less of a problem now than in the Vegas 2 days, but the "save early, save often" approach has saved my tail more than once.

It's a good idea for the program (and your eyes) to save the project every couple of hours, close Vegas to recover memory, and reopen the project. And when I've finished editing, before I render, I always reboot.

I typically have 12-20 incremental backups saved by the time I finish a typical DVD project. Veggies are cheap insurance.

craftech wrote on 4/10/2009, 6:47 AM

That is good advice. I do it all the time. But then again I always did it so it is a habit. If the OP doesn't he should start getting into that habit.

John

TheHappyFriar wrote on 4/10/2009, 8:00 AM

could it be there's an FX on the current project that isn't on the old one & thus that FX is causing the video to crash?

L8R wrote on 4/10/2009, 3:43 PM

Good advice, thanks everyone.
I did have some issues last month on my one computer... this one that that wedding is on.
I was finding every now and again the program would freeze, probably working it hard with fx and what not. Every now and again I would get a Blue screen. I did update my video drivers after getting errors because of the errors related. So, it could be somewhere in that time frame.
I usually always do have quite a few differnt .vegs of the same project. Different stages in the process. There wasn't much differnt in the project before the one that would open to the last except final tweaking, chapter marks and names.
It just frustrates me because this particular wedding, they had no changes before finalizing, but yet I have to now go back and check it all out to see what needs to be tweaked again.
I also do frequent backups of the entire folder containing everything.
Thanks again to everyone. I was just hoping there's a way to maybe isolate in the data info, what the actual error was.
Is it an effect that's hung, is there a way to bypass it?

TheHappyFriar wrote on 4/10/2009, 8:16 PM

well, bypas all the FX via the preview window, see if it works. If it does, undo that & then bypass on all events/tracks. then undo one at a time until you find the issue.

Every FX related crash I've had has been due to the footage, not the FX. Could be a file got messed up somewhere too, but I'm betting drivers.

Best idea: transfer the whole project to another comp & try rending there.

L8R wrote on 4/13/2009, 7:57 AM

Hey Happy.... you are my hero buddy!
You hit it right on the head with opening it up with my other computer.
I had backed up the main folder a few days after finishing this project as I knew it would be a few weeks before returning to it.
I put that drive on my other computer and it opened no problem.
Now I wonder what the issue is, with the other computer.
My other projects open.
Thank you so much Happy, as I wipe my forehead.