HELP, please. Crash on Render

Widetrack wrote on 9/16/2008, 8:32 AM

I'm trying to render a 31-minute nested project to MPG-2 (video only) for a DVD, and Vegas keeps crashing. It always happens at different points, but they're all within a minute or so of one another. I've repeatedly gone back and looked at the different projects, cleaned out unused references in the project media area and made sure there's no apparent problem, but it still crashes.

I've managed to render half the project at a time it into 2 files, and they're both under 1GB. Would this suggest it's a RAM problem?

I've had Dynamic RAM preview set to 656 and Vegas says I have 1024MB available. I'll set it real low next time. It's also set to 4 rendering threads.

System:
Core 2 duo, win XP Pro, 1GB RAM, plenty of disk space, SP 3, Vegas 8.0b, build 217.

If anyone has any idea, please help.

Here's the dump:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2BC43000
Thread: ProgMan ID=0xBC4 Stack=0x339C000-0x33A0000
Registers:
EAX=00000000 CS=001b EIP=2bc43000 EFLGS=00010202
EBX=ffffffff SS=0023 ESP=0339ce3c EBP=0339d410
ECX=009e01a4 DS=0023 ESI=0339cf20 FS=003b
EDX=00629690 ES=0023 EDI=1ea8be10 GS=0000
Bytes at CS:EIP:
2BC43000: 00 00 00 00 00 00 00 00 ........
2BC43008: 00 00 00 00 00 00 00 00 ........
Stack Dump:
0339CE3C: 0339CE78 032A0000 + FCE78
0339CE40: 0BDE1768 0BAF0000 + 2F1768
0339CE44: 2BC42FF0 28D50000 + 2EF2FF0
0339CE48: 48C9E1E0
0339CE4C: 64655F58
0339CE50: 78787879
0339CE54: 77787979
0339CE58: 85868585
0339CE5C: 85858585
0339CE60: 565B6063
0339CE64: 67635E59 67600000 + 35E59 (QuickTimeVR.qtx)
0339CE68: 64686C6B
0339CE6C: 62646463
0339CE70: 79797978 790C0000 + 6D7978 (mscorlib.ni.dll)
0339CE74: 7A7A7979 7A440000 + 367979 (System.ni.dll)
0339CE78: 1EA8BE10 1D9A0000 + 10EBE10
> 0339CE90: 7A7A7A7A 7A440000 + 367A7A (System.ni.dll)
> 0339CEB4: 797A7B7A 790C0000 + 6E7B7A (mscorlib.ni.dll)
> 0339CEF8: 364D9365 36340000 + 199365 (sfmarket2.dll)
> 0339CF30: 7B7B7A7A 7AFD0000 + 7E7A7A (System.Windows.Forms.ni.dll)
> 0339CF34: 7B7B7B7B 7AFD0000 + 7E7B7B (System.Windows.Forms.ni.dll)
> 0339CF4C: 797D7D76 790C0000 + 717D76 (mscorlib.ni.dll)
> 0339CF50: 7B7B7B7B 7AFD0000 + 7E7B7B (System.Windows.Forms.ni.dll)
> 0339CF54: 7B7B7B7C 7AFD0000 + 7E7B7C (System.Windows.Forms.ni.dll)
> 0339D018: 7C91925D 7C900000 + 1925D (ntdll.dll)
> 0339D01C: 7C9192EF 7C900000 + 192EF (ntdll.dll)
> 0339D15C: 7C93770D 7C900000 + 3770D (ntdll.dll)
> 0339D178: 7C936EB3 7C900000 + 36EB3 (ntdll.dll)
> 0339D184: 7C937233 7C900000 + 37233 (ntdll.dll)
> 0339D188: 7C936F08 7C900000 + 36F08 (ntdll.dll)
> 0339D19C: 7C937129 7C900000 + 37129 (ntdll.dll)
> 0339D1A4: 01160151 01150000 + 10151 (vegas80k.dll)
> 0339D1A8: 003B0003 00370000 + 40003 (sfwbdmux.dll)
> 0339D1AC: 7C936F08 7C900000 + 36F08 (ntdll.dll)
0339D1B0: 0000C248
0339D1B4: 2BC42FF0 28D50000 + 2EF2FF0
> 0339D1B8: 00740002 00400000 + 340002 (vegas80.exe)
0339D1BC: 0001786B
0339D1C0: FFFF0000
0339D1C4: 0000184B
0339D1C8: 000BA17E 00030000 + 8A17E
> 0339D1D8: 003B0003 00370000 + 40003 (sfwbdmux.dll)
0339D1DC: 2BC42FE8 28D50000 + 2EF2FE8
0339D1E0: 000001C0
0339D1E4: 2BC42FE8 28D50000 + 2EF2FE8
0339D1E8: 2BC42FF0 28D50000 + 2EF2FF0
> 0339D1EC: 7C97D80C 7C900000 + 7D80C (ntdll.dll)
> 0339D230: 7C90E900 7C900000 + E900 (ntdll.dll)
> 0339D234: 7C9192F8 7C900000 + 192F8 (ntdll.dll)
> 0339D23C: 7C9192EF 7C900000 + 192EF (ntdll.dll)
> 0339D240: 7C918F01 7C900000 + 18F01 (ntdll.dll)
> 0339D24C: 7C9101BB 7C900000 + 101BB (ntdll.dll)
> 0339D258: 7C8850E0 7C800000 + 850E0 (kernel32.dll)
> 0339D264: 7C90E900 7C900000 + E900 (ntdll.dll)
> 0339D268: 7C936F10 7C900000 + 36F10 (ntdll.dll)
> 0339D270: 7C936F08 7C900000 + 36F08 (ntdll.dll)
> 0339D274: 7C9101BB 7C900000 + 101BB (ntdll.dll)
> 0339D3E0: 01226512 01150000 + D6512 (vegas80k.dll)
0339D3E4: 00000000
0339D3E8: 0339D430 032A0000 + FD430
0339D3EC: 0BDE18A8 0BAF0000 + 2F18A8
0339D3F0: 0000000D
> 0339D400: 006CF886 00400000 + 2CF886 (vegas80.exe)
- - -
0339FFF0: 00000000
0339FFF4: 005258F0 00400000 + 1258F0 (vegas80.exe)
0339FFF8: 00ADA678 00400000 + 6DA678 (vegas80.exe)
0339FFFC: 00000000

Comments

TheHappyFriar wrote on 9/16/2008, 9:27 AM

i'd say it has something to do with something quicktime related you're rendering. a TIFF or mov perhaps?

Grazie wrote on 9/16/2008, 9:29 AM

I always render a full project interim AVI first. Nested projects? Well, try an interim AVI and then render that.

Grazie

Widetrack wrote on 9/16/2008, 10:05 AM

Yes, there are four short .mov's in the project where V V hangs.

Why would that be a problem? I have QT installed and these .mov's and all tiffs play fine?

And on the chance they are the problem, what should I do about it--render them individually as .avi's?

TheHappyFriar wrote on 9/16/2008, 10:33 AM

could be a codec thing. re-render to AVI & then replace the mov's with the avi's. Should work perfectly then. :)

Widetrack wrote on 9/16/2008, 1:01 PM

it's rendering the second half now, and it got past the section that includes the .mov's with no problem.

I appreciate the suggestions, but I can't help but think it's a memory problem, somehow.

John_Cline wrote on 9/16/2008, 2:28 PM

It seems unlikely, although not impossible, that RAM is at the root of your crashing issue. If WinXP is working correctly, it will use the page file as additional RAM and the render would slow to a crawl, but it shouldn't necessarily crash.

However, if you only have 1GB of RAM, setting the preview to 656MB sure isn't leaving much RAM available to get any work done. That leaves barely enough room for the operating system and Vegas, much less the buggy Quicktime application as well. I'd suggest turning the preview RAM down to 128MB or even 64MB and buying another 1GB of RAM.

Widetrack wrote on 9/16/2008, 4:54 PM

John:

Yup. I turned it down to 64MB and another stick of RAM is on my list. It's amazingly cheap these days.

Like I mentioned, I started rendering the latter half of the project, including the part where it hung before, and Vegas got thru it handily.

I think I'll join the two files together with the shareware I got long ago and put it in DVDA. It's been so long since I used DVDA, it'll be a learning curve.

Thanks to all for the suggestions.