Curse

Harah Shadowstorm · Oct 07, 2006, 02:57 AM // 02:57

Ok so about 4 hoursago i was starting to experience lag and a few mins ago i was checking out my processes, and looking at the processes Spoolsv.exe was using 95+% of my CPU! is this normal? or should i be worried about this.
UPDATE: when i tried ending spoolsv, the System Idle Process took its place as dominating my cpu -_-

Miss Eisei · Oct 07, 2006, 03:39 AM // 03:39

google is ur best freind ;D

http://www.liutilities.com/products/...brary/spoolsv/

Abuh · Oct 07, 2006, 07:49 AM // 07:49

Probablly have some printer tasks that are stuck. Just end spoolsv.exe, remove all your printer tasks and execute spoolsv.exe again

Had this loads of times on computers of allot of people. Silly windows :x

Phrozenflame · Oct 07, 2006, 08:43 AM // 08:43

It could also be sdbot/vanbot file aka trojan/worm.

Get Ewido, for free, google it, then download it, update it and it will fix your problem.

Harah Shadowstorm · Oct 07, 2006, 12:17 PM // 12:17

Also, when i end spoolsv, System Idle Process takes its place as dominating my cpu -_-

Ziil · Oct 07, 2006, 01:41 PM // 13:41

When system idle process is at 95-99% or so then that is a good thing

it pretty much shows you that your pc aint doing anything

Tarun · Oct 07, 2006, 03:11 PM // 15:11

spoolsv.exe should never take up that high of a percentage. Run the following command.

Start > Run > cmd
sfc /purgecache
sfc/scannnow

Let it run it's course and the issue should be resolved.

System Idle Process is supposed to take up 99%.

Tachyon · Oct 07, 2006, 07:02 PM // 19:02

If you don't have a printer connected to your PC then the simple thing is to just disable spoolsrv from within the Services and Applications panel. That way, it doesn't even start at boot-up and if you ever ned it to run then you just activate it again.

Tarun · Oct 07, 2006, 07:27 PM // 19:27

Do NOT, under any circumstances, ever disable or modify any services.

Tachyon · Oct 07, 2006, 07:39 PM // 19:39

Quote:

Originally Posted by Tarun

Do NOT, under any circumstances, ever disable or modify any services.

Why not? I've got the majority of unused and unneeded services disabled, alway's have had. Never caused any problems at all, infact it's the first thing I do when I install Windows. I can't see the point in having a myriad of services running that quite frankly you don't need.

Mushroom · Oct 07, 2006, 08:52 PM // 20:52

Quote:

Originally Posted by Tarun

Do NOT, under any circumstances, ever disable or modify any services.

I would say it a bit differently.

Do NOT, under any circumstances, ever disable or modify any services, unless you know what you are doing.

It is basically the same advice I give when talking about the System Registry. If you know what you are doing, fine. But if you do not know what you are doing, you have no business being in there.

Sounds to me like you have either a print job that is hung up, or a virus/spyware. More and more Virus and SPyware programs try to hid themselves as "innocent" appearing tasks. That often makes it much harder to find them.

Make sure you use a good antivirus. Keep it updated and run it at least weekly. And install Microsoft Defender. It is a pretty good program, and it is free. It is one of the better spyware blockers that I have found.

And also get both AdAware and SpyBot. Update and run them at least once a week. That should keep you good, unless you get something like CoolWebSearch or Aurora. THen, your best bet would probably be to wipe and reload the system.

Tarun · Oct 07, 2006, 10:24 PM // 22:24

No. I said it exactly how I meant it to be said.

Do NOT, under any circumstances, ever disable of modify any services.

If you knew what you (not you as in YOU, but you as in anyone) were doing, you'd know not to disable services at all. Also, disabling idle services offers zero performance gain. Idle services take no RAM or CPU power at all. I'd love to quote the MSDN article, but I can't find it at the moment. The basic summary is that disabling a service that wasn't doing anything frees absolutely no resources.

You should never disable the error reporting service. Error reporting allows the end-user to obtain information after "serious error" crash dumps (STOP errors/BSoDs). It also provides the user with feedback if an issue has already been resolved. Example: http://support.microsoft.com/?kbid=894391
I had submitted an error report about this crash one day, and got no response back. The problem kept happening, and on multiple computers, so a few days later, I submitted it again, but this time, error reporting took me to a page stating that the cause was unknown but it research was in progress. Four days later, I submitted it again, and it took me to a page with the patch and the error never happened again.

I know a tech who is going to write a program just to undo all the bullshit that users are doing to their systems these days, including disabling what they think are "unused" services. If there weren't used, why would they exist? If they were unused, then they would be idle, and not taking up any resources at all. When the time comes to use the service, it will work fine, and all will be well. 6 months later, a program attempts to use a service that you've disabled because you think you are better than your OS, and you get a generic error: "The RPC server is unavailable". Now you think that the program you're using is a piece of crap, or Windows is a piece of crap, and you format/reinstall, and it works for a while... until you do your "tweaking" routine again.

In summary, if you continue to disable "unused" services, and I meet you on the street, I will punch you right there in the center of your face.

cannonfodder · Oct 07, 2006, 10:48 PM // 22:48

There is no problems with disabling services you dont need, though a word of caution should be if you dont know what it does leave it alone.

I have all the ones my system doesn't need disabled, and I do know what im doing.

Edit, and all sfc /scannnow will do is scan the system files, you forgot to mention that a full version of XP is needed if it finds any files are missing, and to be honest this wont really help the OP's problem, which has already been noted that it can be also a virus.

Tarun · Oct 07, 2006, 11:04 PM // 23:04

I just had this issue at the tech shop where I work. Doing the SFC resolved the issue.

If you had read my post in full, you would understand the purpose of services and why to never disable them.

Tachyon · Oct 08, 2006, 01:30 AM // 01:30

Quote:

Originally Posted by Tarun

I know a tech who is going to write a program just to undo all the bullshit that users are doing to their systems these days, including disabling what they think are "unused" services. If there weren't used, why would they exist? If they were unused, then they would be idle, and not taking up any resources at all. When the time comes to use the service, it will work fine, and all will be well. 6 months later, a program attempts to use a service that you've disabled because you think you are better than your OS, and you get a generic error: "The RPC server is unavailable". Now you think that the program you're using is a piece of crap, or Windows is a piece of crap, and you format/reinstall, and it works for a while... until you do your "tweaking" routine again.

No, I'd think "Hang on, that may have been disabled. I'll just enable it and then try again". Not that I have RPC disabled to begin with, but if I did get such an error that's what I'd check out first.

Quote:

Originally Posted by Tarun

In summary, if you continue to disable "unused" services, and I meet you on the street, I will punch you right there in the center of your face.

That's not very nice is it? Just remember though, some people would knock you the hell out if you actually did that!

Mushroom · Oct 08, 2006, 02:59 AM // 02:59

Quote:

Originally Posted by Tarun

In summary, if you continue to disable "unused" services, and I meet you on the street, I will punch you right there in the center of your face.

You have to realize, that the people in here cover the spectrum of computer familiarity. Some can't tell the difference between a video and a sound card. Others can program in assembly with their eyes closed.

Myself, I am on the other side of the spectrum. I started by programming COBOL on an IBM mainframe with keypunch cards. I have been working with the PC for over 20 years, everything from the 8086/8088, to dual processor PII, PIII-P4 and Athlon MP systems, to the LGA775 and AM2 systems of today. I have even worked on 12+ processor backplane server systems. I can even tell you how to low-level format an MFM-RLL drive for an XT class system, even though I have not had to do so in over 15 years (debug g=c800:5).

I have worked with everything from Pet, Vic-20/C-64/Amiga, Apple OS, Atari 400/800/ST, MAC OS 1-OS 9, DOS 3,3+, Windows 1.02R to 3.11, NT 3.51, NT4, 2000, XP, and Vista. I was a beta tester for 95, 98, and 2000. I have also worked with Novel, and am certified in Netware 2 and 3. I have my MCP for NT3, and MCSE for NT4 and 2000. In addition, I was certified by Mac for OS 7-8.

I frequently go in and customize services running, and do registry tweaks. Sometimes I do it for performance, most of the time I do it for security. In fact, a great many of them were taught to me in my various certification classes. Are you trying to tell me that Microsoft taught me wrong?

I do not recommend that people ever go into their registry, or to adjust services unless they really know what they are doing. It is a very complex area, and not meant for laymen to work in. However, turning off and disabling services is something I do almost every day in my line of work.

lord_shar · Oct 08, 2006, 03:04 AM // 03:04

Isn't it generally a good idea to shut down exploitable services like telnet, remote access, and similar if you don't plan on accessing your pc by remote?

trickfred · Oct 08, 2006, 03:33 AM // 03:33

Quote:

Originally Posted by lord_shar

Isn't it generally a good idea to shut down exploitable services like telnet, remote access, and similar if you don't plan on accessing your pc by remote?

Yes it is, though SP2 does disable many exploitable services that may have been enabled previously (such as 'Messenger' (which is different from MSN Messenger)).

Disabling services that your system will never use is perfectly fine, as long as you know what you're doing, and which ones to turn back on if you ever want to restore the missing functionality. If you're not sure what they're for, then leave them as they are. To that end, there are several good guides online explaining what each Service is for, and whether or not it is safe to disable. Google is your friend.

Not something I'd recommend the casual computer user undertake, but certainly not sonething that can never be done.

Oct 08, 2006, 06:14 AM // 06:14

http://www.dead-eye.net/WinXP%20Services.htm

if i find a better one then ya.

when u click the process name on the website, it explain what it is and does, its dependencies and what-not.

-edit-
another from majorgeeks.
http://majorgeeks.com/page.php?id=12

Tarun · Oct 08, 2006, 03:32 PM // 15:32

People still think Black Viper was smart.. Sad. All his "tweaks" are good for, is breaking your computer.

Service Tweaks Debunked