Vegas crashes, causing me to open veins!

[Ted OMalley]

Tried the second minute a second time - worked perfectly. Go figure.

[Steven Davis]

Yeah Ted,

Welcome to the world of 'Unknown Vegas Errors.' There are many documented on this board, and to be honest, the users on this board know more, or are willing to explain more than SONY. But just for laughs, send Sony that error and if you get a response, that'll be your laugh for that day. I'm glad you got it worked out.

[Ted OMalley]

So, I figured it was time to try rendering the entire project since all of the pieces rendered correctly. It got to 27 percent and Vegas crashed.

Upon restarting, I received the following Exception error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x74EC79
In Module 'vegas80.exe' at Address 0x400000 + 0x34EC79
Thread: VideoCache ID=0x1F60 Stack=0x76ED000-0x76F0000
Registers:
EAX=00000000 CS=0023 EIP=0074ec79 EFLGS=00010246
EBX=00000000 SS=002b ESP=076edcd4 EBP=076edd18
ECX=5f942665 DS=002b ESI=076edfc0 FS=0053
EDX=eb851eb8 ES=002b EDI=80004005 GS=002b
Bytes at CS:EIP:
0074EC79: 0F B7 08 66 85 C9 74 2D ...f..t-
0074EC81: 0F B7 C9 66 83 F9 20 74 ...f.. t
Stack Dump:
076EDCD4: 0074F37D 00400000 + 34F37D (vegas80.exe)
076EDCD8: 00000001
076EDCDC: 00000005
076EDCE0: 076EE3AC 075F0000 + FE3AC
076EDCE4: 076EE3C8 075F0000 + FE3C8
076EDCE8: 0074F689 00400000 + 34F689 (vegas80.exe)
076EDCEC: 076EDD18 075F0000 + FDD18
076EDCF0: 076EE6AC 075F0000 + FE6AC
076EDCF4: 256946E0 254C0000 + 1D46E0
076EDCF8: 256946A8 254C0000 + 1D46A8
076EDCFC: 00000000
076EDD00: CA200000
076EDD04: 076EE3C4 075F0000 + FE3C4
076EDD08: 00000000
076EDD0C: 00000000
076EDD10: 00000000
> 076EDF68: 0065004B 00400000 + 25004B (vegas80.exe)
076EDF6C: 00350079 002A0000 + B0079
076EDF70: 00000000
076EDF74: 00000006
076EDF78: 00000000
> 076EDFB0: 65000000 64E70000 + 190000 (System.Data.dll)
> 076EDFC0: 006F004E 00400000 + 2F004E (vegas80.exe)
> 076EDFC4: 0065006E 00400000 + 25006E (vegas80.exe)
076EDFC8: 002C0000 002A0000 + 20000
076EDFCC: 00360020 002A0000 + C0020
076EDFD0: 00300034 002A0000 + 60034
076EDFD4: 00200000 001E0000 + 20000
> 076EE02C: 76B9B132 76B00000 + 9B132 (kernel32.dll)
> 076EE03C: 76B4ACF1 76B00000 + 4ACF1 (kernel32.dll)
> 076EE04C: 76B2D045 76B00000 + 2D045 (kernel32.dll)
> 076EE058: 76B4B7EF 76B00000 + 4B7EF (kernel32.dll)
> 076EE064: 779B1C78 77900000 + B1C78 (ntdll.dll)
> 076EE068: 7792889F 77900000 + 2889F (ntdll.dll)
> 076EE070: 7792BC0B 77900000 + 2BC0B (ntdll.dll)
> 076EE074: 7792BB62 77900000 + 2BB62 (ntdll.dll)
> 076EE07C: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE080: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE084: 253100F8 25310000 + F8 (stl2plg.dll)
> 076EE090: 7797C50B 77900000 + 7C50B (ntdll.dll)
> 076EE094: 779E01A0 77900000 + E01A0 (ntdll.dll)
> 076EE098: 7797C4A0 77900000 + 7C4A0 (ntdll.dll)
> 076EE0A0: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE0C0: 779B1C78 77900000 + B1C78 (ntdll.dll)
> 076EE0C4: 7792B2BF 77900000 + 2B2BF (ntdll.dll)
> 076EE0D4: 7792BC0B 77900000 + 2BC0B (ntdll.dll)
> 076EE0E4: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE0F0: 7792B53A 77900000 + 2B53A (ntdll.dll)
> 076EE0F8: 7796310A 77900000 + 6310A (ntdll.dll)
> 076EE104: 77963251 77900000 + 63251 (ntdll.dll)
> 076EE130: 006E0065 00400000 + 2E0065 (vegas80.exe)
- - -
076EFFF0: 00000000
076EFFF4: 005995C0 00400000 + 1995C0 (vegas80.exe)
076EFFF8: 00ADC81C 00400000 + 6DC81C (vegas80.exe)
076EFFFC: 00000000

Saying OK to the exception error of course crashed Vegas again.

Next time I opened Vegas - it opened fine. I'm beginning to see a pattern here...

[Ted OMalley]

Just can't render in Vista.

Partioned my drive and installed XP in a dual-boot scenario. Installed Vegas and opened my project.

I rendered it and 2/3 of the way through it crashed.

I tried a second time and found the following error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0xC1C0 IP:0x6C81A2
In Module 'vegas80.exe' at Address 0x400000 + 0x2C81A2
Thread: ProgMan ID=0x140 Stack=0x301E000-0x3020000
Registers:
EAX=0301efc0 CS=001b EIP=006c81a2 EFLGS=00010246
EBX=47129ee4 SS=0023 ESP=0301ef34 EBP=02c01db0
ECX=00000020 DS=0023 ESI=0301ef40 FS=003b
EDX=0301f0bc ES=0023 EDI=0000c1c0 GS=0000
Bytes at CS:EIP:
006C81A2: F3 A5 8B 43 0C A8 05 74 ...C...t
006C81AA: 0A 8D 54 24 0C 52 E8 07 ..TR..
Stack Dump:
0301EF34: 47129EE4 44950000 + 27D9EE4
0301EF38: 00000000
0301EF3C: 0301F308 02F20000 + FF308
0301EF40: 00000000
0301EF44: 3FF00000 3E900000 + 1600000
0301EF48: 00000000
0301EF4C: 00000000
0301EF50: 00000000
0301EF54: 00000000
0301EF58: 00000000
0301EF5C: 00000000
0301EF60: 00000000
0301EF64: 00000000
0301EF68: 00000000
0301EF6C: 3FF00000 3E900000 + 1600000
0301EF70: 00000000
> 0301EFC0: 006C83F7 00400000 + 2C83F7 (vegas80.exe)
0301EFC4: 47129EE4 44950000 + 27D9EE4
0301EFC8: 0301F02C 02F20000 + FF02C
0301EFCC: 47129E70 44950000 + 27D9E70
0301EFD0: 00000001
> 0301EFE8: 006D4FF6 00400000 + 2D4FF6 (vegas80.exe)
0301EFEC: 02C01DB0 02A70000 + 191DB0
0301EFF0: 0301F308 02F20000 + FF308
0301EFF4: 9C61F9EB
0301EFF8: 00000000
> 0301F0AC: 006BDB04 00400000 + 2BDB04 (vegas80.exe)
0301F0B0: 47129E70 44950000 + 27D9E70
0301F0B4: 02C01DB0 02A70000 + 191DB0
0301F0B8: 0301F308 02F20000 + FF308
0301F0BC: 00001EBF
> 0301F0EC: 006BE10A 00400000 + 2BE10A (vegas80.exe)
0301F0F0: 2933A020 28340000 + FFA020
0301F0F4: 02C01DB0 02A70000 + 191DB0
0301F0F8: 0301F308 02F20000 + FF308
0301F0FC: 00001EBF
> 0301F144: 7C8399F3 7C800000 + 399F3 (kernel32.dll)
> 0301F17C: 009F2118 00400000 + 5F2118 (vegas80.exe)
> 0301F180: 011C62F9 01150000 + 762F9 (vegas80k.dll)
- - -
0301FFF0: 00000000
0301FFF4: 005258F0 00400000 + 1258F0 (vegas80.exe)
0301FFF8: 00ADA678 00400000 + 6DA678 (vegas80.exe)
0301FFFC: 00000000

So, there is either something wrong with my hardware, with Sony Vegas (I'm guessing NOT at this point), or ... my project.

There must be some part or parts of my project that are fighting with Vegas - time to do some more troubleshooting.

[Matthew Chaboud]

Ted, I'd bet on it being a Vegas problem.

You're likely running out of virtual-address space, which is like running out of memory, but it doesn't have so much to do with the amount of memory that you have on your system.

Definitely try rendering with one video rendering thread and only, say, 64MB of video preview cache (both in prefs).

If that still blows up in 8.0b, the file plug-ins are just being too darned greedy. There are several ways to inspect the metrics on the process to determine if this is the case, but it may be most prudent to get your project/media to someone who can debug the problem if you can do it.

Seemingly random crashes with the same project generally stem from memory allocation failures not being handled properly (i.e. telling the user that the application is low on memory) and blowing up later.

You can also render your track contents without filters or motion to uncompressed (or lightly compressed) avi's and bring them back in to do any compositing work. This is akin to "freezing" for audio, and it was something that we all used to have to live with in the days of limited system resources.

What you're running up against is probably the single strongest argument for 64-bit applications. Please keep us posted.

Thanks,
Matt

[Mike Kujbida]

Originally Posted by Matthew Chaboud

What you're running up against is probably the single strongest argument for 64-bit applications. Please keep us posted.

Matt, when is the promised 64-bit version of Vegas coming?
I know, NDA says you can't say anything :-(

[Jeff Harper]

I would like to add to the image aspect of the discussion I have had best luck with png's, not jpgs. Don't know the why or wherefore, just seems Vegas likes the png's best.

[Andris Krastins]

I'm close to slicing my veins too....
I have Sony Vegas Pro 7.0c It all worked fine, but now, when I'm editing my first short, it crashes, and crashes, and crashes, and... it's depressing.

ImageShack - Hosting :: 17808176se8.jpg

[Jeff Harper]

Andris, consider that possibly a software or hardware change might be the thing to look into.

I had issues with 8 initially, but Vegas 7 was REALLY stable for so many of us. You might consider biting the bullet and wipe your hard drive clean and start over, saving your project files. Good luck, your crashes do sound very frustrating!

[Edward Troxel]

The last version of 7 was 7.0e. Might be work updating to the last version.

[Jeff Harper]

Of course Edward is right, as always! Didn't notice you didn't have latest version. Definitely try that!

[Andris Krastins]

Ok, thanks for your advice!

At the moment I'm having 2 instances of Vegas open.
One is the master which crashes all the time, the other is where I edit particular parts of the short and then just paste it into the master and try to save before everything crashes again.

I don't understand really. My computer is quite powerful, I'm using XP and there is no apparent reason for this to happen. I'm not even using that much effects, except for radial blur in a few scenes.

[Andris Krastins]

I now think it really was my computer. I divided my short into smaller fragments of 5 minutes each vegas file and no more crashing.
Maybe it's because I have very many small fragments with slightly variable effects applied to each separately, don't know...

I've got Core 2 Duo 6700 @ 2.66Ghz and 3.25GB of usable RAM.

[Jeff Harper]

Glad you found the solution. Your computer is certainly not weak, by Vegas standards. You have a very good processor. Certain tasks we give our PCs are more difficult for it to handle than we are aware. This will cause issues without our knowing why, oftentimes.

[Mark Goldberg]

I had serious crashing problems when I first updated from Vegas 7 yo Vegas Pro 8. I wound up keeping 7 on the system for renders.

Basically, the problem was that render times were much longer in 8, and it crashed when trying to render a result to various formats, especially Windows Media. I contacted tech support and was advised to check photo sizes.

Turned out that the crashes usually occured when I had large photos, or a composite of several showing at once, when total horizontal res. went to about 4000 pixels.

The fix was resizing the photos such that the max across the image (HD) kept not too far from 2000 pixels.