Calling Vegas Experts - (access violation) CRASH

new2Vegas wrote on 6/21/2009, 9:56 AM
This is terrible I have created a movie with many time intensive edits and have about 10 three minute sequences on the time line.

Vegas will "crash" every time I try opening the file and the last 5 minutes of video does not complete rendering upon opening the file and the video events have a "red" color to them.

I have so much time invested in this project and it is due for school "very soon", pleas help me. My PC is very fast w/ AMD Athlon 64 X2 Dual Core Processor 6000+ with 4GB RAM

I HAVE ATTACHED A CRASH REPORT FILE OF VEGAS CRASHING...
Thank you :)


/*******************************************/
crash report
/*******************************************/

Sony Vegas Pro 8.0
Version 8.0c (Build 260)
Exception 0xC0000005 (access violation) READ:0x80808088 IP:0x7C9113B5
In Module 'ntdll.dll' at Address 0x7C900000 + 0x113B5
Thread: VideoCache ID=0x1254 Stack=0x4B9F000-0x4BA0000
Registers:
EAX=80808088 CS=001b EIP=7c9113b5 EFLGS=00010282
EBX=7fcbb164 SS=0023 ESP=04b9f18c EBP=04b9f1c4
ECX=7ffad000 DS=0023 ESI=80808080 FS=003b
EDX=7c97e140 ES=0023 EDI=7c809be7 GS=0000
Bytes at CS:EIP:
7C9113B5: 8B 08 89 4D D8 8B 40 04 ...M..@.
7C9113BD: 89 45 D4 89 08 89 41 04 .E....A.
Stack Dump:
04B9F18C: 7C809BE7 7C800000 + 9BE7 (kernel32.dll)
04B9F190: 7FCB8048 7FAF0000 + 1C8048
04B9F194: 7C80A0B7 7C800000 + A0B7 (kernel32.dll)
04B9F198: 04B9FFA4 04AA0000 + FFFA4
04B9F19C: 7C90E920 7C900000 + E920 (ntdll.dll)
04B9F1A0: 80808088
04B9F1A4: 80808080
04B9F1A8: C0000008
04B9F1AC: 04B9F18C 04AA0000 + FF18C
04B9F1B0: 04B9EDB0 04AA0000 + FEDB0
04B9F1B4: 04B9FFA4 04AA0000 + FFFA4
04B9F1B8: 7C90E920 7C900000 + E920 (ntdll.dll)
04B9F1BC: 7C9113F8 7C900000 + 113F8 (ntdll.dll)
04B9F1C0: 00000000
04B9F1C4: 04B9F218 04AA0000 + FF218
04B9F1C8: 153B7AD0 15380000 + 37AD0 (WMVDECOD.dll)
> 04B9F1DC: 153A8658 15380000 + 28658 (WMVDECOD.dll)
> 04B9F1EC: 153973B3 15380000 + 173B3 (WMVDECOD.dll)
> 04B9F1FC: 15398A85 15380000 + 18A85 (WMVDECOD.dll)
> 04B9F21C: 15398B2E 15380000 + 18B2E (WMVDECOD.dll)
> 04B9F228: 1538B2D4 15380000 + B2D4 (WMVDECOD.dll)
> 04B9F24C: 15390A16 15380000 + 10A16 (WMVDECOD.dll)
> 04B9F250: 32564D57 32420000 + 144D57 (colorcorrector.dll)
> 04B9F278: 151234A0 15110000 + 134A0 (WMVCore.DLL)
> 04B9F298: 32564D57 32420000 + 144D57 (colorcorrector.dll)
> 04B9F314: 32564D57 32420000 + 144D57 (colorcorrector.dll)
> 04B9F354: 151BA179 15110000 + AA179 (WMVCore.DLL)
> 04B9F38C: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F39C: 7C910222 7C900000 + 10222 (ntdll.dll)
> 04B9F3A0: 7C91019B 7C900000 + 1019B (ntdll.dll)
> 04B9F3A4: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F3B4: 7C910222 7C900000 + 10222 (ntdll.dll)
> 04B9F3C8: 7C911028 7C900000 + 11028 (ntdll.dll)
> 04B9F3CC: 7C911086 7C900000 + 11086 (ntdll.dll)
> 04B9F3D0: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F3E0: 7C910222 7C900000 + 10222 (ntdll.dll)
> 04B9F3E4: 7C91019B 7C900000 + 1019B (ntdll.dll)
> 04B9F3E8: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F3FC: 7C90E920 7C900000 + E920 (ntdll.dll)
> 04B9F400: 7C936F40 7C900000 + 36F40 (ntdll.dll)
> 04B9F40C: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F418: 7C80AC61 7C800000 + AC61 (kernel32.dll)
> 04B9F460: 7C910222 7C900000 + 10222 (ntdll.dll)
> 04B9F480: 7C90E920 7C900000 + E920 (ntdll.dll)
> 04B9F484: 7C910228 7C900000 + 10228 (ntdll.dll)
> 04B9F48C: 7C910222 7C900000 + 10222 (ntdll.dll)
> 04B9F490: 7C91019B 7C900000 + 1019B (ntdll.dll)
> 04B9F494: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F4B4: 0144E00B 01260000 + 1EE00B (vegas80k.dll)
04B9F4B8: 0000007F
04B9F4BC: 017A0178 017A0000 + 178
04B9F4C0: 0000123A
04B9F4C4: 4F1F6A90 4EA50000 + 7A6A90
> 04B9F4C8: 0144E9E1 01260000 + 1EE9E1 (vegas80k.dll)
04B9F4CC: 4F200980 4EA50000 + 7B0980
04B9F4D0: 0000000C
04B9F4D4: 017A0178 017A0000 + 178
04B9F4D8: 4F200988 4EA50000 + 7B0988
> 04B9F4E4: 7C9374BA 7C900000 + 374BA (ntdll.dll)
> 04B9F4F0: 7C910222 7C900000 + 10222 (ntdll.dll)
> 04B9F520: 7C911086 7C900000 + 11086 (ntdll.dll)
> 04B9F558: 7C910228 7C900000 + 10228 (ntdll.dll)
> 04B9F560: 7C90E920 7C900000 + E920 (ntdll.dll)
> 04B9F564: 7C9101E0 7C900000 + 101E0 (ntdll.dll)
> 04B9F56C: 7C9101DB 7C900000 + 101DB (ntdll.dll)
> 04B9F570: 77C2C3C9 77C10000 + 1C3C9 (msvcrt.dll)
> 04B9F57C: 77C2C3CE 77C10000 + 1C3CE (msvcrt.dll)
> 04B9F584: 1530A270 15110000 + 1FA270 (WMVCore.DLL)
> 04B9F588: 32564D57 32420000 + 144D57 (colorcorrector.dll)
> 04B9F5A0: 77C35C94 77C10000 + 25C94 (msvcrt.dll)
> 04B9F5A4: 77C12088 77C10000 + 2088 (msvcrt.dll)
> 04B9F5AC: 77C2C3CE 77C10000 + 1C3CE (msvcrt.dll)
> 04B9F5B0: 77C2C3E7 77C10000 + 1C3E7 (msvcrt.dll)

Comments

musicvid10 wrote on 6/21/2009, 10:04 AM
To isolate your problem, you could:
1) Open your media in a new project and see if it crashes.
2) Recapture your media and see if it crashes when you add it in your old project.

If by chance you captured your video to WMV using Windows Media Maker, you are better off capturing in Vegas and starting anew.

You may want to see this thread for some general tips.
new2Vegas wrote on 6/21/2009, 10:10 AM
Hi musicvid, thanks for responding...

To isolate your problem, you could:
1) Open your media in a new project and see if it crashes.

*** I had tried that and it also crashed, I started a new file and brought the original .veg in and it almost seemed to complete rendering but crashed as soon as I clicked the mouse on the timeline.


2) Recapture your media and see if it crashes when you add it in your old project.

*** What do you mean by "Recapture your media"??? I am new here so I don't know all the lingo.... :)




re: "If by chance you captured your video to WMV using Windows Media Maker, "

***no WMM... I had captured my video using a logitech orb webcam and it creates .wmv files
TheHappyFriar wrote on 6/21/2009, 10:27 AM
To eliminate a non-video issue, move all the videos to a different spot on your drive. Vegas will say they're missing, click the ignore option for all of them.

If it opens, it's one of your video clips. I'd suggest bringing them in one by one & seeing which one, then fix that one.

But I'm confused how vegas will crash when you open the file but you say you can render all but the last 5 minutes. You can't render what you can't open...

I'd convert all the videos to DV AVI's or HDV Mpeg2's if they're HD, vegas can handle those better.

musicvid10 wrote on 6/21/2009, 10:33 AM
"no WMM... I had captured my video using a logitech orb webcam and it creates .wmv files '

No experience with that here. I would try converting them to a friendlier format first as HappyFriar suggested.
new2Vegas wrote on 6/21/2009, 10:36 AM
Hello HappyFriar

re: "I'm confused how vegas will crash when you open the file but you say you can render all but the last 5 minutes. You can't render what you can't open..."

I guess what I am trying to say is the .veg file will open, then all the video events on the timeline start to fill in so you can see what they are (there are lots of them) and the last 5 minutes worth of video events do not show the content, rather the events show up as blocks of solid red color....

As soon as I try and click the mouse on the timeline that is when I receive the error message - saying I have an access violation.

* I don't know all the technical lingo here but have successfully made lot's of movies with Vegas so far and never had a problem before.

*** Does Vegas start to choke when it has too much to think about with many video clips brought into it.. I have about 35 minutes of video in the session.
TheHappyFriar wrote on 6/21/2009, 11:15 AM
red, 99% of the time = bad video file. Does vegas crash when you click anywhere or just on the area with the red files?

If it's just the area with the red files, delete all those files from the project media list. Perhaps try replacing them with something to see if then vegas crashes or not.

Personally, I'd use something like Super! to convert all your wmv's to DV AVI's.
new2Vegas wrote on 6/21/2009, 12:24 PM
Well of all things... drastic measures here but I think I have fixed the issue (at least for now???)

I went ahead and restored my install of Windows and updated some drivers and now my .veg file opens right on up once again and I may continue!!!!!!!!!

man what a headache ...



HappyFriar
re: "Personally, I'd use something like Super! to convert all your wmv's to DV AVI's"

Who makes Super? is it expensive?