Defragging RAM

  • Thread starter Thread starter Industrial One
  • Start date Start date
I'm still running SP2 and have heard nothing but
horror stories about installing SP3.


Whenever a new version of *anything* comes out, you always read about
"horror stories" with it. But realize two things:

1. If you're reading about problems *here*, this is where people come
with their problems, not with their successes. You get a very
distorted view of what's going on in the real world here; as someone
once said, "hang around a transmission shop and you will think that
all cars have transmission problems."

2. Most problems, by far, that people report here--whether or not they
are SP3-related--have nothing to do with defects in the software. They
result from people's ignorance, from bad or inadequate hardware, from
old drivers, from viruses, from spyware, and so on. And except for
very rare situations, they always get a fix for their problems, and in
most cases, that fix is a very simple one to implement.

I no longer run XP on any of my computers, but when I did, I ran SP3
on all of them and had no problems with any. I know lots of other
people who have had the same experience.
 
Allright, okay, I concede that defagging RAM is placebo bullshit. All
I know is that in the past (I had even more hot programs back then, I
had a script kiddy's paradise) on my P4 with 256 MB of RAM, I never
had these problems, and any time I did have RAM buildup, SM would
recover and defrag the RAM. It doesn't work with 4 GB DDR3 RAM though
for some reason.

Also, these programs don't run in the background. Only my firewall and
IP shitlister do, and they don't take up much. But as I said, I've
been somewhat careless lately and often set systemguard to ignore some
programs which I didn't feel like configuring the access limitations
like a paranoid douchenozzle. An angry nerd from an online game also
managed to give me a rootkit a week ago, which I had a fun time
cleaning and rebooting 15 times before I flushed the piece of shit
out.

Paul said:
Industrial said:
Industrial One wrote:
Industrial One wrote:
Is there any tangible solution to fixing application RAM buildup?
svchost.exe is now taking up over 400 megs and my comp has been on
for
a couple days. Firefox does the same thing, but firefox I can
fortunately restart, svchost I can't without restarting the whole OS.
If your symptoms match this, for the time being, disable the
update function.
"Windows XP: High memory usage for
svchost+wuauclt"http://forums.cnet.com/5208-6142_102-0.html?threadID=408643
http://social.answers.microsoft.com/Forums/en/vistawu/thread/c41d2ef2...
   "visithttp://update.microsoft.com/microsoftupdate
    click Change Settings on the left
    Scroll down and DISABLE MICROSOFT UPDATE"
Perhaps that will help, until Microsoft issues a fix.
    Paul
My Automatic updates are already turned off... I don't trust M$'s so-
called "security fixes."
The only other thing I can suggest, if you have WinXP Pro, is
go to command prompt and do
    tasklist /svc
which will list the contents of each service host. Maybe that
will tell you what the svchost is doing, which is using so much RAM.
These are my svchost entries:
svchost.exe                 1228 DcomLaunch, TermService
svchost.exe                 1316 RpcSs
svchost.exe                 1440 AudioSrv, CryptSvc, Dhcp, dmserver,
ERSvc,
                                  EventSystem,
FastUserSwitchingCompatibility,
                                  helpsvc, Irmon, LanmanServer,
                                  lanmanworkstation, Netman, Nla,
RasMan,
                                  Schedule, seclogon, SENS,
SharedAccess,
                                  ShellHWDetection, srservice, TapiSrv,
                                  Themes, TrkWks, W32Time, winmgmt,
wscsvc,
                                  wuauserv, WZCSVC
svchost.exe                 1540 Dnscache
svchost.exe                 1652 Alerter, LmHosts, RemoteRegistry,
SSDPSRV
svchost.exe                  592 WebClient
svchost.exe                  860 stisvc
My svchost PID 1440 is using 22MB of RAM, the others around 4MB or so
each.
If you have WinXP Home, you can use Process Explorer to list the same
kind of info. In fact, with Process Explorer, you can at least get
a text string for each of those services, so you can get a better idea
as to what they are.
http://technet.microsoft.com/en-ca/sysinternals/bb896653.aspx
So far, I can't find a utility that will give a breakdown of the
resources
used by each item inside a svchost. That would be useful info, as the
other debugging method (shutting down services one by one), is dangerous
and time consuming. Never shut down a service, without seeing what other
services depend on it first.
    Paul
How exactly will this tell me who the memory-hungry ****er is? Here's
a list of services run by svchost, not that it will tell anyone
anything:
I:\WINDDWS\system32\svchost.exe
Services:
Automatic Updates [wuauserv]
Background Intelligent Transfer Service [BITS]
CDM+ Event System [EventSystem]
Computer Browser [Browser]
Cryptographic Services [CryptSvc]
DHCP Client [Dhcp]
Distributed Link Tracking Client [TrkWks]
Fast User Switching Compatibility [FastUserSwitchingCompatibiIity]
Help and Support [helpsvc]
HID Input Service [HidServ]
Logical Disk Manager [dmserver]
Network Connections [Netman]
Network Location Awareness [NI..A] [Nla]
Flemote Access Connection Manager [FIasMan]
Secondary Logon [seclogon]
Security Center [wscsvc]
Server [Ianmanserver]
Shell Hardware Detection [SheIIHWDetection]
System Event Notification [SENS]
System Flestore Service [srservice]
Task Scheduler [Schedule]
Telephony [TapiSrv]
Themes [Themes]
Windows Audio [AudioSrv]
Windows FirewaII.··'Internet Connection Sharing [ICS] [SharedAccess]
Windows Management Instrumentation [winmgmt]
Windows Time [w32time]
Wireless Zero Configuration [WZCS\·"C]
Workstation [Ianmanworkstation]
Excuse the spelling errors, ProcessXP produced that as a picture, so I
used OCR. Btw, I disabled automatic updates in the services right
after seeing that there, and svchost.exe is still growing, so you can
be assured it's not the culprit.

In Process Explorer (Sysinternals), if you right click on a SVCHOST entry,
then select properties, a separate window pops up. Select the "Threads" tab
in that window.

http://technet.microsoft.com/en-ca/sysinternals/bb896653.aspx

The CSwitchDelta column, shows activity when the thread is active. Perhaps
you can get a name, based on something in there having excessive
CSwitchDelta.

I still haven't found anything to display memory consumption of the threads.
Using CSwitchDelta, you may at least be able to see a thread which is
abnormally active, inside a SVCHOST process.

I did manage to use LiveKD (kernel dump) from Sysinternals, and convinced
it to dump a 2GB .dmp file, which should be a copy of the entire computer
memory. I've tried to feed that to windbg, but the learning curve for
that program is pretty bad.

    Paul

I looked and and none of the threads except 3 have CSwitch delta, two
have 1 and ESENT.DLL has 3, and apparently took 21 of the 26 minutes
of CPU time, so it might be the culprit, but a quick search on
win7dll.info tells that it's an essential system file. My system
probably is dirty, with a mass trojan ****fest somewhere, but what can
I say, Ad-Aware and Avast! both turned up nothing.

I should also note that not only have I observed this behavior with
svchost.exe but probably every process. Filesharing apps (no traffic
or torrents running), antivirus updater, MSN and all kinds of other
apps are just getting seriously fat.
 
Industrial said:
An angry nerd from an online game also managed to give me a
rootkit a week ago, which I had a fun time cleaning and rebooting
15 times before I flushed the piece of shit out.

Ding! Ding! Ding! Ding! Ding! Ding! Ding! We have a winner!
 
Bill said:
I agree. I was wondering how long it was going to take before
someone corrected this misunderstanding!


Again, this has nothing to do with "defragging RAM", but there
obviously is a problem, if its using that much RAM. I think the OP
mentioned in another post he had been using a registry cleaner
(System Mechanic), which may possibly have been a contributing
factor, but it's hard to know.

I had a memory leak once (that would eventually use up all the RAM) and
found an orphaned driver was chewing it all up, trying to access an
application that had been uninstalled.

It was quite a trick to identify it. I had to use the poolmon.exe program
to sort it out. It wasn't that easy.

Poolmon. exe: http://support.microsoft.com/kb/177415
 
Henry said:
Daave wrote:


What precautions please? I'm still running SP2 and have heard
nothing but horror stories about installing SP3.

Thanks

That's because the millions of people that successfully installed SP3 didn't
come to Usenet to crow about it; it just worked.. There is NO reason to not
use SP3, and you can't get MS updates without it.
 
Back
Top