Sony Vegas Keeps Crashing – HELP!!!

[John Rofrano]

Does it crash right away or does it render for a while and then crash. What exactly happens when it crashes? Is there any error message? The more you can tell us, the better chance someone might figure it out.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Alfie Gale]

To be honest, it really depends. Sometimes it will start to render, the clock will stop and it will not respond. Other times it will literally just close with no message and some times it just says Vegas is not responding immediately.

-AH

[Alfie Gale]

One of the error messages says this:

”An error occured during the current operation.

An exception has occured.

Vegas Movie Studio HD 9.0
Version 9.0c (Build 30)
Exception 0xE06D7363 (Unknown Type) IP:0x76D6B727
In Module ‘KERNELBASE.dll’ at Address 0x76D60000 + 0xB727
Thread: ProgMan ID=0xDC4 Stack=0x5C9E000-0x5CA0000
Registers:
EAX=05c9e42c CS=0023 EIP=76d6b727 EFLGS=00000202
EBX=00000ff0 SS=002b ESP=05c9e42c EBP=05c9e47c
ECX=00000003 DS=002b ESI=5d7f71b0 FS=0053
EDX=00000000 ES=002b EDI=00000078 GS=002b
Bytes at CS:EIP:
76D6B727: C9 C2 10 00 CC CC CC CC ……..
76D6B72F: CC 8B FF 55 8B EC 56 8B …U..V.
Stack Dump:
05C9E42C: E06D7363
05C9E430: 00000001
05C9E434: 00000000
05C9E438: 76D6B727 76D60000 + B727 (KERNELBASE.dll)
05C9E43C: 00000003
05C9E440: 19930520 18EF0000 + A40520
05C9E444: 05C9E4C4 05BA0000 + FE4C4
05C9E448: 5D754924 5D3E0000 + 374924 (sony4vem.dll)
05C9E44C: 0000002C
05C9E450: 5D3ECD42 5D3E0000 + CD42 (sony4vem.dll)
05C9E454: 5D9E0A1C 5D9E0000 + A1C
05C9E458: 00000078
05C9E45C: 00000FF0
05C9E460: 5D7F71B0 5D3E0000 + 4171B0 (sony4vem.dll)
05C9E464: 05C9E470 05BA0000 + FE470
05C9E468: 5D3EF379 5D3E0000 + F379 (sony4vem.dll)
> 05C9E46C: 5D7F75B8 5D3E0000 + 4175B8 (sony4vem.dll)
> 05C9E474: 5D3EFFDD 5D3E0000 + FFDD (sony4vem.dll)
> 05C9E480: 5D3EBEE7 5D3E0000 + BEE7 (sony4vem.dll)
> 05C9E4B0: 5D754924 5D3E0000 + 374924 (sony4vem.dll)
> 05C9E4B8: 5D3EB442 5D3E0000 + B442 (sony4vem.dll)
> 05C9E4C0: 5D754924 5D3E0000 + 374924 (sony4vem.dll)
> 05C9E4C4: 5D752DA8 5D3E0000 + 372DA8 (sony4vem.dll)
> 05C9E4C8: 5D752D80 5D3E0000 + 372D80 (sony4vem.dll)
> 05C9E4D4: 5D6BCB38 5D3E0000 + 2DCB38 (sony4vem.dll)
> 05C9E4D8: 00C6B884 00400000 + 86B884 (VegasMovieStudioHD90.exe)
05C9E4DC: 00000000
05C9E4E0: 5D9E0000 5D9E0000 + 0
05C9E4E4: 00000078
05C9E4E8: 00000022
> 05C9E504: 5D6C253A 5D3E0000 + 2E253A (sony4vem.dll)
> 05C9E510: 5D438C33 5D3E0000 + 58C33 (sony4vem.dll)
> 05C9E5A4: 5D6C7034 5D3E0000 + 2E7034 (sony4vem.dll)
> 05C9E5B0: 5D46E6C5 5D3E0000 + 8E6C5 (sony4vem.dll)
> 05C9E5E8: 5D271DCB 5D250000 + 21DCB (mp4plug2.dll)
> 05C9E614: 5D46E954 5D3E0000 + 8E954 (sony4vem.dll)
> 05C9E620: 5D434E62 5D3E0000 + 54E62 (sony4vem.dll)
> 05C9E638: 5D2543D4 5D250000 + 43D4 (mp4plug2.dll)
> 05C9E6A0: 00F42400 00400000 + B42400 (VegasMovieStudioHD90.exe)
05C9E6A4: FFFFFFFF
05C9E6A8: FFFFFFFF
05C9E6AC: 00000000
05C9E6B0: 00000000
> 05C9E6E0: 0112A880 01120000 + A880 (vegasmoviestudiohd90k.dll)
> 05C9E6E4: 0112A880 01120000 + A880 (vegasmoviestudiohd90k.dll)
05C9E6E8: FFFFFFFF
05C9E6EC: FFFFFFFF
05C9E6F0: FFFFFFFF
05C9E6F4: FFFFFFFF
> 05C9EE64: 00F42400 00400000 + B42400 (VegasMovieStudioHD90.exe)
05C9EE68: 00000002
05C9EE6C: 00000780
05C9EE70: 00000438
05C9EE74: 00000000
> 05C9EED0: 00400010 00400000 + 10 (VegasMovieStudioHD90.exe)
– – –
05C9FFF0: 00000000
05C9FFF4: 00528730 00400000 + 128730 (VegasMovieStudioHD90.exe)
05C9FFF8: 00AF4D58 00400000 + 6F4D58 (VegasMovieStudioHD90.exe)
05C9FFFC: 00000000

”

This is the only message that goes into detail. Hope this helps solve the problem!?

-AH

[Alfie Gale]

I also sometimes get the message ”Sony Vegas Movie Studio has stopped working”…

Aaaargh!

-AH

[John Rofrano]

What I pulled out of that message was:

Exception 0xE06D7363 (Unknown Type) IP:0x76D6B727

Is it possible that there is a type of media on the timeline that is confusing Vegas? Only the Sony developers can read that error dump. I would definitely send it to them in an email and see what they say. That’s your only chance of understanding what might be causing the problem.

One way to debug this is to remove a piece of media from the timeline and try and render, then remove another, then another. When it starts to render, the last piece of media you removed might be the problem.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Graham Bernard]

Y’know, it would be really neat if there was an “audit” of the proposed media, by Vegas, that would identify potential issues prior to render, or come to think about it, when I set up my Project?

Just ‘cos Vegas sells itself on the back of it being format agnostic (which is why I like it! I am not knocking it . . ) , doesn’t mean it shouldn’t/couldn’t also highlight just what isn’t potentially possible, with those same mixed formats? If it can produce this dump, then surely it could also deliver a more USER friendly way of presenting to that User just where the potential issues lie. Seems obvious to me? But that’s where I have a great advantage – I ain’t no programmer – and as such, I can come out with these ill-informed observations.

Sony could really take a load off their Support time if we were given the tools to audit our own Timelines. Too fanciful? Well, that’s me, that’s my own type of hard-wired format my brain works on.

Grazie