Link to home
Start Free TrialLog in
Avatar of rstuemke

asked on

Mystery SLxxx.TMP processes eating up processor utilization


Have a PC that was just reloaded with WinXP PRo SP2 and all fixes.  Its performances has gone down the toliet due to several mystery processes running.  They are SL304.tmp, SL4B2.tmp and the like.  Have Spycatcher Express running and COmodo Firewall and neither appears to have caught anything.  Use may have allow something....I do not know.  They are taking up 100% processor utilization.  There are 4 of them.  Any idea what these are?
Avatar of Jonvee

Hi  ...  SL304.tmp, SL4B2.tmp are not recognised.
Suggest you download and run Superantispyware >

Also you could try this free version of Ewido anti-malware.
Update first, then scan in Safe mode:

Then you could try at least two of these free virus scanners, as no one scanner can guarantee finding & fixing everything.
This article discusses several common causes of High CPU Usage >>
You could also select Start > Run and type MSCONFIG.  
From the System Configuration Utility select the Startup tab.  
Look at the programs that start up, and see if there are any you don't recognise.
Uncheck(untick) any unwanted items.    Reboot.     Any improvement?         

These two should help >>:             

If you still have a problem, let's try a scan for rootkit >
F-Secure Blacklight Rootkit Elimination ..
Please post back if you require any additional instructions to use this one.  Good luck.
If you click on the "kadaitcha" link above first, you'll see this next article.  It's worth going stright to this one and checking it out >>

    > was just reloaded with WinXP PRo SP2 and all fixes <
"CPU utilization reaches 100 percent when you run programs after you install Windows XP Service Pack 2":
for "stright" please read "straight".

Note the comments under "RESOLUTION" in the MS KBA.  You may well wish to consider installing this hotfix if you are being severely affected by this problem, and the other suggestions above do not help.
Dropped by with the idea of running this small utility Process Explorer version 10.0, to show a list of your currently active processes.  
Hopefully you'll see what is taking up 100% processor utilization.
It's been described as an advanced process management utility that picks up where Task Manager leaves off:

You might even wish to consider first *disconnecting* from the internet, and then temporarily 'disabling' Spycatcher Express & Comodo Firewall to check for any improvement.
Avatar of rstuemke


the programs taking up the CPU are the mystery SLxxx.TMP processes.  This is what I would like to know....what are these.....anybody seen them before......PC was running fine, prior to Friday...
Nope, can find no reference to the those SLxxx.TMP processes.

Can only suggest you treat them as suspicious and use virus & Malware scans, unless or until proven otherwise.
Avatar of Jonvee

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The processes are child process for NDP1.1sp1-KB886903-X86.exe, according to process explorer.
Not running Zone Alarm, but Comodo Firewall.
Ok, so they presumably are generated by >>
ASP.NET Security Update for Microsoft .NET Framework 1.1 Service Pack 1
File Name: NDP1.1sp1-KB886903-X86.exe

MS Knowledge Base (KB) Articles:

As you've recently reloaded with WinXP PRo SP2, have you got the latest security updates?

Apart from that you may wish to quickly review this article >
"Get Your PC Ready for Windows XP SP2":
After reviewing the above article, and if there is any doubt about the previous readiness of the PC for SP2, suggest you may want to consider removing SP2 using one of the three methods described here.
Carry out any appropriate adjustment(eg virus scans), then try another reinstal of SP2 ...
"How to remove Win XP SP 2 from your computer":
It was the Comodo Firewall.

Just FYI....SP2 works fine on this PC and all other PCs I've installed it onto.....
Ok, thanks .. so it *does* appear that the SLxxx.TMP processes are the result of some interaction involving the Firewall, although it wasn't ZA  ..  interesting!

Anyway, glad it's resolved.   Thank you.