Unable to start Vegas Pro 12 in Windows 8.1

Sijon wrote on 10/17/2013, 1:20 PM
In attempting to run Vegas Pro 12 in Windows 8.1 I get the startup splash screen and it goes to the point where it says, "Creating Windows," and then goes no further. Vegas will not execute. I've tried compatibility modes, run as administrator, re-installing, all the usual but nothing works.

Anyone have any ideas? (SF 10 and 11 work OK)

Comments

CJB wrote on 10/17/2013, 2:42 PM
Hmmmm, guess I will wait till the dust settles before updating.... ;)
Larry M. Gibson wrote on 10/17/2013, 3:14 PM
I have been using Vegas Pro 10 on a laptop with Vista and on a desktop with XP. When I recently built a new computer with Windows 8, I had problems getting it to open. Finally had to remove an update of .net framework and block automatic windows updates. It worked for one more short project. Now it won't open again. I thought I would upgrade to Vegas 12 to help make it compatible with Windows 8, but now after reading your post, I'm not sure what to do. (I also tried all the "usual" things.)

P.S. What is SF 10 and 11? Sound Forge, maybe? If I get mine working again, I will post.
Sijon wrote on 10/17/2013, 4:22 PM
Yes, SF is Sound Forge.

I had trouble running SF 11 under Win 8 but Vegas ran fine. Now SF 11 works OK under Win 8.1 but Vegas won't execute. But I sure want it to - Win 8 was much faster than Win 7 and now Win 8.1 is noticeably faster than Win 8.
ddm wrote on 10/17/2013, 4:49 PM
Been running Vegas 12 on Win 8.1 with no problem on two different machines.
warriorking wrote on 10/17/2013, 5:10 PM
Running fine for me, I updated 2 computers this morning from windows 8 to 8.1.
I had to reinstall sound forge 11 however, other than that all are running smoothly..
Sijon wrote on 10/17/2013, 6:21 PM
After a long afternoon the problem is solved. It was a conflict between my Nvidia drivers and Displayport video drivers. I have installed an older Nvidia driver that works correctly in conjunction with my Displayport video drivers..

Vegas Pro 12 runs very nicely now under Windows 8.1 as do SF 10 and 11. Apologize for the false alarm but it definitely was not immediately apparent.
skeeter123 wrote on 10/17/2013, 9:06 PM
Sijon,

Glad you got it running!

What Nvidia driver did you end up using? (Building an 8.1 system this weekend..)

Cheers!

..
Sijon wrote on 10/20/2013, 4:19 PM
Hello Skeeter,

I have a GT660M GPU and ended up using Nvidia driver 327.23. I believe I somehow had the wrong driver earlier and it ran fine under Win 8 but definitely crashed with Win 8.1 when used in conjunction with Displayport driver 7.4.
jeh wrote on 11/13/2013, 10:25 PM
I am having a similar problem - Vegas 12 startup crashes within the "Creating windows" step. But the 327.23 driver did not help. I don't think I have a "displayport driver". I have sent in several crash reports with the "extended" log info. The last log file updated is gpu_video_x64.log and it does not show any sort of completion message at its end. HELP!
skeeter123 wrote on 11/13/2013, 10:53 PM
Rats. I don't have any stability issues with 8.1 (so far) and VP 12. I know that is no help...

Have you tried Sony Customer Service via phone yet?

Which video card do you have? CPU/Mobo? Is it the one in your sys info?

...sk
jeh wrote on 11/14/2013, 12:27 AM
Hey, thanks for the reply! Yes, the stuff in my sys info is correct. Except that there is another video card in the system as well, an nVidia 9800 GT. It drives monitors 2 and 3. The 560 is devoted to monitor 1.

I've tried nVidia drivers 331.65 (the latest), 327.23, and 314.07. I've tried Vegas build numbers 367 (from the product DVD), 563, and 726. I tried running in "compatibility mode" for Windows 7, and then for Vista. Nothing worked. I have not, of course, tried all possible combinations of the above.

The crash info shows a memory access violation (fault 0xC0000005) at fault address 0x00000000132CAD50. The sysinternals tool "VMmap", Process Explorer shows that this address is in a thread stack... it appears it is trying to execute code directly from a stack. There's no code at that location, just a lot of zeroes.

I've allowed Vegas to report the failure back to Sony after each trial with a significant change. (Has anyone actually got any responses from that?)

Thinking of trying to go back to Vegas 11 for a while, at least to get off of zero here. But Googling around the web shows a lot of similar-sounding startup problems in 11 as well.
skeeter123 wrote on 11/14/2013, 12:48 AM
Take out one of the video cards....give that a whirl....

No. Never got any sort of response from the reporting "tool". I don't think it is designed for that....

jeh wrote on 11/14/2013, 1:27 AM
I need my third screen, durnit! Also by connecting the two "secondary" screens to the weak old card, I am able to dedicate the more powerful GPU to my main screen. At least, that's my theory.

But I'll admit, it would be useful as a troubleshooting step. Everything I've read about these issues suggests it's a video driver issue.
skeeter123 wrote on 11/14/2013, 1:37 AM
Yeah. I hear ya....but.... for girbilshooting......I'd remove one....might save you some time in the long run....
jeh wrote on 11/14/2013, 2:06 AM
Removing the 9800GT didn't change anything. :(

I've sent in an email support request... we'll see what they say. Phone call costs $30 per incident.
skeeter123 wrote on 11/14/2013, 2:26 AM
grrrr...
jeh wrote on 11/14/2013, 2:55 AM
Now it gets weird... booting in "basevideo" mode (used to be called "VGA mode") didn't help either. Not that I would want to run in that mode, but it's often a useful test tool - you're running with a bare bones VGA video driver. But it didn't help this time. Exact same error footprint (except, of course, the address was not quite the same - this is due to the stack not being in the same place every time you run the app).

Since most of the problem reports I've found on this "crash after Vegas says 'Creating windows'" problem seem to focus on nVidia video drivers, this was quite a surprise.

I do have an ATI card I was going to try, but now I don't think I'll bother. I'm not up for any more gyrations tonight, anyway.
jeh wrote on 11/14/2013, 9:58 PM
I believe I have found the answer. The debugger log showed that the address with no code in it had once belonged to a DLL that's part of J. River Media Center. Removing JRMC from the machine has allowed VP12 to start correctly. I then reinstalled JRMC, and VP12 *still* starts correctly. It appears that if JRMC is on the machine when VP is first installed, the problem occurs. If not, then VP works, and VP12 still works after subsequent installation of JRMC.

I've added my debug log to the support request form. I'm also going to post a note on the JRMC forums. I hope these two companies can get together and fix this problem.
Woodenmike wrote on 12/3/2013, 12:19 PM
Anybody else using Win 8.1 with Vegas? going to start a new build soon and thinking about it...
ddm wrote on 12/3/2013, 6:46 PM
I am. I have it on 3 machines and I have no problems with Vegas on any of them. I did have some issues getting optimal GPU performance from my Nvidia 570 card, but now, with the latest Nvidia driver I get almost identical GPU preview performance as when I boot into Windows 7 (on the same machine) and use the old, preferred Nvidia driver.
rob99 wrote on 2/23/2014, 9:09 PM
Unbelievable! Thank you sooo much for saving me any more headaches. I'd looked all over the internet - removed/reinstalled ATI Catalysts & Drivers; tried disabling video drivers completely - nothing worked. Vegas Pro 12 just crashed immediately at the 'creating windows' point on the splash startup.

This was a fresh reinstall onto a very fresh replacement hard drive and I had happened to have re-installed JRiver Media Center 19 before Vegas Pro 12.

Followed your instructions as above and in a matter of seconds, both are now working fine and dandy, thank you :D

(I'm running Windows 7 btw)
Steve Mann wrote on 2/24/2014, 7:43 AM
"No. Never got any sort of response from the reporting "tool". I don't think it is designed for that..."

It's an aggregate collection of data.
mattchamlee wrote on 3/23/2014, 7:32 PM
JRMC was the issue for me as well. Many hours of researching this and trying many multiple solutions for both Movie Studio Platinum 12 and 13 did not help. I uninstalled JRMC and MSP 13 started without issue.

For the record I'm running Windows 7 64-bit SP1.
Snarglefarg wrote on 5/13/2015, 12:46 AM
Wow. I never would have put that together. In my case, I was using J.River Media Center 20, Sony Vegas 12 and Windows 7.

Once I uninstalled Media Center 20, I was able to run Vegas 12.

My troubleshooting had me install Vegas 9, which also crashed when Creating Windows. Oddly enough, the demo of Vegas 13 worked just fine.