Vegas Pro 11.0.701 64-bit Will Not Start On PC

Jamil wrote on 12/24/2013, 9:13 AM

I just got a new Dell Precision T7600 workstation. I am now migrating all licensed software to my new computer. I have installed Vegas Pro 11.0.701 64-bit onto this machine. However, I get a problem report pop-up with the Vegas splash screen still open each time I start the installed application. After I enter text stating all I was trying to do was start it, I get referred to an update download link to update the same level of software I already have installed.

When I click show problem details in the problem reporter, this is what I see:

Extra Information
File: C:\Users\Jamil\AppData\Local\Sony\Vegas Pro\11.0\gpu_video_x64.log
File: C:\Users\Jamil\AppData\Local\Sony\Vegas Pro\11.0\dx_video_grovel_x64.log
File: C:\Users\Jamil\AppData\Local\Sony\Vegas Pro\11.0\svfx_video_grovel_x64.log
File: C:\Users\Jamil\AppData\Local\Sony\Vegas Pro\11.0\dx_grovel_x64.log
File: C:\Users\Jamil\AppData\Local\Sony\Vegas Pro\11.0\vst_grovel.log

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 701) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module:
Fault Address: 0x000000001420FD70
Fault Offset: 0x000000001420FD70

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 11.0\vegas110.exe
Process Version: Version 11.0 (Build 701) 64-bit
Process Description: Vegas Pro

Why won't Vegas Pro run on my computer?

Thanks.

Back to post

Comments

Jamil wrote on 12/25/2013, 2:24 PM

I may do this later, but I am not going to do it right now. I have an idea of what the issue is. I think Vegas Pro simply cannot handle my hardware. I have two CPUs with too many hyper threaded cores that it is blowing up on.

To test this, I am installing Windows 7 x64 under VMware using a virtual machine with only an 8 core CPU. If Vegas Pro works on this VM, the issue is most likely what I had suspected. The logs I posted are confirming my theory. I will test it on my VM, and my current installed OS will not be changed.

pwppch wrote on 12/25/2013, 4:43 PM

I use a dell precision workstation and other Xeon based machines with 6 to 12 cores, and Vegas is more than capable of dealing with it. I develop our apps on these boxes with out issue.

While anything is possible, I doubt it is the number of cores.

What is interesting about the crash report is that it does not indicate the module that is causing the fault.

Peter

Jamil wrote on 12/25/2013, 5:56 PM

Vegas Pro 11.0.701 64-bit worked on my VM machine running under VMware. I am running it in trial mode, since I did not wish to enter my license key. This is a VM with one CPU having eight cores.

I then shut down the VM wanting to simulate the problem I am running into. That is two CPUs with eight hyper-threaded cores. In VMware, this would be 32 cores (that simulate 16 hyper threaded cores to Windows). Unfortunately, VMware has a CPU limit of 16 cores, which is half of what I am running. I cannot create the hardware image in VMware that I actually run, so I cannot determine for certainty that the issue is Windows showing 32 cores. I think that is the problem considering this is a new machine with nothing installed on it yet.

If you have a new Dell Precision that has dual CPUs of this type, I'd be interested in knowing if it works. 12 or 6 cores is not close enough to what I have.

Jamil wrote on 12/25/2013, 7:36 PM

I tried a few more things that did not resolve the issue:

1) I disabled hyper-threading in the BIOS thinking the number of cores Windows shows may have something to do with it. 16 cores then showed matching my VM. Problem remained.
2) Uninstalled two Dell utilities (Dell Data Protection & Protected Workspace) followed by rebooting. Problem remained.

Jamil wrote on 12/26/2013, 11:29 AM

I am now downloading the trial of Adobe Premier Pro CS5 to install on my workstation. I could not find a trial of CS6 to download, so CS5 will have to do for now. After my download is done, I will install and attempt to execute to see if it starts.

Note that the only software I am currently having issues with is Vegas Pro 11 and 12.

Jamil wrote on 12/26/2013, 12:42 PM

Good news (for me anyway)--

I did find a trial of Adobe Premiere Pro CS6. I have downloaded it (1.81GB download), installed it, and it executed with no issues whatsoever on my current Windows 7 installation. I am now running Adobe's update to install all latest updates to my trial.

This means I have something to work with if Vegas Pro never does start on my workstation. I have thirty days in my trial, and I will find out from Adobe if they offer competitive upgrade pricing, or can at least give me a discount considering I am a licensed user of two other CS6 products.

There is hope after all...

pwppch wrote on 12/26/2013, 5:48 PM

"Vegas Pro 11.0.701 64-bit worked on my VM machine running under VMware. "

I assume this is using a fresh windows install for the VM. This would indicate that there is something about the native Windows install on the machine that Vegas does not like.

You might try setting up a new boot partition for a fresh windows install and see how that works out.

Peter

Jamil wrote on 12/26/2013, 6:26 PM

Thanks, but not needed now. Yes -- it was a fresh Windows install under VMware, but I did install the VMware drivers too. The problem with VMware is that all hardware is not accessible (at least under VMware Workstation 10, since I don't have VMware drivers for everything). Running Vegas Pro under VMware isn't the solution for me.

Just as a warning to others, Vegas Pro has compatibility issues with recent Dell Precision workstations.

Jamil wrote on 12/26/2013, 6:36 PM

So I played around with Premiere Pro CS6 for a little today. I actually was a licensed user of a very old version (this was back in the Windows 3.1 days it was so long ago).

The software is intuitive enough to use that I had immediate success rendering a few videos. This software was created to take advantage of NVIDIA GPU hardware, which I do not have. However, my workstation has enough power and the software was designed to take advantage of it. I rendered a non-HD one hour and four minute video using standard AVI NTSC DV Widescreen codec in around 4 minutes and 6 seconds. This is with rendering set to highest quality. I have also found that a company developed rendering plugins for Premiere Pro allowing use of my GPU for hardware acceleration. Out of curiosity, I downloaded a trial of this to repeat this rendering test to see improvements in rendering time.

Here's what task manager showed while it was running with nothing else running:

http://www.file-shop.com/Images/Misc/premiere_pro_screenie.jpg

So far, so good. I will continue with my trial to thoroughly test this.

pwppch wrote on 12/27/2013, 11:43 AM

"Running Vegas Pro under VMware isn't the solution for me."

Did not mean to imply it was. My point was that since a fresh install of windows allowed it to work, then a fresh install of windows natively may solve your Dell issues.

My dell is less than 6 months old, and it support Vegas. I don't believe it is the problem. Personally the first thing i do with a new Dell box is to start from scratch with a fresh Windows install.

Up to you of course.

Peter

Steve Mann wrote on 12/27/2013, 1:21 PM

Sony won't fix your PC. Sony tech support is great at telling you how to accomplish a task in Vegas, but fixing your PC isn't in their scope. The first thing they will tell you is to reinstall Vegas.

An "unmanaged exception" is almost always a driver issue. Often using a 32bit driver in a 64bit system.

When starting a new PC with Vegas, first install Vegas then load and render a simple project. Then start adding other hardware and drivers, each time running your test project.

Jamil wrote on 12/27/2013, 1:53 PM

Sorry, but an unmanaged exception is buggy code.

pwppch wrote on 12/27/2013, 9:43 PM

"Sorry, but an unmanaged exception is buggy code."

I agree. Problem is with the information you provided there is no indication what caused the fault.

I still believe that a fresh install of Windows to a new bootable partition could help to determine the cause. Lots of moving parts on a stock Dell machine. I know what I had to go through to get a fresh install of different variants of Windows on my Dell Precision.

Would like to help solve this. I have not encountered problems with the Dell Precision I have, but I started from scratch with fresh Windows installs.

Again, your call on what to do.

Peter

DiDequ wrote on 12/28/2013, 2:47 AM

I agree with all those trying to explain a fresh install could solve the problem.

Did you try opening a command line window, running chkdsk c: /f
to repair the C drive ?

Concerning the number of cores, you can very simly set it to one, do your test and set it back to it's maximum: just run msconfig - my window capture is into french, but you will understand ! you need to click on the advanced button :

To go back to the maximum number, simply uncheck the box "Number of processors"

Jamil wrote on 12/28/2013, 9:19 AM

I do appreciate the attempts to help. I really do. I don't want to give the impression that I am being ungrateful. However, at this point, I feel this is all a waste of my time. Especially a reinstall of WIndows that takes way too long to do (I have installed this quite a few times under my old desktop and my current under VMware. It is slow).

I will be more than happy to share the configuration of my workstation so that development may investigate the fault on their own. Simply visit dell.com, select workstation followed by T7600. Click customize then select these options:

Dual CPU: Two Intel® Xeon® Processors E5-2680 (Eight Core, 2.7GHz, 20M, 8.0 GT/s, Turbo+)
Windows 7 Professional, SP1, No Media, 64-bit, English
No Energy Star
64GB, DDR3 RDIMM Memory, 1600MHz, ECC (8 x 8GB DIMMs)
(note that the video card is not available from Dell, so my sales guy gave me the cheapest at no charge that I then replaced with an AMD FirePro W9000)
No GPU computing (no Telsa)
PERC H310 for Dell Precision, SATA/SAS 6Gb/s, RAID 0/1/5/10 (8 ports)
6X Blu-ray Disc (BD-RE) Burner
1394A Controller Card,Dell Precision T3600, T5600 and T7600
19 in 1,Media Card Reader,Dell Precision T5600
Internal Speaker,Dell Precision T3600 and T7600

Windows currently runs at 2560x1440 resolution. I did try lower resolutions that did not prevent the problem. Again, it also happens with Windows running in safe mode where only standard VGA is used.