Did you already instead of changing all kind of settings in Preferences did a total reset of Vegas 20 exactly following this https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/ ?
 

Hello @j-v - Thank you so much for responding. No, I have not done a reset yet. I appreciate the link that you sent with the step-by-step instructions. I guess I could try that. Again, thank you for the link! 😊

If that fails, please give us an idea of what kind of media you are using in your project, as well as your project settings. To give us media details, download a free app called mediainfo (you can google it, should be the first result that pops up). Install that, and once it is installed, right clicking on any of your media files that are being used in your project will open the right click context menu, and you should see an option called "mediainfo" in that list. Clicking that opens the app, and then you can copy and paste the report it generates here. You may have to set the view in mediainfo to ""html" to show all the details. If I remember right, the default view doesn't show everything.

That will tell us exactly what type of media you are using, which will help us to help you troubleshoot the best way to make it decode more stable.

From there, let us know the project settings (resolution and frame rate, 8 bit or 32 bit, which resample mode you're using, that should be enough).

Another thing that can improve stability is to update that RTX 3070's drivers. There's a driver update utility in the VEGAS help menu that will automatically download the correct driver to use for you, then you just install it from there.

@Debbie-Whitmer

I was crashing yesterday when I was using the effect Upscale. 2560x1920, 59.97 fps AVC AAC. Project 8-bit

Upscale became overwhelmed and gradually slowed down and went into an endless loop, it seemed, when I used Good - Full preview mode. I had to use Preview - Full preview mode.

@Debbie-Whitmer

I was crashing yesterday when I was using the effect Upscale. 2560x1920, 59.97 fps AVC AAC. Project 8-bit

Upscale became overwhelmed and gradually slowed down and went into an endless loop, it seemed, when I used Good - Full preview mode. I had to use Preview - Full preview mode.

 

@Robert Johnston - Oh my. Thank you for sharing that. At least I know I'm not alone!

Did you already instead of changing all kind of settings in Preferences did a total reset of Vegas 20 exactly following this https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/ ?

@j-v - Hi there. I did a total reset. I made snap shots FIRST of all my settings in File/Properties and Options/Preferences before I did the reset. I actually did not make that many changes to the default settings. But in any event, I started from scratch doing an entire radio broadcast that I had previously done to see how everything was working and it still crashes on me. However, I'm glad I did the reset as you suggested just to see how many changes I did make from the default settings. Thank you.

If that fails, please give us an idea of what kind of media you are using in your project, as well as your project settings. To give us media details, download a free app called mediainfo (you can google it, should be the first result that pops up). Install that, and once it is installed, right clicking on any of your media files that are being used in your project will open the right click context menu, and you should see an option called "mediainfo" in that list. Clicking that opens the app, and then you can copy and paste the report it generates here. You may have to set the view in mediainfo to ""html" to show all the details. If I remember right, the default view doesn't show everything.

That will tell us exactly what type of media you are using, which will help us to help you troubleshoot the best way to make it decode more stable.

From there, let us know the project settings (resolution and frame rate, 8 bit or 32 bit, which resample mode you're using, that should be enough).

Another thing that can improve stability is to update that RTX 3070's drivers. There's a driver update utility in the VEGAS help menu that will automatically download the correct driver to use for you, then you just install it from there.

 

@fr0sty - Hello.  Thank you for your reply.  I did the reset first and I actually did not make that many changes from the default settings, just the tweaks I mentioned in detail in my original post and that's it.  But it still freezes/crashes on me.  As far as what media I use, in just one of the projects I do, I use LIVE streaming videos in .MP4 format in which I do the post production on them.  I use .MP4's ONLY on the video formats, short .MP4 clips I create with Vegas Pro 20, bitmap images with the .jpg and.png extensions.  All other things that I use are the internal plugins inside of Vegas Pro 20; that's about it.  I mentioned in my original post that I have everything updated including the newest version of Windows Pro 11 and my graphic and audio drivers are all updated.  I NEVER update my graphic drivers directly from Vegas Pro because I have had problems with that in the past.  I always go  directly to the manufacturer and download my drivers from there and then install them.  Everything I have is all up to date.  Just one of the YouTube channels I manage and have created all of these videos myself is located here for the radio broadcast that I do called "Open Up The Doors with Andy White" located here:   https://www.youtube.com/@AndyWhiteOpenUpTheDoors/videos

All of the settings that I use are the default settings plus the tweaks I mentioned in my original post.  Since I have been doing this for years, in order to save disk space, because I make a back up of everything I do, I always render at 720p.  Along with my tweaks above WHILE EDITING and then restore them before rendering out, the rendering format I use is:  MAGIX AVC/AAC MP4 and the template I use is:  Internet HD 7620p 29.97 fps (NVENC)

Thus far, I’m still stuck with the freezing up/crashing. 

@Debbie-Whitmer my PC specs are in my signature. I had the Ryzen 9 3900X before the 5950X.

My experience is sort of the opposite of yours. I've found this build, although initially, a crash fest, has been rock stable for me, editing 5 hours (my limit) without a crash. I edit images, 10bit 4K video from Panasonic cameras, using plugins like BorisFX Continuum Complete 2023.5, NBFX Total FX7, Ignite Pro 5, and others, without any issues. Especially Continuum.

Looking at the youtube video, what records your source video and what does MediaInfo say about it? Download MediaInfo HERE. It's free. Open it and drag your video on top of it. Click in MediaInfo View>Text. Copy and paste the text in your next post. MP4 is a container. It can have anything in it, like a trashcan can have all types of garabe in it.

Also, have you tried disabling your GPU?

@Debbie-Whitmer my PC specs are in my signature. I had the Ryzen 9 3900X before the 5950X.

My experience is sort of the opposite of yours. I've found this build, although initially, a crash fest, has been rock stable for me, editing 5 hours (my limit) without a crash. I edit images, 10bit 4K video from Panasonic cameras, using plugins like BorisFX Continuum Complete 2023.5, NBFX Total FX7, Ignite Pro 5, and others, without any issues. Especially Continuum.

Looking at the youtube video, what records your source video and what does MediaInfo say about it? Download MediaInfo HERE. It's free. Open it and drag your video on top of it. Click in MediaInfo View>Text. Copy and paste the text in your next post. MP4 is a container. It can have anything in it, like a trashcan can have all types of garabe in it.

Also, have you tried disabling your GPU?

 

@Reyfox -

Hello.  Thank you for your message.  By the time I received your message around 5:30 AM ET, I could not address it then.

During this issue of crashing/freezing up during the editing process in Vegas Pro 20 build 411, if everyone has been following along this conversation, it was asked if I had changed  back to the default settings in Vegas (along with “Delete all cached  application data” box as an option which I did choose).  I guess I opened up a can of worms when I did that because now I have a more serious problem which is more important to me right now instead of the editing process crashing on me. 

AFTER I changed back to default settings in Vegas Pro 20 build 411, I wanted to render a project that I had successfully worked on previously in which the final .MP4 output is 49 minutes and 28 seconds long.  After I changed back to default settings, now the rendering process is freezing up on me and it will not render out completely!  If I cannot render out a video to its completion, I have absolutely nothing to offer anyone and have nothing to upload to any video hosting site. Since I was up all night trying to deal with this, to make a long story short, with all the setting changes I made, the only way to make the video FINALLY render out completely was to go to Options/Preferences then go to the Video tab and change my “Dynamic RAM Previewing max: to 0 (zero) % and let my NVIDIA GeForce RTX 3070 graphics card handle everything and it finally worked!! What I do not understand is that I made snapshots of ALL of my previous settings BEFORE I set everything back to the default settings and I had the Dynamic Ram Preview Max set to 75% (full max) and it was working THEN but NOW it won’t work at 75% AFTER I set back to default settings in Vegas Pro 20.  Something happened when I went back to the default settings. And I did not have that many changes from the default settings; only a few changes.

ANYWAY, at least I have a fully rendered video now but some good news came along with that. As I previously mentioned, this video was 49 minutes 28 seconds long.  It always USED TO render out about 4 minutes less time than the actual video.  In other words, it took about 46 minutes to render out that video; almost minute for minute.  HOWEVER, NOW, the same video with the configurations I have now as mentioned above, it now takes between 26 to 30 minutes to render!  So, it’s rendering faster than it was before!  HOWEVER, before I got to that point, I put the dynamic RAM Preview Max back up to 75% like I had it originally.  Then I shut my down my PC all the way off and brought it back up and started to render with the Dynamic RAM being at 75%.  It actually rendered out successfully ONE TIME in 17 minutes!!  I could not believe it!   Everything was moving really fast in the preview window. However, when I ran the test again WITHOUT shutting down my computer and just rerendering again, it would NOT render out but would freeze up in different places as I kept trying to render it over and over and over again to see if it was stable. It was NOT stable.  I even set the Dynamic Ram at various places such as 5% and even around 30% but it still would not work.  I WISH it would work with the Dynamic RAM being set at 75% because that is a great savings in time!!  But I cannot keep turning my computer off every time I want to render something as I keep my computer on all the time running continuously.  Even after just rebooting it would NOT work but it would only work AFTER I shut my computer all the way off and then bring my PC back up again.  But, again, it only worked  one time. 

So, right now, I will have to settle with what I described above with a little bit better of rendering time which works every single time without having to shut down or rebooting my PC. I think I’m going to leave this topic as is and I will do more research and testing to figure out the crashing/freezing up WHILE EDITING issue in Vegas Pro 20 build 411 UNLESS someone has an idea for a simple change in Vegas Pro 20.  I have found out in using Vegas Pro 20 that it may only be one setting which makes the difference.  I only like to make ONE change at a time to see what works and not mix many changes together if you know what I mean.  Thank you to everyone for replying and helping me to work through this.  It is greatly appreciated.  Have a good day! 

@Debbie-Whitmer I have Dynamic Ram set at 5% (1634MB) and no problems. I have zero idea of how or why it might affect you rendering a final project. I thought it had more to do with timeline work and I've also had it at 0% and no problems. But my projects run 15 minutes or less.

I read of other users having issues that I haven't experienced in Vegas and oft wonder why. But I did IT work in the past and have always maintained my computers that I build myself. And if there is an issue, I make sure before doing anything if it's everyone or just me. If just me, then there is something going on with my computer and the software. I usually start by uninstalling the offending software using Revo Uninstaller Pro. There is a free version of it. After doing the initial "Vegas" uninstall, it hunts through the registry looking for leftovers, and does the same thing with folders. Uninstalling the graphics driver, many use Display Driver Uninstaller (DDU) before installing a new driver. Then there is the virus/malware scan, and then running sfc /scannow in the Command Prompt running it as Administrator.

Making sure that there are no bad sectors on a mechanical drive is good also if it's used. Keeping thermals in check on the CPU and GPU are important as is cleaning the inside of the computer. Once a year I take the entire computer apart, cleaning dust out of everything, and every two years, new thermal paste on the CPU and 3 years, the GPU.

As for having to reboot the computer... you shouldn't have to, but if you have Fast Startup enabled, it keeps things in Windows kernal. "Fast Startup combines elements of a cold shutdown and the hibernate feature. When you shut down your computer with Fast Startup enabled, Windows closes all applications and logs off all users, just as in a normal cold shutdown. At this point, Windows is in a state very similar to when it’s freshly booted up: No users have logged in and started programs, but the Windows kernel is loaded and the system session is running. Windows then alerts device drivers that support it to prepare for hibernation, saves the current system state to the hibernation file, and turns off the computer.

When you start the computer again, Windows does not have to reload the kernel, drivers, and system state individually. Instead, it just refreshes your RAM with the loaded image from the hibernation file and delivers you to the login screen. This technique can shave considerable time off your start up." I personally do not have it enabled.

@Debbie-Whitmer I have Dynamic Ram set at 5% (1634MB) and no problems. I have zero idea of how or why it might affect you rendering a final project. I thought it had more to do with timeline work and I've also had it at 0% and no problems. But my projects run 15 minutes or less.

I read of other users having issues that I haven't experienced in Vegas and oft wonder why. But I did IT work in the past and have always maintained my computers that I build myself. And if there is an issue, I make sure before doing anything if it's everyone or just me. If just me, then there is something going on with my computer and the software. I usually start by uninstalling the offending software using Revo Uninstaller Pro. There is a free version of it. After doing the initial "Vegas" uninstall, it hunts through the registry looking for leftovers, and does the same thing with folders. Uninstalling the graphics driver, many use Display Driver Uninstaller (DDU) before installing a new driver. Then there is the virus/malware scan, and then running sfc /scannow in the Command Prompt running it as Administrator.

Making sure that there are no bad sectors on a mechanical drive is good also if it's used. Keeping thermals in check on the CPU and GPU are important as is cleaning the inside of the computer. Once a year I take the entire computer apart, cleaning dust out of everything, and every two years, new thermal paste on the CPU and 3 years, the GPU.

As for having to reboot the computer... you shouldn't have to, but if you have Fast Startup enabled, it keeps things in Windows kernal. "Fast Startup combines elements of a cold shutdown and the hibernate feature. When you shut down your computer with Fast Startup enabled, Windows closes all applications and logs off all users, just as in a normal cold shutdown. At this point, Windows is in a state very similar to when it’s freshly booted up: No users have logged in and started programs, but the Windows kernel is loaded and the system session is running. Windows then alerts device drivers that support it to prepare for hibernation, saves the current system state to the hibernation file, and turns off the computer.

When you start the computer again, Windows does not have to reload the kernel, drivers, and system state individually. Instead, it just refreshes your RAM with the loaded image from the hibernation file and delivers you to the login screen. This technique can shave considerable time off your start up." I personally do not have it enabled.

 

 

 

@Reyfox - Thank you for your message. It was very informative and you have been very kind. Yes, my husband has built all of my computers and so he's responsible for keeping things clean. smile

Just one more followup on this. I told you before that when I put Dynamic RAM up to 75% it kept freezing up on me during rendering on my last project and it only rendered out correctly one time but, afterwards, the rendering process kept freezing up on me over and over again. Well, I took a break from all this and, later, I decided to do some more testing just to see what it would do with the Dynamic RAM up to 75% again. I decided to re-render a project of mine in which the host of the radio broadcast that I do post production on did an interview with someone and that interview totaled 1 hour and 44 minutes long after I cut out the music part and just kept the interview. Well, I made absolutely NO CHANGES AT ALL and started rendering this long interview with the Dynamic RAM up to 75%. Well, it rendered all the way out and completed! And it rendered the whole thing in 1 hour and 13 minutes. Then without rebooting my system or doing anything different, I re-rendered the whole interview AGAIN just to see what it would do. Well, it rendered out all the way again and it rendered it in 1 hour and 12 minutes (SMH = Shaking My Head). THEN I decided to re-render again my original project in which the broadcast lasted for 49 minutes. THAT re-rendered all the way through and it rendered in 15 minutes!!! WHY it was constantly freezing up on me consistently and NOW it's not is beyond me!! I made absolutely no changes!! Sometimes this stuff drives me crazy because like you said in your last message, sometimes you often ask WHY?!?! Needless to say, even though being perplexed, I was happy about the results. But it makes me wonder what it will do tomorrow!! LOL! Thank you again for all of your input, your kindness, and it was nice "meeting" you. Take care.