Why does Vegas crash when Ram preview is above 0?

VMP wrote on 7/28/2015, 1:19 PM

One of the advice given when Vegas crash is to set the ram preview to 0, or turn off GPU.

As long as the Ram preview is 0 my Vegas 13 never crashes (even with GPU acceleration enabled).

But when ram preview is set above 0 it does crash, randomy during edits, no error message either.
Just the default Windows message 'this program is no longer responding'

So what is actually causing Vegas to crash when ram preview is set above 0?

I do find the ram preview a handy feature.

VMP

Comments

astar wrote on 7/28/2015, 2:30 PM

Preview should be kept to the default minimum, a 0 setting can actually increase render times in my experience. I run mine at 2048 with no crashing, and use the build to ram at time.

The Nvidia card in your system is not that great for Vegas. Try uninstalling the NVidia drivers removing the card, and then testing for the error on the onboard Intel HD graphics adapter. If you do this, after pulling card open an admin level terminal, and run "winsat formal" Then hold down CNTL+SHIFT and click to open Vegas. (this will reset Vegas entirely to defaults.)

Here are some other things with your configuration to try:

Uninstall all old applications not needed anymore.

Update windows fully and reboot

Use Ccleaner

Use the Windows Disk Sweeper tool and clean the windows system updates and old windows installations. reboot.

Check for more windows updates, reboot if more installed.

Make sure Vegas is fully updated.

Make sure BIOS, GPU, Z77 Chipset, SATA controller, sound card, Network

Make sure all memory chips are the same make, model, timing. Speccy can help see this. For Z77 this should be DDR3 1333/1600 and not overclocked, use a stock profile.

Make sure GPU is interfacing at maximum interface speed, is in the 1st x16 slot. GPU-z can help see the interface speed. Some motherboards share bandwidth with onboard PCIe devices.

Remove all user addon boards, disable onboard devices in BIOS except sound, this is an attempt to rule out bad devices or drivers.

Verify chipsets and GPU are staying below 70C during editing and rendering.

Verify the DPClatency of the system, this will check for bad drivers, the line should be relatively flat and not spiking greatly.

xberk wrote on 7/28/2015, 3:35 PM

same here. V13 has been solid for me. Running Dyanmic Ram at 1000 and 2000 and higher with no problem. Running it at zero too with no problem. No linkage to crashes for me. Very very few crashes on V13 for me. Hard to remember the last one.

VMP wrote on 7/29/2015, 10:36 AM

Thanks astar & xberk,

Ah maybe I should give it a try between1000-2000. I have usually set it at around 12000, that may be too high.

VMP

VMP wrote on 7/29/2015, 10:50 AM

Astar,

Here are some screenshots from speccy:

Summary:
http://www.v-mp.com/Files/sonyforum/VMP-spec.jpg

Ram:
http://www.v-mp.com/Files/sonyforum/VMP-ram.jpg

GPU:
http://www.v-mp.com/Files/sonyforum/VMP-gpu.jpg

CPU:
http://www.v-mp.com/Files/sonyforum/VMP-cpu.jpg

The chipsets are build into the motherborad, so they should be fine right?
I never overclock anything on my PC.

VMP

Steve Mann wrote on 7/31/2015, 11:07 PM

That's a more than sufficient system, but why so little memory? The MB supports 32Gb, so that would be the first step.

I have my RAM preview set to 16Gb because I like to do long shift-B previews.

Are you overclocking?

Laurence wrote on 8/1/2015, 1:05 AM

I have no problem using large RAM preview buffers in V13. My buffer is currently set to 3GB (I have 16GB).

With Vegas 11 and 12, I couldn't go above 0GB without constant crashing.

I only figured this out in V12 however. In V11, the crashing was so bad, I never actually managed to make through even a single project. I probably would have been able to use it had I realized that this was the problem.

astar wrote on 8/6/2015, 1:26 PM

The system looks good in terms of memory speed for the chipset.

I would try some renders using the "default all" setting for RAM Preview. Then, with 16GB of ram not, go higher than 2048 (set memory sizes in byte multiples.) If you do not use CRTL+B, leave the setting at the default. There is background rendering or anything that you need to keep preview renders in memory. Preview size only determines how long of timeline playback at a given project size you get. Windows will use the remaining system memory for disk cache. This disk cache is why you want 32GB of ram, since pulling video from memory is so much faster than calling from disk.

Did you verify the GPU interface speed with GPU-z? Just to make sure all the PCI lanes are available to the card?

GPU wise you could improve a bunch in terms of Vegas. The gtx670 is well below the most of the AMD HD series cards in terms of OpenCL performance. This chart below shows smalLux render which uses OpenCL in the same manner as Vegas. You can see where the 670 falls in comparison to the now old school hd7970, which you can get for about 150-175 on ebay.

http://www.anandtech.com/show/5818/nvidia-geforce-gtx-670-review-feat-evga/15

Here is another view http://www.tomshardware.com/reviews/geforce-gtx-670-review,3200-11.html

If you change the card to AMD, search other posts I have made with how to do this correctly.