I have not had to hunt these down too much but it seems that the DNS resolver is pushing the cpu up to 100% and it just started doing it. Nothing really changed with the computer. It was fine last night, they left it on overnight and this morning it was stuck at 100% cpu usage.
I restored to yesterday- no change.
I cleared out the startup apps.- no change
I did a repair install with XP Pro- Little change, then no change, but it is more manageable now.
The computer is a Pentium 4 single core with 2GB of RAM and a sata HD + 2 PATA opticals.
I ran process killer (sysinternals) and found the culprit I THINK, according to the program it showed DNS RESOLVER as being the process that was being a jerk.
I looked for a few ways to fix and I found maybe editing the host file to make it too big could do it, so I gave it an MVP host file instead of the long one it might have had. Kinda helped, but not really.
Tonight I am heading to Microcenter to get a new case/mobo/cpu/ram/dvd drive and a few other odds and ends and then tomorrow I plan to show up and take the HD out and drop it into the new computer. Then reconnect the booting strings, take care of the mass storage controller issues and the intel PPM files and THEN hunt down the process that is causing me issues.
I just want to be well versed when I go to war in the morning. I saw an option to make a full memory dump and a mini dump. Would either of those have a solution or at least give me a good idea what is going on? I was going to look up what the DNS resolver is and why it would run at such high CPU. I gotta head out now though so I will get to that tonight hopefully.
Anyways, anything I might have missed? Thanks for any info on this.
I restored to yesterday- no change.
I cleared out the startup apps.- no change
I did a repair install with XP Pro- Little change, then no change, but it is more manageable now.
The computer is a Pentium 4 single core with 2GB of RAM and a sata HD + 2 PATA opticals.
I ran process killer (sysinternals) and found the culprit I THINK, according to the program it showed DNS RESOLVER as being the process that was being a jerk.
I looked for a few ways to fix and I found maybe editing the host file to make it too big could do it, so I gave it an MVP host file instead of the long one it might have had. Kinda helped, but not really.
Tonight I am heading to Microcenter to get a new case/mobo/cpu/ram/dvd drive and a few other odds and ends and then tomorrow I plan to show up and take the HD out and drop it into the new computer. Then reconnect the booting strings, take care of the mass storage controller issues and the intel PPM files and THEN hunt down the process that is causing me issues.
I just want to be well versed when I go to war in the morning. I saw an option to make a full memory dump and a mini dump. Would either of those have a solution or at least give me a good idea what is going on? I was going to look up what the DNS resolver is and why it would run at such high CPU. I gotta head out now though so I will get to that tonight hopefully.
Anyways, anything I might have missed? Thanks for any info on this.



Comment