VP19 new build 361 gets the crash window on every close down

Comments

Kimberly-Durecki wrote on 9/13/2021, 10:21 AM

<user email> Just updated and it crashes everytime :(

 

michael-harrison wrote on 9/13/2021, 10:21 AM

Also not seeing any crashing on 361 with light use. Opened and saved several projects after making small edits.

System 1:

Windows 10
i9-10850K 10 Core
128.0G RAM
Nvidia RTX 3060 Studio driver [most likely latest]
Resolution        3840 x 2160 x 60 hertz
Video Memory 12G GDDR5

 

System 2:

Lenovo Yoga 720
Core i7-7700 2.8Ghz quad core, 8 logical
16G ram
Intel HD 630 gpu 1G vram
Nvidia GTX 1050 gpu 2G vram

 

Grazie wrote on 9/13/2021, 10:38 AM

I'm smashing and Bashing B361 - Its Greeeeat!

Grazie wrote on 9/13/2021, 10:39 AM

I've got a TEN-hour project on one timeline. Luvin' it.

Kimberly-Durecki wrote on 9/13/2021, 10:44 AM

Same here, I just upgraded and each time on closing it crashes....

mysticaleditor wrote on 9/13/2021, 11:15 AM

Updated 3 editors now projects will not open projects created yesterday on 19 prior version.

 

RogerS wrote on 9/14/2021, 1:59 AM

If it crashes can you also include hardware details and any 3rd party Fx and plugins you use to help narrow down why this is happening?

Grazie wrote on 9/14/2021, 2:04 AM

@mysticaleditor - Did you do an “Install-Over” installation?

VEGASPascal wrote on 9/14/2021, 2:16 AM

@Dexcon @Kimberly-Durecki We would like to give you specific feedback but you have to write something in the description (the last steps and your username) and create a screenshot of this in your post. This report is now grouped with similar bugs. I am not able to find your bug report. Sorry

Dexcon wrote on 9/14/2021, 2:59 AM

@VEGASPascal  ... I've just sent another report from the 'Vegas has stopped working' window. It is marked to your attention. Thanks in advance.

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 20, 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

VEGASPascal wrote on 9/14/2021, 3:25 AM

@VEGASPascal  ... I've just sent another report from the 'Vegas has stopped working' window. It is marked to your attention. Thanks in advance.

What are the words in the description that I will find this report? I could try to search for "Dexcon"

Dexcon wrote on 9/14/2021, 3:30 AM

@VEGASPascal  ... The report starts off with 'Att: VEGASPascal' (without the quotation marks of course), and 'Dexcon' is also in the text. 'Mocha Pro' is also in the text as is 'BCC 2021.5'.

I hope this helps. Cheers.

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 20, 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

mysticaleditor wrote on 9/14/2021, 9:33 AM

@mysticaleditor - Did you do an “Install-Over” installation?


@Grazie - thanks for asking. I did an install from the Vegas GUI so 361 was installed over the prior version.

The issue I had may not be related to the version upgrade. Although a new drive (2 months old with one other project), there was some sort of file corruption (albeit only on .veg files) which rendered them unopenable and a files size of 0 bytes. Strange. I make it a process to dump copies of .veg files into an /OLDVEGS directory which had a .bak of one of the projects which I was able to rename and save. The others were unsalvagable. A Win 10 checkdisk did find an error on the drive. I recreated the project this morning after the version upgrade and it seems to be going smoothly. tx, Paul

Grazie wrote on 9/14/2021, 10:09 AM

@mysticaleditor - I’m noted all those here who’ve installed-over and not getting a full working installation with symptomatic crashes and whiteouts.

dortith wrote on 9/14/2021, 10:32 AM

Help! Just loaded Build 361 - won't get passed the loading window before message 'Vegas Pro has stopped working' - this is my crash report. Worked fine before the update. What should I do?

Extra Information
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\fileio_x64.log
   File:                C:\Users\tfgmc\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\tfgmc\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\dx_video_grovel_x64.log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_video_grovel_x64.log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (0, Multiple Contexts).log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Colorization' (0, Filter).log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (1, Multiple Contexts).log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_StyleTransfer' (1, Filter).log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Upscale' (2, Multiple Contexts).log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\svfx_Ofx1_1_plugin_x64-'de.magix_Upscale' (2, Filter).log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\ocio_x64.log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\dx_grovel_x64.log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\vegas_script_x64.log
   File:                C:\Users\tfgmc\AppData\Local\VEGAS Pro\19.0\gpu_video_x64.log

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 19.0 (Build 361)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\Common Files\OFX\Plugins\NewBlue\TitlerEx.ofx.bundle\Contents\Win64\TitlerEx.ofx
   Fault Address:       0x000000000A0D1880
   Fault Offset:        0x0000000000001880

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
   Process Version:     Version 19.0 (Build 361)
   Process Description: VEGAS Pro
   Process Image Date:  2021-09-02 (Thu Sep 02) 20:28:28

 

VEGASPascal wrote on 9/14/2021, 10:33 AM

@Dexcon I am sorry but I am not able to give you some feedback. The crash happens deep in Mocha (error-ID: 0x00007FFDE01FEA4E (mocha.dll))

MartinVS wrote on 9/14/2021, 12:36 PM

Just uninstalled and reverted to the old 341 build. Luckily, their installer app will still install the 341 build, if anyone is wondering how to revert. Everything works as before now. This is a shame, though.

I'd suggest waiting to see if there are any official comments on this situation before updating to the latest build. I usually always update to the latest version, but unfortunately can't complete my work if I update to the 361 build.


(Screenshot from the newly installed old 341 build).


(You might not want to hit that update button if you have critical projects going on right now)

Is it still possible to revert to 341 somehow? 361 won't even start for me as I unfortunately updated, and it just crashes on startup all the time. When I grab the installer from my account it automatically downloads 361

John-Ivar wrote on 9/14/2021, 12:50 PM

@MartinVS I guess they've updated their installer. In that case, I'm not really sure how to revert. Sorry.

Maybe try uninstalling completely and installing the new build without installing over the old build? I will hold on to the previous build until the next update or something I guess.

vkmast wrote on 9/14/2021, 12:53 PM

Please try Direct Links, section 6 in Nick's D/L FAQ..

MusicVideoManSolo wrote on 9/14/2021, 1:38 PM

I'm glad I'm not the only one having this issue. Has anyone found a resolution? The program will not even start up on my end

Kimberly-Durecki wrote on 9/15/2021, 7:49 PM

Any sololutions yet, Mine crashes everytime I close out. So annoying. Thank you.

RogerS wrote on 9/15/2021, 9:55 PM

Any sololutions yet, Mine crashes everytime I close out. So annoying. Thank you.

Remove 361 and reinstall 341.