There's a common thread between the 3 of you somewhere that is different than our situation. Are you a fresh install of Vegas for the first time or an upgrade?

There's a common thread between the 3 of you somewhere that is different than our situation. Are you a fresh install of Vegas for the first time or an upgrade?

Not fresh….Upgraded to Vegas Pro from MovieStudio 16 Platinum and before MovieStudio 16 I had MovieStudio 13.

I am currently going through the whole uninstall / Clean registry again.... and will ensure plugins are not installed.... We do certainly appreciate everyones suggestions. I had no problems with MovieStudio 16 at all.

Ok, So this time (after deleting left over folders and registry clean etc) I downloaded and installed the Pro 17 Trial version (to try something different) Installed without DVD Architect and Lens flare plugin.

1. Loaded program once then exited without doing anything at all.

2. Loaded program second time again exiting without doing anything at all.

3. Attempted to load program 3rd time and it halted with KerelBase error. Now cant load at all and program stops with KernelBase error.Sent dumps to support again.

Hope someone at Vegas support is looking at this.....

> Hope someone at Vegas support is looking at this

If they cannot re-produce the issue they can do nothing. This is why you should help to find out what exactly causing the issue.

So yes, for me this is fresh install of Vegas on this machine. used Powerdirector for years on my old PC, then upgraded to this PC a couple of months ago.

I suspect that with the holiday sales that this is why there's an influx of new users. I'm pretty confident that after all the benchmark testing, there's no hardware issues on my end. What's interesting about this is that...

• I did a clean boot of the system and error still occurred, implying that the KernelBase error wasn't related to a conflict with another non-system application installed on my machine.
• I also did a repair install of windows (while keeping apps & data) and the error still occurred, implying that it wasn't windows.

What I can't prove but it still could be...

• Something related to fresh installs of Vegas and not an upgrade that's causing it (I don't have a machine to test this personally)
• Windows update (may Net Framework or security or etc etc...) that is in conflict with fresh installs of the software (i'm not technical enough to know how to test this)

Not sure if i'm making sense but I guess I could do another full reinstall of windows; but I really doubt it if a repair install didn't correct the issue, this would of either. I'm going to see what I can see in the event log if there's a pattern.

What keeps getting me is that, again, if I try to run it multiple times, it eventually gets through - which means it's not a hard conflict that's screwing this up. If it wasn't for the fact that I've done tons of testing - I would agree that it all points to a hardware error; but nothing is failing in these tests and no other application I've installed recently is having problems.

That being said, I do appreciate your guys help; also, I think it's safe to say defect reporting doesn't imply product bashing, it just means defect reporting. Thanks for being great users and still hoping this can work out, this product (told by my peers) is a great product that's significantly better than the ones I've used before.

Merry Christmas guys.

Hope someone at Vegas support is looking at this

Be patient, the team is aware of what is going on and is looking into finding a solution. Please be aware that process involves diagnosing the problem, and in the event it is indeed a Vegas related issue, coming up with a solution, and then properly testing that solution to make sure it solves the problem while not creating new ones. Therefore, the process will take some time to complete. In the mean time, we'll continue working here to see if we can't identify a common thread between you all that is causing this, that will help them to help you. It may turn out there is a workaround that doesn't require them to patch Vegas that will get you going.

Any info you can post that may be relevant, keep posting it here. We'll find that common link.

Common threads identified so far:

- All of you are using Vegas 17, build 387

- The issue isn't dependent on whether users were upgrading previous versions of Vegas or installing brand new versions.

- I've confirmed 3 of the 5 of you are using Nvidia GPUs (strat and ploan, can you please give us your specs @hadef-a and @Brett-Maloney?)

- I've confirmed 3 of the 5 of you are using Intel CPUs.

- I've confirmed 3 of the 5 of you are using Windows 10 64 bit (again, hadef-a and Brett, please give us this info).

- Re-installing Vegas or Windows does not seem to affect the issue.

- Always happens after launching the program once, and then closing it. Subsequent attempts will fail in a crash. Some users report success in getting it to open again after trying 7-8 times.

Just to reassure all, these sorts of errors are not uncommon. Eyes are on this and we'll solve the issue. This strikes me as some sort of conflict whereby a resource may be requested that is inaccessible thus precluding the continuing loading of whichever application is making that request.

As I said, not unheard of and not exclusive to Vegas. I suggest some research, working backwards from the error to see if some solutions already found would work in these cases. Understand that while the error may be common to the users in this thread, the cause of that error may be different to each based in part on the hardware/software configuration instances.

Doing some cursory searching, this thread my prove to have some value: https://www.sevenforums.com/bsod-help-support/246531-appcrash-kernelbase-dll-error.html

edit: the above thread involves Windows 7 so can be used as an analogue of what may be happening in Windows 10. Windows 7 has/was been around a long time so there's more of a history to draw upon that can be applied to the current iteration.

Secondly, as a suggestion, users could try disabling certain subsystems temporarily (individually), like audio or USB (unplug all USB devices as a matter of course while troubleshooting anyway) to see if something shakes loose.

Would just like to say, I'm having the same problem as well, so that's at least 5 of us. Only opens on a fresh install, and kernalbase.dll error after that. Not sure if mine will open after trying 7 or 8 times.

Mine is not a new purchase, I got it a few months back and it worked perfectly until it updated to 387. My old Vegas 15 still works for me. And if I rolled back to the old version of Vegas 17 before build 387, it works. It was the update that did it. I already attempted to reinstall windows while keeping apps and files. So it is not likely to be a windows corruption.

specs wise, lets see

intel i7 8700k
2 X Nvidia 1080Ti in SLI
win 10 pro 64 bits
 

That's now 3/5 of you using NVidia GPUs, intel chips, and windows 10. Still no specs from the other 2.

However, this is not a fresh install of Vegas, it is updating from a previous version, so we can rule that common link out.

Thanks for the encouragement everyone!

My PC Specs are -:

• Microsoft Surface Book 1 ;Intel i7, 16GB Ram; NVIDIA GPU graphics (performance base version of the surface book) Intel HD graphics GPU in the screen. - user selectable which one is used (I have tried both) ; Microsoft Surface Book Dock -> have tired with dock and without it

I have mentioned Windows version etc previously in this thread

Have been contacted by support and have provided support with more detailed sysinfo /log. Happy to help to try to resolve this issue.

Could the Windows version be the commonality? At least here everyone affected has the current Windows version Win 10 1909.

Could the Windows version be the commonality? At least here everyone affected has the current Windows version Win 10 1909.

But 2 of them stated more than once that they saw build 837 was installed.??????????

Another idea: if possible, you can try to disable Intel iGPU in BIOS and try with NVIDIA GPU.

The team has asked everyone experiencing this issue to make sure that you have submitted a tech support ticket at this link, it will make it easier for them to follow up with you and get more information to help hunt this bug down.

https://support2.magix.com/customer/en/vegas/form

DragonInwhite's data probably has the most clues given that he didn't get the KernelBase error prior to build 387 ..unless there was a windows update to throw into the mix during this period as well....

fifonnik , I'll try to disable intel GPU..

@Stratman Are you also game enough to uninstall VP then reinstall with Build 353. That would help identify whether build 387 is involved with the problem. If you don't have the build backed up you can get it from this post https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-update-2-build-353--117761/

Edit: Reading through the thread again I note 'DragoninWhite' has already done this and reported the previous build doesn't give the problem.

EricLNZ, happy to try build 353 and report back.. Question ..Will the trial key work with that?

@Stratman I don't know. In your first post you said you had purchased VP17 so why is a trial key involved? Use your purchased key.

To further update windows build, I'm on 1909, os build 18363.535. I know I had a recent windows update, but not exactly sure when. I did notice the problem with the next startup after I updated it. So, unless it updated on that startup as well, which might be possible. Thou I recall reverting and it worked again until I updated Vegas. So not likely the windows update for me. I open vegas up every 2 or 3 days to render videos but i been using it almost everything in this period. So the timeframe I noticed this was not too long.

i tried removing my usb harddrives and it worked once... that got my hope up. Unfortunately, I could not repeat that again, problem still persists. For now, just having to reinstall every time I have to use vegas 17. If problem dont get solved, I prob will have to revert to an older build.

Maybe I am lucky .
My laptop as well PC from signature don't accept the latest Windows updates ( nov + dec) so I'm still on W 1903 buildnr. 18362.387. Not one problem with all the Vegas versions with all latest upgrades. Maybe going back in Windows 10 is an option?

To check this, I installed the latest available Windows 10 version on another 5 years old desktop (now Windows 10 version 1909, build 18363.535) and installed the latest VPro 17 build and loaded my 2 latest projects. No problem with previewing and rendering, so my suggestion to go back in Windows is not for that install.

OK, here's a good one, this link will give you the previous build of Vegas Pro 17. See if this solves your issue until we can sort out what is causing the issue with build 387.

http://dl04.magix.net/2019/VEGASPro17/Update/VEGAS_Pro_17.0.0.353_DE-EN-FR-ES.exe