All vers. of Vegas crash ONLY rendering

Samus wrote on 10/10/2006, 2:57 PM
Hi, I had Vegas 5, 6 and 7 all give me this problem. When I render my project to output it to a DV file, Vegas crashes. I get the error message "An error occured during the current operation. An exception has occured."

Then, and you'll excuse me, I get this error log:

Sony Vegas 7.0
Version 7.0a (Build 115)
Exception 0xC0000005 (access violation) READ:0x13125DC IP:0x70000C
In Module 'vegas70.exe' at Address 0x400000 + 0x30000C
Thread: ProgMan ID=0xF30 Stack=0x1DBE000-0x1DC0000
Registers:
EAX=01dbeec0 CS=001b EIP=0070000c EFLGS=00010206
EBX=07f36270 SS=0023 ESP=01dbee64 EBP=01dbf434
ECX=00990158 DS=0023 ESI=0231a8f8 FS=003b
EDX=0070000a ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
0070000C: C4 89 84 24 98 00 00 00 ...: 8B 84 24 A4 00 00 00 8B ......
Stack Dump:
01DBEE64: 00732ECB 00400000 + 332ECB (vegas70.exe)
01DBEE68: 0231A8F8 021B0000 + 16A8F8
01DBEE6C: 0230BFF8 021B0000 + 15BFF8
01DBEE70: 07F46D28 07E30000 + 116D28
01DBEE74: 0C24F018 0BF40000 + 30F018
01DBEE78: 006C0399 00400000 + 2C0399 (vegas70.exe)
01DBEE7C: 01DBEEC0 01CC0000 + FEEC0
01DBEE80: 0230BFF8 021B0000 + 15BFF8
01DBEE84: 0C24F008 0BF40000 + 30F008
01DBEE88: 0A9EC7D0 0A9D0000 + 1C7D0
01DBEE8C: 00000000
01DBEE90: 00000215
01DBEE94: 00000000
01DBEE98: 00000002
01DBEE9C: FC3BF544
01DBEEA0: 07F36270 07E30000 + 106270
> 01DBEEF8: 7C931C41 7C900000 + 31C41 (ntdll.dll)
> 01DBEF28: 7C931F6B 7C900000 + 31F6B (ntdll.dll)
> 01DBEF2C: 7C931C41 7C900000 + 31C41 (ntdll.dll)
> 01DBEF4C: 781C31A0 78130000 + 931A0 (MSVCR80.dll)
> 01DBEF68: 7C90D4EA 7C900000 + D4EA (ntdll.dll)
> 01DBEF6C: 7C9180FF 7C900000 + 180FF (ntdll.dll)
> 01DBF008: 7C91B5F4 7C900000 + 1B5F4 (ntdll.dll)
> 01DBF00C: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 01DBF034: 7C91B5F4 7C900000 + 1B5F4 (ntdll.dll)
> 01DBF038: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 01DBF05C: 7C91B5F4 7C900000 + 1B5F4 (ntdll.dll)
> 01DBF060: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 01DBF0BC: 781779EF 78130000 + 479EF (MSVCR80.dll)
> 01DBF0FC: 7817CA54 78130000 + 4CA54 (MSVCR80.dll)
> 01DBF100: 3990D7C8 396A0000 + 26D7C8 (vegas70k.dll)
> 01DBF110: 396C19D8 396A0000 + 219D8 (vegas70k.dll)
> 01DBF118: 3990D7C8 396A0000 + 26D7C8 (vegas70k.dll)
> 01DBF120: 396C19FB 396A0000 + 219FB (vegas70k.dll)
> 01DBF13C: 00650053 00400000 + 250053 (vegas70.exe)
> 01DBF140: 00760072 00400000 + 360072 (vegas70.exe)
> 01DBF144: 00630069 00400000 + 230069 (vegas70.exe)
01DBF148: 00200065 00140000 + C0065
> 01DBF14C: 00610050 00400000 + 210050 (vegas70.exe)
- - -
01DBFFF0: 00000000
01DBFFF4: 00519610 00400000 + 119610 (vegas70.exe)
01DBFFF8: 00A7B160 00400000 + 67B160 (vegas70.exe)
01DBFFFC: 00000000
------------------------------------------------------

Then when I hit OK, Vegas closes. This happens with Vegas 4-7 as I said.
However, I can render to any other DV codec or any other codec period for that matter and not have this problem, so something strange is amiss.

If someone could help me figure this problem out I'd appreciate it muchly.

Comments

busterkeaton wrote on 10/10/2006, 6:26 PM
You should call Sony support and talk to them.
Samus wrote on 10/11/2006, 2:06 PM
No offense but does anyone have an answer other than call tech support?
jetdv wrote on 10/11/2006, 2:34 PM
No offense but does anyone have an answer other than call tech support?

How about: Reinstall the OS from scratch, reinstall Vegas, and then try?

Seriously, your best bet is to contact tech support.
ForumAdmin wrote on 10/11/2006, 2:49 PM
Are you using the Sony DV codec for both reading and writing?
FrigidNDEditing wrote on 10/11/2006, 2:53 PM
Just what codec are you talking about when you say DV file?
"However, I can render to any other DV codec or any other codec period for that matter"

As far as you wanting some other solution beyond saying call tech support, I can't help you, the fact is this is a very strange problem you're having, many if not most of us probably render to the Main Concept DV Codec much of the time we use Vegas. You problem is very much a problem on your end, quite possibly with the codec you are using (I'm not sure if Main Concept allowed Sony to make the codec file accessible but you might try uninstalling and re-installing the codec).

Dave
Samus wrote on 10/11/2006, 6:52 PM
ForumAdmin said: "Are you using the Sony DV codec for both reading and writing?"

Hi, thanks, I captured the videotape with Vegas from my DV camera, and now am trying to render the DV with the internal standard DV output. I liked the one built in the best, so I do appreciate some help with this. Thanks!

EDIT: If it helps, if I do like a small clip or something, Vegas will not crash. It seems to only happen within like 15 minutes or longer in the video. But if I just do like a minute or so it does not crash.
fldave wrote on 10/11/2006, 7:10 PM
When was the last time you did a clean operating system install? It sounds like your hard drive may have taken a hit where some of the core DV codec and related files are.

Did this start suddenly? Install anything besides V7 recently?

Or, maybe a dirty PC? open it up and blow some air around.

Memory chip died? Try memtest. search the forum for the link to the test program.
ForumAdmin wrote on 10/13/2006, 11:43 AM
Please confirm your drives are formatted as NTFS.
ScottW wrote on 10/13/2006, 1:56 PM
You might also want to try blowing the dust out of the inside of your case - get some canned air, blow the dust off the CPU fan and heatsink, motherboard, memory and power supply and any other heat sinks you can see.

--Scott
Samus wrote on 10/14/2006, 1:59 PM
Cleaned off everything, same thing.

ForumAdmin, yes it's NTFS
Samus wrote on 10/18/2006, 3:19 PM
Can someone help? Please? ForumAdmin?
fldave wrote on 10/18/2006, 3:24 PM
What were the results of my recommendations/questions?

Can you post the veg file so others can look at it (no video/audio)?

What kind of video is on the timeline?

Do other veg renders do the same thing?
Samus wrote on 10/20/2006, 3:39 PM
fldave,

I regularly blow dust out of my PC.

This started suddenly, yes. It started even before I had V7 installed (V6) but this problem happened to ALL versions of Vegas.

I tried memtest, no bad memory.

The video in the timeline is regular DV tape footage captured in Vegas. I am using the finished VEG files inside of Vegas from the individual videos. I never had a problem doing that before.

I have never had other veg renders that were this long (over an hour) so I couldn't tell you if other renders did the same, but doing a 2 minute video or so does not seem to crash it. The video I am having problems with is over an hour, and Vegas crashes anywhere from one second in to 15 minutes, so I don't think it could be related to my footage since it's not the same place every time.

Here is my veg file:
http://members.aol.com/filesftp/videos.veg
fldave wrote on 10/20/2006, 4:12 PM
Samus,

You have 20 nested veg files in this main veg. Nesting taxes system resources somewhat, and one of those is as much memory you can throw at it. Nested veg support I don't think came about until V6, so V5 probably won't work at all. V6 had a problem with lots of veg files, but 20 should be fine, if you have enough physical memory.

How much memory do you have in your system, both physical and page file?

One big thing, make sure your Dynamic Ram option in the preferences video tab is set very low, say 16. The higher the number, the less memory Vegas allows for other operations.

Another way to see what is going on is to launch the Task Monitor and see how much memory you are really using before it crashes.

Also, you can't open a V7 veg file in V6. Once they are opened and saved in V7, V6 will not be able to use it anymore.
auggybendoggy wrote on 10/20/2006, 8:06 PM
dave I have mine set to 600???
I'm having crashing while rendering issues. Should I change this?

Auggy
fldave wrote on 10/20/2006, 8:15 PM
Auggy,
Worth a try. How much physical RAM do you have? Set it to 16 and see what happens. I set mine to zero a lot, until Sony recommended a slightly larger value to someone having render problems. I've found that 16 caused longer render times with some veg files, but if it means it doesn't crash, it's worth it.
auggybendoggy wrote on 10/20/2006, 8:34 PM
I read - using the ?- on the menu bar that it should be approx 64.
I have 1 gb of mem with lots of background progs runnin.
I had it set to 600 and it would render for about 8 min of video (probably for a few hours) and then crash.

I'll try bringing it to 16 like you recommend and give it a go tonight.

I thought this number was ONLY for the preview window. I did not think it would affect the render. I'm guessing that this number allocates and reserves that memory meaning the system is on a shortage to run???


Auggy
fldave wrote on 10/20/2006, 9:19 PM
It takes it away, (seemingly) from the pool of available system memory. So your 400MB left means your render has to go to your swap drive frequently.

V7 has capped the value to 1024, even if you have 2-3GB available.
auggybendoggy wrote on 10/20/2006, 9:27 PM
well I'm droppin it to 16 because I've tried about 5 different things...
for examp.

turn off all audio
turn off professional audio card
render to SD (instead of HD)
render to different formats
and Blammo CRASH!
when I first purchased 7 I tried changing these settings to see if 7 was gonna zoom zoom zoom and while I love its new little features of snapping to everything :) its only prob is crashing ....but like I said I upped it from a small number to 600 and I've been using it since hoping to help my preview....no luck as preview must be scrubbed slowly to get any real time audio-video syncing or preview to play.

I'll keep you posted dave tonight as I let vegas render all night.

Thanks for the help man,

Auggy