Vegas Pro 19 Random Crashes - 4k Video

DelGreco wrote on 10/10/2022, 6:26 AM

Hi, I'm hoping the group here can help me. I've been editing video for quite a while now as a hobby, (started in the early 2000s) and i've been moving through the various editing suites, and really like Vegas at the moment. I've been using it almost exclusively for the last ~3-4 years for occasional hobby editing.

Anyway, my editor keeps crashing, and really unpredictable times, across a range of settings. Some crashes are terminal, requiring a hard reset of the while PC. Some crash out of Vegas, but windows is recoverable, and others are caught by Vegas and allow me to send in an error report, view logs, etc.

 

Overview of the setup.

I have windows 10 64bit.
Intel I7700K,
32GB RAM
AMD 6800XT GPU
Multiple HDDs, NVMe, etc.

Video Footage:
From Canon R5, 4K 60FPS.
From GoPro 6 & 10 Black. ~2.7k@120FPS, or 4K 60FPS.

 

I was running the latest AMD drivers, however, when I checked in Vegas, it said to downgrade to 22.5.1 from 30.0.15021, which I did, but this didnt seem to change anything.

 

The following settings seem to give me the best performance:

Preferences / Video :
- Dynamic RAM ~65% (21GB)
- Max rendering threads: 28
- GPU Accel: OFF
- Thumbnails: Head only
Prefereces / File IO:
- MKV Reader: OFF
- Legacy AVC: ON
- Legacy HVEC: ON

 

So far this morning I have crashed a few times. Once killed Vegas, once was caught by Vegas and allowed me to capture the following Crash Detail:
Crash Type: Caught (System, App, Caught)
Crashed when watching footage through - No editing/scrubbing, just watching the edited video in the preview window. Preview(Auto) quality.


Crash Information
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\fileio_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\persist.prefs
   File:                C:\Users\user\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\user\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\dx_video_grovel_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\svfx_video_grovel_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\ocio_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\dx_grovel_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\vegas_script_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\gpu_video_x64.log
   File:                C:\Users\user\AppData\Local\VEGAS Pro\19.0\hub.log
   File:                Z:\Video Editing\Projects\BestLathePlans\BLP-0025 - Cringle Engineering and Castings\BLP-0025 - Cringle Engineering and Castings.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 19.0 (Build 643)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\u0382767.inf_amd64_2ba2e1bcba1eb9ff\B378972\atio6axx.dll
   Fault Address:       0x00007FFE107E9B48
   Fault Offset:        0x00000000008B9B48

 

Has anyone else had similar issues, and know of any fixes?

 

Kindest Regards,

Del

Comments

Former user wrote on 10/10/2022, 6:36 AM

@DelGreco Hi, Gopro videos come up on here a few times,

there's an App called MediaInfo, download it, it's free & a fast download with no added adverts or any of that rubbish. 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 -

RogerS wrote on 10/10/2022, 6:38 AM

Personally I find 19.550 more reliable than 643.

You definitely want to downgrade to the stable AMD 22.5.1 driver as newer ones introduce color problems upon render among other things.

For your error, atio6axx.dll is the AMD driver though.

Dynamic ram is set quite high. Perhaps go back to 5% or 10%?

I'm surprised that GPU preview off and legacy AVC decoding give best performance. Disabling GPU support for the preview may yield better stability but should be much worse performance.

For the media can you share MediaInfo for which formats you are using? Instructions: https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Dexcon wrote on 10/10/2022, 6:42 AM

Does this happen with either or both Legacy AVC and Legacy HVEC turned off in Preferences / File I/O?

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

DelGreco wrote on 10/10/2022, 9:00 AM

Hey all, and thanks for the quick replies.

So, since posting i've had 3x new crashes. 2 were the AMD driver,
Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\u0382767.inf_amd64_2ba2e1bcba1eb9ff\B378972\atio6axx.dll
and one was
Fault Module:        W:\Program Files\VegasPro19\vegas190k.dll

 

Interestingly, the last crash all was working fine until I enabled the video preview on external monitor. It worked for about 1 min, then the video files flickered, then a crash of Vegas. Not the whole system, luckily!

Also, none of the video files were GoPro files at this point...

R5 video details below:

General
Complete name                            : Y:\Photos and Video\2022-2025\Canon R5\R5_2022\2022_06_15 - Engineering - Cringle Engineering Foundry\CR5_9390.MP4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (mp42/avc1/CAEP)
File size                                : 150 MiB
Duration                                 : 10 s 210 ms
Overall bit rate                         : 123 Mb/s
Encoded date                             : UTC 2022-06-15 12:14:09
Tagged date                              : UTC 2022-06-15 12:14:09

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.2
Format settings                          : 2 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=3, N=30
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 10 s 210 ms
Bit rate                                 : 123 Mb/s
Width                                    : 4 096 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 1.896
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.232
Stream size                              : 149 MiB (100%)
Language                                 : English
Encoded date                             : UTC 2022-06-15 12:14:09
Tagged date                              : UTC 2022-06-15 12:14:09
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 10 s 197 ms
Bit rate mode                            : Constant
Bit rate                                 : 256 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 315 KiB (0%)
Language                                 : English
Encoded date                             : UTC 2022-06-15 12:14:09
Tagged date                              : UTC 2022-06-15 12:14:09

Other
ID                                       : 3
Type                                     : Time code
Format                                   : QuickTime TC
Duration                                 : 10 s 210 ms
Bit rate mode                            : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Time code of first frame                 : 04:13:55;00
Time code, striped                       : Yes
Language                                 : English
Encoded date                             : UTC 2022-06-15 12:14:09
Tagged date                              : UTC 2022-06-15 12:14:09

 

 

I think it's unlikely to be a specific video file/format as the error seems to happen really intermittently.

 

Also, I'm on the correct driver, but in the app it seems confused what version i'm using...

 

I've also dropped back the dynamic ram 5%, and the active render threads to 32.

 

Re the Legacy AVC, If I disable legacy, the preview window plays really horribly. Shows a frame every 2-3 seconds, very laggy, out of sync with the audio.

With Legacy AVC, its far more usable. Still not perfect, but not anywhere near as bad!

 

Lastly, is there a way to enable more detailed app logs? none of the files listed in the extra info crash report have any useful crash details data in them. just system loading stuff.

 

Finally, the windows event viewer event log, (Windows Logs, Application) has a few errors, this one being the most relevant...
Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2075, time stamp: 0x923a0837

No real idea what is going on with the windows desktop manager though!

DelGreco wrote on 10/10/2022, 9:02 AM

Also, when editing, i've had task manager running and been looking at the system stats. The GPU never really goes above 10% usage, and the CPU is around 80% used.
I've loads of spare RAM too (40% spare, ~12GB)

DelGreco wrote on 10/10/2022, 9:03 AM

Oh, and one other wierd thing which may or may not be related, every time I launch the app I have to reactivate my license.

vkmast wrote on 10/10/2022, 9:10 AM

 every time I launch the app I have to reactivate my license.

Please see if this thread is helpful.

DelGreco wrote on 10/10/2022, 9:31 AM

 every time I launch the app I have to reactivate my license.

Please see if this thread is helpful.

Fixed that issue. Now I can reload the app faster after a crash at least! :)

DelGreco wrote on 10/10/2022, 10:33 AM

Just had another crash that killed vegas and no error handling / error report.

This is from the windows event log.

Faulting application name: vegas190.exe, version: 19.0.0.643, time stamp: 0x62a9244f
Faulting module name: ntdll.dll, version: 10.0.19041.2075, time stamp: 0x89a237de
Exception code: 0xc0000374
Fault offset: 0x00000000000ff789
Faulting process ID: 0x5694
Faulting application start time: 0x01d8dcb56401eb06
Faulting application path: W:\Program Files\VegasPro19B\vegas190.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: ce75dc30-c07a-4fcb-9b48-5cd182b8a9de
Faulting package full name: 
Faulting package-relative application ID: 

Former user wrote on 10/10/2022, 7:19 PM

A number of people now have mentioned VP19b643 crashing their computer. Vegas is infamous for crashing a lot but not taking down windows in the process. I"m beginning to think it's a real thing, not a coincidence. I went back to b550 after a plethora of crashes. I knew something was very wrong when the 4K Vegas benchmark project could no longer load without crashing, even though it would load on initial install. It's stability deteriorated until it was unusable