0xC0000005 (access violation) Help!!!!

Austin wrote on 12/18/2007, 12:56 AM
When I try to place a few videos on the timeline, I get this error:
It also seems to pop up randomly and kill whatever I'm doing!
Please help!
Thanks!
-Austin

Sony Vegas Pro 8.0
Version 8.0a (Build 179)
Exception 0xC0000005 (access violation) READ:0xC61FF06 IP:0x133C72A
In Module 'vegas80k.dll' at Address 0x1150000 + 0x1EC72A
Thread: VideoRender ID=0x36C Stack=0xC4CF000-0xC4D0000
Registers:
EAX=00000000 CS=001b EIP=0133c72a EFLGS=00010202
EBX=00000000 SS=0023 ESP=0c4cf904 EBP=00000000
ECX=00000000 DS=0023 ESI=0c61ff00 FS=003b
EDX=00000004 ES=0023 EDI=0c620a40 GS=0000
Bytes at CS:EIP:
0133C72A: 0F B6 5C 32 02 0F AF D8 ..\2....
0133C732: 0F B6 44 8E 02 C1 FD 0E ..D.....
Stack Dump:
0C4CF904: 00000000
0C4CF908: 0C4CFA18 0C3D0000 + FFA18
0C4CF90C: 00004000
0C4CF910: 0000028F
0C4CF914: 00000000
0C4CF918: 00000000
0C4CF91C: 00004000
0C4CF920: 00000000
0C4CF924: 0C4CFDB0 0C3D0000 + FFDB0
0C4CF928: 00000001
0C4CF92C: 7C80FCD8 7C800000 + FCD8 (kernel32.dll)
0C4CF930: 000000FF
0C4CF934: 0133DF7D 01150000 + 1EDF7D (vegas80k.dll)
0C4CF938: 02155594
0C4CF93C: 00000000
0C4CF940: 00004000
> 0C4CF9A8: 01336930 01150000 + 1E6930 (vegas80k.dll)
0C4CF9AC: 02155594
0C4CF9B0: 0C4CFBFC 0C3D0000 + FFBFC
0C4CF9B4: FFFFF5C4
0C4CF9B8: 0C4CFAFC 0C3D0000 + FFAFC
> 0C4CFA00: 009E7868 00400000 + 5E7868 (vegas80.exe)
0C4CFA04: 43691C98 42E20000 + 871C98
0C4CFA08: 4360C1C0 42E20000 + 7EC1C0
0C4CFA0C: 00000001
0C4CFA10: 0015BC08 00140000 + 1BC08
> 0C4CFA3C: 00A3C000 00400000 + 63C000 (vegas80.exe)
> 0C4CFA40: 00780000 00400000 + 380000 (vegas80.exe)
0C4CFA44: 00000000
0C4CFA48: 00000000
> 0C4CFA4C: 00A3C000 00400000 + 63C000 (vegas80.exe)
- - -
0C4CFFF0: 00000000
0C4CFFF4: 0059E390 00400000 + 19E390 (vegas80.exe)
0C4CFFF8: 05656060 05400000 + 256060
0C4CFFFC: 00000000

Comments

Austin wrote on 12/18/2007, 1:04 AM
I now can not even open my project due tomorrow for mid-term without Vegas crashing!!!!

Please Help!!!
essami wrote on 12/18/2007, 1:50 AM
Quick and easy first thing to try is to re-install Vegas. Sorry if it seems very obvious and you've done it already.
Austin wrote on 12/18/2007, 2:10 AM
Tried that, but same problem. :(
CorTed wrote on 12/18/2007, 10:37 AM
I had his problem early on when V8 was released on a particular project. The exeption error is most likely caused by using up too much memory by placing pictures which are too big, or filling up memory with too many clips. (keep memory usage below 60%)
Try to downsize the PICs if you are using any. If that does not work split up your project in 2 or 3 sections, then try to render them.

Be sure none of the pics and or video is corrupted somehow, as that may also cause this type of crash.


Ted
AnnieK wrote on 12/18/2007, 10:46 AM
Austin - whenever we have projects that start to crash frequently, we do the following -
Open the file.
Open a second session of Vegas.
Edit > Select All > Copy in the problem file.
Edit > Paste to the new file.

It doesn't solve every problem - there are way too many reasons that Vegas can crash - but it will often save your bacon. But you will need to get the project to open, I'm sorry to say. Hopefully auto-save is turned on - try to open the veg.bak file, or see if there is a crash file in the directory that Vegas uses for temps. And more unfortunately, you could be dealing with a bad memory or bad block issue, in which case no amount of fiddling with Vegas is going to help.

If you do manage to paste to a new file, note that not "everything" will transfer from the editing choices. You will probably have to re-set the track compositing; probably have to re-set some effects chains; anything more complex is likely to need re-doing, but that' s a better place to be than starting over from scratch.

Been there - done that - keep pounding on the forum, it's your best place for help at this stage.
dirtynbl wrote on 12/18/2007, 6:49 PM
Vegas 8 is a joke right now when it comes to crashing.

I'm editing an HD music video right now and its just a mess.

Two Vegas windows is a necessity. Also, make sure the out-saving is on and frequent.

I have found that Vegas does a wonderful job of corrupting your veg file even if you saved it prior to adding whatever clip it took exception too.

@ whoever said 60% of memory? I have SD Vegas 7 projects for feature films that are 2.5 hours long and loaded with footage and stills. Vegas never crashed. Currently Vegas 8 is using 600mb of ram (15% of my total) and its crashing regularly for no reason other than that its poorly made and poorly tested.

Hopefully Sony will get on this as they usually do and release a fixed version that isn't as tempermental.
spotlightlover wrote on 12/31/2007, 1:28 PM
I have had a similar problem, but it's caused specifically by compositing. All I have to do is create a project with a parent/child composite using "multiply" mode. It plays fine, renders fine in 8.0; but once I save the project, and try to re-open it, Vegas crashes.

Fortunately I have a second computer which doesn't have the problem so I am able to edit the project there. Both computers are running Windows XP with Service Pack 2, so I am at a loss as to what the difference could be. I don't see how it can be memory as I can cause the crash with a very small project containing only stills with no audio.

ETA: MH_Stevens, none of the things you suggest affects my crash. I can take any two uncorrupted files -- video of any format or just stills -- and once I create a composite layer, the project will no longer open on the affected system. I have no viruses on the system; I use Norton Utilies, SpyBot and Ad-Aware regularly. My disk drive was recently de-fragmented and I have 40GB of free space. I've tried un-installing and re-installing Vegas 8.0 to no avail.

I can create the same project in Sony Vegas 6.0 with no problem whatsoever.
MH_Stevens wrote on 12/31/2007, 4:18 PM
If none of the above solved your problem do some house keeping. Save your work and remove Vegas - uninstall it. Run a system cleaner and check for major errors and viruses. CCleaner and Trend Micro's House Call are both FREE and top rate. Then defrag your drive and reinstall Vegas. Now add your files to the time-line slowly saving between each one in case an error reoccurs. If it does look closely at what you just added. Is it corrupt? Does its resolution match the project? That sort of thing. Good luck with the mid-term.
Paul Mead wrote on 1/1/2008, 5:10 AM
An access violation is a bug -- end of story. It might not be a bug in Vegas, it could be some other DLL being used by Vegas, but it is still a bug. So at least attempt to ask Sony about it and send in a service request. I know, good chance that will be a waste of time, but it is definitely worth a try. Juggling things around till it happens to work right is not a solution, it is a workaround. A solution is found when the vendor fixes the bug, and the only way the bug will be fixed is if people report it to the vendor. So do everybody a favor and hold Sony's feet to the fire when you trip over something like this -- report it.