svchost.exe Network Service problem

[Ichigo]

Cliff Notes:

-svchost.exe NETWORK SERVICE (the only one) slowly increases it's memory usage from around 4MB at -bootup to 90MB within several hours, more or less depending on for how long I go without restarting Windows XP SP2
-with greater memory usage comes greater CPU usage, after it reaches 90MB, for example, CPU usage flip flops between 0-20% constantly, spinning the fans up erratically.
-the "tasklist" command doesn't work in Command Prompt (it isn't recognized); i tried using this to check PID and it didn't work
-this particular svchost.exe has to do with the Remote Procedure Call service

I'm running a Bootcamped XP SP2 on a 2.2Ghz Macbook Pro.

I'm assuming it's a virus/spyware/something like that just because it randomly (not randomly, rather consistantly actually) eats away at memory.

Help?

EDIT: Weird, I was running the Windows Live OneCare online scanning thing and the memory usage has stopped going up at 8216KB. If it's a virus, it's a damn smart one.

 

[robisbell]

1. bad install of XP.
2. bootcamp causing it.
3. running incompatible software.

as for #3 there is a alist of programs that do to work well under bootcamp, I'd start there, and also, was the XP cd and key you used from a full retail version?

 

[Ichigo]

It's an OEM copy of XP w/ SP2 that's been updated over the months.

Also, what do you mean by incompatible software? I Google'd and didn't find a list or anything.

Reinstalling XP would be a PITA, but do you think it's the only way?

 

[robisbell]

it's actually in the Bootcamp manual, you may have to download it and print it out, but for oems, you have to let OS X copy and create it's own cd copy of the XP cd, oem's are iffy if they'll have the correct drivers included or not.

 

[Ichigo]

Bootcamp makes a CD of Bootcamp drivers, does it not? I've never heard of Bootcamp creating an XP CD...

 

[robisbell]

it's actually listed on page 10 about using full retail version of XP or Vista.
as for the issue of making a copy of the xp cd inside of OS X, I had to hunt the info down when I setup a new Intel Imac for a Professor I know, kept BSOD during install and found out I had to make a copy of the retail XP cd with the mac and the copy worked and installed fine, something about the file format and OS X not understanding it, or something. I do know OEM cd's do not either install properly, or the OS fails to operate properly.