wmiprvse.exe 100% CPU in Windows XP Pro
I have several equipment with Windows XP Pro, in which the process wmiprvse.exe consumes the 100% CPU,in fact they are four processes with he himself name, a SYSTEM and other Service Network. I have looked for solutions in this Web, but all aims at W2K3. Please help me Thanks and regards Tony - Spain Sorry by my english
November 28th, 2007 5:24pm
it would be solved with this installation? http://www.microsoft.com/downloads/details.aspx?familyid=0638D919-109B-41C6-851D-0BE19D29172E&displaylang=en oronly is been worth for Windows 2003 server? it is very important that it solves it. Thanks Tony
November 29th, 2007 10:04am
November 29th, 2007 1:34pm
Hi, This forum is for SCE related issues. For questions about Windows XP, please use the Microsoft public newsgroups. The following web link would be the most relevant newsgroup for your question. http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?dg=microsoft.public.windows.mediacenter Thanks.
November 29th, 2007 4:56pm
Hi: I have this problem on a XP Pro machine. It will keep the CPU usage at 25% and will jump up to 50% if left un-rebooted, this is not related to 2003 Server .. Is there a solution to this files hight CPU use in a XP machine? Thanks!!
June 12th, 2008 9:38pm
You may have already solved this one, but if not, try clearing your application and system event logs. That made a difference for my situation.
June 12th, 2008 10:27pm
Clearing my application and system event logs did the trick for me on my windows 2003 server
January 21st, 2010 5:03pm
I understand this is not the thread that Jie-Feng wanted this dialogue on, but I must add that we have had this behavior on a Windows 2003 server since it was P2V'd to a VM server a year ago. It probably had nothing to do with moving to VM, just a coincidence. Also, the wmiprvse.exe consumed the CPU (actually 4 CPU's at 20-50% consumption) only when a third party scheduling app was running. This app does all the scheduling of jobs, day and night, so the app is always running in the background. Restarting the scheduling app helped reduce the CPU consumption some, but it always built back up. The support for the app was non-existent, but we had become rather dependent on it, so have been putting up with the CPU consumption issue for some time. Well, after finding this, I cleared all the Event Logs, reduced their sizes and magic - the CPU consumption dropped off to nothing. I can't wait to see how the overnight jobs run tonight, which is when the server gets hit the hardest. Thank you to Wesley Jones for the answer, and the other 3 parties in this dialogue.
March 10th, 2011 12:52am