@RogerS are u saying that vegas can't work on some type of media?

take a look

i am working on pexels.com stock footages 4k or high quality images.

nothing my personal

Yes, I'm saying VEGAS is unstable with certain media. I don't know what Pexels stock footage is like- can you share Mediainfo for it?

If high quality image= jpeg that should be fine.

now i am trying to do the same project with compressing my all images from 4k to normal.

may it will work

Yes, I'm saying VEGAS is unstable with certain media. I don't know what Pexels stock footage is like- can you share Mediainfo for it?

If high quality image= jpeg that should be fine.

but sir it should not be like this if vegas is a ready to use software for 4k to 8k media. i am confused.

VEGAS works with 4K media.

What is the stock footage exactly? MOV? Does it use the old QuickTime 32-bit decoder? MediaInfo can answer this.

@iEmby I see you have 16 GB of memory, this is below the 32 GB as recommended for 4K / 8K editing as is posted on the Vegas 20 official webpage. Also windows 11 will take more memory with bigger available memory. In your case I expect a lot of swapping going on which can lead to instability. Having a Radeon card does not help eighter, Radeon cards have good hardware, but their drivers and software are notoriously buggy.

I would invest in more memory, also as an experiment to rule out your external video card, disable your external graphic card in windows device manager (display adapter), select disable device, then restart your PC.

You could also first reduce your 4K jpg source material to HD in an external photo editing program, before importing into your HD project and see if that helps.

@iEmby, curious as to what drivers for your RX560 are being used. When you get the white screen of death, do you also get a window saying that there has been a crash to send a crash report back to Vegas devs?

@bitman, I've been using AMD graphics since VP14-20, the RX480 8GB card, and now the RX 6700XT. No real problems with the drivers. I don't upgrade for the purpose of upgrading if a current driver is working. But I am on a driver from May of last year, not because of Vegas, but because of NBFX TP7, BorisFX Title Studio, and Ignite Pro 5 not working or partially working. With AMD's latest, TP7 works, Ignite is a bust, and Title Studio still doesn't function as it should. Your suggestion to disable the AMD card is one that might solve the problem, but then, there are the usual, "update you iGPU drivers" to be sure.

It seems that drivers of all the graphics cards have been problematic in working. Why? I wish I knew.

@iEmby, curious as to what drivers for your RX560 are being used. When you get the white screen of death, do you also get a window saying that there has been a crash to send a crash report back to Vegas devs?

Actually .. it gives white dead freeze screen and it will stay still there for 20 to 30 minutes if i will not close it manually. And sometimes after 20 to 30 minutes it resume otherwise it gives that send report dialogue box.

@iEmby

Post any errors from Windows Reliability History.

@iEmby Hi,, the Media Info you've been asked for is easy to share 👍

The App is called MediaInfo, download it, it's free & a fast download with no added adverts or any of that rubbish & it's a good learning tool . https://mediaarea.net/en/MediaInfo

After downloading, right click on the media file in your Windows folder, open MediaInfo, choose Text from the options at the top, Copy & paste the information in a new comment on here 👍

Like this
 

@iEmby

Post any errors from Windows Reliability History.

 

Source
VEGAS Pro

Summary
Stopped working

Date
‎25-‎07-‎2023 23:30

Status
Report sent

Description
Faulting Application Path:    C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe

Problem signature
Problem Event Name:    BEX64
Application Name:    vegas200.exe
Application Version:    20.0.0.411
Application Timestamp:    64875a02
Fault Module Name:    amdocl64.dll
Fault Module Version:    31.0.21001.45002
Fault Module Timestamp:    64921e06
Exception Offset:    00000000003e5ddd
Exception Code:    c0000409
Exception Data:    0000000000000007
OS Version:    10.0.22621.2.0.0.256.48
Locale ID:    16393
Additional Information 1:    b405
Additional Information 2:    b40536924820cc81fd2f88ede4890e9c
Additional Information 3:    9d21
Additional Information 4:    9d21b54564ba28e98946fb94e04069b7

Extra information about the problem
Bucket ID:    7168821096e968e149f8269a3a8a18b1 (1871288089021388977)
 

and this is again... occurs in next 20-30 minutes

Source
VEGAS Pro

Summary
Stopped responding and was closed

Date
‎26-‎07-‎2023 00:03

Status
Report sent

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe

Problem signature
Problem Event Name:    AppHangXProcB1
Application Name:    vegas200.exe
Application Version:    20.0.0.411
Application Timestamp:    64875a02
Hang Signature:    ad74
Hang Type:    67278849
Waiting on Application Name:    ErrorReportClient.exe
Waiting on Application Version:    20.0.0.411
OS Version:    10.0.22621.2.0.0.256.48
Locale ID:    16393
Additional Hang Signature 1:    ad74e5577ee69a4a1090c7b0db7b9cb9
Additional Hang Signature 2:    d671
Additional Hang Signature 3:    d6718e6ccd0126483b5633a8304bd623
Additional Hang Signature 4:    5a6a
Additional Hang Signature 5:    5a6a3a8b3a8aa52aff3b8370bef64042
Additional Hang Signature 6:    1bf5
Additional Hang Signature 7:    1bf508a56abb2507af3a0ff955009678

Extra information about the problem
Bucket ID:    123f465538cb1426e59f4b1c289077df (1558046580405204959)
 

...still no info on your graphics driver...

@iEmby

BEX64 may be associated with driver.

I gave up: https://www.vegascreativesoftware.info/us/forum/my-running-log-of-vegas-pro-service-interruptions--137804/?page=3#ca886142

Someone more intimate with Vegas code will have to comment on Problem Event Name:    AppHangXProcB1.

actually i tried with my last option i have.. which is reset my bios and reinstall entire windows. bios disable my iGPU and windows installation affect on errors. now its working smooth than last one. not lagging or crashing in every 2 3 minute but it is still crashing in 20-30 minutes

I would reenable the IGPU.

Are you still working with 4K and 16GB ram only? This is below the technical specification for Vegas pro 20.

https://www.vegascreativesoftware.com/us/specifications/

Have you seen this posting by bitman?

I doubt ram is the cause of instability- edited using >4K jpegs for years with 8GB of ram in VEGAS. The recommended specs are odd- haven't seen an 8-core 7th gen i7 CPU.

This instability is media x AMD GPU though still unclear what the media is or the graphics driver.

The Intel iGPU is known to do a good job with decoding so having that working should be a plus for stability.

I doubt ram is the cause of instability- edited using >4K jpegs for years with 8GB of ram in VEGAS. The recommended specs are odd- haven't seen an 8-core 7th gen i7 CPU.

This instability is media x AMD GPU though still unclear what the media is or the graphics driver.

The Intel iGPU is known to do a good job with decoding so having that working should be a plus for stability.

 

 

How can you know that?

@Wolfgang S.

@RogerS

@bitman

I upgraded my RAM to 32 GB just 2 hours before.

still getting same freeze problem.

problem description

Description
Faulting Application Path:    C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe

Problem signature
Problem Event Name:    BEX64
Application Name:    vegas200.exe
Application Version:    20.0.0.411
Application Timestamp:    64875a02
Fault Module Name:    amdocl64.dll
Fault Module Version:    31.0.21001.45002
Fault Module Timestamp:    64921e06
Exception Offset:    00000000003e5ddd
Exception Code:    c0000409
Exception Data:    0000000000000007
OS Version:    10.0.22621.2.0.0.256.48
Locale ID:    16393
Additional Information 1:    31f0
Additional Information 2:    31f03d3ba7454c0936199525d1677ea9
Additional Information 3:    6a9b
Additional Information 4:    6a9b0c4f73b66cbd80360ac1092f9dbd

Extra information about the problem
Bucket ID:    7168821096e968e149f8269a3a8a18b1 (1871288089021388977)

this is my system information

i asked to ChatGPT by pasting my problem description and it gives me this.

Based on the error information provided, it appears that there is a problem with the application "VEGAS Pro 20.0" (vegas200.exe) running on your system. The error indicates a "BEX64" issue, which stands for Buffer Overflow Exception. This type of error is often related to compatibility or stability issues between the application and the operating system or other software components.

The faulting module responsible for the crash is "amdocl64.dll," which is a library associated with AMD OpenCL (Open Computing Language) runtime. OpenCL is a framework for utilizing the computing power of GPUs (Graphics Processing Units) for general-purpose computations.

now please don't say change your graphic card.

give me a solution pls.

i can't afford new graphics card.

I doubt ram is the cause of instability- edited using >4K jpegs for years with 8GB of ram in VEGAS. The recommended specs are odd- haven't seen an 8-core 7th gen i7 CPU.

This instability is media x AMD GPU though still unclear what the media is or the graphics driver.

The Intel iGPU is known to do a good job with decoding so having that working should be a plus for stability.

 

 

How can you know that?

Lot of experience helping users. In general throwing money at hardware to attempt to fix stability in VEGAS is money wasted, and it appears that is the case here and more ram does not help stability (though may benefit performance). If the GPU is not supported in VEGAS that's a different story.

@iEmby What is the GPU and what is the driver version? Maybe I missed it but I don't see it here. Under help/driver update VEGAS should tell you both. You can also go to "device manager" in Windows, click on the display adapter and type in what it says here. Right-click on a GPU and go to properties and under driver you can find the version.