@Howard-Vigorita - I am not sure whether you read my post correctly. My system contains only one dedicated GPU, which is the Radeon RX 9070. The other GPU mentioned is the GPU on the AMD Ryzen 9900X. In Vegas I have to pick which of these two GPU sources to used in GPU acceleration and in my use case is the 9070. For Vegas 16 and 19 I have always selected the separate GPU, which is always faster than a CPU embedded GPU. In my testing for rendering I found that on a particular timeline of 4K clip that with GPU acceleration it render in 50min, with iGPU 23 minutes and the RX 9070 about 6.5 minutes.

For my monitors, they are both the same resolution, one is 144Hz and the other 60Hz refresh rate. I question what the monitor settings would have to do with rendering and the use of the GPU for acceleration. As a side note, I also use Da Vinci Resolve, where I have no problem with as well as Wondershare Demo. I use Vegas as my final product renderer as I found that Da Vinci does not produce a rendered video to the same resolution quality as Vegas, or at least I have not found a setting in it to produce the same or better level of resolution. I don't mean resolution as pixel dimension, but in the apparent resolution of the final video, if I zoom in at 400% or 800%.

What's your vp22 setting in I/O prefs? That's what controls decoding. I think it defaults to Auto in vp22. But if you specifically set it to something different than what you selected in Video prefs, that might be the source of vp22 crashes during rendering. That only applies to vp21 and later. Vp16 and 19 are different.

There's no Vegas choice between 2 gpus for rendering if they are both AMD. You can look in Windows Task Manager at the charts and see where the utilization goes up during renders compared to playing to verify which one Vegas is using. It's only an issue if they picked the igpu to use which is probably less powerful. Only Vegas alternative for you is to choose MainConcept which renders using cpu and will likely be slowest but highest quality. You can however disable the igpu by going into Windows driver config for display adapters and disable the igpu driver so it doesn't show up in Vegas Video or I/O prefs . Or if your mobo bios supports it, disable the igpu there. But if you disable the igpu, you'll have to plug both monitors into the 9070. Which might actually result in higher performance.

@Howard-Vigorita - I am not sure whether you read my post correctly. My system contains only one dedicated GPU, which is the Radeon RX 9070. The other GPU mentioned is the GPU on the AMD Ryzen 9900X. In Vegas I have to pick which of these two GPU sources to used in GPU acceleration and in my use case is the 9070. For Vegas 16 and 19 I have always selected the separate GPU, which is always faster than a CPU embedded GPU. In my testing for rendering I found that on a particular timeline of 4K clip that with GPU acceleration it render in 50min, with iGPU 23 minutes and the RX 9070 about 6.5 minutes.

For my monitors, they are both the same resolution, one is 144Hz and the other 60Hz refresh rate. I question what the monitor settings would have to do with rendering and the use of the GPU for acceleration. As a side note, I also use Da Vinci Resolve, where I have no problem with as well as Wondershare Demo. I use Vegas as my final product renderer as I found that Da Vinci does not produce a rendered video to the same resolution quality as Vegas, or at least I have not found a setting in it to produce the same or better level of resolution. I don't mean resolution as pixel dimension, but in the apparent resolution of the final video, if I zoom in at 400% or 800%.

Try using both monitors on the GPU(connect both to gpu) and set preferred monitor to the 144hz one and see if it crashes. I am suspecting the iGPU to struggle rendering. and also maybe fighting for priority with your dedicated GPU and may crash your PC when rendering.

GPU stress tests usually loads completely different "blocks" of GPU (not decoder/encoder that are mostly used when you working in VP).

I'd try:
- Different version of AMD GPU driver (newer is not always better). You may find version that works.

- Try to load GPU's encoder/decoder using other software (ffmpeg/handbrake). You may find that not the VP is the issue.

- Try to monitor software that is used in parallel with VP (see my findings below).

Right now I am on 9700X + RX 6600 and I noticed that sometimes graphics driver is also crashing when I'm working in VP22.
Not that bad in my case (windows is not disabling the GPU, but I'm on Windows 10 and it might behave differently then your Windows 11).

While monitoring the situation I noticed that this is happening when GPU VRAM reaches max and I've only seen this when I use some other software that also using GPU.

In my particular case it is VP22 + Palemoon (it looks like the web browser has issues with GPU). Have not seen that GPU crash when using VP22 alone or Palemoon alone.

P.S. I'm looking forward to buy 9070. So I might be in the same boat...
 

@fifonik - Thanks for your input. I updated to an optional update version of AMD Adrenalin s/w version 25.6.2 yesterday and will give it a try. Today I plan to resume some of my projects with my 4K clips, from my Sony camera where I do color grading and from my GoPro 7 & 12. I have used Handbrake recently to convert over 1,000 clips of my GoPro12 video from 29.97 fps to 25 fps to use with my Sony 25 fps clips. Handbrake worked fine

In some tests today I will keep HWMonitor open to check VRAM usage of the 9070.

I worked threw several projects today and as of about 16:25 I had another crash. This time whilst the PC screens were frozen, which I assume is the last graphic available to them, I plugged in my primary monitor HDMI cable I keep plugged in, into the PC motherboard onboard HDMI connection as a chance to still be able to see the system running but using the onboard iGPU. After connecting it I saw a blue screen (BOD) popup with a few bits of information. I was not able to see the details before the PC rebooted, but was able to access the minidump file. Using WinDbg I was able to read the minidump file and found a reference to amdkmdag.sys. On restart of the PC the AMD Bug Report Tool popped up and I was able to describe the issue leading to the BOD and I attached the minidump file with the report.

So, it seems that using GPU acceleration with Vegas can cause a BOD. Until this can be resolved I will just have to make a habit of saving my work prior to starting a render. For this particular instance the BOD occurred whilst it was rendering and at the same time I was watching a video on YouTube (using Chrome).

@John-Callahan, have you applied any effects to the events? It's possible that one of the effects is causing the crash.

@VEGAS-Daniel - Not really. At first I am setting up each of my projects as follows before doing anything more advanced such as color grading:

1. Add clips to timeline
2. Clips include a combination of Sony and GoPro. Both are H.264 4K at 25fps
3. Select all clips and run a script I wrote to create a crossfade of 20 frames
4. Save the project file
5. Render using modified template: MAGIX HEVC/AAC MP4 - Internet UHD 2160p 25 fps (AMD VCE)
   1. Preset = Low latency - high performance
   2. Variable bit rate: Max=50mbps, Average=28mbps
   3. Show Video in Preview Window = Off

I did some more tests today using 3 applications:

• Vegas Pro 22
• DaVinci Resolve
• Wondershare

For each I made a simple project with just raw 4K clips (48 clips) of a total of 0:21:27.

Rendering to approximately the same setting. Render times:

• Wondershare = 4min
• Da Vinci Resolve = 4min
• Vegas Pro 22 = 7.5min

Using HWMonitor I checked the PC's usage of my RX 9070 GPU before opening the app's, after the apps had loaded the project and whilst rendering. Once rendering starts and after while I reset the min/max statistics. For all tests the GPU was using about 1Gb of memory prior to opening the respective app. Below is the summary of the amount of memory each app uses after opening (project loaded) and near the end of rendering (min/max):

• Wondershare: 1,749MB dedicated GPU memory after loading, 3,252MB/3,265MB (Min/Max) during rendering
• Da Vinci: 2,696MB dedicated GPU memory after loading, 3,549MB/5,105MB (Min/Max) during rendering
• VegasPro: 14,695MB dedicated GPU memory after loading, 15,347MB/15,441MB (Min/Max) during rendering

Note in the above amount of GPU memory used by Vegas, even before rendering starts. This was about 90% of the available memory of this card. I did another test with Vegas (fresh start of the project) and found the same amount of dedicated memory used after the project loaded. However, I let the project sit in that state for a while and found that some memory was released. Just prior to starting rendering there was 8,995MB of dedicate GPU memory used. Then during rendering it started at about 10,452MB and kept going up, with the peak memory usage of 15,805MB, or 96.9% of the available GPU memory.

I feel that Vegas is not using the GPU memory efficiently and it is most likely causing the GPU to crash. Unless I can log the memory usage (example at 1Hz) whilst rendering, then I cannot be sure whether the crash is related to GPU running out of memory.

My understanding is that the Vegas devs are working on the video engine, and it is a work in progress. I've had GPU RAM up to 11.9GB (I have 12GB dedicated GPU RAM), but everything continued on as I edited and played back the timeline. I do edit only 4K, and mostly 10bit 4:2:2 videos from my Panasonic camera. Vegas has never had any problems with my files.

I used AMD Adrenalin software to log the GPU and CPU metrics whilst I preformed a few render tests. In the spreadsheet linked is the metric data logged at 4Hz over a 40min time period while I did 2 render tests. The tests consisted of the following:

1. Start Vegas (opens last project)
2. Wait a couple minutes for GPU memory to settle to fixed level
3. Render my timeline (48 - 4K H264 MP4 files = 21mi 27s total)
4. Wait 3 minutes before closing Vegas
5. Repeat #1 to #4 for render test #2

In the spreadsheet is a worksheet describing the files used, render settings, testing timeline details (used to line up with the plots plus 4 general observation I got out this tests. Which was that Vegas uses far more GPU & CPU memory than other s/w's I have used (haven't tried Adobe Premier yet) and the fact it is using almost 100% of available GPU memory and that Vegas uses increasing more system memory during the course of the render (always going up), to me seems like a memory leak.

As my crash yesterday was before I knew the amount of memory Vegas takes from the GPU, I will now think twice before attempting to do other tasks which may try to use the GPU (e.g. YouTube videos?).

It seems I cannot attach a simple spreadsheet to this ticket as it seems it can only be images and video media. Therefore, I uploaded my spreadsheet to my OneDrive folder:

https://1drv.ms/f/c/23fbf66dfe042b97/EtKKwEQVcXxJule3huUHOCIBAvxolmwcsRwQxXGUqPTEvA?e=cv5BIk

Vegas Pro 22 GPU and CPU usage testing.xlsx

I tried to find the best VP settings for my hardware (Ryzen 7 9700X, RX 6600 8 GB) & my footage (see below) & my editings in Full HD (1080-60p) and I ended up with:
1. Video tab: Using RX6600, Dynamic RAM Preview 5% (default)

2. File I/O tab: "Hardware Decoder To Use": AMD Radeon (iGPU), "Enable Legacy AVC decoding": ticked, Enable "Experimental HEVC Decoding": un-ticked.

My footage:
- GoPro: mp4, 4K HEVC from 120 Mbps, VP decoded with mxcompoundplug.dll

- Panasonic X1500: mov, 4K AVC from 150 Mbps, VP decoded with so4compoundplug.dll

- Panasonic X1500: mp4, 4K HEVC from 100 Mbps, VP decoded with mxcompoundplug.dll

- Panasonic X920: m2ts, FullHD, AVC, 25 Mbps, VP decoded with so4compoundplug.dll

On preview I usually have 60fps for all the above footage (dropped in transitions). RX6600 VRAM usage is holding at about 70% (of 8GB). No idea about HW rendering as I'm always rendering on CPU.

Note: if you in middle of editing and using proxy -- changing some settings mentioned above may require proxy re-generations and 1-frame offset will happening in some files (this may cause some plugins such as video stabilisation require re-analizys).

On my Ryzen 9 5950X, 32Gb RAM and RX9070XT 16Gb I also experienced hangs/black screen, sometimes only Vegas crashes. This while editing relative short 3 minute show dance clips.
I recently noticed that when editing and rendering the Committed memory use is growing even higher then my 32Gb of memory in the system. So apparently it is using the page file space for something. You can observe this in the Task Manager under the memory tab. Simple playback while editing of a 15 minute long video could cause the memory to go beyond 32Gb.
My solution:
I had my page file set to at max 2Gb, so Vegas could only Commit to 34Gb of memory and it would crash beyond that. Strange enough not all of the actual memory was being used at least according to the graph in the Task Manager.
So what I did is I increased my Virtual Memory custom setting to minimal 4Gb to at max 32Gb. And now it takes very much longer before Vegas crashes. Only when rendering a nearly 2 hour concert video Vegas 22 used like 62Gb of commited memory and the real memory graph showed also full memory use.

The alternative option which worked very well with my former card the RX5700XT with 8Gb of memory was to the setting "Enable Legacy AVC decoding": ticked (under Preferences -> File I/O). But yeah we should actually be using the "improved" new rendering stuff. I am curious if you also would see those massive amounts of committed memory.

@Solmea - I think the crashing is a combination of Vegas and AMD. AMD needs to fix some of the issues where applications attempt to use the GPU in the manner Vegas does. I have been involved in software testing for over 30 years (recently retired). What I see in Vegas is a poor attempt at managing memory usage. Rendering is a transient use of resources as you move through the timeline and therefore should not be increasing in the amount of memory it takes from the o/s. In addition, the amount of memory it uses from the GPU just whilst editing a project is much more than other video processing software's.

I think I will try an older version of Vegas to see if memory management is better. I have V19 and V22 installed and have a license for V16, so will see if I can install it and try it out.

I recently updated to AMD Adrenalin 25.6.2. Version 25.6.1 is the official version suggested, but 25.6.2 and now 25.6.3 are available to install. However, today I found a version called PRO 25.Q2 which they mention is more targeted to professional applications and stability versus gaming. So, I have installed it and will see whether my system behaves better.

John if you do see a regression from 19 to 22 or a an advantage to particular AMD drivers please report it to VEGAS support (and AMD?) The video engine in VEGAS and media decoders are a work in progress from VP 21 so your feedback can help speed development!

I'm not seeing GPU memory issues with NVIDIA (except for the LUT Fx).

@RogerS - I had already made a issue with Vegas (MAGIX Support) a few weeks ago (related to pixelation and stuttering. Their reply was "Unfortunately, there is no specific information available regarding the cause of pixelation with this particular GPU acceleration setting" and that was the end of it. With AMD, after each crash I get a crash report popup (on reboot) and I fill everything in on the symptoms, etc, and the tool grabs what it needs from my PC prior to submission. As I mentioned last, I am now using the PRO version of the AMD driver, which in theory is targeted more towards stability instead of gaming so will see how that goes.

I don't think I can regress to anything other than v22 at the moment as it seems that the project files (.veg) cannot be used in a earlier version. I have about 300 projects I have created over the past several weeks and don't want to start over from scratch. I have workarounds for my project rendering to ensure I get uncorrupted results (e.g. stuttering or pixelation). If the system crashes once a day when I am doing a lot of editing/rendering, then I can accept it for now. However, I would also like to see Vegas make improvements in their memory management.

Hi John thanks for sharing your experience. While you can't directly open VP 22 projects in older versions you can potentially open both at the same time and copy and paste the timeline from one to the other.

If you have a short sample project that exhibits this memory behavior and are willing to make it available privately it could be helpful to the VEGAS AMD beta testers. Feel free to message me.

I agree something is wrong between Vegas and AMD.. On the RX5700XT I had hangs very often and only with the 'Enable Legacy AVC encoding' ticked.. it would let me do my thing... The next best working option was Vegas 21 patch 208. That did not have the new encoding stuff enabled.
Just out of curiousity, what is the setting for your virtual memory?
In my case setting up a custom page file which is at minumum 4Gb and at max 32Gb saves my day and lets me use Vegas 22 a bit more like is should work. It will crash in the end with black screen or what not... but it takes longer.

While there might be something wrong with VEGAS and AMD GPU's, I have had zero, and I mean zero issues with the footage from my Panasonic cameras, which are often 4K 10bit 4:2:2 MOV files.

Without specific files to test, or a small .veg file, it could be anything causing the issues. We all have to be testing the same thing that causes the error. My page file is the stock 2GB.

@Solmea - I normally render to HEVC, but can use AVC instead. I tried the option, with and without enabled. For a 24min timeline of GoPro HEVC 4K media:

• MAGIX AVC (AMD VCE) - Legacy AVC decoding = Disable = Render time = 5min 35s & 4.72Gb
• MAGIX AVC (AMD VCE) - Legacy AVC decoding = Enabled = Render time = 5min 06s & 4.72Gb

So, saved a bit of time. As another test I disabled the Legacy AVC decoding option (default) and rendered like I normally as HEVC and it was:

• MAGIX HEVC (AMD VCE) - Legacy AVC decoding = Disable = Render time = 5min 12s & 4.47Gb

@Reyfox - I can provide a project, but the problem here it is not easily replicated. I am not ever sure which project I was rendering when the last time it crashed. As a former software tester I can say this is a difficult issue when there is no fixed set of data and steps which can replicate an issue.

The only issue I have had so far which I could replicate was with certain 4K clips that rendering using MAGIX AVC (AMD VCE) or HEVC, in which I got a output video with stuttering in it (repeated frames, but other frames missing). My solution to that was to use a preset of 'Low latency', which works 100%. However, I will give the same problems clips a test with the 'Legacy AVC decoding' option enabled and see if that helps.

@John-Callahan if you could provide a .veg with files, I'll give it a go on my end and report back. I know your GPU is newer than mine, but if the issue is with a specific GPU/driver, at least the Vegas devs know what hardware to look at.

The "Pro" drivers might be a better option.