Wmiadap.exe and 100% Processor Usage

  • Thread starter Thread starter Benign Vanilla
  • Start date Start date
B

Benign Vanilla

A friend of mine is running XP Pro on his home PC. Recently, he noticed that
from time to time, the PC would seem to be so busy that nothing could be
done. This occured at boot up, and for some apps, such as Outlook when
launched. He narrowed it down to wmiadap.exe taking the processor to 100% or
two instances of 50% each.

What causes this to be launched? and how do we stop it? It is making the
machine useless.
 
Armando said:
This file is an autodiscovery/autopurge process that runs on bootup or
during net start/stop events (launching services). Check your event log for
WinMgmt type errors to see if you're getting any errors. This page which
should help:
Click to expand...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/
wmi_adap_event_log_events.asp
<snip>

Thanks for the tip, but we checked that site already and I must admit I did
not find it to be much help. I have asked my buddy to check the logs for
errors so we will see. He says he has not installed, nor changed anything,
so we can't figure out why this started happening, and more importantly how
to stop it.
 
Benign Vanilla said:
A friend of mine is running XP Pro on his home PC. Recently, he noticed that
from time to time, the PC would seem to be so busy that nothing could be
done. This occured at boot up, and for some apps, such as Outlook when
launched. He narrowed it down to wmiadap.exe taking the processor to 100% or
two instances of 50% each.

What causes this to be launched? and how do we stop it? It is making the
machine useless.
Click to expand...

I got ahold of the system/application event logs from the errant PC. Nothing
out of the ordinary there. I also got a copy of the wmiadap.log. There many
entries in that file similar to this one:

(Tue Apr 27 09:35:33 2004.110078) : **CRITICAL FAILURE** (Tue Apr 27
09:38:32 2004.289500) : **CRITICAL FAILURE** (Tue Apr 27 11:12:28
2004.44718) : WDM event && WMIBinMof.BinaryMofEventChanged == TRUE
(Tue Apr 27 11:13:31 2004.107875) : **CRITICAL FAILURE** (Tue Apr 27
11:16:28 2004.285078) : **CRITICAL FAILURE** (Tue Apr 27 11:24:16
2004.43125) : WDM event && WMIBinMof.BinaryMofEventChanged == TRUE
(Tue Apr 27 11:25:19 2004.105765) : **CRITICAL FAILURE** (Tue Apr 27
11:28:18 2004.284968) : **CRITICAL FAILURE**

Any thoughts? I can't solve this at all.

--
BenignVanilla
www.iheartmypond.com

Do you want to supplement your income
with a stay at home job, AND help the
environment?

Check www.AMothersDream.com
 
Back
Top