Thanks, but unfortunately DDU did not do the trick. Before I do a full reset, though, it was suggested that I manually delete all of the cached files, but I do not know where they reside for VP 18 and VP 19. Does anyone here know where I can find the cached files for both of these versions?

@Videoimpressions0622, take a look here:

C:\Users\[user name]\AppData\Local\VEGAS Pro\[version number]

There you need to delete these two files:

plugin_manager_cache.bin and svfx_plugin_cache.bin

Then restart VEGAS Pro and it will rebuild the cache files.

That you don't have to know when you use the reset option of Vegas itself.
That one deletes only your cashed files when you follow exactly this tutorial: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

The OP didn't want to lose customizations that come with a reset.

Reset both VP 18 and VP 19. Able to recover preferences for windows layouts and tabbed windows. Had to manually reconfigure custom toolbar, which took just a few minutes. Unfortunately BOTH versions STILL exhibit still frames and titles from different parts of the timeline bouncing on and off the viewing screen and also does so when attempting to render. To be even more specific about the anomaly, shortly after I create an edit on the timeline of either program, when I play back on the timeline I experience video stuttering, black frames, video playback of other clips on the timeline that is not the currently selected clip, and see titles on the screen for titles on the timeline which are not where the cursor resides. I now am starting to think I may have a defective NVDIA graphics card! Even though I used DUU to uninstall then reinstalled the latest drivers (yes, I did try older ones as well), I am at the end of my rope! I even disabled GPU graphics processing and tried to render in a "non" NVENC mode. So do you think it's possible that the rest of my PC system and apps can work fine but I still have a somewhat defective graphics card because of what's happening in two versions of Vegas Pro?

Could you try the VEGAS benchmark project in my signature? It's a known-good project with known-good media. Try putting the settings back to normal (keep the GPU on in video and file io) and see if you get the same errors.

If you do get these errors even with this project, does setting dynamic ram preview to 0MB help?

Which version of the nvidia display driver are you using?

First of all, a big thank you shout out to everyone continuing to try to help me resolve this issue! fr0sty, I am using NVIDIA Studio Driver V 537.42 for my NVIDIA RTX 2060 SUPER graphics card seeing no other anomalies other than that when I run VP 18 or VP 19. RogerS, I will try your project in VP 19 and report back. HOWEVER, more reading and research has led me to believe that I may have a codec problem! Thus far I only have tested footage from my FDR-AX53 camcorder, set to XAVC S HD 60p at 50mbps, up until this current anomaly NEVER having a problem viewing, editing or rendering!!! Close to 4k quality, the raw footage looks better to me than standard AVC HD. This camcorder produces m2ts files when recording in AVC HD and mp4 files when recording in XAVC S HD. So perhaps Vegas Pro now is for some reason not loading the codec it needs to handle this footage? If I am correct and I need to download/install additional codecs, what do I need to obtain and what is the best (free) one to use?

Is it the studio driver? That is the recommended driver to use.

I am near my wit's end, my friiends. I have tried several mp4 files and m2ts files from different sources that successfully were edited in the past, using different combinations of switches in VP 19, with intermittent results. Someimtes I can successfully render a minute or so of footge, then when I go to a different part of the timeline to render a minute or so there the vieo strts acting up again! I now am putting big doubts on codec incompatibilities!! I will attempt to try a couple of old video cards I saved and see what happens. I will report back. If I fail, I just do not know what to do!! Later, my friends...

Oh, oh, RogerS!! I downloaded, played back your 4k demo file and rendered it from PAL to NTSC 29.97 fps progressive MP4, and everything went smoothly!! So now what?? I REALLY now am confused as to exactly what is going on. This does not make a lick of sense to me! HELP!!!! I also just now noticed that when I ran New Blue Title Pro V6 a requester box opened and said that there was a buffer overflow error. I will check this out with them, as well.

Just now added a New Blue Titler Pro V6 title to this project and playback/rendering was 100% OK. Wish I knew what the problem is with all of my footage, both MP4 and M2TS! Any ideas?

So after countless hours of experimentation and changes, it appears it's all focusing in on origination footage. Could it be I need to install additional codecs? What suggestions and/or personal experience do you have with any codec downloads? I'd like to try that route at this point in time. So everyone reading this, I would appreciate your advice on codecs I could try. THANKS!!

More experimentation: Loaded a project shot last summer in 1080 30p (AVC). I am able to view this on the timeline without any problems, but when I attempt to render (ANY render template I have--MAGIC AVC, MAGIX HEVC, SONY AVC, etc.), it renders for awhile and then the video anomalies start somewhere in the render sequence. If I stop the render, I cannot playback the timeline videos--anomalies once again. However, if I close the file and exit VP 19, then laod the file again, I can view the timeline without consequence. All of the rendering templates are for creating MP4 files, and they have problems; all origination MP4 footage has timeline playback and rendering problems. It appears that VP 19 is unable to handle MP4 files now!! Again, is this a codec issue?? Hoping for some more guidance from all of you...

It's not a codec issue and there's nothing to install, but there could be an issue with decoding. Does zeroing out dynamic ram preview help?

What about turning hardware decoding off in preferences file io? Both these fixes will likely worsen performance but may avoid errors.

My program is freezing up when I try to save or move the curser. You have just billed my account for $239.88 for annual fee and I can't talk to a person. I need answers. Thank you.

My program is freezing up when I try to save or move the curser. You have just billed my account for $239.88 for annual fee and I can't talk to a person. I need answers. Thank you.

@Greg-Ganier You should start your own thread describing your issue and system hardware and media for community help. There is support via email and chat.

One idea is to disable live save in advanced save if that's enabled.

Thanks to all of your suggestions, I finally have somewhat good news to report (not done yet, though). Using the same 2 minute segment from the affected project, I set my Dynamic RAM preview to 5% and turned off GPU accelertion of video processing. Under File I/O I selected the default settings which checks Enable legacy HEVC decoding (which I am not using) and Hardware decoder to auto (NVENC) for my video card. The two minute segment renders just fine to MP4! HOWEVER, it screws up rendering if titles are present (New Blue Titler Pro 6). Of course, Titler Pro was working just fine prior to the anomalies observed over the past week!! So apparently one down and one to go!! Perhaps the titles for some reason got corrupted? I will try to repair/redo the titles in the upcoming week (or so) and report back my findings. Again, thanks so much for all of your great suggestions everyone! HAPPY AUTUMN!!

The titles are likely fine. Try setting dynamic ram preview to 0 and see if it helps. You may be able to reenable the GPU processing if it's off (disabling both may not be necessary and really slows things down.)

More testing has revealed strange results. With NVENC rendering on, even though it screws up the video, it actually is slower than rendering without NVENC. I turned off multi-core processing, and a test segment renders fine with no NVENC and no NDVIDIA processing enabled but the same segment screws up when I selected a segment with titles. I have spent an hour and a half trying all different combinations of settings--so frustrating. Maybe my graphics card for some reason currently is not working right with VP (any version)? Maybe I should switch out to an older graphics card and see if it will work? I just do not know what to do, but I'll really be in big trouble if I don't get it resolved soon (wedding next weekend, and how will I edit it??)!! Thanks, Roger. Looking forward to your next suggestion...

For what it's worth I don't have issues with my 2080 card so doubt replacing the GPU is a reasonable solution.

Could you make the .veg file available with media used for the troublesome title segment?

Try just changing one variable at a time and using MagixAVC with Mainconcept to start with.

...then I have NO idea what is causing this mess! My constant fiddling around is getting me nowhere...so please direct me how to make the .veg file, media and Title Pro titles available to you (an others...). I probably should save a new .veg file with just 5 minutes or so of footage and titles, making sure that the files I do send are in fact acting up for me. If you don't use New Blue Titler Pro, I can just make the files available without the titles, which are the least of my problem. Just to be able to render the footatge itself would be a big relief! As always, thanks so much Roger!!