@Musicvid

I did both the bullet points.

It is still the same.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 452)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170k.dll
   Fault Address:       0x00007FFE54D8AC44
   Fault Offset:        0x000000000038AC44

Try rendering as Magic AVC instead of HEVC, which requires a lot more power to create.

@fr0sty I tried it. This time it rendered until 3%. :(

Find out what video or audio event might be at that time in the timeline. Then check what processes it needs - like what FX you applied, etc.

I found out that Vegas Stabilization plug-in crashed one of my projects so bad that I had to remove it manually in order to un-freeze it.

@Musicvid

I did both the bullet points.

It is still the same.

To be sure, is this the setting you tried? I was almost certain this would help.

Yes @Musicvid That is what I turned off.

@adimatis It was just a simple Titles and Text FX.

Well, the idea would be to identify if there is something in the timeline at that particular point that might be the problem.

And to follow what @fr0sty advice, try other formats too. If all you try only takes you that far, see if re-doing the project into a new one, with the same events would produce the same crash/freeze, as I would say most definitely something in the timeline give Vegas headaches.

And BTW, check the disk available storage. It might be a full-disk error.

Are you monitoring memory use while you're rendering? If not, you should be. 8G is borderline useful.

@adimatis I have tried several formats. Same issue.

Redoing the Project will take me 2 days to complete lol

I have over 50GB available.

@michael-harrison I increased the Affinity to Above normal too. Didnt work.

CPU usage: 1.4 GB while rendering and 550MB when Project in use.

I was able to find the error report on our system. According to the logs, the settings were,

<Windows Media Video V11> resolution:1280 x 720, PAR:1.000000, bit depth:24, FPS:25.000000, length:2002000000, interlace:0

It is quite surprising that this would cause a problem. Your drivers are all up to date, but the gpu and cpu are rather low powered. I am currently debugging the dump file, but that will take a bit of time.

@ROCKY007

I think you have your terms mixed up.

Memory = RAM = 8G on your system. You might have 50G of disk space available but not memory.

CPU usage: what you show is memory use.

You should also look at the Performance tab and highlight overall memory use to make sure you aren't getting close to max

I don't see anywhere that you say what gpu you're using, or do you not have one at all?

It's a bit of a hail mary but have you disabled so4compoundplug?

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-16-try-disabling-so4compoundplug-dll--108345/

@ROCKY007: It looks like the crash is happening when generating the frame from the source media. We probably need to get some media-info information from your source or have you share the source media with us.

Rocky, if you cannot upload a sample of your media to dropbox/google drive or something like that, give us a mediainfo report on it. That will help isolate your issue.