Vegas Pro 13 Crash because of NewBlueFX updates

GaryX1001 wrote on 5/30/2014, 4:14 PM

today i tried to render some footage i recorded today (flying my RC F-4 Phantom)
and after 128 frames the graphics driver went offline or stopped responding or something like that. at first i thought the new nvidia driver 337.88whql is the culprit, but wrong, reverted back to 335.23whql and same crash. it always happened when i used the newblue light blends. so i installed the last old version i still had (from december 2012) and voila - no crash!
something must have been f... up with the last updates... (downloaded yesterday),
please fix that!

Comments

OldSmoke wrote on 5/30/2014, 4:42 PM

I am not a big fan of the new Nvidia drivers, especially anything after 334.89, if you can, revert to this driver. A couple of month ago I posted a tweak for this driver here in the forum. Basically it involves changing the OpenCL Memory setting on the VP internal tab to a higher number, from the default 384 to 1024, you may want to try this little tweak and driver 334.89.

GaryX1001 wrote on 5/30/2014, 4:49 PM

well, thanks for the suggestion, but i did not have driver problems, the crashes were because of the updated effects/transitions from 29.may.
if i had the money i would have bought a titan already, but so i have to play with the gtx 570 :)

OldSmoke wrote on 5/30/2014, 5:18 PM

I just bought and installed the latest NB Titler Pro 3 and I don't have any issues with it. I have 2x GTX580 in my system and driver 296.10.

As for the Titan. Keep in mind that newer Kepler based cards are not well supported in VP and your GTX570 is still one of the best cards you can have. Any driver higher then 296.10 is suffering from performed issues with the exception of 334.89 together with my tweak mentioned earlier will give equal performance.

jetdv wrote on 6/2/2014, 12:36 PM

Gary, as this is very specific to your machine, you would need to send full details to support at newblueinc.com.

Byron K wrote on 6/3/2014, 3:28 AM

I had a similar issue. Battlefield 4 on my rig, it would keep on intermittently crashing, could not complete a round w/ out it hanging the system or go a few rounds and it would kick me out of the game.

Funny thing is, Vegas 12Pro, and all the other apps seem to work fine.

I was looking forward to replace the old GTX550 and purchase a new GTX780 and decided to re-seat the video card. No luck. Last ditch effort was to move the card to the 2nd SLI slot and now it works fine haven't had a crash since.

GaryX1001 wrote on 6/3/2014, 11:54 AM

well, i said that it only crashes with the latest newbluefx updates, ALL other version were stable! my computer is stable, no crashes! this 140320 build has made things bad. using 131212 now and all works. i don't know if there was a build between these, but if, then it was stable also! i regularly check for updates.

OldSmoke wrote on 6/3/2014, 1:02 PM

Strange, mine says Version 140411 and I don't have any issues with it.

GaryX1001 wrote on 6/3/2014, 1:59 PM

what plugin are you talking about?
i checked all i have and only colorfast is in the 140xxx region and works.

the plugin which caused the crash was light blends, transition between two clips.
and i re-checked for updates, still says 140320 online.

OldSmoke wrote on 6/3/2014, 5:26 PM

@Gary

I have to apologize. I was looking at me NB Titler Pro 3 and assumed all other NB FX would have the same version number. Again, my appologies.

VidMus wrote on 6/3/2014, 5:56 PM

OldSmoke said, "I am not a big fan of the new Nvidia drivers, especially anything after 334.89,..."

I just installed the latest driver, 337.88, and it solved a number of crash issues that I was having with Vegas 13 when working with a slide show with scanned pictures and other issues.

Also makes Vegas more stable. I was stopping the crashes by setting the preview memory to zero but I was not fond of that. I could also stop the issues by turning off the GPU, but that makes everything way too slow.

The latest driver allows me to keep the preview memory at 200 without a crash BUT I will get flakey renders with it. So I now keep the preview memory at zero and it works great. Apparently, the preview memory is not totally compatible with GPU usage so it is best to just leave it at zero.

Note: With earlier drivers and preview memory at zero, the rendering speed would be slower. With the latest driver, having the preview memory at zero, the rendering speed is a little bit faster but still a little bit slower than with the 296.10 driver with preview memory at 200. While I like the greatest speed possible, reliability is much more important.

NB Titler Pro 3 does not like the older driver (296.10) and had some crash issues with it as well as complains about it at times with a dialog message saying I should install the latest drivers.

So the latest driver, 337.88, is the one I will use for now with preview memory set for zero.

I hope this helps anyone who may be having problems.

NVidia 580.

LV studio wrote on 6/4/2014, 8:05 AM

I noticed a similar experience with preview at 200 and zero. VP13 editing appears stable at 200 but some projects renders will crash. Setting preview to zero for these projects renders, is slower, but completes the tasks.

OldSmoke wrote on 6/4/2014, 9:02 AM

I use driver 296.10 with NB Titler Pro 3 and have yet to experience a crash... all good so far.

VidMus wrote on 6/4/2014, 10:48 AM

@ OldSmoke

I had to push NBTP3 very hard with a long credit roll from pasted text.

No matter what, the credit roll would work perfectly most of the time but after saving it and then reloading it, it would not work correctly. I have not checked it again since using the latest driver.

Vegas itself is a little bit slower but much more reliable and stable with the latest driver. So as far as my system is concerned, I will stay with the latest driver for now.

I think it is more about the project type and its media than the system itself. I very seldom ever do a slide show with pictures, so that may have just exposed a problem I did not know I had.

Maybe those who do not have problems with Vegas actually do, but they do not notice it because of the type of editing they do and/or media they use.

And then there is that funny little bug critter that lurks in some computers... LOL...

OldSmoke wrote on 6/4/2014, 11:59 AM

@Vidmus

I had similar render issues with later then 334.89 drivers and hence stay away from it, crashes, intermittent frame jumps are among the most common. I will use 296.10 until an app or plug-in forces me to change. I do use 334.89 with Win 8.1 because 296.10 just doesn't work there at all but I haven't touched that setup in a long time and won't until Win 9.