Repeatable crashes

Aram wrote on 7/15/2012, 3:50 PM

Hi everyone again. I keep having the same old crashes that I had before when using FX. The crash happens easily 4 out of 5 times when I close the window with the FX UI. Since vegas does not report those, here is what I could get from Windows.

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: vegas110.exe
Problem Signature 02: 11.0.0.683
Problem Signature 03: 4f967c0e
Problem Signature 04: Sony.MediaSoftware.VideoEffectsUI
Problem Signature 05: 11.0.0.683
Problem Signature 06: 4f967ba2
Problem Signature 07: 574
Problem Signature 08: d
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 6153

My system information can be seen and I have both vegas and my GPU graphics up to date (but vegas crashes when trying to render certain codecs using the GPU, not using it is much more stable for me).

Comments

rmack350 wrote on 7/15/2012, 6:10 PM

Do you have a Wacom tablet attached to your computer? If so, remove it. Or, try running Vegas in compatibility mode. It should be enough to set Vegas back to run as Windows 7 compatible (if you've installed Win7 SP1) or you can step it back all the way to one of the Windows Vista compatibility modes.

Or...it could be something else.

Rob

Grazie wrote on 7/15/2012, 10:59 PM

What are your Project settings?

What source Media formats are you using?

What "certain" CODECS?

What render templates?

Does your Graphics card sit squarely with SCS: " • Quadro GPUs: Quadro 600 or higher (or Quadro FX 1700 or higher with driver 285.62 or later)." ? Yours is the Quadro 1000.

I believe it aint the FX that is the problem ( oh yeah, what FX does it choke on?), otherwise we would be hearing/reading more instances of this or that FX crashing Vegas. Are you using NewBlue anything?

Cheers

Grazie

Aram wrote on 7/16/2012, 10:55 AM

I do have a wacom tablet, but it is never attached when I am editing. I will try the compatibility mode hack, it sounds like a good idea. Thanks.

Aram wrote on 7/16/2012, 11:18 AM

720p, 24fps, defaults otherwise except for the "pixel format" (which I am dubious about the English translation, since this is the Spanish locale) which I have at "32 bit floating point (video levels)". Best render quality, gausian blur, no interlacing.

Audio is sterro, 0 buses (I have no idea of what that means), 48Khz, 16bit, good "sampling quality".

I am using Motion Jpeg as source.

I don't remember the codecs and do not really want to start trying to find out since I am not that bothered by the rendering crashes. It is the FX one that drives me crazy.

It chokes on a lot of FX, right now I can think of levels, colour correction, colour curve, gausian blur, brightness and contrast, but I can assure you there are more. Basically, if I have used an effect in the past, there is a very, very, very high chance the vegas crashed on me. It used to crash more, though, so that's something.

My card is the Quadro 1000M, the driver is 276.58. which is the latest sactioned by lenovo. In the past I have installed drivers directly from NVIDIA which are some versions ahead (301.42 right now), but those caused system wide issues in the past, so I went back to using the lenovo sanctioned ones for the moment.

I honestly don't know if my card "sits squarely with SCS", it is Quadro 1000M, I guess that makes it higher than a Quadro 600.

I think the issue is probably not related to drivers. It is a System.NullReferenceException. I have basic programming skills, if my memory does not betray me, that means that the program was expecting go get a value from somewhere, but when it checked for the variable that was supposed to contain it, the variable was empty.

I have not used any of the NewBlue plug ins that I have installed, but I do have the starter pack and the titler pro installed.

Let me know if there is any other question that I can answer that may help us nail this down.

Aram wrote on 7/16/2012, 11:29 AM

I have just found this on notebookcheck.net.

Compared to the 5010M, the 1000M does not support ECC memory and DP floating point calculations.

Are the floating points in the pixel format DP (double precision)? I don't think so, but that could be it. Still, I do not remember, I could check tonight, but I think I got just as many crashes when using 8bit.

ForumAdmin wrote on 7/16/2012, 2:38 PM

Aram said: "I do have a wacom tablet, but it is never attached when I am editing."

Most likely, disconnecting the tablet will not resolve the issue, because the crash is due to a conflict with the driver. I would recommend disabling the driver. You can do this through Device Manager. (Locate the driver, right-click, choose Disable.)

Hope this helps,
Paddy
SCS

TheRhino wrote on 7/16/2012, 3:29 PM

We have some proprietary hardware & drivers that do not always play nicely with other programs. To eliminate problems we have setup all of our workstations to multi-boot between (3) SSDs. When we need to use proprietary hardware we boot to that SSD and when we need Vegas stability we boot to another SSD. The last SSD has a combination of programs that work well together, including Vegas 9e, 10e, CS5.5 and Office 2010. Right now that is the one we are using since V11 renders slower without a powerful GPU & still has stability issues...

Aram wrote on 7/17/2012, 8:12 AM

The whole tablet issue is completely new to me. I don't understand how the driver should affect it, but I will definitely give it a go soon.

Thanks for your suggestions.

rmack350 wrote on 7/17/2012, 10:41 AM

The whole tablet issue is completely new to me. I don't understand how the driver should affect it, but I will definitely give it a go soon.

The issue with FX dialogs crashing and the link to Wacom drivers has been discussed quite a bit here but no one can be expected to read every single post.

I've had other programs affected by pointer drivers. Even Macromedia Dreamweaver had settings to turn of mouse hardware acceleration.

As for Vegas, the only change to the way it handles pointers (that I know of) is that it started playing nice with my MS Wireless Natural Laser Mouse 6000, which is a "High Definition" mouse. I'm not pointing a finger at that but it's an example of Vegas having problems with very specific pointers.

I should point out here that the problem I was experiencing with Wacom drivers was very specific to OFX effects dialog windows. I didn't experience the same crashing if I was adjusting a DirectX effect. Oh, and I was never actually using my Wacom stylus when Vegas crashed, it was just installed and plugged in.

I think there are probably a number of quirky things going on. Windows does a bit of geometry juggling with themed windows. The window's underlying geometry may have borders while the theme may be removing the border. Windows then compensates for that lack of windowborder (I had read an account recently about how Windows sizes a window to Full Screen when the border is hidden by a theme, for example). Also, I've noticed that some programs start with Windows Classic tools in the top right corner before repainting them as Win7 themed buttons (like the big red X button).

Applications have to listen to information coming from the mouse in order to make button clicks, window focus, and rollover actions happen. If you've got Windows fudging geometry to make themes work, and Wacom fudging geometry to make their stylus work, and some other mouse driver fudging their geometry, and an OFX filter dialog fudging it's geometry...that's a recipe for a gooey mess.

Compatibility mode is yet another fudge factor. It's there to allow other people's fudge factors to continue to work.

Rob

Aram wrote on 7/17/2012, 11:57 AM

Interesting. I actually work on a lenovo w520 and use the trackpoint, instead of the trackpad or a mouse. I will try disabling the wacom under processes in the task manager, but now I fear that it could be the trackpoint or the disabled trackpad that are messing with the windows.

And sorry about bringing up the same issue again. Before posting, I did do a search for FX UI crash and a few other things that I thought could bring up relevant threads, but found nothing.

rmack350 wrote on 7/17/2012, 2:15 PM

I think that it probably should be brought up over and over. As I said, people can't read every single post, or they're gone for a month, or whatever.

I'd stick with disabling the Wacom tablet because that's the only pointing device *known* to cause a problem. And remember, actually disable or uninstall the driver. Killing it's process won't stop it from coming back on the next boot.

Setting Vegas to Compatibility Mode seems to be a workaround for the Wacom Driver problem, so that's Option B.

mudsmith wrote on 7/18/2012, 10:59 AM

I would add that simply setting Vegas to Win7 compatibility mode (which seems counterintuitive, since you are running in Win 7 already) has fixed a whole slew of crashes for folks, notably the NB Titler crash and other FX crashes for me and several others.

Since there does not seem to be a downside to using this fix, perhaps it should be considered SOP.