I second @RogerS suggestion to try the 22.5.1 driver and reset Vegas. The older driver is very stable and your older 560 gpu probably will not benefit from newer drivers anyway. Strongly suggest you remove newer graphics drivers with DDU before going backwards in versions. Also, if you haven't already, suggest you make sure you can run prime95 without error for 8 hours minimum. You might need to adjust memory timing in bios if older memory cannot keep up with your new cpu. Another thing to consider is pcie bus specs... your older gpu is not pcie4 capable and your motherboard should auto-detect that and drop back to pcie3. That card also cannot run x16. If detection isn't working or is disabled, it might help if your your bios has a setting to explicitly select pcie3 x8 operation for the gpu slot. Personally, with a mb/cpu system like yours processing double-rate footage, I'd go for a pcie4 gpu with 8gb or more vram and a minimum of 32gb of fast mb ram.

I second @RogerS suggestion to try the 22.5.1 driver and reset Vegas. The older driver is very stable and your older 560 gpu probably will not benefit from newer drivers anyway. Strongly suggest you remove newer graphics drivers with DDU before going backwards in versions. Also, if you haven't already, suggest you make sure you can run prime95 without error for 8 hours minimum. You might need to adjust memory timing in bios if older memory cannot keep up with your new cpu. Another thing to consider is pcie bus specs... your older gpu is not pcie4 capable and your motherboard should auto-detect that and drop back to pcie3. That card also cannot run x16. If detection isn't working or is disabled, it might help if your your bios has a setting to explicitly select pcie3 x8 operation for the gpu slot.

sir I upgraded my motherboard too..as mentioned in my signature.

my driver also older not latest .. latest one make my preview purple while playback not after render. so i don't updated it yet.

That's good on the MB.

Did you do the driver reinstall and Vegas reset? There may be old settings causing some conflict in Vegas?

That's good on the MB.

Did you do the driver reinstall and Vegas reset? There may be old settings causing some conflict in Vegas?

sir one thing i want u to notice that i even do it by not only reinstall VEGAS.. even i reset my PC. it was giving me same problem.

but right now something happened. may be i am reacting so fast should be wait, but my vegas is not crashing now i just change

to --> this

bcoz my all files are AVC

can this setting be cause of crash or stability .

or i am reacting so soon. should be wait till it again crash lol.

bcoz often it crashes in 5 minutes.

but its running stable now from last 20 minutes atleast on same project same settings except above ones.

my driver also older not latest .. latest one make my preview purple while playback not after render. so i don't updated it yet.

Upgrading my Intel drivers made all the difference to me. No preview issues are apparent.

@iEmby Getting fewer crashes with Legacy-AVC suggests there's a problem with your Intel Graphics driver. You shouldn't have to do that. What Intel graphics driver version are you running? Intel drivers may benefit from being cleaned up with DDU too. The Intel advice when their graphics malfunction is to revert to the driver on the support site for your motherboard maker (Asus) as a starting point before testing later updates from Intel.

@iEmby Getting fewer crashes with Legacy-AVC suggests there's a problem with your Intel Graphics driver. You shouldn't have to do that. What Intel graphics driver version are you running? Intel drivers may benefit from being cleaned up with DDU too. The Intel advice when their graphics malfunction is to revert to the driver on the support site for your motherboard maker (Asus) as a starting point before testing later updates from Intel.

may be u can be right sir.

@iEmby Getting fewer crashes with Legacy-AVC suggests there's a problem with your Intel Graphics driver. You shouldn't have to do that. What Intel graphics driver version are you running? Intel drivers may benefit from being cleaned up with DDU too. The Intel advice when their graphics malfunction is to revert to the driver on the support site for your motherboard maker (Asus) as a starting point before testing later updates from Intel.

Updated now.. should i check on default settings of File I/O.. ? Or i just keep mine?

Got the same Command Center and os but the correct driver for may laptop may be totally different:

Updated now.. should i check on default settings of File I/O.. ? Or i just keep mine?

Generally you should get identical quality but better performance without legacy-avc checked.

Got the same Command Center and os but the correct driver for may laptop may be totally different.

now showing like this.. its update now.

also automatically installed this.

thanks for this suggestion, sir.

let's see it will work or not.

Updated now.. should i check on default settings of File I/O.. ? Or i just keep mine?

Generally you should get identical quality but better performance without legacy-avc checked.

ok got it... i changed it to default now check on only HEVC.

I personally don't care for the Arc app but maybe it's less annoying now than the last time I looked. It has capture functionality (used to be in the Intel Graphics Command Center) if you plug your monitor into a motherboard hdmi port. Don't know that it'll do much else for you if your monitor is plugged into the Amd gpu... the Amd driver has Screen Capture functionality for when you are plugged into their board... Amd calls it ReLive.

I second @RogerS suggestion to try the 22.5.1 driver and reset Vegas. The older driver is very stable and your older 560 gpu probably will not benefit from newer drivers anyway. Strongly suggest you remove newer graphics drivers with DDU before going backwards in versions. Also, if you haven't already, suggest you make sure you can run prime95 without error for 8 hours minimum. You might need to adjust memory timing in bios if older memory cannot keep up with your new cpu. Another thing to consider is pcie bus specs... your older gpu is not pcie4 capable and your motherboard should auto-detect that and drop back to pcie3. That card also cannot run x16. If detection isn't working or is disabled, it might help if your your bios has a setting to explicitly select pcie3 x8 operation for the gpu slot. Personally, with a mb/cpu system like yours processing double-rate footage, I'd go for a pcie4 gpu with 8gb or more vram and a minimum of 32gb of fast mb ram.

It crashed again in 4 minutes of work. screen got freezed... nothing appears... same again i hv to close it from Task manager.

So does using legacy-avc still help?

So does using legacy-avc still help?

Yes.. with that settings vegas works well. But i checked in task manager while checked on AVC.. Intel GPU stays on 0%.. it only run while i checked on HEVC.

Well I think I've exhausted all my ideas except, stick with what works.

Btw, the legacy-hevc setting won't matter without hevc footage in your project. If Vegas crashes with the igpu trying to decode avc, hevc probably will too. If you check both legacy boxes, the igpu selection will be greyed out because it's bypassed for both avc and hevc. Not sure it's the same processing library but setting the igpu to off with the boxes unchecked should also bypass the igpu. Be a shame if you cannot use your igpu because it provides a huge advantage if you can get it working.

Well I think I've exhausted all my ideas except, stick with what works.

Btw, the legacy-hevc setting won't matter without hevc footage in your project. If Vegas crashes with the igpu trying to decode avc, hevc probably will too. If you check both legacy boxes, the igpu selection will be greyed out because it's bypassed for both avc and hevc. Not sure it's the same processing library but setting the igpu to off with the boxes unchecked should also bypass the igpu. Be a shame if you cannot use your igpu because it provides a huge advantage if you can get it working.

Yes.. sir.. thats why i am going to send now a request to customer support with vegas dump file along with all necessary information. May be they have any solution for this.

I konw a weird workaround from other users, you can give it a try : find "errorreportclient.exe" in vegas directory, then rename it to anything to see if this help you.

If no help, please rename it back.

I konw a weird workaround from other users, you can give it a try : find "errorreportclient.exe" in vegas directory, then rename it to anything to see if this help you.

If no help, please rename it back.

Ok, let me try this.. thanks 👍

Updated now.. should i check on default settings of File I/O.. ? Or i just keep mine?

Generally you should get identical quality but better performance without legacy-avc checked.

ok got it... i changed it to default now check on only HEVC.

My rule with Vegas is don't use it's poor quality GPU decoder if you don't have to. 1080P60 AVC with a Intel12700 CPU means you don't need it unless you are using a CPU intensive FX (where you would benefit). It doesn't get to your core problem, because we know 1080P60 AVC doesn't cause crashing on other systems to the same extent as you but maybe not using the GPU decoder is a solution until next release where you may not have such problems due to your interaction with Vegas developers helping to fix bugs.

On a related note. I"ve always found editing 1080P60 AVC on Vegas smoother and less laggy without GPU decoder, than with, and this experience has been true for both Intel IGPU decoder(couple of years ago) and Nvidia GPU decoder now. It's not the hardware that's the problem, it's Vegas

Todd has right. Exactly the same problem on both my i7 system and my daughter's Ryzen5 system.
GPU decoding is just buggy, not matter what drivers we use (studio or 22.5.1 on amd side).

Of course every other video or vga related app works fine.