Hello,
I just purchased VP 17, upgrading from VP 14. After installing VP 17, it crashes every time upon launch.
VP 14 still works fine.
Intel Core i7 3.4 GHz
16 GB RAM
GeForce GTX 580 (not used for GPU rendering in VP 14)
326 GB free on C: drive, secondary drive has 717 GB free.
I also have Vegas Pro 10 (32 AND 64-bit) and Vegas Pro 13 installed.
Help?
Give us also that extra information you can select in the error message and than maybe we can give some help
Sure, here you go:
Problem Description
Application Name: VEGAS Pro
Application Version: Version 17.0 (Build 421)
Problem: Unmanaged Exception (0xe0434352)
Fault Module: C:\WINDOWS\System32\KERNELBASE.dll
Fault Address: 0x00007FF9B9FDA859
Fault Offset: 0x000000000003A859
Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
Process Version: Version 17.0 (Build 421)
Process Description: VEGAS Pro
Process Image Date: 2020-02-08 (Sat Feb 08) 07:06:34
I did uninstall it and reinstalled it, this time without bonus Boris Continuum plugin.
No change.
I do not see anywhere to submit a ticket anymore...only a search box for solutions.
Re support, please see here https://www.vegascreativesoftware.info/us/forum/how-does-the-support-work--115914/#ca745090
Thanks, I submitted a ticket (gotta love how they bury that, though).
So I'm the first to have this problem? Ugh. Waited 3 years to upgrade; not a good experience out of the box.
<rant off>
So I'm the first to have this problem?
No, a lot of people has, mostly when Windows and drivers are not updated or are not sufficient for Vegas 17, like your processor that have only 4 cores while in the specs is stated that that is not enough. Look
Could you be more specific?
I'm running Win 10 Pro 1903 (OS Build 18362.720).
I updated my NVidia drivers yesterday before purchasing today.
What version of MS .NET is required for VP 17?
See my updated answer above
I have .NET 4.8 installed. Also, not sure if your red highlight box re: 8 cores for 4K is for me...
I'm just trying to get the software to open...can't even get that far, let alone bring in media.
When it starts up it does say "Initializing GPU..." before the crash
Is there some special key command to get it to open without initializing that?..just wondering if that is to blame.
I did try using one monitor hooked into the DVI on my mobo (therefore not using the NVIDIA card). No change, still crashes.
When it starts up it does say "Initializing GPU..." before the crash
Looks very logic to me, because at that moment the GPU, your processor, becomes messured and the program sees it is only 4 cores for that i7 and that is not sufficient to use this program. Your solution only can be to add a processor that meets the specs or don't use this program untill you can install it on the proper hardware.
Except that the specs say "4 core minimum" unless your editing 4K, which need 8 cores. So it doesn't make sense that the program would crash just upon opening if I have 4 cores. (I agree, it's probably a GPU compatibility issue, but it still should open when I am hooked into my mobo DVI port.)
Actually, I watched it trying to open more closely...
It gets past the "Initializing GPU acceleration...", and also "initializing UI, and crashes right after "Creating windows".
Yep, just tried that. No luck.
I also tried builds 387 and 353. No luck.
The download link for 321 appears non-functional due to an expired certificate.
So I'm the first to have this problem?
No, a lot of people has, mostly when Windows and drivers are not updated or are not sufficient for Vegas 17, like your processor that have only 4 cores while in the specs is stated that that is not enough. Look
Not really relevant as I'm running an I5 4 core just fine.
I went for a walk and thought about this some more...
When my monitors are connected to my GTX 580, I can see how that GPU is *possibly* not supported and therefore get the crash.
So, okay, let's take that out of the loop: I hooked up one monitor to my mobo directly, and had the same problem with that.
Then I looked more closed at the minimum chipset required on a mobo for VP 17, and that is the Intel GPU HD Graphics 530 series or higher, and I only have the Intel HD Graphics 3000 chipset, so that may explain why that doesn't work either.
(My Intel Core i7-2600K is a 2nd gen processor with 4 cores.) :-(
In short, it is looking like my mobo/processor/GPU are too old...
Thanks to everyone for taking the time to respond!
Hello again!
So here's the end of the story:
I remembered I had my PC that runs my home entertainment projector, and checked it out; it has a 6th gen Core i5 quad core processor, Intel 530 graphics chip, and 32 GB of RAM.
So I took the SSD that was in the PC that was not working with VP17 (crashes upon launch) and put it this higher powered PC. (There is a way to do this; delete/uninstall all drivers specific to the old mobo, use "sysprep", shutdown, and pull it and put it in the new PC, sign in using MS credentials, and voila.) Vegas still crashed...Everything else worked fine after the SSD transfer in this scenario (i.e., older versions of Vegas and other photo/video apps).
I swapped out the SSDs again, so that the home entertainment PC had its original SSD, and installed VP 17 on that and it launched with no problems! Yay! So, I've spent the last three days installing all my photo/video editing software on this machine. The upside is this PC's SSD is uncluttered and pretty fresh.
So, take home message is that the SSD that was not working with VP17 has something on it causing a conflict. My suspicion is that it is either earlier versions of Vegas (10, 13, 14) or one or more of the accompanying (old) plugins.
This Core i5 machine is working at an acceptable speed with 4k footage when using proxies. 😀
Thanks for listening and helping! Maybe this info will help somebody else down the road.