urgent help please....

ushere wrote on 6/9/2012, 12:37 AM

so, just done a full reinstall on new ssd. all went well, vegas up and runing, then rebooted.

getting this at startup when 'creating screen'

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

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 683) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554\MSVCR90.dll
Fault Address: 0x000000007434E5C1
Fault Offset: 0x000000000001E5C1

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 11.0\vegas110.exe
Process Version: Version 11.0 (Build 683) 64-bit
Process Description: Vegas Pro
Process Image Date: 2012-04-27 (Fri Apr 27) 06:43:00

anyone have any idea?

if i reinstall vegas (it says i already have installed and to install first) will i lose all my setting up of plugins - this is a nightmare i don't need right now....

help please ;-(

Comments

Soniclight wrote on 6/9/2012, 1:10 AM

I can't help you on interpreting the messages, but one thing I do when I've run into install/uninstall nightmares is that I copy out folders like plugin ones that I've set up to my desktop so that I don't have to redo everything in those. Then I just paste the contents back into their after-reinstall "virgin" folder. Save time and frustration.

Soniclight wrote on 6/9/2012, 1:25 AM

Something occurred to me as I re-read the error messages you got, this line - specifically the .dll:

Fault Module: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554\MSVCR90.dll

Looks like that file is missing or corrupted -- I've run into something similar years ago though not sure with what application.
As per one description of this file:

In other words, it seems to me that you are having a Visual Studio boo-boo, not a Vegas one.

Back when I had XP, such things could be fixed with a an sfc/ scannow and the installation disk. I have Win7 and it doesn't act the same anymore -- I don't know if it stores local backups of such files or not.

Hopefully someone else here can help you replace that .dll. And/or Google it--just be wary of scan/registry fixing software scams. Perhaps just finding and re-installing the right version of Microsoft Visual Studio will do the trick.

~ Philip

ushere wrote on 6/9/2012, 2:02 AM

thanks for that philip, appreciated, however i tries a reinstall of all the visual studio's various packages to no avail,

then a uninstall / reinstall of vegas. still the same error. i'm beginning to think it's time i gave up and moved over to cs6 - but over there i've got problems with my intesity card.

maybe start from scratch - as if i javen't got anything else to do!!!!

Red Prince wrote on 6/9/2012, 2:09 AM

That error indicates a memory access violation. That is, Vegas is trying to access memory that either does not exist or whose access is prohibited. In other words, Vegas is passing a bad pointer to msvcrt (which is not missing because the fault cannot happen in a missing DLL).

Soniclight wrote on 6/9/2012, 2:22 AM

....(which is not missing because the fault cannot happen in a missing DLL)

True, but it couldn't it still be not corrupt enough to be recognized - but too corrupted to work properly?

Soniclight wrote on 6/9/2012, 2:32 AM

Ushere,

If you've installed the right Visual Studio successfully, how about installing Vegas in an alternate folder location in Program Files -- not the default one fired up on install? May or may not change anything. Perhaps just grasping at straws here.

There's got to be a "Duh..." simple solution here (that's what usually happens with me after I've torn my hair out...)
It's just one freakin' .dll file, youknowhudamean? Like a gnat messin' with a grown tiger.
I hope you find a fix soon -- I know how this kind of stuff can drive one nuts.

ushere wrote on 6/10/2012, 5:28 AM

well red and philip,

thanks for your help.....

i finally (after 3 head-banging days) discovered on my third clean install that my 'latest' logitech g100 keyboard drivers somehow conflicted with my 'latest' wacom drivers. dropping the keyboard back to legacy seems to have stopped the rot.

i have reloaded cs6 and 11 and both appear to be relatively stable - i haven't done any heavy lifting as yet, but i start a three day shoot on wends that'll have hours of interviews (two camera) to test out reliability.

i just hate this sort of time wasting escapade, it does little for my nervous disposition and even less for my sleeping pattern.

meanwhile i do have one problem, but that's in ppro with my intesity card - it showing 4:3 instead of 16:9 and there's no drop down selection that i can see within ppro that'll let me change it.....

Soniclight wrote on 6/10/2012, 7:59 PM

ushere -

Glad to know it's somewhat panned out for you :) Hopefully someone can help you with your 4:3/16:9 issue -- I don't have that software, so I'm of no use to you.

I'm dealing with more or less regular daily crashes and at times have keyframes go invisible in some FX lanes that sometimes require an app or even system reboot. No point my indulging in more "what's happened to Vegas in the last couple of years?" rant for there are plenty of threads on this. It started happening once I went from a 32-bit XP and VP6 to VP8c - then to Win7 64-bit VP10e. The latter is when the boo-boos became chronic. That said...

Unlike many here, my livelihood does not depend on my video work hence Vegas -- it's just a serious hobby. So irritating, yes, but not a total meltdown matter. I can't afford another--especially more expensive--NLE, so I'm stuck in this relationship for better or worse :)

ushere wrote on 6/10/2012, 10:37 PM

well philip,

with a foot in both camps now, though not at all proficient with cs6 ppro yet, my feelings are still that vegas is (when it's working!), the fastest, simplest nle out there, and capable of holding its own apart from my one big gripe for many years, lack of edl functions. it's the best nle for a one man band.

if only we could get the stability of say ver 7 back again it would be a cert....

Soniclight wrote on 6/11/2012, 9:48 AM

"...my feelings are still that vegas is (when it's working!), the fastest, simplest nle out there."

Yes, she may not be as slick and sexy-looking and NLE-snobs tend to chuckle at her seemingly lower-class origins, but she's better at holistic editing than most. Now if she could just get rid of that nasty viral infection and stop coughing, I'd be more inclined to hug her more often... :)

chap wrote on 6/11/2012, 1:15 PM

What about using Vegas 10? Does that work? When you upgrade Vegas it doesn't uninstall the old one.

ushere wrote on 6/11/2012, 6:39 PM

the problem is they're are / were compelling reasons for upgrading (otherwise we'd never buy would we ;-)).

in my case i did have 10 installed along with 11, however, going to a 60gb ssd some time ago it was simply a case of not enough space for everything.

as it is i've only ever installed 64bit since 9, which worked quite reliably.

not to harp on about this as there's many like minded souls out there, it's more a case of having bought it - IT should work properly (well, after the first point release).