render freezes and got black screens

RogerS wrote on 4/17/2025, 7:58 PM

What does Windows Reliability History show?

Reyfox wrote on 4/18/2025, 7:53 AM

I am using 25.3.1 for my RX 6700XT. No issues with Mini 3 Pro footage.

Can you supply a sample of problematic footage that has black frames?

As for updating AMD drivers, I use AMD Cleanup Utility, which boots the computer into Safe Mode to remove the old driver. Then when you boot back to normal, you install the new version GPU driver.

BONLEV wrote on 4/18/2025, 11:21 AM

What does Windows Reliability History show?

never heard of this before but I have found this after a search on my pc:

the most common error I saw was:

Program vegas220.exe version 22.0.0.248 no longer communicates with Windows and is closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance Control Panel.

werkt niet meer = no longer works -> that's the most common I see in the list and also

reageert niet meer = no longer responds

the latest "werkt niet meer" from 16:51 is this one:

Beschrijving
Toepassingsnaam met fout: vegas220.exe, versie: 22.0.0.248, tijdstempel: 0x67f55391
Naam van foutmodule: ntdll.dll, versie: 10.0.26100.3775, tijdstempel: 0x5e4be250
Uitzonderingscode: 0xc0000374
Foutoffset: 0x0000000000115f55
Foutproces-id: 0xA0C
Begintijd van foutieve toepassing: 0x1DBAFA6CC5779E7
Faulting-toepassingspad: C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
Faulting-modulepad: C:\WINDOWS\SYSTEM32\ntdll.dll
Rapport-id: 732939f1-e890-4008-8fc3-dd3bb2c82a5e
Faulting-pakket volledige naam:
Faulting-pakket-relatieve toepassings-id:

desktop window manager in detail error says:

Beschrijving
Pad naar toepassing met fout: C:\Windows\System32\dwm.exe

Probleem met handtekening
Naam van probleemgebeurtenis:   APPCRASH
Naam van de toepassing:   dwm.exe
Versie van toepassing:   10.0.26100.3624
Tijdstempel van toepassing:   b9885ec0
Naam van foutmodule:   amdxx64.dll
Versie van foutmodule:   32.0.12033.1030
Tijdstempel van foutmodule:   6746e701
Uitzonderingscode:   c0000005
Uitzonderingsmarge:   000000000035065e
Versie van besturingssysteem:   10.0.26100.2.0.0.256.48
Landinstelling-id:   2067
Aanvullende informatie 1:   6f9f
Aanvullende informatie 2:   6f9fe9a1a302bbc4af9b880e8f9caca6
Aanvullende informatie 3:   c205
Aanvullende informatie 4:   c205bac5c04b0181c70a2cb41040e649

Extra informatie over het probleem
Bucket-id: c63fe7a9408883fbebfc96aa0ebe6544 (2016652390291105092)

BONLEV wrote on 4/18/2025, 11:26 AM

I am using 25.3.1 for my RX 6700XT. No issues with Mini 3 Pro footage.

Can you supply a sample of problematic footage that has black frames?

As for updating AMD drivers, I use AMD Cleanup Utility, which boots the computer into Safe Mode to remove the old driver. Then when you boot back to normal, you install the new version GPU driver.

thx for the help! I don't have black frames in my footage but my whole screen goes black and starts glitching and then vegas crashes. Mostly then windows freezes and I have to force to shut my pc down.

I wait first for the answer of RogerS about my Windows Reliability History. After that I can I have I look at your possible solution.

RogerS wrote on 4/18/2025, 7:13 PM

Thanks for sharing. Look for critical events and see what fault modules are listed.

amdxx64.dll

Suggests an AMD driver issue so a clean install of a different driver version could help. I'd report it to AMD support, too. Vegas itself can't crash Windows in my experience but driver issues can (reported problems to NVIDIA years back).

BONLEV wrote on 4/19/2025, 6:39 AM

Reyfox en RogerS. Thank you so much! a clean install with the AMD cleanup utility fixed my problem! Now I'm on version 25.3.1 and the render went fine without any glitches of my screens!

RogerS wrote on 4/19/2025, 7:11 AM

Now that's great news!!!

Reyfox wrote on 4/19/2025, 7:14 AM

@BONLEV awesome!

Now, back to editing for you! 😉

BONLEV wrote on 4/20/2025, 7:08 AM

back a freeze when rendering in VP22 build 248. I tested 2 different projects. Both contains DJI pocket 3 and DJI mini 3 pro footage. One project was only pocket 3 with the m-log to rec 709 lut on it. Stuck on a certain percentage. Now it was at 99% but my previous test where at a different percentage.

This time a received an AMD + vegas pro error. I attached these.

Strange thing is when copied the timeline in VP21 the rendering went fine on both of my tested projects.

I sended this error to AMD.

RogerS wrote on 4/20/2025, 7:12 AM

Since it says the error was with an Fx, what Fx were in use? If it was the LUT Fx can you try adding a LUT via the color grading panel instead?

Reyfox wrote on 4/21/2025, 5:19 AM

@BONLEV are your issues when using just the the Mini 3 Pro? Can you provide a specific problematic clip and the LUT?

BONLEV wrote on 4/21/2025, 11:24 AM

@BONLEV are your issues when using just the the Mini 3 Pro? Can you provide a specific problematic clip and the LUT?

not just mini 3 pro footage. Also with panasonic GH5S (8bit) , sony FX6 footage... it seems that every project I made now in VP22 crashes on export and the same project (with copy paste) in VP21 does not crash on render. At this moment I think the problem is with VP22. I will update this tread when I have more time to test it out.

BONLEV wrote on 4/21/2025, 11:26 AM

Since it says the error was with an Fx, what Fx were in use? If it was the LUT Fx can you try adding a LUT via the color grading panel instead?

it was the lut filter. I still have to test it out with the grading panel. Even a simple white balance did crash my export in VP22. Not in VP21.

Reyfox wrote on 4/21/2025, 12:13 PM

Interesting in deed. I have the Mini 3 Pro and and a G9 that I shoot in 4K 10 bit 4:2:2 in addition to 8 bit. The files can be MOV or MP4. I will use plugins, color correct/grade and always never an issue rendering the finished videos.

BONLEV wrote on 5/28/2025, 1:20 PM

I now random have glitches on my timeline. It's not in original footage. when I did a test export and it was NOT ok and the glitch was also in it. Sometimes if I cut a bit sooner or later on the timeline I can avoid this glitch but that's not a solution.

It seems only a problem (the random) glitches in my wide shots from my sony FX6 in the mxf format. My close up shot in MP4 not found a glitch at this moment.

I'm the latest build and also my graphics card is on the latest. Someone else experience this?

Reyfox wrote on 5/28/2025, 4:20 PM

Can you upload a sample of a problematic footage to the cloud? It can be anything that would cause the problem...

RogerS wrote on 5/28/2025, 8:51 PM

What is in the MXF? (MediaInfo would be good).

It's most likely GPU x media. We've gotten these decoding bugs addressed with NVIDIA but there may be some remaining for AMD. Uploading a sample would help others confirm the nature of the issue.

Do you still have 21.208 around (from your signature) and do you see glitches there? I'd guess there aren't any.

BONLEV wrote on 5/29/2025, 6:38 AM

Can you upload a sample of a problematic footage to the cloud? It can be anything that would cause the problem...

i uploaded 2 examples of glitches to youtube. the strange thing about the second one is that the glitched scene is not from that point on the timeline.

BONLEV wrote on 5/29/2025, 6:42 AM

What is in the MXF? (MediaInfo would be good).

It's most likely GPU x media. We've gotten these decoding bugs addressed with NVIDIA but there may be some remaining for AMD. Uploading a sample would help others confirm the nature of the issue.

Do you still have 21.208 around (from your signature) and do you see glitches there? I'd guess there aren't any.

still have vegas pro 21 with build 208 on my pc and I just did a copy paste of my current project into it. It seems It gave me no glitches there But my previous project was also containing the mxf files and there I didn't had those glitches... (vegas pro 22) In the meantime (as a workaround) I can finish my project in pro 22 and render it in pro 21.

mediainfo:

General
Complete name : D:\romeo en julia moes 3mei25\FX6\741_1443.MXF
Format : MXF
Format version : 1.3
Format profile : OP-1a
Format settings : Closed / Complete
File size : 40.4 GiB
Duration : 55 min 37 s
Overall bit rate mode : Variable
Overall bit rate : 104 Mb/s
Frame rate : 25.000 FPS
Encoded date : 2025-05-02 19:50:33.000
Writing application : Sony Mem 2.00

Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.1
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 2 frames
Format settings, GOP : M=3, N=12
Format settings, wrapping mode : Frame
Format settings, Slice count : 8 slices per frame
Codec ID : 0D01030102106001-0401020201314001
Duration : 55 min 37 s
Bit rate mode : Variable
Bit rate : 100.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.482
Stream size : 38.6 GiB (96%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio #1
ID : 3
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 55 min 37 s
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 25.000 FPS (1920 SPF)
Bit depth : 24 bits
Stream size : 458 MiB (1%)
Locked : Yes

Audio #2
ID : 4
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 55 min 37 s
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 25.000 FPS (1920 SPF)
Bit depth : 24 bits
Stream size : 458 MiB (1%)
Locked : Yes

Audio #3
ID : 5
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 55 min 37 s
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 25.000 FPS (1920 SPF)
Bit depth : 24 bits
Stream size : 458 MiB (1%)
Locked : Yes

Audio #4
ID : 6
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300-0402020101000000
Duration : 55 min 37 s
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 channel
Sampling rate : 48.0 kHz
Frame rate : 25.000 FPS (1920 SPF)
Bit depth : 24 bits
Stream size : 458 MiB (1%)
Locked : Yes

Other #1
ID : 1-Material
Type : Time code
Format : MXF TC
Frame rate : 25.000 FPS
Time code of first frame : 01:38:44:18
Time code of last frame : 02:34:22:13
Time code settings : Material Package
Time code, stripped : Yes

Other #2
ID : 1-Source
Type : Time code
Format : MXF TC
Frame rate : 25.000 FPS
Time code of first frame : 01:38:44:18
Time code of last frame : 02:34:22:13
Time code settings : Source Package
Time code, stripped : Yes

Other #3
ID : 7
Format : Acquisition Metadata
Format settings, wrapping mode : Frame
Muxing mode : Ancillary data / RDD 18
Codec ID : 0D010301020E0000
Frame rate : 25.000 FPS
TransferCharacteristics_FirstFrame : 0E06040101010705
ColorPrimaries_FirstFrame : BT.709
MatrixCoefficients_FirstFrame : BT.709
IrisFNumber_FirstFrame : 4.494283
FocusPositionFromImagePlane_FirstFrame : 16.350 m
LensZoom35mmStillCameraEquivalent_FirstF : 95.200 mm
LensZoomActualFocalLength_FirstFrame : 90.000 mm
LensAttributes_FirstFrame : 0000000000
FocusRingPosition_FirstFrame : 90.4984%
ZoomRingPosition_FirstFrame : 59.9594%
AutoExposureMode_FirstFrame : Shutter Priority Auto
AutoFocusSensingAreaSetting_FirstFrame : Manual
NeutralDensityFilterWheelSetting_FirstFr : Clear
ImageSensorDimensionEffectiveWidth_First : 35.616 mm
ImageSensorDimensionEffectiveHeight_Firs : 20.092 mm
CaptureFrameRate_FirstFrame : 25.000 fps
ImageSensorReadoutMode_FirstFrame : Progressive frame
ShutterSpeed_Angle_FirstFrame : 180.0°
ShutterSpeed_Time_FirstFrame : 1/50 s
CameraMasterGainAdjustment_FirstFrame : 26.00 dB
ISOSensitivity_FirstFrame : 6400
ElectricalExtenderMagnification_FirstFra : 100%
AutoWhiteBalanceMode_FirstFrame : Preset
WhiteBalance_FirstFrame : 3244 K
CameraMasterBlackLevel_FirstFrame : 1.0%
CameraAttributes_FirstFrame : ILME-FX6V 4012741 Version4.00
ExposureIndexofPhotoMeter_FirstFrame : 6400

Other #4
ID : 7
Format : 53-01
Format settings, wrapping mode : Frame
Codec ID : 0D010301020E0000
Duration : 55 min 37 s
Frame rate : 25.000 FPS

Other #5
Type : Time code
Format : SMPTE TC
Muxing mode : SDTI
Frame rate : 25.000 FPS
Time code of first frame : 01:38:44:18

Reyfox wrote on 5/29/2025, 8:06 AM

@BONLEV you have to upload to the cloud, the actual footage, not a Youtube video. Also include an easy to follow replication steps that can be done by others to see if it is an issue with other system builds.

I'm willing to give it a go on my all AMD computer.

RogerS wrote on 5/29/2025, 8:12 AM

Can you upload a sample of a problematic footage to the cloud? It can be anything that would cause the problem...

i uploaded 2 examples of glitches to youtube. the strange thing about the second one is that the glitched scene is not from that point on the timeline.

@BONLEV Could you please upload a file to Google Drive, Dropbox, Box or another service? We need the original MXF footage, not the one that was edited in VEGAS.

BONLEV wrote on 6/9/2025, 8:01 AM

I uploaded a mxf to dropbox. https://www.dropbox.com/home/Teammap%20van%20vegas%20proI hope this worked. In the meantime I converted the mxf files with handbrake and even then I had glitches in VP22 with it. I also tried amd driver version 25.3.1 and 24.12.1 with the same results.

Now this time I couldn't copy my timeline into VP21. It didn't do anything so exported to edl text file in vp22. I lost all my effects with this in VP21 but I copy pasted them from VP22. Now my render from VP21 seems fine without any glitches.

I don't think the problem is in the original mxf files but in VP22 because after mxf to mp4 with handbrake the glitches are still there...

RogerS wrote on 6/9/2025, 9:14 AM

@BONLEV I think your link is broken, could you try again? Right click on the file or folder and select Dropbox/ copy dropbox link. Then post it here.

I'm happy to test the file and am sure others would too. I agree it's probably an issue with how VP 22 is reading the file.

BONLEV wrote on 6/9/2025, 9:23 AM

https://www.dropbox.com/scl/fi/9ubx8l2to2gignmpk8z2j/741_1449-1.MXF?rlkey=cuyy7akb8cj3gn807o0hd2o82&st=a1iukkqi&dl=0

I think sharing MXF is not possible with dropbox?