VMS rendering problems

dan-hedrick wrote on 5/12/2010, 5:58 PM
I have VMS6, Windows 7, 64 bit, HP Pavilion Elite HPE, Pnehom II processor with 8 GB RAM.
I have made slide show videos with this configuration with very good success. However, recently I have had trouble my project locking up during rendering at about 87% complete. Forum members suggested reducing the size of the digital photos which helped somewhat...but the solution that I found that works is to split the project up into small segments , render these smaller projects separately and then combine them into a new project. This works well but is a little cumbersome.
I think part of my problem is the number of processes that I have running in the background...87. From what I understand, it may be normal to have about 34-45 processes running in the background at any one time....but 87 seems like a lot to me....and I think it is using up a good portion of my RAM. (I do have other files open while working in VMS...eg. music folder, photo folder, but not much more).
A "GeeK" from the "GEEK SQUAD" said that it is normal for Windows 7 to have more processes running in the background....that other versions of windows. I find this strange....and would think that new (and improved) operating systems would be operating more efficiently.
What experience do other forum members have with Windows 7 (64 bit)....do you have a lot of processes running in the background. Could this high number of processes be part of my problem with lockup during rendering?
Comments and discussion are really appreciated. Are there any way to prevent a build-up of these processes running in the background.?

lcdrdan

Comments

david_f_knight wrote on 5/12/2010, 7:33 PM
The number of processes running in the background should not be able to influence whether Vegas locks up or not. The only way it could is if Windows has a bug (okay, people, stop rolling on the floor with laughter), or if one of those background processes somehow explicitly interferes with Vegas. By design, Windows should never allow any process to interfere with any other, though there are some ways they can (that's how anti-virus programs work, for instance, and some viruses, and atypical programs like those).

I wouldn't worry much about the number of background processes you have running, unless you notice that everything on your computer has gotten slower than it used to be.

Windows is really quite sophisticated in how it handles all the various requirements of multiple processes. Those that aren't currently executing needn't be loaded in RAM (and won't be if there is a need for that RAM), for instance, so they needn't take anything away from those processes that are currently executing.

Something you might try to help with your problem was suggested by BreachPattern today in this thread.
Birk Binnard wrote on 5/16/2010, 10:03 AM
87 is a lot. Did you buy your system from someplace like Dell or HP? If so it will have tons of bloatware/crapware installed and set to operate all the time. Cleaning this stuff up is a royal pain for sure.

My system is WIn7-64 also and right now I have 50 processes running, and that includes my web browser, a file manager, and Vegas MS rendering a 23 min. HD video.

Right after booting with nothing started by me my system has 44 processes running. In spite of the previous reply, which I agree with, 87 is a lot and certainly a lot more than is reasonable or needed. A good (free) utility to control started tasks is AutoRunS. Check it out.
musicvid10 wrote on 5/16/2010, 10:58 AM
Try turning off antivirus programs first.