New
#11
Once the computer get done with all the Startup their is a bunch of checking for updates using the internet.
Way to much going on for 3 gigs of ram on a Windows 7/64 boot.
Once the computer get done with all the Startup their is a bunch of checking for updates using the internet.
Way to much going on for 3 gigs of ram on a Windows 7/64 boot.
Gav yours and my system would slow down on boot but it would not grind down to unworkable.
Our systems would still work reasonable well after the slow boot.
When a system has little ram left to use after boot, not much to work with for everything else one wants to do.
Years ago I had a 64 bit system with 3 gigs of ram. Because I kept a lean and mean the system worked nicely. It wasn't a barn burner but it worked for what I was requesting it to do.
That is the secret. Don't ask your system and the way it is set up to do more than it is designed or capable of doing.
Thanks for the suggestion. I've disabled some more startups. I've previously disabled a large number of startups & services using Autoruns. However Autoruns shows that I have many more dll's being loaded at bootup than exe's. I've been hesitant to disable the dll's as I don't know what they do or what the ramifications of disabling them would be (DLL hell?).
Also, I want to emphasize that while my system is not a "barnburner", it normally operates quite satisfactorily for my purposes. It's only on occasion (usually, as I said, when I'm desperate to get something done) that it switches to glacial pace. I don't know why or what causes it.
You have been given reasons this happens and have chose not to do what has been suggested in the fashion those suggested curtailed.
Huh? Did I give offense? I thought I *did* follow your suggestion by disabling more startups! I had also hoped that someone might enlighten me as to whether it's safe to disable dll's. Finally, I can't tell immediately whether your suggestion worked because - as I stressed - the problem only happens occasionally, so I'll have to wait to see if in the long run I no longer get the problem. (Not sure what you mean by "curtailed".) Thank you for your help.
Okay; show us some more pictures of msconfig/Startup and Microsoft Services plus Non Microsoft Services and lets see if we can find some more to trim.
Leave dll alone. Don't mess with them. Nobody posted to fool with dll.
coffent given the many-and-varied startup programs you have left enabled (way, way too many IMO), it is possible (likely?) that the "only occasional" problem is due to one of those startup programs attempting e.g. to "phone home" and then its update server is down or busy (as just one example).
There is a free program I use from R2Studios called Startup Delayer which has a tab for Running Tasks and which shows When (date/time) that running task started. By looking at the long list of startup programs, and the time each starts before the next one starts...you might be able to identify the one(s) that are bogging you down. Just an idea. I leave Startup Delayer running on all my PCs so I can refer to it "just in case".
Thanks for the suggestions - I agree that a snafu with a startup program could be causing the problem. I will try Startup Delayer. That said, I have far more Microsoft services loading at startup (which I've been hesitant to disable), and I question whether one (or more) of them may be a cause. The only non-Microsoft programs I have loading at startup are an anti-virus and a VPN service, Java, Google and Mozilla updaters, and a few non-internet-connected programs that I use all the time. Is that "way too many"? FWIW, I'm posting the many Microsoft startup programs shown by msconfig. I'll be more than willing to try disabling any that others have found not to be essential.