Do you really have a Q9650 Core2Quad that was announced in 2008? I still have a Q9450 and it won't get out of it's own way on UHD video.

Yes, it's a core2Quad. Vegas Pro 14.

Vegas pro 14 working properly on the same video.

My video is an 1080p project.

Thanks.

Do you really have a Q9650 Core2Quad that was announced in 2008? 

Any chance there is a decade of dust clogging your cooling fins?

What is your type of sourcefiles, are they the same you used in 14?
How big is and where do you store your Windows Virtual memory?

Troubleshooting suggestions: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/

Do you really have a Q9650 Core2Quad that was announced in 2008? 

Any chance there is a decade of dust clogging your cooling fins?

There's no dust in my computeur ! it's clean.

What is your type of sourcefiles, are they the same you used in 14?
How big is and where do you store your Windows Virtual memory?

It's the MTS filses from my camera (1080p).

there is one hour of film. Each file is more than 4 GB.

I've modified the Virtual memory.

I test and give you a feedback.

thanks

Thank you Nike Hope

In first time, I desactivate GPU option and put dynamic ram at zero.
Secondely, I use the video project option: match the video parameters of the media to my video file.

the rendering is good, but very slow..... 17 hours of rendering, with all the video effects, for 80 minutes of video in 1080p.......

it's sad that the graphics card isn't activated!

I waiting a "patch" to Vegas...

If you have a trick to run the GPU, I'm a taker

Thanks

What is the rendertemplate and codec you are using to render your project?
Which rendertemplates do you see, screenshot please.

There is no trick in Vpro 16 to use the GPU, you can use it for
- hardware acceleration of many OFX plugins and you can use it
- to start and run the program and you can use it
- at some rendertemplates.

It's all up to you to use the GPU and use the latest driver for that GPU nr. 417.35 dd. 12/12/1918

I've Vegas Vidéo 16 and it crash after 15 minutes working.

It works for 15 minutes, and then crashes?

That sounds to me pretty much an overheating issue. If not at your CPU, it could be you graphics card too. Or even worse, your power supply may near at the end of life.

Can you download GPU-Z, and watch thermal sensors for that 15 minutes?

hello,
I've update graphic card video
I've update windows 10 at october version
Vegas video runing at 77 % before no responding
I see, full memory (vidéo and ram)

Here are the screenshots

So it hangs there. I see GPU memory usage at a limit.

Can you please select a loop region from the end back to the 2/3 of the project, and render and try to render that loop region only?

Does it finish?

Not all the RAM is used, but indeed it looks that the memory of the GPU is all been used.
But you did not show us the possible renderoptions you have, but only your own favorites.
Turn that option off so we can see all your possibilities.
What I don't get is why you did not choose the Nvidia NVENC option for rendering assistance, now you are trying to render with an old codec with less possibilties than the new Magix ones for QSV and NVENC.

Hello J-v,

I testing NVENC and it crashing at 16 % (see picture). It working very speed (*6).

Hello klt,

I'm rendering the last 2/3 of the project tonight.

Result tomorrow.

Ok, note where it hangs. If it hangs near 33%, we have to seriously think its a media problem. Damaged or malformed file.

I think there is something terrible wrong with the memory usage of your used GPU.

With both renders you made and sent here with the screencaptures it turns out to show the full use of the granted amount of memory for encoding. When I compared it to mine, busy with rendering of a 4K AVC project to 50 p with the same NVENC option, you can see the differences in Memory use for encoding. Mine has less than yours and comes to max 40% of the sustained amount of 4GB.

I don't know what is wrong with yours but a repair or trying another slot in your hardware you can always try to do.

The last 2/3 are ok. RAM memory and video memory are full.

Vegas Video also generates an error report.

First it fills the video memory. When it is full, it fills the ram memory. I mean, when everything's full... he crashes.

Thank you j-v,

there must be something I don't understand in my project. Several cameras were used: a 4k, 2 1080p cameras and a go pro. I converted the 4k files after extracting a 1080p zone. I think I made a mistake in the conversion. I'll keep you informed.

Thanks

Hi @thurefil,

Instead of hanging it is crashing now. Do I understand it correctly?

On your screenshot I see insane memory usage, this time not only on GPU.

The graph's show a sudden jump. Is that when you started task manager, or is that jump while rendering?

I suspected there's something wrong with a media, because once I had a similar problem. I edited a presentation, in which a talent talked, that was shot with my camera, and in post I created a series of png's from his powerpoint. But his presentation contained also 3 videos which he shot with his phone, and one of those phone videos caused a huge memory leak in Vegas while working with it.

I'm not sure what the problem exactly was, because mediainfo did not tell anything suspicious about that file (yes, it was CFR). I had to convert it with ffmpeg, but NOT with -vcodec: copy option.

There was something in that file that Vegas could not handle properly.

Another time I blindly inserted a logo which I got as a png, and could not render. That png was insanely huge, can't remember the size, but more than 3000 pixels in each direction. Didn't check the png size, just added to timeline, and wondered how Vegas crashed :) Of course after resizing the png things went normal.

In my case it was easy to find the file being the culprit, but I see you have a tons of events on your timeline. I'd keep to try to render smaller portions of the project, until you narrow down the problem to a few events.

I converted the 4k files after extracting a 1080p zone.

How did you do that?

Thanks to your help, I was able to find the source of the problem.

It is the "AutoLooks" effect that causes memory saturation and vegae blockage.

I unchecked it from my track effects and no more problems...

Thank you to all of you.
I mark the problem as solved.

For those who are interested, the rock band kodama (rock band located in France in Montmorillon) posted the editing (the title was integrated by the band kodama) on youtube here in 480p version :

and on his facebook page here: https://fr-fr.facebook.com/kodamarock/

Thank you again