Error after render, from 6.0c

john-beale wrote on 11/17/2005, 9:13 AM
I did a two-hour render from Vegas 6c to DV format. It actually got to 100% and the output file is all there, but at the very end Vegas did not return, it just froze with the below error message. When I clicked "OK" the whole Vegas window disappeared. I'm running WinXP SP2 on a P4 with hyperthreading on and Vegas set to use two rendering threads. Any idea what's going on here?

-----------------
An error has occurred during the current operation.
An exception has occurred.

Sony Vegas 6.0
Version 6.0c (Build 153)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x0
In Module 'vegas60.exe' at Address 0x0 + 0x0
Thread: ProgMan ID=0x2A4 Stack=0xAB4F000-0xAB50000
Registers:
EAX=2cfd3414 CS=001b EIP=00000000 EFLGS=00210246
EBX=00000000 SS=0023 ESP=0ab4faa4 EBP=00000000
ECX=2d271008 DS=0023 ESI=2cfba938 FS=003b
EDX=0b2d9ad8 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
00000000: .. .. .. .. .. .. .. .. ........
00000008: .. .. .. .. .. .. .. .. ........
Stack Dump:
0AB4FAA4: 09D201B4 09D10000 + 101B4 (aviplug.dll)
0AB4FAA8: 2CFD3414 2C870000 + 763414
0AB4FAAC: 00000000
0AB4FAB0: 2CFBA938 2C870000 + 74A938
0AB4FAB4: 2CF11438 2C870000 + 6A1438
0AB4FAB8: 09D201FD 09D10000 + 101FD (aviplug.dll)
0AB4FABC: 00000000
0AB4FAC0: 2D0E13E0 2C870000 + 8713E0
0AB4FAC4: 00562658 00400000 + 162658 (vegas60.exe)
0AB4FAC8: 2CFBA938 2C870000 + 74A938
0AB4FACC: 2CF1146C 2C870000 + 6A146C
0AB4FAD0: 00000000
0AB4FAD4: 09A6FFE8 09A30000 + 3FFE8
0AB4FAD8: 2CFBA938 2C870000 + 74A938
0AB4FADC: 00000000
0AB4FAE0: 0016EE30 00140000 + 2EE30
> 0AB4FAE8: 0057005C 00400000 + 17005C (vegas60.exe)
> 0AB4FAEC: 006E0069 00400000 + 2E0069 (vegas60.exe)
> 0AB4FAF0: 00650074 00400000 + 250074 (vegas60.exe)
- - -
0AB4FFF0: 00000000
0AB4FFF4: 00501F10 00400000 + 101F10 (vegas60.exe)
0AB4FFF8: 00987688 00400000 + 587688 (vegas60.exe)
0AB4FFFC: 00000000

Comments

mdopp wrote on 11/17/2005, 12:39 PM
Yep, looks like 6.0c is quite instable when rendering. I always get a "low on memory" message on my 2 GB machine. Downgrade to 6.0b and your problems should be gone. Or wait for 6.0d...
Good luck ;-)
ForumAdmin wrote on 11/17/2005, 2:18 PM
Some other experienced users who have encountered instability in Vegas 6 when rendering have found a solution- read about it here:

http://www.sonymediasoftware.com/forums/ShowMessage.asp?MessageID=422708&Replies=5

Dust and heat are no joke in fast machines like yours running multi-threaded apps like Vegas.
Logan5 wrote on 12/13/2005, 2:47 PM
When V6 has an “Exception occur” on a 15 min avi render at 100 %( the rendered file is intact) – it happens 2 out of about 5 times with the same render.
Is the cause a simple V6 instability issue or a heat issue?
Mentioned above there are two thoughts. Has anyone got a sold idea on the cause?
Thanks

Pentium D 3.2 – 2gig ram - new system
gdstaples wrote on 12/13/2005, 4:40 PM
Does anyone have a link to the 6.0b patch? Sony just has the 6.0c patch on their site and my version on CD is 6.0a.

Thanks,
Duncan
JJKizak wrote on 12/13/2005, 4:58 PM
My latest project was a 1 hr HDV with stills on the front and rear with many zooms, velocity changes, texts, radial blurs, bump maps, and about 30 cookie cutters. The rendered files to NTSC widescreen at best quality and default 16 meg ram and default bitrates took 4 hrs and 18 minutes( 3.2gig file) with 4 gig of ram and AMD 4600+ X2. I did this approximately 7 times (mistakes) and one time at 99% it gave me the low memory message and I said OK but I did not loose what already had been rendered which I thought was pretty neat as with V5 you would loose the whole thing. I then rendered the first still section to 1080-60i intermediate avi which took about 3 hrs 50 minutes and applied it to the timeline and then deleted and removed from project all of the still stuff that was rendered. This really cut the memory usage down so I rendered the back end of stills to 1080-60i intermediate avi and applied it to the timeline and took a huge chunk out of the memory usage again after deleting the stills from the project. Rebooted each time to reset the paging file. Then rendered to HDV 1080-60i and it took about 4 hours and created an m2t file of 12.4 gigs. Rendered again to HDV 720-30p and the m2t file was 9.4 gig which took 3.5 hrs. Took that file and printed it to JVC D-VHS tape in full auto (crash) and it was flawless using V6c. When I first opened V6 before cutting the memory usage the opening percent would hit 49% before opening. After it would hit 25% before opening. I have said before on the this forum that vegas needs about 16 gig of ram to be on the safe, balls ass to the wall, for no memory problems and I still believe this.

JJK