Yes, hello! :)

It's probably running out of VRAM... your graphics card has its own RAM that VEGAS also needs. Sometimes certain plugins can take too much and not leave enough for VEGAS. For instance, Neat Video, it's possible to set its VRAM usage so high that it causes VEGAS to throw this error, as it does not leave enough for VEGAS to do its thing.

Are you using any effects on your videos? Or other plugins like noise reduction, etc?

VRAM is 12GB. More, than in the recommended configuration.

Yes, I use some effects. I don't think it is too much for a NLE.

Best, if I attach screenshots.

You can see the cursor is at 04.19. This is the farthest the rendered video got, before crashing. It stopped sometimes before this time and never got to the event on the second video track.

I made an other try just now. The rendering started with like 60fps or higher, and then after 5seconds dropped to 1.4 fps. Kept on rendering for like 10 seconds more and then the Problem Riport window popped-up. :(

I have got screen shots and error riports to provide if upload here is possible.

Can you show here such a problem report?

The ZIP file? Or which file do you exactly mean?

To be on the safe side I send you all:
https://drive.google.com/file/d/1VUfUtxQYTH12q64EYAOuF325xjrXgtBE/view?usp=sharing

Is it OK, like this?

No and I think I cannot further help you, sorry

Thank you for trying, I appreciate for your effort! :)

Even having the recommended amount of VRAM doesn't mean that some effect isn't taking all of it and not leaving any for VEGAS to use, which is why I asked which effects you were using. I had 16GB when Neat Video caused the same error on my system, for instance, I had to go into Neat Video's preferences and turn down the amount of VRAM it was taking and then it fixed it.

If slow motion and PiP are all you are using, then it shouldn't be doing this, however.

To figure out what is causing the issue, Try to disable each effect one at a time, and see if it renders without it. If you get a successful render without an effect enabled, we know it was that effect causing the issue and can move forward with troubleshooting it.

Set your dyn. ram preview size to 0 MB and voila!
I also hate rendering crashes, which was never ever exist by me on Vegas19!
But now on V21, not only timeline crashes but also often rendering crashes!
Only solution is to set ram size to 0. But rendering will be much slower in this case.

Dear fr0sty and relaxvideo,
I muted video track 2 and 3, and the rendering went OK with only Pan/Crop aplied to a track 1 video. With super fast fps, dyn.RAM 5% (I did not want to change it yet).

BUT when I switched on track 2, with crop/slowmotion/PIP, the program crashed again and generated problem details (see below).

However when I was watching closely the memory usage in task manager, I realised Vegas changed to onboard graphics card despite I set every option to Nvidia (to my knowledge).

Is there anywhere else I need to set it to Nvidia?

--------

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 208)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Windows\SYSTEM32\d3d9on12.dll
   Fault Address:       0x00007FFA74443EEB
   Fault Offset:        0x0000000000053EEB

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 208)
   Process Description: VEGAS Pro
   Process Image Date:  2023-11-30 (Thu Nov 30) 05:19:46

Also check this thread to see if you are using/doing anything similar?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-208-the-system-is-low-on-memory-error--143884/#ca900791

Thank you! I checked the other thread. Pagefile is OK, I set it to fix 8GB. Ran rendering, but crash.

I am getting to have a hunch of what happening, but don't know the reason why.

Look et this picture!

Rendering started with Nvidia (like 250fps) and the in a few seconds rendeding changed to Intel onboard GPU (with rediciolus 1.4fps). You see the graph? What is going on?

And again my question is, where else I need to change in Prefernces to make it use ONLY Nvidia?

So how about that? :)

And again my question is, where else I need to change in Prefernces to make it use ONLY Nvidia?

AFAIK nowhere and the strange thing is that in other machines at FileI/O and Video when the Nvidia is choosen it is stated as "Auto Nvidia ....." or "Optimal Nvidia...", like mine

but not with you.
Can you share here a completed screenshot of the Vegas Help/Check for Driver Updates?

@j-v

I also get : Optimal - NVIDIA GeForce GTX 1660

Jøran

What is the best pick?

No conflict in control panel:

And I installed the latest driver from Nvidia site 3 days ago. Actually I made a clean install, inclueding Win11.

What is the best pick?

For decoding the Intel is the best pick. Raw doesn't matter unless you shoot raw video.

For preferences video it should be the NVIDIA GPU by default. Consider a reset of VEGAS as this behavior is odd.

Also are you using adjustment events? Others found a memory issue with them.

As far as GPU use during rendering you need to look at what each GPU is doing, not the overall percentage. The first few seconds may have been easy to process so all the activity was on NVENC encoding.

Driver should be fine, you have the latest NVIDIA.

Hi!

1. I'll try to turn RAW processor off. I don't shoot RAW video.

2. Did not use adjustment layer.

3. I'll do reset Vegas, however I just installed it 3 days ago.

4. The reason I allways wrote just a few seconds, because rendering did not last longer than that, befor it crashed.

----

I still don't understand, if I select Nvidia everywhere in Preferences, during rendering, why does Vegas change to Intel onboard GPU? Since it happens, it can really cause lack of memory error. I don't know how much memory Intel onboard GPU has, but definetly not o lot wich is enough for nothing for Vegas. :)