August 20, 2017

Fixing Vegas Pro 13 Initializing GPU-accelerated video processing Crash

Today I resolved a Sony Vegas Pro 13 startup crash problem which started happening after I upgrading my HP DV6-6190US Pavilion laptop’s operating system from WIndows 7 Home Premium x64 to Windows 10 Home x64.

The purpose of the Windows 10 install onto the older HP DV6 6190US system was to test Windows 10″s compatibility with my applications software before upgrading my main computer, a MacBook Pro A1398 15 inch system currently running Windows 8.1 under Bootcamp, to Windows 10.

Fortunately I was able to use the HP DV6 system as a test system before attempting the Windows 10 upgrade on my primary MacBook Pro system. And given the degree of problems I experienced just with getting one of my core video editing programs to work, that is Sony Vegas Pro 13, using a test system turned out to be a beneficial situation  given the problems I encounter getting it to run properly.

So let’s get the specifications out of the way for my test system as follows which has recently been upgraded from Windows 7 Home Premium to Windows 10. Its specifications are and what Vegas Pro 13 was installed onto are:

Windows 10 Home x64
HP DV6-6190US
2nd generation Intel Core i7-2630QM Processor 2.00GHz with Turbo Boost Technology up to 2.90 GHz
8GB DDR3 System Memory (2 DIMM)
Radeon HD 6770M
15.6″ diagonal Full High Definition HP Anti-glare LED Display (1920 x 1080)
750GB (7200RPM)
Digital Media Card Reader for Secure Digital and Multimedia cards
2 SuperSpeed USB 3.0
2 Universal Serial Bus (USB) 2.0

Just for clarification, Vegas Pro 13 build 290 was previously installed and working fine on the HP DV6-6190US system. However, I had to install a fresh basic copy of Windows 7 onto it during the Windows 10 upgrade process.

You see, the only way you get Windows 10 to install for free under Microsoft’s free upgrade scheme is for users of valid activated Windows 7  and 8.1 to perform an “upgrade” and not a “fresh” install of Windows 10 onto their systems.

Because I first tried installing Windows 10 onto the system as a fresh clean install, I later found out that the subsequent activation process would reject my old Windows 7 key.

This is probably where my Windows 10 install journey really started. That is, to simply get it installed and activated properly in the first place.

So even before encountering this recent Vegas Pro 13 startup crash problem, many hours have already been spent on this journey into Windows 10.

As a side note, and to Microsoft”s credit, with respect to the proper way to install Windows 10 onto your system in order to qualify for the free upgrade offer, both types of installs worked seamlessly.

The upgrade, which consequently saves all your applications, and the  fresh install procedures worked flawlessly and confidently.

To even get further off topic. The process of restoring my DV6-6190US system back to a fully functional, activated Windows 7 system was is itself another meticulous process. especially when HP (i.e., Hewlett Packard), did not include original install disks in the box when the system was first purchased. Don’t worry, you can still get the disks but of course for a price. I think HP tried reducing customer resentment by calling these disks they will now sell you a “Recovery Kit” instead of “original install disks which is really what they are.

One thing I will add when thinking about recovering your system back to Windows 7 so you can then try installing Windows 10 as an upgrade vs. a fresh install. Remember, you will also need all the special, and now mostly outdated device drivers for each piece of hardware on your system.

simply finding a clean copy of Windows 7 Home Premium x64 bit is not enough. As I do apply found out.

Again, HP will generously provide these drivers to you free of charge online. But you will have to go to their product page for your system and download them one by one. But here is the catch, how do you get the drivers installed onto a naked HP system with a generic copy of Windows 7 installed? Remember, without the hardware drivers, the disk drive, thumb drive, SD card port, and most severely, the network adapters, both of them, the wireless and the LAN ports all don’t work after simply installing a naked copy of Windows 7 onto a system.

Lets just say several hours were spent slicing and dicing ways to get the drivers installed without any working hardware except the CD-ROM drive. This is where creative trouble shooting kicks in. I have yet to have everything work as expected when performing a high level procedure on a system. And installing Windows 10, free or not, drew upon my many years of trouble shooting experience to get me this far.

I think Microsoft anticipated users would try to install Windows 10 as a fresh install vs. an upgrade install. Then, when those users saw the daunting task of having to reinstall their old Windows 7 operating system back onto there systems, without the original install disks and, without the patience, will power and determination to weather the re installation storm, paying the $112 or a Windows 10 Home key makes perfect sense. Especially when your system is directing you to the Microsoft store immediately upon notifying you your old key is not valid, and you need to buy a new one. This all the while your system is smiling at you with a fully functioning Windows 10 GUI.

if you ask me, Microsoft did the bean counting and banked on a high percent of people installing their advertised as “free upgrade” as a fresh install. And like any sane person would, just fork over the $112 and be done with it. It’s inconceivable anyone in there right mind would op to ensue the painstaking task to recover their system back to Windows 7 in order to then properly “upgrade” to Windows 10 all to save $112.

Unless your a techno geek like me.

I”m waiting for the class action lawsuit to be filled against Mucrosoft for unfair and deceptive trade practices with their “upgrade for free” arresting to entice users to own load and install Windows 10.

Time will tell.

Anyway, where were we?

Oh yea, why I had to reinstall Vegas Pro 13 in the first place. That is why. I had to reinstall it because I first wiped the system when installing Windows 10 as a fresh install.

The clean install was done primarily to avoid any remnants of the old Windows 7 operating system contaminating the “new and improved” Windows 10 system. Boy, that was a time consuming and educational experience.

Okay, back on track. Oh yea, the fix to the “Vegas Pro 13 crashing on startup after installing on Windows 10” problem.

The fix:

Good news is that I finally got Vegas Pro 13 build 453 to start in Windows 10 today after a few hours of tinkering and troubleshooting.

What DID NOT work:

1. Installing the latest build Sony Vegas Pro 13 build 453. This did not work. Note: I was previously running build 290;

2. Disabling the AMD catalyst manager from starting. Or actually uninstalling it completely; and

3. Going directly to the AMD website and downloading and installing the latest AMD catalyst manager driver for my Radeon 6770M graphic card.

What DID work:

1. Going into device manager and locating the graphics adapter driver, which was set, by the Windows 10 install procedure, to a Intel(R) HD Graphics Family adapter and driver designation, and completely uninstalling it. The thinking here was that the Intel(R) HD Graphics Family graphics adapter designation was preventing the actual AMD Radeon HD 6700M Series adapter and software from designated and installed respectively.

2. Upon restart, my video resolutions were not set to optimum setting, which is 1920 x 1080P, but what the basic driver was able to handle. What is important to note is that the AMD Radeon HD 6700M Series adapter was not showing in the Device Manager but with errors (i.e., icon had an “!” over it). This still was good news, because it confirmed the theory that the Intel(R) HD Graphics Family designation was some how preventing the actual Radeon adapter and software drivers from being recognized and designated.

Note: I think it’s important to note, that the Device Manager properties window reporting that the best driver was still in use while the Intel(R) HD Graphics Family driver was designated. I say this because this is a false negative. That is, a premature determination could be that the the graphics adapter settings are okay, and the problem must lie elsewhere (i.e., with the Song Vegas Pro 13 software). Nonetheless, in this case, the Intel(R) HD Graphics Family designation, confirmed by its removal, was causing Vegas Pro 13 to not start up..

This does not necessarily mean that Windows 10 is the culprit either. It did its best to determine the best graphics adapter settings suitable to run the machine, and not necessarily the Sony Vegas 13 software.

Now that the primary problem has been resolved, that is to get Vegas Pro 13 to complete its start up process, I now have to find out why, even when latest AMD catalyst manager and the AMD Radeon HD 6700M Series display adapter have been installed and designated, why the Device Manager is reporting an error (i.e., “Windows has stopped this device because it has reported problems. (Code 43) over the AMD Radeon HD 6700M Series‘ icon.

While in this error state, the system is relying on the Microsoft Basic Display Adapter to determine the resolution configuration which has a maximum depth of 1280 x 1024.

In summary, it turns out that the “Initializing GPU-accelerated video processing” crash experienced by Sony Vegas Pro 13 during start up problem is not necessarily a Sony Vegas Pro 13 problem.

If a finger has to be pointed, it should start to be pointed at AMD, or at AMD and Microsoft at the same time. Why? Because even after loading its latest driver software into Windows 10, it reports the error indicated above.

I would add, this troubleshooting can say that the problem does not reside in the either the Vegas 13 build 290, or build 453 software versions respectively either. Or at least with the test system this matter pertains to.

Now that Vegas Pro 13 has successfully started up under Windows 10, the next task is to figure out:

  1. Why the AMD Radeon HD 6700M Series graphics adapter, even with AMD’s latest driver software installed, is reporting an error in Windows’ Device Manager; and
  2. Ultimately to get the system to be able to configure itself to its maximum graphics adapter resolution.

 

For screen shots of this ordeal, see my post on CreativeCow below:

Vegas Pro 13 Initializing GPU-accelerated video processing CRASH RESOLVED! (Windows 10)

 

 

 

Comments

  1. Same issue than you. Found a quicker solution by disabling AMD graphic adapter in device manager…

Speak Your Mind

*