That's a fault that goes back to the introduction of GPU processing in Vegas11/12 and never fixed. Therefore if you turned GPU processing off, it should fix, but that is not a good solution

You can try dynamic ram preview 0, and ticking enable legacy AVC decoding

Disable resample, that will improve performance.

Disable Legacy decoding of any kind, you want to avoid this when possible.

From there, let's see if we can figure out which media clip is playing when it crashes. That'll help isolate the issue. Does it crash randomly on all 3 media sources, or is one in particular causing the issue?

Version 482 is completely broken for me with a 3900X and an Nvidia 3080. I can't render anything at all without it crashing within the first 30 seconds.

Turns out the new version HATES anything legacy. Turn off all legacy settings.

About a day or so before installing VP build 482, I updated the NVIDIA studio driver to build 461.72 for my computer's 2070 SUPER. After installing VP b482 and checking on one particular 4K project, I got lots of flashes, flickering and short black-outs similar to that described by the OP. After trying a lot of legacy settings and thinking that 482 was the problem, I uninstalled 482 and re-installed 434 where the problem had not previously existed. But ... the problem persisted though maybe not as bad as in 482. Bugged by the 'update available' alert each time b434 was opened, I uninstalled 434 and re-installed 482. The problem was still there but was alleviated somewhat by activating 'Enable legacy AVC decoding' in File I/O. But my thinking was that it was not b482 that was the problem - it was the 461.72 NVIDIA studio driver.

Build 461.92 has just been released - after installing using the 'clean install' option, the flickering etc seems [so far] to have vanished.

@david-b7658 ... if you haven't already done so, try updating to the 461.92 NVIDIA studio driver to see if that helps in some way.

EDIT: I should add that no crashing per se though, but lots of white screening which is tantamount to crashing because the only way to get out of it is to close Vegas Pro via Task Manager.

In the meantime, thank you all for the answers,
 

Your hardware should work. If nobody helps you here, try filing a support request and include a link to this thread.

If you are using the same frame rate on your cameras, turn resample to disable resample.

What number is dynamic ram preview set to? Try 0.

tried with the ram at 0 (which was at 200) in addition to the fact that I lose fluidity in the preview I have blocks with white screens

About a day or so before installing VP build 482, I updated the NVIDIA studio driver to build 461.72 for my computer's 2070 SUPER. After installing VP b482 and checking on one particular 4K project, I got lots of flashes, flickering and short black-outs similar to that described by the OP. After trying a lot of legacy settings and thinking that 482 was the problem, I uninstalled 482 and re-installed 434 where the problem had not previously existed. But ... the problem persisted though maybe not as bad as in 482. Bugged by the 'update available' alert each time b434 was opened, I uninstalled 434 and re-installed 482. The problem was still there but was alleviated somewhat by activating 'Enable legacy AVC decoding' in File I/O. But my thinking was that it was not b482 that was the problem - it was the 461.72 NVIDIA studio driver.

Build 461.92 has just been released - after installing using the 'clean install' option, the flickering etc seems [so far] to have vanished.

@david-b7658 ... if you haven't already done so, try updating to the 461.92 NVIDIA studio driver to see if that helps in some way.

so for now I am testing the old bild 373 (always with the 461.72 driver) and for now, in my 10 minute test project, many slow motion 50/75%, 6 tracks without fx I have not had blocks doing a couple of views in play totals ...
now I put the 482 and the new geforce driver back and update you ...

Turns out the new version HATES anything legacy. Turn off all legacy settings.

Reading 1440p NVENC OBS files is stable in legacy mode for me, but highly unstable otherwise so that's one reason for using it, If what you say is true, then what happens now when Vegas crashes in default mode... there used to always be legacy for improved stability... that's a bit worrying

 

Build 461.92 has just been released - after installing using the 'clean install' option, the flickering etc seems [so far] to have vanished.

@david-b7658 ... if you haven't already done so, try updating to the 461.92 NVIDIA studio driver to see if that helps in some way.

EDIT: I should add that no crashing per se though, but lots of white screening which is tantamount to crashing because the only way to get out of it is to close Vegas Pro via Task Manager.

nothing to do, neither bild 373/482 with 461.72 nor with 461.92 works ...
all tried with repeated clean installations from windows only image with Acronis tru image ... the problems always those:
flashes, black frames, and consequent crash with white screen or nvopencl error
I do not know what to do...
it seems incredible to me that with pc as I listed at the beginning of the post I am forced to use vegas 13,
I repeat if I had the certainty of functioning I would also change the pc to make it compatible with vp 18

@david-b7658
First of all execute this exactly as written for clearing the cache: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/
After that without making any change in Options/Preferences/Video and Options/Preferences/File I/O show us here a screenshot of both.

I have almost the same machine as yours (see mine in signature) with 461.72, will upgrade to 92. Stable on my side but with many tweaks, let me know if you want to test those twesks.

@david-b7658
"First of all execute this exactly as written for clearing the cache: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/"

I have done even better I have installed vegas 18 clean, in a system with only win 10, as already said, all the tests I have done by restoring the partition from an image with only win 10

After that without making any change in Options/Preferences/Video and Options/Preferences/File I/O show us here a screenshot of both.

I have almost the same machine as yours (see mine in signature) with 461.72, will upgrade to 92. Stable on my side but with many tweaks, let me know if you want to test those twesks.

I would be enormously grateful ...😀
we have almost the same machine, so if it works for you I have to understand what the problem is ... in the end the files I use are very common ...
xavc 1920x1080 50fps bitrate 50 of sony a7iii and all the others of the normal avchd fullhd 50fps standard

@david-b7658
"First of all execute this exactly as written for clearing the cache: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/"

I have done even better I have installed vegas 18 clean,

Sorry, but that is not better and has no sense because all the changes you made earlier are back in a clean install.
Thatswhy on this forum we say all the time that RESSETTING is the best option to start fresh.
But probably you know things better and does not need my help.
Your choice. 😌

 

Sorry, but that is not better and has no sense because all the changes you made earlier are back in a clean install.
Thatswhy on this forum we say all the time that RESSETTING is the best option to start fresh.
But probably you know things better and does not need my help.
Your choice. 😌

sorry, maybe I didn't understand, I didn't mean to be rude ...
I immediately try to reset even after the first installation

unfortunately, even after the vegas reset, the blocks remain ...😤😭