Vegas 4.0d crashes: please help me...

PDB wrote on 9/12/2003, 5:03 AM
Sad news...but I can no longer keep Vegas running for more than a few minutes...its just crashes on me with an exception error...Here's some backround info...

I updated to vegas 4.0d yesterday and worked on a project in the evening: so far ok...This morning though and having worked on same project for a couple of hours, it just refuses to work: It seemed to crash the moment I started adding a whole bunch of stills to the timeline..I orignially thought this was a ram issue (only 256 mb here..) so I slowly managed to get rid of all the previous video in the project by saving a new veg with just the stills and soundtrack but it still crashes after a couple of minutes: I must have been through 10 crashes in less than 30 mins so far...The message I get is:

Sonic Foundry Vegas 4.0
Version 4.0d (Build 205)
Exception 0xC0000005 (access violation) WRITE:0x5D041BEB IP:0x900006
In Module 'vegas40.exe' at Address 0x400000 + 0x500006
Thread: VideoCache ID=0x92C Stack=0x4DFF000-0x4E00000
Registers:
EAX=ffffffff CS=001b EIP=00900006 EFLGS=00010286
EBX=070bcf7d SS=0023 ESP=04dffa08 EBP=058a8a50
ECX=7c028680 DS=0023 ESI=00000000 FS=0038
EDX=058a8a61 ES=0023 EDI=7c007c53 GS=0000
Bytes at CS:EIP:
00900006: 00 BC FF 00 BD FF 00 BD ........
0090000E: FF 00 BB FF 00 BD FF 00 ........
Stack Dump:
04DFFA08: 058A8A48 05800000 + A8A48
04DFFA0C: 058A8698 05800000 + A8698
04DFFA10: 070A16E6 070A0000 + 16E6 (stl2plg.dll)
04DFFA14: 0B980020 0B980000 + 20
04DFFA18: 00900000 00400000 + 500000 (vegas40.exe)
04DFFA1C: 04DFFA90 04D00000 + FFA90
04DFFA20: 04DFFAC8 04D00000 + FFAC8
04DFFA24: 00000000
04DFFA28: 058A8EA0 05800000 + A8EA0
04DFFA2C: 070A1A7E 070A0000 + 1A7E (stl2plg.dll)
04DFFA30: 04DFFA68 04D00000 + FFA68
04DFFA34: 058A8EA0 05800000 + A8EA0
04DFFA38: 01835EC8 017F0000 + 45EC8
04DFFA3C: 04DFFEFC 04D00000 + FFEFC
04DFFA40: 05997798 05800000 + 197798
04DFFA44: 005BD227 00400000 + 1BD227 (vegas40.exe)
> 04DFFAA4: 0105818F 01000000 + 5818F (vegas40k.dll)
04DFFAA8: 00DA28BC 00DA0000 + 28BC
04DFFAAC: 018AAB90 017F0000 + BAB90
04DFFAB0: 018AAB70 017F0000 + BAB70
04DFFAB4: 018CB728 017F0000 + DB728
> 04DFFAE8: 77E06418 77DA0000 + 66418 (ADVAPI32.dll)
> 04DFFAEC: 77DA8D32 77DA0000 + 8D32 (ADVAPI32.dll)
> 04DFFAF4: 77E06418 77DA0000 + 66418 (ADVAPI32.dll)
> 04DFFB30: 77102D91 770F0000 + 12D91 (OLEAUT32.dll)
> 04DFFB34: 770F0000 770F0000 + 0 (OLEAUT32.dll)
> 04DFFB4C: 770F0000 770F0000 + 0 (OLEAUT32.dll)
> 04DFFBDC: 77DA90D7 77DA0000 + 90D7 (ADVAPI32.dll)
> 04DFFBE4: 77DA90E0 77DA0000 + 90E0 (ADVAPI32.dll)
> 04DFFBEC: 77E06418 77DA0000 + 66418 (ADVAPI32.dll)
> 04DFFBF8: 77DA8F17 77DA0000 + 8F17 (ADVAPI32.dll)
> 04DFFC34: 77F48B33 77F40000 + 8B33 (ntdll.dll)
> 04DFFC3C: 77F48B49 77F40000 + 8B49 (ntdll.dll)
> 04DFFC78: 73E6101C 73E60000 + 101C (KsUser.dll)
> 04DFFC8C: 77F416F5 77F40000 + 16F5 (ntdll.dll)
> 04DFFCA4: 77F6F3EF 77F40000 + 2F3EF (ntdll.dll)
> 04DFFCAC: 77F72402 77F40000 + 32402 (ntdll.dll)
> 04DFFCB8: 77F42DBB 77F40000 + 2DBB (ntdll.dll)
> 04DFFCBC: 77F42E0F 77F40000 + 2E0F (ntdll.dll)
> 04DFFCC0: 77F4180B 77F40000 + 180B (ntdll.dll)
> 04DFFCDC: 77F416F5 77F40000 + 16F5 (ntdll.dll)
> 04DFFCFC: 77F72402 77F40000 + 32402 (ntdll.dll)
> 04DFFD08: 77F42DBB 77F40000 + 2DBB (ntdll.dll)
> 04DFFD0C: 77F42E0F 77F40000 + 2E0F (ntdll.dll)
> 04DFFD10: 77F4180B 77F40000 + 180B (ntdll.dll)
> 04DFFD28: 77DA8E43 77DA0000 + 8E43 (ADVAPI32.dll)
> 04DFFD40: 77DA8E0D 77DA0000 + 8E0D (ADVAPI32.dll)
> 04DFFD60: 77DA8DBC 77DA0000 + 8DBC (ADVAPI32.dll)
> 04DFFD7C: 77C97D86 77C90000 + 7D86 (RPCRT4.dll)
> 04DFFD84: 77C97D8F 77C90000 + 7D8F (RPCRT4.dll)
> 04DFFE28: 77F416B3 77F40000 + 16B3 (ntdll.dll)
> 04DFFE58: 006DB256 00400000 + 2DB256 (vegas40.exe)
- - -
04DFFFF0: 00000000
04DFFFF4: 00546D50 00400000 + 146D50 (vegas40.exe)
04DFFFF8: 006DE020 00400000 + 2DE020 (vegas40.exe)
04DFFFFC: 00000000

Could this be something to do with the stills? For what its worth, the stills and sound are all on an internal drive (plenty of space) but the veg has been saved on an external drive (plenty of space): the rest of the original project is on the external but have had no problems until I added the stills...

Thanks in advance for any help...

Paul.

Comments

PDB wrote on 9/12/2003, 5:15 AM
Just wanted to add to that: tried with Vegas Video 3.0c and also get the crashes so I guess that discards Vegas as the culprit...
PDB wrote on 9/12/2003, 6:09 AM
the problem of course...

Seeing as both versions of Vegas were having the same crash issue, I decided to:
1) re-build peaks
2) add the stills 1 by 1...
and guess what?? the moment I added still number Z boom! crash! tried again and skipped adding that particular still and so far (lots of fingers crossed over here...) it now seems to be stable: that particular still must have been corrupt or something I guess..

Anyway, goes to show that Vegas is as trustworthy as it ever was..:-) I just wished it would tell me "I'm gonna crash on you till I bore you silly unless you take that piece of f***ing media off my timeline!"

Happy again,

regards

Paul.
BillyBoy wrote on 9/12/2003, 9:28 AM
Every time I've seen a exception error it has turned out to be a corrupt source file. The problem of course is finding it. Vegas isn't the only application that stumbles when trying to open a "corrupt" file. Many, I dare say most applications crash. For example ACDSee, another normally very stable and user friendly piece of software. However, give it a corrupt JPEG to digest and not only will it freeze dead in its tracks trying to display oa thumbnail of the corrupt file, it can and has corrupted its entire database of all its other thumbnails.