M
msk_30339
My mother is running WinXP SP2 on her computer with a local printer
attached. Everything worked great until a few days ago, when the
printer stopped working. (According to her, she didn't do anything
new, didn't install anything, etc). After some poking around, I found
that spoolsv.exe was using all of the local resources. I stopped the
service, cleaned out the files in the C:\Windows\System32\Spool
\Printers folder and restarted the service. The process came up with
no problems, using almost none of the CPU. But as soon as I tried to
print something, we got the same problem. The document doesn't print,
and it sits in that folder, with the service chewing up the
processor. I've tried printing from MS Word, Notepad and from a 3rd
party app (for printing forms, etc). None of them work, all result in
the same behavior. I also tried to set the properties to print
directly to the printer and bypass the spooling, but that didn't help.
Any idea what's going on? Any and all suggestions are welcome.
Thank you!
-Murali
attached. Everything worked great until a few days ago, when the
printer stopped working. (According to her, she didn't do anything
new, didn't install anything, etc). After some poking around, I found
that spoolsv.exe was using all of the local resources. I stopped the
service, cleaned out the files in the C:\Windows\System32\Spool
\Printers folder and restarted the service. The process came up with
no problems, using almost none of the CPU. But as soon as I tried to
print something, we got the same problem. The document doesn't print,
and it sits in that folder, with the service chewing up the
processor. I've tried printing from MS Word, Notepad and from a 3rd
party app (for printing forms, etc). None of them work, all result in
the same behavior. I also tried to set the properties to print
directly to the printer and bypass the spooling, but that didn't help.
Any idea what's going on? Any and all suggestions are welcome.
Thank you!
-Murali