Vegas Pro 15 Has Stopped Working. Constant crashing.

JoeAustin wrote on 4/8/2018, 9:20 AM

I was having crashing issues on the previous version of Vegas Pro 15 (311 I think?) and hoped the upgrade to 321 would fix the issue. Important to note that the crash will occur without any project loaded, and nothing on the timeline.

Tried the usual things
Disable GPU acceleration
Disable S04 codec
Disable multi core rendering

Below is the crash report. Any help on this would be much appreciated. It's unusable in the present state.


 

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 15.0 (Build 321)

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 15.0\vegas150.exe
   Process Version:     Version 15.0 (Build 321)
   Process Description: VEGAS Pro
   Process Image Date:  2018-03-05 (Mon Mar 05) 23:00:04

 

Comments

ritsmer wrote on 4/8/2018, 10:39 AM

I have had that error more than hundred times: Just start V15, do not open a project or anything - and then - after a short while left totally untouched - "Vegas stops working".

Also if I load a project and try to get some work done - after a short while: "Vegas stopped working"

Sometimes Vegas 15 runs for many hours - but this morning Vegas 15 was insane - stopped working more than 10 times within a couple of hours.

I have done ALL the things described (A HUGE thank you to Nick Hope) - like DRAM to 0 and, and, and - like you have tried too - but nothing helps. (actually I do not understand why we have to do the strangest things like setting DRAM to 0, disable the new and "faster" so4compoundplug, disable GPU this and that, keep the breath etc. etc. to try to keep Vegas from crashing :) )

Today I simply could not stand this crazy crashing any more and went back to V13 build 543. Made the quicktime things (QT 7.7.9) to make Vegas 13 accept my mp4 and avi files - re-installed Newblue and Boris FX'es - re-entered my current project (not much done because of all the crashes) - and right now I have been editing about 6 hours without a crash. What a relief.

matthias-krutz wrote on 4/8/2018, 11:22 AM

Was Vegas already reset to factory settings?

Another thought is worth a try.
If in the Explorer of Vegas the thumbnails are turned on, I would switch to list or details. These thumbnails are generated at start of Vegas and in the background. If a folder with many files is selected, a lot of memory will be allocated and Vegas will be slowed down for a while. The memory is not released when switching to another folder. In sum come quickly a few GB together.

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

JoeAustin wrote on 4/8/2018, 2:32 PM

Today I simply could not stand this crazy crashing any more and went back to V13 build 543. Made the quicktime things (QT 7.7.9) to make Vegas 13 accept my mp4 and avi files - re-installed Newblue and Boris FX'es - re-entered my current project (not much done because of all the crashes) - and right now I have been editing about 6 hours without a crash. What a relief.

I've done the same. Back to 13 to get this project finished. Left it installed due to the various troubles with 15.

JoeAustin wrote on 4/8/2018, 2:37 PM

Was Vegas already reset to factory settings?

Yep. Tried that too. I understand the point about thumbnails, but this happens with nothing loaded, and nothing browsed or in project media. The only thing I've not tried is reinstalling, but that is next.

ritsmer wrote on 4/8/2018, 3:06 PM

Was Vegas already reset to factory settings?

As JoeAustin has done it, that is one of the many, many things tried here too - but it did not help.

And yes: I can confirm that Vegas 15 can crash without any project loaded, without even a single track inserted on the TL.

matthias-krutz wrote on 4/8/2018, 3:31 PM

but this happens with nothing loaded, and nothing browsed or in project media.

I also restarted Vegas without a project, and nothing browsed.

I noticed that the creation of thumbnails from a folder with 1500 JPGs (time-laps) 3.5GB of additional memory needs! Depending on the CPU usage, it may take minutes for the process to complete. The files themselves occupy only 2.2GB.

The trial would be easy to exclude the suspicious creation of thumbnails.

 

 

Desktop: Ryzen R7 2700, RAM 32 GB, X470 Aorus Ultra Gaming, Radeon RX 5700 8GB, Win10 2004

Laptop: T420, W10, i5-2520M 4GB, SSD, HD Graphics 3000

VEGAS Pro 14-18, Movie Studio 12 Platinum, Vegasaur, HOS, HitfilmPro

ritsmer wrote on 4/9/2018, 1:21 AM

A hint if anybody cares: try to search for "stopped working" in this forum.

The random "Vegas stopped working" seem to have started with Vegas 14 build 211. See this thread

https://www.vegascreativesoftware.info/us/forum/vegas-build-211-crashes-all-by-itself--105174/#ca678272

That is why I changed all the way back to editing in V13 - and - believe it or not - have not seen one single "Vegas stopped working" for many happy editing hours now.

So there is a strong probability that "something" was introduced into the Vegas code between build 201 and 211 and which causes the heavy increase in the "Vegas stopped working" crashes.

Just my 2 cents: When Vegas 13 just runs perfectly on an machine - then why should we try to rebuild our machines, reinstall Vegas, roll back GPU drivers, set DynRAM to 0, switch off GPU support and many other things just to make Vegas 14 after 211 and Vegas 15 run without crashing ?

NickHope wrote on 4/9/2018, 3:18 AM

@JoeAustin @ritsmer Could you both please let us know what OS, CPU & GPU(s) your machines have so we can look for common aspects that your machines have and mine doesn't, since VP15 build 321 doesn't crash for me. These are my specs:

  • OS: Windows 10 version 1511 (Old version. Windows Update is off)
  • CPU: Intel i7-5960X
  • GPU: AMD Radeon HD6970 (Catalyst driver 15.7.1)
  • No Intel graphics

In particular, do you have Intel graphics as well as discrete NVIDA/AMD graphics? It seems there's currently an issue with having both enabled, and that disabling Intel graphics in the BIOS can help stability in some cases.

Peter_P wrote on 4/9/2018, 4:02 AM

I would like to add my system specs, where I also do not see this problem to happen:

  • Vp15 B321
  • OS: Windows 10 version 1709
  • i7-8700k with 32GB RAM
  • AMD R7 250 – driver 22.19.677.257
  • Intel UHD 630 – driver 22.20.16.4758

GPU acceleration for video set to AMD, QSV enabled in BIOS ans used for (HEVC) rendering.

UHD-Monitor attached to system-board (Intel GPU) via DP 1.2.

OldSmoke wrote on 4/9/2018, 5:09 AM

@JoeAustin @ritsmer Could you both please let us know what OS, CPU & GPU(s) your machines have so we can look for common aspects that your machines have and mine doesn't, since VP15 build 321 doesn't crash for me. These are my specs:

  • OS: Windows 10 version 1511 (Old version. Windows Update is off)
  • CPU: Intel i7-5960X
  • GPU: AMD Radeon HD6970 (Catalyst driver 15.7.1)
  • No Intel graphics

In particular, do you have Intel graphics as well as discrete NVIDA/AMD graphics? It seems there's currently an issue with having both enabled, and that disabling Intel graphics in the BIOS can help stability in some cases.

I would also ask where the monitor or monitors are connected and which connection method is used; it seems to make a difference too.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

ritsmer wrote on 4/9/2018, 5:19 AM

@Nick Hope

Vegas Pro 15 321.

Windows 10 Pro 1709 build 16299.309 (latest). Windows update ON.

i7-4930 not OC'ed Liquid cooled with 16 GB RAM

AMD RX 480 - driver 18.3.2

GPU accell. set to OFF.

No Intel graphic in CPU

Machine not used for gaming - so no games installed.

Edit: Monitor 1: 3840x2160 HDMI Monitor 2: 2560x1440 DVI

Edit2: Found one more user with a crashing "empty" Vegas:

https://www.vegascreativesoftware.info/us/forum/need-help-vegas-pro-14-has-stopped-working-with-unknow-reason--110303/

From his picture it seems to be Vegas 14 - but I also saw this crash the first time in Vegas 14 211.

Edit3: If anybody could provide a link I am ready to try Nick's driver 15.7.1 (have searched, but no luck so far)

JoeAustin wrote on 4/9/2018, 7:25 AM

Here's mine:

 

OS: Windows 10 Pro Version    10.0.16299 Build 16299

CPU: Intel 4790K

GPU: AMD Radeon R9 380 Driver 17.12.1

Intel Graphics Enabled

 

This is the first I've heard that having the on board graphics enabled is a problem. I will disabled it just to see what happens, but this would be a total bummer if so, as disabling it would kill QSV support.

JoeAustin wrote on 4/9/2018, 8:14 AM

@JoeAustin @ritsmer Could you both please let us know what OS, CPU & GPU(s) your machines have so we can look for common aspects that your machines have and mine doesn't, since VP15 build 321 doesn't crash for me. These are my specs:

  • OS: Windows 10 version 1511 (Old version. Windows Update is off)
  • CPU: Intel i7-5960X
  • GPU: AMD Radeon HD6970 (Catalyst driver 15.7.1)
  • No Intel graphics

In particular, do you have Intel graphics as well as discrete NVIDA/AMD graphics? It seems there's currently an issue with having both enabled, and that disabling Intel graphics in the BIOS can help stability in some cases.

I would also ask where the monitor or monitors are connected and which connection method is used; it seems to make a difference too.

Two primary monitors in my case are connected to the R9 380. One to the HDMI, and one to a DVI port. A third monitor is connected to the HDMI on the system board via Intel Graphics. One issue I do know, is that trying to use that third monitor as a preview will cause an immediate crash on VP 15, but works fine on 13. so the preview is on the second monitor via the Radeon.

 

ritsmer wrote on 4/9/2018, 8:38 AM

Thanks to an old Nick Hope post I found a link to the 15.7.1 driver and downloaded it (whql-win10-catalyst-15.7.1-oct30.exe)

Uninstalled the RX480 card in the Device Manager (and its software), then rebooted, then installed the driver and rebooted again.

Now Windows reports the driver version as: 23.20.15007.1005.

Now (03:30 PM) I have started 2 x Vegas 15 with each a small project - plus an empty version - and hope for the best....

Will be back with news when available...

OldSmoke wrote on 4/9/2018, 9:19 AM

Here is something I believe to denver from the past with R290 cards. If I remember it correctly, the card has a low power state from which it was very difficult to get “out” into the next higher power level. That very low power state caused issues with games when left running in the back ground and switching to another program in Windows and back to Vegas would drop the preview speed to a few fps, the card didn’t wake up anymore.

Maybe this is no longer valid with newer cards and rivers although a symptom like Vegas crashing when left alone sounds “similar”?

Note that the power state of the GPU is independent of the Windows power state.

 

Edit: it's actual called Ultra Low Power State and here is how it can be disabled.

Last changed by OldSmoke on 4/9/2018, 9:25 AM, changed a total of 3 times.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

ritsmer wrote on 4/9/2018, 9:32 AM

Could be an idea - but I have seen V15 stop working while I was writing some e-mails - and think that the activity from displaying the e-mail typed letters should be enough for the Gr.card not to switch to ULPS ?

OldSmoke wrote on 4/9/2018, 9:43 AM

Could be an idea - but I have seen V15 stop working while I was writing some e-mails - and think that the activity from displaying the e-mail typed letters should be enough for the Gr.card not to switch to ULPS ?

Well, it's disabled on my system, I just checked my registry and I don't have issues. It's also simple to do, takes at most 10min. including a restart.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

ritsmer wrote on 4/9/2018, 10:57 AM

Well, it's disabled on my system, I just checked my registry and I don't have issues. It's also simple to do, takes at most 10min. including a restart.

Thank you - and right: whatever improves stability is worth trying.

Found a description of how-to here:

https://community.amd.com/thread/176003

and have disabled the ULPS. Thereafter I rebooted the machine - now let us see...

OldSmoke wrote on 4/9/2018, 11:07 AM

Found a description of how-to here:

https://community.amd.com/thread/176003

Yes, that is the same thread I provided a link as well. Let's keep our fingers crossed and thank you for trying it.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

NickHope wrote on 4/10/2018, 1:50 AM

Thanks to an old Nick Hope post I found a link to the 15.7.1 driver and downloaded it (whql-win10-catalyst-15.7.1-oct30.exe)

Uninstalled the RX480 card in the Device Manager (and its software), then rebooted, then installed the driver and rebooted again.

Now Windows reports the driver version as: 23.20.15007.1005.

The filename for my driver was amd-catalyst-15.7.1-win10-64bit.exe (at least I *think* that's what I installed way back then) and Windows reports the driver version as 15.201.1151.1008. The fact that Windows lists such a later number for yours makes me wonder if 15.7.1 hasn't actually been installed, or has somehow been immediately replaced again by a later driver??

This is the "Information > Software" page from my AMD Catalyst Control Center:

From this index of old AMD drivers for Windows 10 64-bit there is a version that is also "15.7.1" but the longer-version number is slightly different.

Anyway that seems a bit irrelevant since I don't think that version would support your cards like the RX480 and Joe's R9 380. The oldest listing I can see in that index that states support for your cards is the 16.7.3 driver. If you want to try a much older driver then that would seem like a reasonable bet.

ritsmer wrote on 4/10/2018, 2:42 AM

Yes - I also frowned at the numbers too - but chose to give it a shot now that the installer exe file had 15.7.1 in its name and because 15.7.1 was mentioned at several places as a good openCL driver (if I understood it correctly)

AMD Radeon settings on my PC reports:

Maybe I have not done it correctly - but the results so far are that of the 3 instances of Vegas 15 I launched after the driver install and the reboot - 1 stopped working after a couple of hours (left untouched). I do not blame Vegas for that one because it was a project with a couple of 1 and 2 GB files from a DJI drone - which are known to be - say "tricky". The 2 other Vegas instances including 1 totally empty did not crash during these hours - which was better than I was used to.

Then I got the post from OldSmoke and disabled the ULPS (Ultra Low Power State of the Radeon graphics card). Rebooted the machine and started the same 3 Vegas instances again.

That was yesterday evening here - and since I have touched them a little from time to time - and the machine even went to "sleep" sometime in the night - BUT: this morning they are all 3 still running well and responsive.

I leave these 3 Vegas instances running - and work with some other things (including some editing in other Vegas instances)

If everything survives this day I think we have found something good.

Will report back in the evening.

 

NickHope wrote on 4/10/2018, 3:21 AM

@ritsmer Looking at the numbers in your screenshot, I think you've got driver 17.2.2. Click it in this list, then click "release notes". Could imply that things went pear-shaped with driver 18.X.X. How long have you and @JoeAustin had the crashing problems?

ritsmer wrote on 4/10/2018, 5:02 AM

Good idea to compare the dates of a new GPU driver release to the dates of the Vegas stopped occurrence.

My first occurrence was around January 6. 2017 as reported here:

https://www.vegascreativesoftware.info/us/forum/vegas-build-211-crashes-all-by-itself--105174/

and was as described there (AFIK) very much a result of going from Vegas 14 build 201 to build 211.

In that thread see that Paul-priestley had precisely the same Vegas stopped experience after changing from 201 to 211 - but xberk did not have the problems - but he has a NVIDIA GPU.

The first Radeon 18.x.x driver appeared January 18. 2018

The first Radeon Software Crimson ReLive driver ver 17.1.1 appeared January 17. 2017 - so the "Vegas stopped" with Vegas 14 build 211 was some days before that - but more urgent: with a driver that worked well with Vegas 14 build 201

PS: My 3 Vegas instances are still running. I start to think of something changed in V14 build 211 in connection with AMD ULPS ??

JoeAustin wrote on 4/11/2018, 7:35 AM

@ritsmer Looking at the numbers in your screenshot, I think you've got driver 17.2.2. Click it in this list, then click "release notes". Could imply that things went pear-shaped with driver 18.X.X. How long have you and @JoeAustin had the crashing problems?

I can't say for sure exactly when this started, but it's been weeks now.