G
Guest
System: Windows XP SP2 Fully Updated
Location: The University of Notre Dame Campus Network
Problem: After running for an extended period, the kernel processor usage
reported by Task Manager and other tools hovers around 50%. The system slows
down accordingly. This is when ONLY confirmed standard Windows processes (by
name and signature) are running. Also, another friend on the network has the
exact same problem.
Temporary Solution: When I disable my NIC, the kernel processor usage drops
back under 1% like it should be. When I reenable it, the usage is still below
1%. If the system is left to run for awhile, after hours or days (seemingly
random) the kernel usage will jump to around 50% directly and then hover
around there again.
My Theory: I noticed that disabling/reenabling the NIC fixes the problem
temporarily. I have checked the error reports and there are MrxSmb warnings.
I used to appropriate MS hotfix to solve this issue when I first noticed it
but I still get the warnings. I sort of wonder if my computer is being
bombarded by ARP requests. If it's something like that, however, why doesn't
the usage jump immediately after reenabling.
You have probably heard this several thousand times, but I am certain this
is not malware related. I have had this problem for months now, and have
performed scans with Norton, ewido, McAfee, AVG, TrendMicro, Spybot, Hijack
This, AdAware, and have used SysInternals tools such as Rootkit Revealer,
Processor Explorer, and Startups but they yield nothing. I have also gone
through the standard MSConfig clean. The same symptoms eventually occur
unless the NIC is disabled and reenabled.
Thanks,
Ryan
Location: The University of Notre Dame Campus Network
Problem: After running for an extended period, the kernel processor usage
reported by Task Manager and other tools hovers around 50%. The system slows
down accordingly. This is when ONLY confirmed standard Windows processes (by
name and signature) are running. Also, another friend on the network has the
exact same problem.
Temporary Solution: When I disable my NIC, the kernel processor usage drops
back under 1% like it should be. When I reenable it, the usage is still below
1%. If the system is left to run for awhile, after hours or days (seemingly
random) the kernel usage will jump to around 50% directly and then hover
around there again.
My Theory: I noticed that disabling/reenabling the NIC fixes the problem
temporarily. I have checked the error reports and there are MrxSmb warnings.
I used to appropriate MS hotfix to solve this issue when I first noticed it
but I still get the warnings. I sort of wonder if my computer is being
bombarded by ARP requests. If it's something like that, however, why doesn't
the usage jump immediately after reenabling.
You have probably heard this several thousand times, but I am certain this
is not malware related. I have had this problem for months now, and have
performed scans with Norton, ewido, McAfee, AVG, TrendMicro, Spybot, Hijack
This, AdAware, and have used SysInternals tools such as Rootkit Revealer,
Processor Explorer, and Startups but they yield nothing. I have also gone
through the standard MSConfig clean. The same symptoms eventually occur
unless the NIC is disabled and reenabled.
Thanks,
Ryan