It's Vegas Pro 365, that is the name of the subscription service. There is no more "Sony" Vegas. Sony sold it 4 years ago.

For Nvidia, you want to use the Studio drivers, not game ready.

If this does not help and you still have that same error, there may be a problem with your GPU hardware.

If you still have issues after that, go into preferences and disable GPU acceleration both in the video tab and in video decoding in the file i/o tab, see if the crashes stop.

I am currently trying to use the monthly MAGIX subscription of Sony Vegas Pro.

😆
This would be perfect if there was some sort Sonic Foundry reference in it too.

It's Vegas Pro 365, that is the name of the subscription service. There is no more "Sony" Vegas. Sony sold it 4 years ago.

For Nvidia, you want to use the Studio drivers, not game ready.

If this does not help and you still have that same error, there may be a problem with your GPU hardware.

If you still have issues after that, go into preferences and disable GPU acceleration both in the video tab and in video decoding in the file i/o tab, see if the crashes stop.

 

 

I don't believe you use "the monthly MAGIX subscription of Sony Vegas Pro"

The name must be another.

Which driverversion exactly ( number) do you use with your Nvidia?

Which Windows version?

What are your projectproperties?

Which are your sourcefiles?

Which is your rendertemplate and what is the goal of your render?

Thank you for your reply,

Sorry, I did mean Magix Vegas Pro 365, I'm just used to calling it 'Sony' Vegas.

The driver version is the NVIDIA GeForce GTX 1650 driver with GeForce Game Ready Driver Version: 445.87

I am running Windows 10.

Project properties are 3840x2160, 59.590 fps

Source files are gopro video .MP4 video files 3840x2160, 59.590 fps

My Render goals are a Sony AVC AVCHD 1440x1080-60i

Let me know if you need more information.

Thank you for the information you supplied.
No problem for me to render that kind of file, but your exact rendertemplate is not possible.
60i is only possible when rendering to AVCHD with that Sony AVC codec.
What is the reason (goal?) you render with that very old Sony codec in VPro 17?
Magix has a lot better AVC codec with also good help at rendering from your NVidia GPU

Further, the Vegas development advice not to use the gamedriver for your GPU but the much better and stabile Studio driver, the last one for your GPU is nr. 442.92

As always when I read of this kind of issues, I have to share my experience and maybe for someone will prove to be useful information:

For unknown (by me and by all the other people I talked with) reasons, with ANY other driver than the old nVidia 399.24 for my 1050Ti, Vegas gets chocked and freezes and I have to kill it in Task Manager as gone it is. The other option, which is not acceptable, is to turn GPU off completely.

So, in order to prevent Windows to update this old driver I had to change some ”group policies” after doing some research on the net, of course.

Just my experience.

@adimatis

I don't know the people you normally are talking to, but this

with ANY other driver than the old nVidia 399.24 for my 1050Ti, Vegas gets chocked and freezes

I don't see and I never did with a lot of others.
From the time on that especially the Studio drivers has been introduced the NVidia's that have NVENC encoding and NVDEC decoding are functioning better and better.

@j-v

Hi, do you recall our last discussion here? https://www.vegascreativesoftware.info/us/forum/difference-in-timeline-playback-performance--119796/

Guess what I have been doing in the meanwhile? :)

I decided right after that conversation to give it another try, why not... Maybe something will be different... So went ahead and remove the Windows restriction to driver updates, downloaded and installed the latest nVidia driver version, opened Vegas. All good. Started to edit, all fine for about 15 minutes. Then BANG! Oh what a glorious crash! And as always before, as I noticed, on a cross-fade or on a beginning of a overlayed clip.

All same old!

So, I did some work in the meanwhile with other program and then actually yesterday I did again the whole procedure on reinstalling the old 399.24 GPU driver and making sure the automatic Windows updates do not update it. Again, anything other - admittedly I am talking about anything NEWER - then this driver version turns working with Vegas basically into a headache and a lottery. And a very frustrating experience which does not do justice to editing in Vegas itself.

For reference, here is the original thread about this, a while ago. Thank you again everyone for helping me to actually figure this solution, which is not altogether unacceptable. :) https://www.vegascreativesoftware.info/us/forum/a-suggestion-please-constant-crashes-with-gpu--115293/

Now...

I admit the issue I have is weird, unheard of, hard to believe, inexplicable, all that.

I also realize - and you all do I am sure - that this might be a very peculiar issue between Vegas 17, my Asus notebook, the 1050Ti in it and the work-together with the on-board UHD630, the other components, etc. So that is that and could be a very specific thing to my system and maybe NO ONE else has it in the whole world, given that each system is a unique environment. More often than not, could be very difficult to pin down such a problem, particularly with notebooks, which by definition are rather closed systems...

BUT, like I said, IT IS my experience and maybe someone can learn something from it that might help them. I know I was happy to understand it and that allowed me to continue using Vegas.

So, in conclusion, given all this, I have to say, updating to the latest driver version does not ALWAYS work... Quite the opposite. And this has nothing to do with the people I talk with, it is a fact. :)

Thanks for reading all of this.

Your problem and your workaround, let's get back to @Katharine-Chevrier and her problem.

Right.

So, @Katharine-Chevrier, my suggestion is to try installing an older driver, despite the usual advice routine.

That might be a workaround that might work for you too.

Right.

So, @Katharine-Chevrier, my suggestion is to try installing an older driver, despite the usual advice routine.

That might be a workaround that might work for you too.

Your problem sounds identical to mine and I have since given up on Vegas Pro and am now working with Adobe products all together, but for the sake of argument I will be attempting your fix and letting you know if it works for me. Plus the toggling between tool settings is annoying compared to the short keys in Vegas.

I have never been more frustrated with software issues in my life, and I wish the manufacturer would take on some of the responsibility for fixing the problem or at least providing better customer service technical support.

Thank you for your help.

Thank you for the information you supplied.
No problem for me to render that kind of file, but your exact rendertemplate is not possible.
60i is only possible when rendering to AVCHD with that Sony AVC codec.
What is the reason (goal?) you render with that very old Sony codec in VPro 17?
Magix has a lot better AVC codec with also good help at rendering from your NVidia GPU

Further, the Vegas development advice not to use the gamedriver for your GPU but the much better and stabile Studio driver, the last one for your GPU is nr. 442.92

I tried the updated more stable studio driver and it doesn't work either. Same issues arise.