Comments

Dan Sherman wrote on 11/24/2005, 10:04 AM
Rebooted.
25% in.
For far,---so good.
OOPS!
Spoke too soon.

"An error occured during current opertion.
An exception occured."

Details,----below
Any help appreciated.

Sony Vegas 6.0
Version 6.0c (Build 153)
Exception 0xC0000005 (access violation) READ:0x25 IP:0x25
In Module 'vegas60.exe' at Address 0x0 + 0x25
Thread: ProgMan ID=0x814 Stack=0xD99C000-0xD9A0000
Registers:
EAX=3305c418 CS=001b EIP=00000025 EFLGS=00210202
EBX=090e1d60 SS=0023 ESP=0d99cf9c EBP=0d99d4e0
ECX=2c563f98 DS=0023 ESI=2c563f98 FS=003b
EDX=0d99cfc4 ES=0023 EDI=00000000 GS=0000
Bytes at CS:EIP:
00000025: .. .. .. .. .. .. .. .. ........
0000002D: .. .. .. .. .. .. .. .. ........
Stack Dump:
0D99CF9C: 006E3ECD 00400000 + 2E3ECD (vegas60.exe)
0D99CFA0: 2C563F98 2C4C0000 + A3F98
0D99CFA4: 27C8B228 27AC0000 + 1CB228
0D99CFA8: 00000000
0D99CFAC: 3327AF40 32F00000 + 37AF40
0D99CFB0: 00665267 00400000 + 265267 (vegas60.exe)
0D99CFB4: 0D99CFC4 0D8A0000 + FCFC4
0D99CFB8: 27C8B228 27AC0000 + 1CB228
0D99CFBC: 3327AF30 32F00000 + 37AF30
0D99CFC0: 2498152B 215C0000 + 33C152B
0D99CFC4: 2C563F98 2C4C0000 + A3F98
0D99CFC8: 00000000
0D99CFCC: 00000000
0D99CFD0: 00000000
0D99CFD4: 090E1D60 09070000 + 71D60
0D99CFD8: 00000000
> 0D99D054: 2FF50900 2FE30000 + 120900 (WMVCore.DLL)
> 0D99D0E0: 7C91B5F4 7C900000 + 1B5F4 (ntdll.dll)
> 0D99D0E4: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 0D99D108: 7C91B5F4 7C900000 + 1B5F4 (ntdll.dll)
> 0D99D10C: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 0D99D2CC: 00CBC5B8 00400000 + 8BC5B8 (vegas60.exe)
0D99D2D0: 00000000
0D99D2D4: 00000000
0D99D2D8: 00000000
0D99D2DC: 0023E200 00140000 + FE200
> 0D99D2F8: 7C90EE18 7C900000 + EE18 (ntdll.dll)
> 0D99D2FC: 7C91B690 7C900000 + 1B690 (ntdll.dll)
> 0D99D304: 7C91B686 7C900000 + 1B686 (ntdll.dll)
> 0D99D308: 7C91B298 7C900000 + 1B298 (ntdll.dll)
> 0D99D314: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 0D99D320: 7C8830E0 7C800000 + 830E0 (kernel32.dll)
> 0D99D324: 7C8830E0 7C800000 + 830E0 (kernel32.dll)
> 0D99D328: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 0D99D33C: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 0D99D348: 7C8830E0 7C800000 + 830E0 (kernel32.dll)
> 0D99D34C: 7C9106EB 7C900000 + 106EB (ntdll.dll)
> 0D99D4A8: 010BD462 01000000 + BD462 (vegas60k.dll)
0D99D4AC: 00000000
0D99D4B0: 0D99D4F8 0D8A0000 + FD4F8
0D99D4B4: 27C8B358 27AC0000 + 1CB358
0D99D4B8: 00000005
> 0D99D4C8: 00664560 00400000 + 264560 (vegas60.exe)
0D99D4CC: 0EAD6A8E 0E4C0000 + 616A8E
0D99D4D0: 00000000
0D99D4D4: 71805493
0D99D4D8: 00000000
> 0D99D4E4: 006665AD 00400000 + 2665AD (vegas60.exe)
- - -
0D99FFF0: 00000000
0D99FFF4: 00501F10 00400000 + 101F10 (vegas60.exe)
0D99FFF8: 00987688 00400000 + 587688 (vegas60.exe)
0D99FFFC: 00000000

ScottW wrote on 11/24/2005, 10:26 AM
Start by doing a dust bunny patrol on your CPU heatsink. Open up the case, and with some canned air, blow all the dust off the CPU heatsink and anything that may have accumulated on the motherboard, fans, etc.
mikelinton wrote on 11/24/2005, 10:36 AM
One option would be to render your nested projects out to two files, then import the rendered files into a new timeline and render that to your MPEG2 file.

That would probably be the best work around...

I've found nested projects to be buggy at times. If you render to a new DV AVI file the quality will be good enough for your client to review it, and should only take a few seconds to dump to an new AVI (unless you have tons of effects).



Mike.
Dan Sherman wrote on 11/24/2005, 10:45 AM
Thanks anyway Scott,
This machine is as clean as a whistle.
It has been gone over from stem to stearn.
Also replaced paste on heat sink.
Do you know what the error message refers to?
Is it in fact a heat issue? Hardware issue of some kind?
Jibberish to me.
Maybe some Sony folks looking in.
In the meantime I'm rendering the old way, with UN-nested project files.
Render's OK so far, 18% in.
Last render stopped at 25%.
A couple of times render refused to start at all.
First time around render stopped deliciously close to the end.
Dan Sherman wrote on 11/24/2005, 10:49 AM
Yeah,---pretty heavy on the effects Mike.
Going to stick with rendered un-nested.
Never had a problem that way.
Was unaware of bugs when rendering nested project files.
Maybe not my machine after all?
Liam_Vegas wrote on 11/24/2005, 11:00 AM
If you still have a render failure - try rendering the project to AVI.. when it crashes you will have a partially completed AVI file. Load that back onto the timeline above your existing tracks. Where that AVI stops is the EXACT point which is likely responsible for the crash.

You may now find that some FX - or other asset (such as some still image etc) is to cause... some change to that might fix things.

You can also continue the render from the point that it stopped... and with any luck it will either complete - or at least get further. Load THAT AVI file into the timeline. Repeat as necessary.

At the end... just render the entire timeline to MPEG (solo the A/V tracks for the rendered pieces otherwise you'll have duplicate audio portions and your levels will be too high). This will render much faster anyway... as the timeline is merely "encoding" and not actually "doing" anything.
Dan Sherman wrote on 11/24/2005, 12:54 PM
I find it surprising that a still image may cause a render failure.
How so, I wonder?
It would seem to my pea brain that still images have much less information to crunch.
For those following this thread,---managed to render un-nested project files.
All went smoothly.
Rendering again,---as I found some stuff to fix.
That's always the way isn't it?
Post render,--the imperfections always stick out like a sore thumb.
Stuff you would never see while auditing the veg file suddenly appear obvious.
Liam_Vegas wrote on 11/24/2005, 3:58 PM
Check back on prior posts regarding use of stills... as surprising and incredulous as it may seem... quite a significant number of crashes have ocurred due to use of stills - either related to the size and/or number of them.

Strange but true.

Glad you solved your problem in any case.