Vegas 13 crashing render under Windows 10

[Mateusz Duzinkiewicz]

Somebody must do the hard work 🙂

[Mateusz Duzinkiewicz]

Driver you say? It could be it, day before my Vegas 13 broke down, there was some update from Microsoft regarding NVIDIA. I will remove that update and tell.

[Steve Rhoden]

We here on this forum has been doing the hard work for years now
Mateusz, None of us here is being paid for any of this, we are ordinary
users of Vegas just like you!

Steve Rhoden (Cow Leader)
Film Maker & VFX Artist.
Owner of Filmex Creative Media.
Samples of my Work and Company can be seen here:
https://www.facebook.com/FilmexCreativeMedia

[Mateusz Duzinkiewicz]

I rolled it back and deleted all updates ect. but unfortunetly it did not help. I am going to clean install Windows 10 and then test V13 again. Tomorrow will tell.

[Russ Froze]

Mateusz,
I did not wish to chime in this conversation at first because I do not have Win 10, hell I refuse to move from Win7. That made clear, I relate my experience with Vegas 13. As usual I waited till the last minute to do and upgrade from Veg 12 avoiding the plethora of bugs from new releases. Veg 13 opened up great all the plugs are there and everything works until it’s time to render. Problem is the rendering template is empty, hangs for a few seconds and then Vegas crashes. Also I have noticed various frames, panels, windows whatever you wish to call them are not installed.

After several weeks of a support ticket submission, Vegas support got back to me with an extensive list of things to do. In short it’s the old windows permissions problem. Basically uninstall Vegas root through the registry and remove certain entries, create new user account and install Vegas from there and all should work fine. So Vegas support says. I don’t have time to fiddle around with this but I did instal Vegas 13 on a cloned machine where it works just fine.
If you wish I can relay the support info to you but you will have to adjust for Win 10.

And yes Mateusz, we are not paid to do this, we are simply paying it forward for help we’ve received from others in the past. Boy I miss those old TV broadcast fellows that used to peruse this forum. They has decades of experience spanning from the old and obscure up to the moment bleeding edge tech and systems. Debates raged on for months and never, no never did anyone suggest stupidity or some derogatory comment was made. No matter what the discussions, opinions held by others, there was always a respectful tone, that is until the weekend warriors showed up and the slurs began. So we lost access to all that knowledge and experience. So if there is an unsatisfactory answer, just smile politely, say thank you and move along to the next answer.
Russ Froze

[Mateusz Duzinkiewicz]

Thanks for the trick. I made a step backward to Windows 8.1 with Vegas 12, got new project to edit and no time for experimants. By the end of 2014 I will try again, maybe till then Microsoft with Sony will make some improvements.

Yes, in someway that one time I was unpolite, but I am the working man and got no time for messing around with people who do not understand what this forum is for.

[Russ Froze]

I Know, I’ve been watching. But I just can’t loose any more veterans, soo we must play nice. We are all very sensitive artists you know. Good luck and maybe some day soon you can get back to us on how things are turning out for you and stick around, all too soon it may be your turn to parcel out hard earned experience.
Russ Froze

[Mateusz Duzinkiewicz]

On Microsoft forum there is new info about Vegas. In this thread one person claims, that fix worked, other it did not. Can anybody check it under Windows 10?

https://answers.microsoft.com/en-us/insider/forum/insider_apps-insider_feedback/windows-10-technical-preview-and-sony-vegas-pro-13/2cb2a534-8776-483e-8f2c-424c54beafaa?page=3

“Have you tried going to Control panel as in the picture below and turning on all the .Net Framework versions???
I have had to do that for some software because Net Framework 2.0, 3.0 and 3.5 were turned off during one of the builds”

[Stuart Soled]

I had a similar problem on upgrading from windows 8.1 to 10. what it turned out to be was not a sony vegas problem but an nvidia problem. I found out that when i used my amd radeon r7 260 card , which is a few years old, things worked fine and better than ever. however when i used a newer nvidia card with their drivers. (msi geforece gtx 950 (and i have an msi motherboard and no problem with anything else) it would continually crash during rendering no matter what i did. i went back to the radeon card and now i can render multiple files at once and i have not had a single problem. i certainly do not have good feelings about nvidia at this moment as it took some time to piece this apart and get my vegas pro working again like it used to.