I've been struggling for weeks now - hopefully one of you guru's can help.

I've got Vegas 8.0b loaded on my editing workstation. This machine is loaded with a Quad-Core processor, 4GB of RAM, RAID1 system drive - half full, 500GB Video drive - mostly emptly, and dual 7800GT Graphics cards for my monitors.

The clincher (maybe), I'm running Vista.

Worse yet - it's Vista Ultimate 64

Vegas has been terribly unstable. After reading hundreds of posts, I'm still having trouble. I've tried changing between 32-bit and 8-bit for projects. I've tried adjusting virtual memory between 0 and 512K. I've tried excluding Vegas from Data Execution Prevention. Nothing has worked yet.

Generally, Vegas just crashes with unknown exceptions. Finally, this evening, I received the first bit of information. Can anyone help??

Here's the latest error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0x0 IP:0x2303B990
In Module 'mcmpgvdec.dll' at Address 0x23000000 + 0x3B990
Thread: VideoCache ID=0x1420 Stack=0x8F6E000-0x8F70000
Registers:
EAX=00000001 CS=0023 EIP=2303b990 EFLGS=00010212
EBX=00000000 SS=002b ESP=08f6efe0 EBP=08f6eff8
ECX=3efc0000 DS=002b ESI=00000010 FS=0053
EDX=00000000 ES=002b EDI=00005ebc GS=002b
Bytes at CS:EIP:
2303B990: 89 3B EB 95 8D B6 00 00 .;......
2303B998: 00 00 8D BF 00 00 00 00 ........
Stack Dump:
08F6EFE0: 08F6EF80 08E70000 + FEF80
08F6EFE4: 04765D70 04660000 + 105D70
08F6EFE8: 08F6F048 08E70000 + FF048
08F6EFEC: 00AA0000 00400000 + 6A0000 (vegas80.exe)
08F6EFF0: 00AA0000 00400000 + 6A0000 (vegas80.exe)
08F6EFF4: 00005000
08F6EFF8: 08F6F088 08E70000 + FF088
08F6EFFC: 2302E829 23000000 + 2E829 (mcmpgvdec.dll)
08F6F000: 00AA0000 00400000 + 6A0000 (vegas80.exe)
08F6F004: 00000010
08F6F008: 04765D70 04660000 + 105D70
08F6F00C: 03AA3930 039C0000 + E3930
08F6F010: 000002D0
08F6F014: 00000500
08F6F018: 00000006
08F6F01C: 04765D70 04660000 + 105D70
> 08F6F02C: 00AA0000 00400000 + 6A0000 (vegas80.exe)
08F6F030: 046AE558 04660000 + 4E558
> 08F6F034: 23030F82 23000000 + 30F82 (mcmpgvdec.dll)
08F6F038: 04765D70 04660000 + 105D70
08F6F03C: 2DE6E098 2DA20000 + 44E098
> 08F6F05C: 2303118E 23000000 + 3118E (mcmpgvdec.dll)
> 08F6F060: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 08F6F064: 231C728E 23000000 + 1C728E (mcmpgvdec.dll)
> 08F6F06C: 2302EA7A 23000000 + 2EA7A (mcmpgvdec.dll)
> 08F6F08C: 2302D765 23000000 + 2D765 (mcmpgvdec.dll)
> 08F6F09C: 23028344 23000000 + 28344 (mcmpgvdec.dll)
> 08F6F0BC: 231D5018 23000000 + 1D5018 (mcmpgvdec.dll)
> 08F6F0E8: 769222F1 76910000 + 122F1 (kernel32.dll)
> 08F6F0EC: 11691CFE 11680000 + 11CFE (mcmpgdmux.dll)
> 08F6F0F4: 231C2B10 23000000 + 1C2B10 (mcmpgvdec.dll)
> 08F6F0F8: 231C725C 23000000 + 1C725C (mcmpgvdec.dll)
> 08F6F100: 2302D0F0 23000000 + 2D0F0 (mcmpgvdec.dll)
> 08F6F10C: 2303B63E 23000000 + 3B63E (mcmpgvdec.dll)
> 08F6F13C: 230297BA 23000000 + 297BA (mcmpgvdec.dll)
> 08F6F15C: 23027CCE 23000000 + 27CCE (mcmpgvdec.dll)
> 08F6F18C: 23026179 23000000 + 26179 (mcmpgvdec.dll)
> 08F6F1AC: 23216DFD 23200000 + 16DFD (mcmpegin.dll)
> 08F6F1EC: 23218527 23200000 + 18527 (mcmpegin.dll)
> 08F6F21C: 2323A5C2 23200000 + 3A5C2 (mcmpegin.dll)
> 08F6F2BC: 10039EE3 10000000 + 39EE3 (sonymvd2pro_xp.dll)
08F6F2C0: 00195C60
08F6F2C4: 00000000
08F6F2C8: FFC1FFC7
> 08F6F2CC: 004DFFF7 00400000 + DFFF7 (vegas80.exe)
- - -
08F6FFF0: 00000000
08F6FFF4: 005995C0 00400000 + 1995C0 (vegas80.exe)
08F6FFF8: 00ADC81C 00400000 + 6DC81C (vegas80.exe)
08F6FFFC: 00000000

Thanks,

And, an now another one:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0x5A721000 IP:0x1B3E2E8
In Module 'vegas80k.dll' at Address 0x1A80000 + 0xBE2E8
Thread: VideoRender ID=0x1494 Stack=0x10E8F000-0x10E90000
Registers:
EAX=5a721000 CS=0023 EIP=01b3e2e8 EFLGS=00010202
EBX=409f5d3a SS=002b ESP=10e8f1f0 EBP=5a720c10
ECX=3ac8c974 DS=002b ESI=00000219 FS=0053
EDX=000000ff ES=002b EDI=3ac8c680 GS=002b
Bytes at CS:EIP:
01B3E2E8: 89 18 88 50 03 8B 59 03 ...P..Y.
01B3E2F0: 89 58 04 88 50 07 8B 59 .X..P..Y
Stack Dump:
10E8F1F0: 00000003
10E8F1F4: 00000000
10E8F1F8: 59A10368 59650000 + 3C0368
10E8F1FC: 00000960
10E8F200: 00000000
10E8F204: 00000175
10E8F208: 023D00C4 023D0000 + C4
10E8F20C: 7776A6CD 77720000 + 4A6CD (ntdll.dll)
10E8F210: 00000258
10E8F214: 0000001C
10E8F218: 00000708
10E8F21C: 00001C20
10E8F220: 59A10390 59650000 + 3C0390
10E8F224: 3A2C0020 3A2C0000 + 20
10E8F228: 00002580
10E8F22C: 6A290000 6A290000 + 0
> 10E8F24C: 01C7BCE0 01A80000 + 1FBCE0 (vegas80k.dll)
> 10E8F250: 01C7BE50 01A80000 + 1FBE50 (vegas80k.dll)
> 10E8F254: 01C7C1B0 01A80000 + 1FC1B0 (vegas80k.dll)
> 10E8F258: 01C7C6A0 01A80000 + 1FC6A0 (vegas80k.dll)
> 10E8F25C: 01C7BD30 01A80000 + 1FBD30 (vegas80k.dll)
> 10E8F260: 01C7BFD0 01A80000 + 1FBFD0 (vegas80k.dll)
- - -
10E8FFF0: 00000000
10E8FFF4: 0059EE70 00400000 + 19EE70 (vegas80.exe)
10E8FFF8: 0E2803F8 0DFA0000 + 2E03F8
10E8FFFC: 00000000

Such a heart rending plea, shame I ain't no guru.................

It'll be the drivers, it's always the drivers with Vista (from my limited knowledge). Vista Ultimate 64?, yee gads, whatever possesed you?

You could try filing those core dumps with MS but have a strange nagging feeling the result will be a black hole.

Don't suppose a re - load with XP is an option?

Short of begging all possible contributors for the latest Beta drivers, can't think of a way out of your problem. Could be the Raid system(s) or those 7800's or even the sound system. Heck, could even be the MoBo drivers or Bios.

It could, shock, horror, even be Vegas 8.0b itself.

Unfortunately that's the problem with flying experimental aircraft without an ejector system, bit of a bugger when they go wrong.

Think you need to get your head around getting out of "experimental" and going to "tried and true".

You don't say whether this system ever was stable and has "gone bad" or whether it was bad "out of the box".

If it was the latter, you have some serious decisions to make, if it's the former I'd suggest a rollback to a fortified position that works.

Sorry if this is of no use whatsoever, just some food for thought.


CS

Do other programs also crash frequently?
Are the crashes very random or weird? (e.g. not consistent... there is no logic/pattern to it)

If so, maybe the hardware is bad. There are ways to fix/check that (just ask).

It must be Vista 64bit,i'm using Vista 32bit with vegas pro 8 and mine is ok.I also use a quad core,q6600 with 4gb ram, a similar setup to Ted.

The system is remarkably stable - I loaded this box with the vista 64 just to play and, hopefully, take full advantage of quad core, 64 bit processing in the near future. I was pretty amazed to discover that the only two drivers that weren't straightforward were an old webcam (didn't use it anyway - just playing around) and my firewire mixer - which I'm still waiting on a driver for.

Now, vista 64 has been out for a year and three months ago I began loading up this box with apps. Everything was working swimmingly!

This 64 bit system is, by far, the most stable platform I've ever worked on to date! It runs beautifully! When I bought the 8.0 upgrade, I saw the first problems begin, but if I'm not running Vegas, I still have a smoothly running machine. I'm not sure, of course, but it sure feels like something funky is going on between Vegas and Vista 64.

Last month, working on a project, once I had built about ten minutes of it I began to have problems. Vegas kept crashing if I tried to work in it or render anything out from it. I managed to open a new project with identical settings and copy the elements over a few at a time. Once that was done, I was able to work fine, but rendering out was still an issue.

I was praying for the b update to 8.0 every day, hoping it would fix and elemetal problem within Vegas. I cheered when it was released, installed it, and was saddened to discover that even though Vegas seemed more reliable on the whole, rendering was still a problem.

I ended up having to render one minute segments at a time as AVI files. Then I'd open up a new project and put in the AVI's and render those. Sad to work around this way - but it was all I could do.

Every time I open the project, which contains HD .m2t, SD .avi, .wmv, .jpeg, .png, .wav, etc., I am alerted by Vegas that transitions that I've used are not installed. I find this odd, since I've simply selected one of the cross-dissolves, wipes, or blurs from the Sony list of installed transitions. Why, then, would I have to tell Vegas to ignore one dialog box listing four transitions (all zero's) three different times upon opening the project?? This makes me think that there is something seriously wrong with Vegas.

I'm thinking that it could be my install of Vegas, and maybe the best solution would be to remove Vegas entirely and reinstall it entirely. Any thoughts about this?

Okay, this may sound strange, but...

While trying to open the project earlier today, I quickly moved the curser to a spot in the timeline where a straightforward video was playing. It OPENED!!

Now, I've found some commonality in the problems that I've been having. Vegas seems to bite it hard when coming across or dealing with JPEGs.
When moving to that point in the project, it crashes every time. I took that section out (was actually an embedded veg file) entirely. I opened that veg file independently and though it usually plays fine, occasionally it trips and falls too. I used Photoshop to turn those 14 jpegs into PNG files. I opened the subclip and selected those files as replacement files and saved it. I opened the main project, and dropped the updated veg file into my timeline. This time it played!! It has not crashed again.

Now, all I have to do is run a batch script in Photoshop and turn the other 250 pics into PNG's, and then go to the corresponding veg files and update their file references to the png ones.

My fingers are crossed to the point of breaking.

Oh, and while I'm running that background batch script, and typing this update, I'm also capturing HD, and monitoring my email. My quad-core processor is averaging about 35% usage.

I'll update this once complete and let you know definitively if the JPEG's are the problem. Or, more specifically, embedded projects containing JPEG's with motion applied to the JPEG's and cropping applied to the embedded project.

BTW, does anyone know of a "batch" way or a quick way to update over 200 files in a Vegas project without just reassigning replacement files one at a time?

Thanks,

Now, I've found some commonality in the problems that I've been having. Vegas seems to bite it hard when coming across or dealing with JPEGs.

Usually when JPEGS give you grief, it's because they're too large, either the file size or the image size.
A lot of folks like to drop 3-4 MB files that are 3,000 x 2,000 pixels in size right on the timeline.
That can work if it's only a few of them but for 250 a workaround like you discovered is in order.

BTW, does anyone know of a "batch" way or a quick way to update over 200 files in a Vegas project without just reassigning replacement files one at a time?

Copy the originals to a new folder, do a batch operation and place the new ones in the folder that the original ones came from.
This will work if you're doing something like a batch resize but you have to keep the same filename and extension, be it jpg, png, etc. That way, Vegas will see them as if they were the original images.

Tears of joy are streaming down my face.

I was able to locate, with a little detective work, the transition glitches I was experiencing. I had used a Gausian blur on some clips in veg files that get embedded in the master project. I built them weeks ago and have not reopened this veg files until today.

Somehow, multiple instances of the gaussian blur effect was applied in several places where only a single instance was necessary. by deleting the redundant effects and saving out the veg files, I no longer have Vegas barking about installed effects upon opening the project.

Much more importantly, Vegas in no longer stumbling through JPEG's. Yes, mine were large in both resolution and in MB's, but I needed that as I was zooming and panning across them in Vegas. I had already set my images up in a seperate folder, so using Photoshop to rework them was a breeze.

Sadly, though, while "specifying a replacement file" for the missing JPEG's, Vegas was no intuitive. It was intuitive in finding other files that were named the same, but didn't want to cross from JPEG to PNG without my intervention.

In retrospect, I wonder if that might be because under Folder Option in Windows, I have selected to NOT hide file extensions. I'd test this, but I'm more interested in getting productive again with this project.

I sure hope somebody can benefit from this thread and solve their issues - it's been weeks of pain for me and I'd like to think that not only are my problems getting worked out, but that someone else's are as well.

The only test I have left is rendering, which has been the consistent bane of this project. So far, I've tested rendering about the first two minutes - more than it could handle previously - and it has performed flawlessly. I'm very optimistic, knock on wood.

Oh, and by the way, Vista 64 is still rockin' it - it hasn't let me down so far!

Sadly, though, while "specifying a replacement file" for the missing JPEG's, Vegas was no intuitive. It was intuitive in finding other files that were named the same, but didn't want to cross from JPEG to PNG without my intervention.

In retrospect, I wonder if that might be because under Folder Option in Windows, I have selected to NOT hide file extensions. I'd test this, but I'm more interested in getting productive again with this project.

My mistake Ted. In my haste to get this post out, I neglected to test what I suggested to you.
It only works if the files keep the same name AND type which is handy if you're doing a batch resize.
I've edited my post to reflect this "oops".
Glad to hear that you've got things working for you.

Project is still opening and running smoothly - and I'm very happy about that. However, rendering is a different story...

I've been trying to render out AVI's and WMV's and neither has worked. While trying to render a WMV, Vegas crashed due to an unknown error.

Next I tried an AVI and watched it. Vegas crashed giving no error messages at a spot about 50 seconds into a 10 minute video. Next I tried to render the section that failed on the previous attempt - from 40 seconds to 60 seconds. It succeeded.

Next, I tried to render a WMV of a two minute section of the project and received my first error message -though it wasn't very helpful:

An error occurred while creating the media file [file name].wmv.
The reason for the error could not be determined.

This sure is fun! Any ideas??

And, now, a new error message on another WMV render...

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x74EC79
In Module 'vegas80.exe' at Address 0x400000 + 0x34EC79
Thread: VideoCache ID=0x1F60 Stack=0x903D000-0x9040000
Registers:
EAX=00000000 CS=0023 EIP=0074ec79 EFLGS=00010246
EBX=00000000 SS=002b ESP=0903dcd4 EBP=0903dd18
ECX=cc2f0f6a DS=002b ESI=0903dfce FS=0053
EDX=00000000 ES=002b EDI=80004005 GS=002b
Bytes at CS:EIP:
0074EC79: 0F B7 08 66 85 C9 74 2D ...f..t-
0074EC81: 0F B7 C9 66 83 F9 20 74 ...f.. t
Stack Dump:
0903DCD4: 0074F37D 00400000 + 34F37D (vegas80.exe)
0903DCD8: 80004005
0903DCDC: 0000000B
0903DCE0: 0903E3AC 08F40000 + FE3AC
0903DCE4: 0903E3C8 08F40000 + FE3C8
0903DCE8: 0074F689 00400000 + 34F689 (vegas80.exe)
0903DCEC: 0903DD18 08F40000 + FDD18
0903DCF0: 0903E6AC 08F40000 + FE6AC
0903DCF4: 2AD0B210 2AAD0000 + 23B210
0903DCF8: 2AD0B1D8 2AAD0000 + 23B1D8
0903DCFC: 00001944
0903DD00: 00000000
0903DD04: 0903E3C4 08F40000 + FE3C4
0903DD08: 00000000
0903DD0C: 00000000
0903DD10: 00000000
> 0903DF68: 0065004B 00400000 + 25004B (vegas80.exe)
0903DF6C: 00310079 002C0000 + 50079
0903DF70: 00000031
0903DF74: 00000000
0903DF78: 2004E000 20000000 + 4E000
> 0903DF9C: 65100270 64E70000 + 290270 (System.Data.dll)
> 0903DFB4: 01944009 01850000 + F4009 (vegas80k.dll)
0903DFB8: 00000030
0903DFBC: 00220020 001F0000 + 30020
> 0903DFC0: 006F004E 00400000 + 2F004E (vegas80.exe)
> 0903DFC4: 0065006E 00400000 + 25006E (vegas80.exe)
- - -
0903FFF0: 00000000
0903FFF4: 005995C0 00400000 + 1995C0 (vegas80.exe)
0903FFF8: 00ADC81C 00400000 + 6DC81C (vegas80.exe)
0903FFFC: 00000000

Been successful on a couple of one minute renders from different sections of the project, so I'm attempting to determine which areas are the problem areas. On my fourth one-minute section, Vegas crashed with no errors. Now, when attempting to open my project which had been saved and was opening fine, I get this error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x74EC79
In Module 'vegas80.exe' at Address 0x400000 + 0x34EC79
Thread: GUI ID=0x1568 Stack=0x17C000-0x180000
Registers:
EAX=00000000 CS=0023 EIP=0074ec79 EFLGS=00210246
EBX=00000000 SS=002b ESP=0017ccd4 EBP=0017cd18
ECX=00000000 DS=002b ESI=0017cfc0 FS=0053
EDX=0017cfc8 ES=002b EDI=80004005 GS=002b
Bytes at CS:EIP:
0074EC79: 0F B7 08 66 85 C9 74 2D ...f..t-
0074EC81: 0F B7 C9 66 83 F9 20 74 ...f.. t
Stack Dump:
0017CCD4: 0074F2C5 00400000 + 34F2C5 (vegas80.exe)
0017CCD8: 00000001
0017CCDC: 00000009
0017CCE0: 0017D3AC 00080000 + FD3AC
0017CCE4: 0017D3C8 00080000 + FD3C8
0017CCE8: 0074F689 00400000 + 34F689 (vegas80.exe)
0017CCEC: 0017CD18 00080000 + FCD18
0017CCF0: 0017D6AC 00080000 + FD6AC
0017CCF4: 265FB4E8 26490000 + 16B4E8
0017CCF8: 265FB4B0 26490000 + 16B4B0
0017CCFC: 93A9D800
0017CD00: D8000000
0017CD04: 0017D3C4 00080000 + FD3C4
0017CD08: 00000000
0017CD0C: 00000000
0017CD10: 00000000
> 0017CF68: 0065004B 00400000 + 25004B (vegas80.exe)
0017CF6C: 00390079 00340000 + 50079
0017CF70: 00000000
0017CF74: 095708BA 094D0000 + A08BA
0017CF78: C2318483
> 0017CF80: 7A25B44F 79E70000 + 3EB44F (mscorwks.dll)
> 0017CFC0: 006F004E 00400000 + 2F004E (vegas80.exe)
> 0017CFC4: 0065006E 00400000 + 25006E (vegas80.exe)
0017CFC8: 002C0000 002C0000 + 0
0017CFCC: 00310020 00310000 + 20
0017CFD0: 00340034 00340000 + 34
0017CFD4: 002C0030 002C0000 + 30
> 0017CFEC: 0020002C 001B0000 + 5002C (sfwbdmux.dll)
- - -
0017FFF0: 00000000
0017FFF4: 0083F20B 00400000 + 43F20B (vegas80.exe)
0017FFF8: 7EFDE000 7EFDE000 + 0
0017FFFC: 00000000

Next, it opened fine (as if by magic??).

I rendered another one minute section and got a memory low warning. I'm going to adjust the virtual memory down to 0 just to see if things change.

8 out of 10 sections rendered perfectly.

Between minute 2 and 3, it reached 100% on the render and then left me with the following two "Exception has occurred" errors:

First -

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0xC1C0 IP:0x6C81A2
In Module 'vegas80.exe' at Address 0x400000 + 0x2C81A2
Thread: VideoRender ID=0x9D0 Stack=0x1383F000-0x13840000
Registers:
EAX=1383f900 CS=0023 EIP=006c81a2 EFLGS=00010246
EBX=0996b4a4 SS=002b ESP=1383f874 EBP=12638538
ECX=00000020 DS=002b ESI=1383f880 FS=0053
EDX=1383f9fc ES=002b EDI=0000c1c0 GS=002b
Bytes at CS:EIP:
006C81A2: F3 A5 8B 43 0C A8 05 74 ...C...t
006C81AA: 0A 8D 54 24 0C 52 E8 07 ..TR..
Stack Dump:
1383F874: 0996B4A4 09840000 + 12B4A4
1383F878: 00000000
1383F87C: 1383FC48 13740000 + FFC48
1383F880: 00000000
1383F884: 3FF00000 3F250000 + CB0000
1383F888: 00000000
1383F88C: 00000000
1383F890: 00000000
1383F894: 00000000
1383F898: 00000000
1383F89C: 00000000
1383F8A0: 00000000
1383F8A4: 00000000
1383F8A8: 00000000
1383F8AC: 3FF00000 3F250000 + CB0000
1383F8B0: 00000000
> 1383F900: 006C83F7 00400000 + 2C83F7 (vegas80.exe)
1383F904: 0996B4A4 09840000 + 12B4A4
1383F908: 1383F96C 13740000 + FF96C
1383F90C: 0996B430 09840000 + 12B430
1383F910: 00000000
> 1383F9EC: 006BDB04 00400000 + 2BDB04 (vegas80.exe)
1383F9F0: 0996B430 09840000 + 12B430
1383F9F4: 12638538 12600000 + 38538
1383F9F8: 1383FC48 13740000 + FFC48
1383F9FC: 00000702
> 1383FA2C: 006BE10A 00400000 + 2BE10A (vegas80.exe)
1383FA30: 25707268 254C0000 + 247268
1383FA34: 12638538 12600000 + 38538
1383FA38: 1383FC48 13740000 + FFC48
1383FA3C: 00000702
> 1383FA84: 76B11220 76B00000 + 11220 (kernel32.dll)
> 1383FB0C: 006B212A 00400000 + 2B212A (vegas80.exe)
1383FB10: 12638538 12600000 + 38538
1383FB14: 1383FC48 13740000 + FFC48
1383FB18: 00000702
1383FB1C: 00000000
> 1383FBD8: 006B2287 00400000 + 2B2287 (vegas80.exe)
> 1383FC30: 76FA4B40 76F90000 + 14B40 (GDI32.dll)
> 1383FC34: 76FA4B4B 76F90000 + 14B4B (GDI32.dll)
> 1383FD60: 76FACADE 76F90000 + 1CADE (GDI32.dll)
> 1383FD70: 006B26A9 00400000 + 2B26A9 (vegas80.exe)
- - -
1383FFF0: 00000000
1383FFF4: 0059EE70 00400000 + 19EE70 (vegas80.exe)
1383FFF8: 0E126BB0 0DEE0000 + 246BB0
1383FFFC: 00000000


Second -

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0xFF131427 IP:0x4CF635
In Module 'vegas80.exe' at Address 0x400000 + 0xCF635
Thread: GUI ID=0x2134 Stack=0x175000-0x180000
Registers:
EAX=00000000 CS=0023 EIP=004cf635 EFLGS=00210206
EBX=b5d2bdd1 SS=002b ESP=00175b84 EBP=ff13140f
ECX=000000f8 DS=002b ESI=0e0a4f08 FS=0053
EDX=0000002f ES=002b EDI=252b1760 GS=002b
Bytes at CS:EIP:
004CF635: 89 4D 18 8B 4C 24 6C 89 .M..L: 55 1C 8B 54 24 70 89 4D U..T00000000.M
Stack Dump:
00175B84: 68011D92 67FE0000 + 31D92 (QuickTime3GPPAuthoring.qtx)
00175B88: 00175E10 00080000 + F5E10
00175B8C: 00175EC0 00080000 + F5EC0
00175B90: 0E0A4F08 0DEE0000 + 1C4F08
00175B94: 00000000
00175B98: 0E0A6210 0DEE0000 + 1C6210
00175B9C: 00000009
00175BA0: 03BA9F78 03B20000 + 89F78
00175BA4: 76C2A7CD 76C10000 + 1A7CD (USER32.dll)
00175BA8: 00130A4A 00080000 + B0A4A
00175BAC: 00000020
00175BB0: 00130A4A 00080000 + B0A4A
00175BB4: 0200FFFE 01EF0000 + 11FFFE
00175BB8: 00000000
00175BBC: 0000029E
00175BC0: 00000000
> 00175BF8: 00488019 00400000 + 88019 (vegas80.exe)
00175BFC: 00000000
> 00175C00: 68011D92 67FE0000 + 31D92 (QuickTime3GPPAuthoring.qtx)
00175C04: 0E0A4F08 0DEE0000 + 1C4F08
00175C08: 00175EC0 00080000 + F5EC0
> 00175C1C: 0053004D 00400000 + 13004D (vegas80.exe)
> 00175C20: 00530020 00400000 + 130020 (vegas80.exe)
> 00175C24: 00650068 00400000 + 250068 (vegas80.exe)
> 00175C28: 006C006C 00400000 + 2C006C (vegas80.exe)
> 00175C2C: 00440020 00400000 + 40020 (vegas80.exe)
- - -
0017FFF0: 00000000
0017FFF4: 0083F20B 00400000 + 43F20B (vegas80.exe)
0017FFF8: 7EFDE000 7EFDE000 + 0
0017FFFC: 00000000

Tried the second minute a second time - worked perfectly. Go figure.

Yeah Ted,

Welcome to the world of 'Unknown Vegas Errors.' There are many documented on this board, and to be honest, the users on this board know more, or are willing to explain more than SONY. But just for laughs, send Sony that error and if you get a response, that'll be your laugh for that day. I'm glad you got it worked out.

So, I figured it was time to try rendering the entire project since all of the pieces rendered correctly. It got to 27 percent and Vegas crashed.

Upon restarting, I received the following Exception error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) READ:0x0 IP:0x74EC79
In Module 'vegas80.exe' at Address 0x400000 + 0x34EC79
Thread: VideoCache ID=0x1F60 Stack=0x76ED000-0x76F0000
Registers:
EAX=00000000 CS=0023 EIP=0074ec79 EFLGS=00010246
EBX=00000000 SS=002b ESP=076edcd4 EBP=076edd18
ECX=5f942665 DS=002b ESI=076edfc0 FS=0053
EDX=eb851eb8 ES=002b EDI=80004005 GS=002b
Bytes at CS:EIP:
0074EC79: 0F B7 08 66 85 C9 74 2D ...f..t-
0074EC81: 0F B7 C9 66 83 F9 20 74 ...f.. t
Stack Dump:
076EDCD4: 0074F37D 00400000 + 34F37D (vegas80.exe)
076EDCD8: 00000001
076EDCDC: 00000005
076EDCE0: 076EE3AC 075F0000 + FE3AC
076EDCE4: 076EE3C8 075F0000 + FE3C8
076EDCE8: 0074F689 00400000 + 34F689 (vegas80.exe)
076EDCEC: 076EDD18 075F0000 + FDD18
076EDCF0: 076EE6AC 075F0000 + FE6AC
076EDCF4: 256946E0 254C0000 + 1D46E0
076EDCF8: 256946A8 254C0000 + 1D46A8
076EDCFC: 00000000
076EDD00: CA200000
076EDD04: 076EE3C4 075F0000 + FE3C4
076EDD08: 00000000
076EDD0C: 00000000
076EDD10: 00000000
> 076EDF68: 0065004B 00400000 + 25004B (vegas80.exe)
076EDF6C: 00350079 002A0000 + B0079
076EDF70: 00000000
076EDF74: 00000006
076EDF78: 00000000
> 076EDFB0: 65000000 64E70000 + 190000 (System.Data.dll)
> 076EDFC0: 006F004E 00400000 + 2F004E (vegas80.exe)
> 076EDFC4: 0065006E 00400000 + 25006E (vegas80.exe)
076EDFC8: 002C0000 002A0000 + 20000
076EDFCC: 00360020 002A0000 + C0020
076EDFD0: 00300034 002A0000 + 60034
076EDFD4: 00200000 001E0000 + 20000
> 076EE02C: 76B9B132 76B00000 + 9B132 (kernel32.dll)
> 076EE03C: 76B4ACF1 76B00000 + 4ACF1 (kernel32.dll)
> 076EE04C: 76B2D045 76B00000 + 2D045 (kernel32.dll)
> 076EE058: 76B4B7EF 76B00000 + 4B7EF (kernel32.dll)
> 076EE064: 779B1C78 77900000 + B1C78 (ntdll.dll)
> 076EE068: 7792889F 77900000 + 2889F (ntdll.dll)
> 076EE070: 7792BC0B 77900000 + 2BC0B (ntdll.dll)
> 076EE074: 7792BB62 77900000 + 2BB62 (ntdll.dll)
> 076EE07C: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE080: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE084: 253100F8 25310000 + F8 (stl2plg.dll)
> 076EE090: 7797C50B 77900000 + 7C50B (ntdll.dll)
> 076EE094: 779E01A0 77900000 + E01A0 (ntdll.dll)
> 076EE098: 7797C4A0 77900000 + 7C4A0 (ntdll.dll)
> 076EE0A0: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE0C0: 779B1C78 77900000 + B1C78 (ntdll.dll)
> 076EE0C4: 7792B2BF 77900000 + 2B2BF (ntdll.dll)
> 076EE0D4: 7792BC0B 77900000 + 2BC0B (ntdll.dll)
> 076EE0E4: 25310000 25310000 + 0 (stl2plg.dll)
> 076EE0F0: 7792B53A 77900000 + 2B53A (ntdll.dll)
> 076EE0F8: 7796310A 77900000 + 6310A (ntdll.dll)
> 076EE104: 77963251 77900000 + 63251 (ntdll.dll)
> 076EE130: 006E0065 00400000 + 2E0065 (vegas80.exe)
- - -
076EFFF0: 00000000
076EFFF4: 005995C0 00400000 + 1995C0 (vegas80.exe)
076EFFF8: 00ADC81C 00400000 + 6DC81C (vegas80.exe)
076EFFFC: 00000000

Saying OK to the exception error of course crashed Vegas again.

Next time I opened Vegas - it opened fine. I'm beginning to see a pattern here...

Just can't render in Vista.

Partioned my drive and installed XP in a dual-boot scenario. Installed Vegas and opened my project.

I rendered it and 2/3 of the way through it crashed.

I tried a second time and found the following error:

Sony Vegas Pro 8.0
Version 8.0b (Build 217)
Exception 0xC0000005 (access violation) WRITE:0xC1C0 IP:0x6C81A2
In Module 'vegas80.exe' at Address 0x400000 + 0x2C81A2
Thread: ProgMan ID=0x140 Stack=0x301E000-0x3020000
Registers:
EAX=0301efc0 CS=001b EIP=006c81a2 EFLGS=00010246
EBX=47129ee4 SS=0023 ESP=0301ef34 EBP=02c01db0
ECX=00000020 DS=0023 ESI=0301ef40 FS=003b
EDX=0301f0bc ES=0023 EDI=0000c1c0 GS=0000
Bytes at CS:EIP:
006C81A2: F3 A5 8B 43 0C A8 05 74 ...C...t
006C81AA: 0A 8D 54 24 0C 52 E8 07 ..TR..
Stack Dump:
0301EF34: 47129EE4 44950000 + 27D9EE4
0301EF38: 00000000
0301EF3C: 0301F308 02F20000 + FF308
0301EF40: 00000000
0301EF44: 3FF00000 3E900000 + 1600000
0301EF48: 00000000
0301EF4C: 00000000
0301EF50: 00000000
0301EF54: 00000000
0301EF58: 00000000
0301EF5C: 00000000
0301EF60: 00000000
0301EF64: 00000000
0301EF68: 00000000
0301EF6C: 3FF00000 3E900000 + 1600000
0301EF70: 00000000
> 0301EFC0: 006C83F7 00400000 + 2C83F7 (vegas80.exe)
0301EFC4: 47129EE4 44950000 + 27D9EE4
0301EFC8: 0301F02C 02F20000 + FF02C
0301EFCC: 47129E70 44950000 + 27D9E70
0301EFD0: 00000001
> 0301EFE8: 006D4FF6 00400000 + 2D4FF6 (vegas80.exe)
0301EFEC: 02C01DB0 02A70000 + 191DB0
0301EFF0: 0301F308 02F20000 + FF308
0301EFF4: 9C61F9EB
0301EFF8: 00000000
> 0301F0AC: 006BDB04 00400000 + 2BDB04 (vegas80.exe)
0301F0B0: 47129E70 44950000 + 27D9E70
0301F0B4: 02C01DB0 02A70000 + 191DB0
0301F0B8: 0301F308 02F20000 + FF308
0301F0BC: 00001EBF
> 0301F0EC: 006BE10A 00400000 + 2BE10A (vegas80.exe)
0301F0F0: 2933A020 28340000 + FFA020
0301F0F4: 02C01DB0 02A70000 + 191DB0
0301F0F8: 0301F308 02F20000 + FF308
0301F0FC: 00001EBF
> 0301F144: 7C8399F3 7C800000 + 399F3 (kernel32.dll)
> 0301F17C: 009F2118 00400000 + 5F2118 (vegas80.exe)
> 0301F180: 011C62F9 01150000 + 762F9 (vegas80k.dll)
- - -
0301FFF0: 00000000
0301FFF4: 005258F0 00400000 + 1258F0 (vegas80.exe)
0301FFF8: 00ADA678 00400000 + 6DA678 (vegas80.exe)
0301FFFC: 00000000

So, there is either something wrong with my hardware, with Sony Vegas (I'm guessing NOT at this point), or ... my project.

There must be some part or parts of my project that are fighting with Vegas - time to do some more troubleshooting.

Ted, I'd bet on it being a Vegas problem.

You're likely running out of virtual-address space, which is like running out of memory, but it doesn't have so much to do with the amount of memory that you have on your system.

Definitely try rendering with one video rendering thread and only, say, 64MB of video preview cache (both in prefs).

If that still blows up in 8.0b, the file plug-ins are just being too darned greedy. There are several ways to inspect the metrics on the process to determine if this is the case, but it may be most prudent to get your project/media to someone who can debug the problem if you can do it.

Seemingly random crashes with the same project generally stem from memory allocation failures not being handled properly (i.e. telling the user that the application is low on memory) and blowing up later.

You can also render your track contents without filters or motion to uncompressed (or lightly compressed) avi's and bring them back in to do any compositing work. This is akin to "freezing" for audio, and it was something that we all used to have to live with in the days of limited system resources.

What you're running up against is probably the single strongest argument for 64-bit applications. Please keep us posted.

Thanks,
Matt

What you're running up against is probably the single strongest argument for 64-bit applications. Please keep us posted.

Matt, when is the promised 64-bit version of Vegas coming?
I know, NDA says you can't say anything :-(

I would like to add to the image aspect of the discussion I have had best luck with png's, not jpgs. Don't know the why or wherefore, just seems Vegas likes the png's best.

I'm close to slicing my veins too....
I have Sony Vegas Pro 7.0c It all worked fine, but now, when I'm editing my first short, it crashes, and crashes, and crashes, and... it's depressing.

ImageShack - Hosting :: 17808176se8.jpg (http://img230.imageshack.us/my.php?image=17808176se8.jpg)

Andris, consider that possibly a software or hardware change might be the thing to look into.

I had issues with 8 initially, but Vegas 7 was REALLY stable for so many of us. You might consider biting the bullet and wipe your hard drive clean and start over, saving your project files. Good luck, your crashes do sound very frustrating!

The last version of 7 was 7.0e. Might be work updating to the last version.

Of course Edward is right, as always! Didn't notice you didn't have latest version. Definitely try that!

Ok, thanks for your advice!

At the moment I'm having 2 instances of Vegas open.
One is the master which crashes all the time, the other is where I edit particular parts of the short and then just paste it into the master and try to save before everything crashes again.

I don't understand really. My computer is quite powerful, I'm using XP and there is no apparent reason for this to happen. I'm not even using that much effects, except for radial blur in a few scenes.

I now think it really was my computer. I divided my short into smaller fragments of 5 minutes each vegas file and no more crashing.
Maybe it's because I have very many small fragments with slightly variable effects applied to each separately, don't know...

I've got Core 2 Duo 6700 @ 2.66Ghz and 3.25GB of usable RAM.

Glad you found the solution. Your computer is certainly not weak, by Vegas standards. You have a very good processor. Certain tasks we give our PCs are more difficult for it to handle than we are aware. This will cause issues without our knowing why, oftentimes.

I had serious crashing problems when I first updated from Vegas 7 yo Vegas Pro 8. I wound up keeping 7 on the system for renders.

Basically, the problem was that render times were much longer in 8, and it crashed when trying to render a result to various formats, especially Windows Media. I contacted tech support and was advised to check photo sizes.

Turned out that the crashes usually occured when I had large photos, or a composite of several showing at once, when total horizontal res. went to about 4000 pixels.

The fix was resizing the photos such that the max across the image (HD) kept not too far from 2000 pixels.

Ted,

A few things:

Have you run memtest86 on your computer? It's a memory testing program.

Are your Virtual Memory setting high enough? Ideally, you want to set a min and a max amount the same and quite high. You also want to have VM set on all your partitions, drives so Windows can choose which one to use.

Are you rendering to a different drive than either your project or Windows are on? You should be.

Last, but not least, why not install the 64bit version if you can't get to the bottom of this.

HTH.

Ted, I read your first post again. And while I doubt it's the cause of Vegas crashing, Virtual Memory should be much higher than 512K.

It should total at least the full amout of RAM you have and probably more. Let's say you have three drives and 4Gig of RAM. There is no reason you couldn't set the Virtual Memory on each drive to 2Gig. You don't want Windows dynamically resizing VM, so set the lower and upper limit to the same amount.

You also want to fully defragment you harddrives (even if Windows says you don't need to) before increasing VM so each VM allocation will be one contiguous block and not fragmented.

HTH

try switching back to Vegas Pro 8a. It fixed all my problems

It should total at least the full amout of RAM you have and probably more. Let's say you have three drives and 4Gig of RAM. There is no reason you couldn't set the Virtual Memory on each drive to 2Gig. HTH

While your advice is obviously well-intentioned, it is not quite complete. There is an excellent reason he might not want to create page files on secondary drives: you should never create page files on drives that are slower than your OS drive. If drive access times, etc are the same on your secondary drives as they are on your OS, fine, but if not, you are wasting space and slowing your system down.

I would like to throw out that I believe the simplest, safest advice one can give to anyone is to allow windows to manage page files. I run without page file sometimes, and run all sorts of configurations as the mood strikes me, but truthfully it all comes out about the same, and I never notice much difference.

I agree it likely has nothing to do with his crashes.