SVMS PE v8.0b: Crash on exit (first ever crash!)

Comments

stevefoobar wrote on 9/10/2007, 10:57 PM
As I said earler, I'm having the exact same exit problem and I filed a trouble report WITH NO RESPONSE WHATSOEVER so far and it's been almost a week....dissapointing. I haven't done anything long enough yet to evaluate whether or not my audio is out of sync. I am also upgraded to 8.0b. I still have Vegas 6 installed and of course, no problems with exiting or sync on this version. Here are my system specs:

Intel MB & chipset
Intel BIOS
Intel Core Duo CPU @ 2.13 gHz
2 GB RAM
2-250GB SATA drives as RAID 0 (striped 500 GB)
ATI Radeon X1600 display
WinXP Pro SP2
IRH wrote on 9/11/2007, 4:40 AM
While I have not experienced this problem, note that there are a couple of threads in the Vegas forum where a number of users of the new Vegas Pro 8 are having exactly the same problem. Seems clear to me that it's a new problem in the code base common to both Vegas Pro 8 and VMSP 8.0b. For this reason, I'd guess you'll see a fix reasonably quickly.

(Interestingly, on the Vegas Pro side, as with this thread, all users experiencing this problem appear to be running XP rather than Vista).

Ian.
dogwalker wrote on 9/11/2007, 11:04 AM
In addition to having XP, I wonder how many of us (yes, I have problems with VMS, too) have dual core systems and/or ATI video cards...
prius2004 wrote on 9/11/2007, 1:00 PM
I have Vegas Pro 8, not SVMS, and am running it under XP Pro with an ATI card and P4 processor so the "memory error issue" is definitely not limited to dual core systems.

It also does not appear to be limited to systems with ATI cards as others have reported experiencing exactly the same issue with GeForce cards (fwiw, I also initially suspected it might have something to do with my ATI card and/or s/w).
dogwalker wrote on 9/11/2007, 1:24 PM
Good info, prius. Ok, what about sound cards? I have an Audigy.
prius2004 wrote on 9/11/2007, 1:33 PM
I have an aging Creative Live!. However, I have noted that others with this same issue are using different sound cards so I'm not sure it's the sound card (or drivers) that are the problem here. Further, I upgraded from Vegas 7 (before that I had Vegas 5) and had no issues with either of those versions.
dogwalker wrote on 9/11/2007, 2:35 PM
hmm, what about chipsets? I have via. I have to head out for a while, but I do hope Sony is noticing these. We're trying to help them isolate configurations where the problems are occuring.

Thanks for the help!
Himanshu wrote on 9/11/2007, 7:55 PM
Many of these replies aren't related to the original post...would you please consider starting a new thread to discuss unrelated topics? That would help others interested in the original topic remain involved in the thread otherwise they would tend to ignore new messages. Thanks for your understanding.

Update on my original issue: two different techs have contacted me about the issue, and so far we have gone through uninstall, reinstall, uninstall, reinstall, stop all processes, take snapshots of error message, etc. The last piece of information I have is that my crash info was being considered to be passed on to the development team.
JediKnight2 wrote on 9/12/2007, 12:10 PM
They know about it. This is happening to me as well. It did it with both the basic and platinum versions.


VegasMovieStudio80.exe - Application Error

The instruction at "0x02a72fa9" referenced memory at "0x02ae22d0". The memory could not be "read".

Click on OK to terminate the program

Their reply was that they have escalated this to development already. It doesn't seem to mess anything up, just aggravating.
Himanshu wrote on 9/13/2007, 5:00 PM
JediKnight2:

It is still dangerous. Here's what I see on occasion after the crash on exit, which has caused me to uninstall 8.0b and go back to 8.0 from the disc:

---------------------------
Sony Vegas Movie Studio Platinum 8.0
---------------------------
The last session did not complete properly.

You can restore the autosaved version of the project that was opened, but you should use the Save As command to rename it immediately.

Would you like to restore the autosaved project?
---------------------------
Yes No
---------------------------

Any case, I heard back from the tech today and they said it's a known issue and will be fixed in the next update.
joecozz wrote on 9/14/2007, 11:39 AM
This is an improvement over Pinnacle. They never acknowledged a problem.
Joe
joecozz wrote on 9/14/2007, 11:40 AM
This is an improvement over Pinnacle. They never acknowledged a problem.
Joe
joecozz wrote on 10/2/2007, 5:30 PM
Hi Himanshu:
Any updates on the crash with version B?
Joe
Himanshu wrote on 10/3/2007, 8:58 PM
Howdy Joecozz,

My case has been closed with tech support's last response being that this is a known, logged issue that would be fixed in the next release. No further information was promised, so it's just wait till the next patch. Luckily none of the crashes have damaged any of my projects in 8.0b so far, and since my OOS issue was resolved, I am working with 8.0b in spite of the crash-on-exit.
joecozz wrote on 10/6/2007, 4:34 AM
I'm holding off on moving to 8.0b. I will try c when it becomes available.
Thanks
Joe
Himanshu wrote on 11/18/2007, 8:32 PM
Version 8.0c has resolved the issue for me. Thank you Sony for fixing this crash.
jmnvideo wrote on 10/22/2008, 10:37 AM
I have 8.0c installed, and I am experiencing the same problem. I have just e-mailed tech support, and expect a reply in the next day or two.
Himanshu wrote on 10/23/2008, 5:30 PM
Are you really getting the exact same message (including the hex address)? My error was already resolved as I stated. Good luck getting your issue resolved as well.