Vegas Pro 11 64-Bit Crash Fix

kakman wrote on 5/1/2012, 10:16 PM
After seeing a post by Royce1 in the "Vegas 11 is Crash Happy" topic I decided to try his "fix". The fix is:

On April 27, 2011, - I suddenly tried changing Vegas Pro 11 by using WINDOWS compatibility feature. (Right click the Icon of Vegas, choose Properties and then choose the Compatibility Tab) - The compatibility options are:

Windows Service 2008
Windows Vista
Windows Vista (Service Pack 1)
Windows Vista (Service Pack 2)
Windows 7

Royce1 selected Windows Vista. I have used Windows 7 (which will be an option if you have Service Pack 1 installed).

This has SOLVED the crash issues I was experiencing, which were that Vegas would crash whenever I used any of the Sony GPU Accelerated Transitions, Video FX, and the Titles & Text Media Generator as well as ANY of the New Blue OFX transitions or Video FX. At times the crash was immediate, other times I would have to edit the item 1 or 2 times before Vegas would crash.

I am using the current Build 595.

I had previously tried many of the "fixes", including a clean install, an install to a new user account, etc., etc., etc.. None of these "fixes" did anything to alleviate the constant crashing of Vegas.

If you have had similar issues I recommend that you give this a try as it is easily reversed if it does not solve your issues.


Kevin

Comments

MTuggy wrote on 5/1/2012, 10:20 PM
I did a couple tests with Sony Text and Titles and with NB Titler Pro in the same timeline, which used to always crash. In Vista, service pack 2 compatibility - no crashes.

Now I'll test Windows 7 compatibility mode.

Maybe we'll get lucky and this is the fix!!

MT
ddm wrote on 5/1/2012, 10:47 PM
How strange. I just ran into a demo of a program that crashed immediately upon loading, Windows 7 suggested that I run it in compatibility mode, I chose Vista x64 and it ran fine. I don't have any issues with Vegas 11 but I thought it strange that the program, which is called PostWorkshop Pro, would just work in compatibility mode even though it was a Windows 7 x64 app. And then to see it mentioned here just a few days later. Would be a nice fix for all of the people who are having problems. Wonder what Vista x64 compatibility does differently?
rmack350 wrote on 5/2/2012, 12:02 AM
I was just searching around to try to figure out what Compatibility Mode does. A few links:

http://stackoverflow.com/questions/8822198/how-does-launching-an-app-in-compatibility-mode-in-windows-affect-the-app-and-ho

http://blogs.msdn.com/b/oldnewthing/archive/2003/12/23/45481.aspx#45590

My search was for "What does Windows Compatibility Mode do?"

My guess that there's some part of Vegas that leveraged something in Vista or a pre-servicepack win7 that's since been changed. Assuming this is really working, of course.

Rob

<edit> Also, if you're curious and recent history minded: http://www.joelonsoftware.com/articles/APIWar.html </edit
Laurence wrote on 5/2/2012, 12:22 PM
I may be a bit premature in saying this, but I'm currently running the latest version of V11 in Windows 7 compatibility mode and I've been working for a good 10 minutes without a crash, doing text and logo animation which usually crashes V11 right away. This is the longest I've gone in V11 yet without a crash. It is strange that this would make a difference because I'm using Windows 7 and so the Windows 7 compatibility mode shouldn't be doing a thing. None the less, I'm working away and things feel downright stable. Maybe there is something to this compatibility mode fix! I sure hope so. Anyway, so far so good.
Jøran Toresen wrote on 5/2/2012, 12:52 PM
Kevin, and all other, I hope you report this to SCS.

Jøran
Laurence wrote on 5/2/2012, 12:55 PM
20 minutes and still going strong. I quite and restarted (still getting the error on quitting the program). This is by far the longest I've gone without Vegas crashing. Could it be that simple? Wow!
JJKizak wrote on 5/2/2012, 12:58 PM
As I have said all along, Vista will suck up any software you have laying around the house so make sure you lock it up to prevent suck up.
JJK
Leee wrote on 5/2/2012, 1:02 PM
I'm wondering if this method is related to the fix I tried a couple of months ago, which was to just start a new Windows user profile and use that while running Vegas. This seemed to make using Vegas much more stable, but not 100% crash proof. Something to do with Windows using less drivers maybe? Less memory used?
rmack350 wrote on 5/2/2012, 1:07 PM
What I'm gathering about compatibility modes is that sometimes a bit of software will be written to exploit a quirk of Windows and that if the quirk is later corrected it'll break the software. Compatibility modes cause an application to make use of OS "shims" that restore the quirk for that particular application.

Since you're able to run steadily in Windows7 compatibility mode I'm guessing that there was a change in Service Pack 1 and compatibility mode restores a quirk from before the service pack.

Rob
vtxrocketeer wrote on 5/2/2012, 1:25 PM
To those who have newfound stability by running in Windows 7 compatibilty mode, have you found that you've LOST anything in Vegas? For instance, a broken feature or something changed that depended on whatever difference resides between Win 7 and the compatibility mode?

I can do just ONE thing (that I frequently use) that will crash Build 595 every time, so if running compatibility mode "fixes" that whilst disturbing nothing else, it's a win for me.

-Steve
Leee wrote on 5/2/2012, 1:38 PM
The only thing that still won't work for me in compatibility mode is NewBlueFx's Titler Pro. In fact now all I have to do is select in (not even apply it to a track) and it will totally freeze Vegas. I have to run Task Manager to close Vegas.

Now I'm not sure if it's because I'm running the "wrong" version of Titler Pro, I downloaded the latest build, but now that I can't even get it to run there's no way (that I know of) to check which version I have installed?
MalcolmM wrote on 5/2/2012, 2:53 PM
Not working for me!

For the past three days I have not been able to render a project, I have updated everthing and uninstalled / reinstalled my graphics drivers and VP11, nothing is working!

Found this tip and it is not working either.
paul_w wrote on 5/2/2012, 3:07 PM
Not working for me either :( newBlue still crashing.. Tested in all modes. But it does sound like its good for others, so good luck to all.

Paul.
Tom Pauncz wrote on 5/2/2012, 3:40 PM
The only combo working for me is VP11/595, nVidia 296.10 driver and NBT build 111213.

Tom
rmack350 wrote on 5/3/2012, 12:13 AM
Setting VP11-64 to Windows7 compatibility mode seems like it's solve one particular type of crash that was dogging me. It probably doesn't solve everyone's problems though.

Rob
MalcolmM wrote on 5/3/2012, 3:29 PM
Finally, after 3-1/2 days of constant crashes, I am able to render my file!

I set project properties to 8 bit from 32 bit FP, for my project and the nested veg files I was using. With everthing set to 8 bit I am able to render again!!!

This is the first time I have not had my project properties set to 32 bit FP? What could have changed in my system to require resetting my properties to 8 bit?

This has been a very strange week with VP11
JeffyB wrote on 5/11/2012, 10:32 AM
Vegas seems to be bugged rendering with the GPU in 32 bit. I always have to turn GPU acceleration off (in the options, preferences, video properties tab) to be able to render 32 bit.

There's sure a lot of annoying workarounds needed in V11 :(
Royce1 wrote on 5/11/2012, 10:43 PM
Hi - I am Royce - the one who figured out the compatibility thing - (I was on my final straw - and it just came to me to try) - great to hear that it is helping others. I haven't had a crash since. I can even run chroma key, title & text and New Blue all on two layers of video - and render - no crashing - !!

For those who are still experiencing the crashing...

Ideas to try ..

1) Check to see if you have other start up programs loaded via the "msconfig" and make sure you don't have a lot of not needed / junk loaded in the start up.

2) Restart your computer - Then change the compatibility of Vegas Pro 11 via the right click - and try "Windows Vista"

3) Then restart your computer again - Then check to see if the compatibility is still set for Windows Vista

4) Then start Vegas Pro 11

Maybe these ideas will help !
Laurence wrote on 5/11/2012, 10:52 PM
I just want to thank you Royce. I still get crashes at render in compatibility mode, but that is way better than the constant crashes I was getting before.

Just a couple of questions for you or anyone else who may no.

1/ is there a performance hit in compatibility mode?
2/ Why would this work? It does, but it doesn't make sense to me why.
Royce1 wrote on 5/12/2012, 6:42 PM
Did you try different "compatibility" modes?

But before you use one - restart the computer and then change it.


Sony took down my find and so far it seems to be helping a lot of people.

I believe this has to do with the code of 64bit.

BTW: I had similar problem with Samsung printer - and oddly the other day, Microsoft sent me two updates exclusively for Samsung. Also with Microsoft's own official Windows 7 mouse - (the blue light / comfort) with the 64bit machine, the zoom feature for photos that are viewed in Microsoft own photo viewer does NOT work anymore. I was really surprised.

The compatibility rolls back small things that were changed (like others have stated).
michael-wildermuth wrote on 5/13/2012, 3:59 PM
I post this in the event it may be of use to someone.

I was having trouble with periodic crashes in V11 64 bit as many have.

Last Sunday, I ran msconfig and disabled the following from startup:

Norton Online Backup from Symantec
OmniPage from Nuance
SSBkgdUpdate from Nuance
QuickTime from Apple

I did that as part of a regular program of system tuning. Since I disabled these items from startup a week ago, V11 Build 683 has crashed only once. Not perfect, but more stable.

For what it's worth.
chap wrote on 5/16/2012, 6:54 PM
I bought V11 and haven't used it once since a nightmarish weekend of trying to edit with it.

I just downloaded the update, I have an edit to do tonight, and I changed it to compatibility mode.

I am very curious about the results, I have a friend coming in tomorrow, I am sure it will start crashing when he is here cause he is aN FCP editor.

Chap