Results 1 to 2 of 2

Thread: Windows 2008 Server, wmiprvse.exe taking up excessive CPU

  1. #1
    Mike M Guest

    Windows 2008 Server, wmiprvse.exe taking up excessive CPU

    Win2008 server running in VMWare Workstation 6 with latest VMWare
    additions installed. Win2008 runs flawlessly in this configuration save
    for the wmiprvse.exe taking up 8-15% of the CPU.

    Turning off the Windows Management Instrumentation fixes the problem but
    is not ideal. Turning the WMI back on seems to "fix" the problem
    however the services "IP Helper" and "Windows Resource Manager" aren't
    automatically started when the WMI service is turned back on.

    Turning the IP Helper service back on has no ill effects on the CPU.

    But turning the Windows Resource Manager on brings the WMIPrvSe.EXE back
    to the top of the CPU's most used processes.

    Would leaving the WRM off adversely affect the system?

  2. #2
    Frankster Guest

    Re: Windows 2008 Server, wmiprvse.exe taking up excessive CPU


    "Mike M" <nospam@nospam.net> wrote in message
    news:uftxZiRkIHA.4120@TK2MSFTNGP06.phx.gbl...
    > Win2008 server running in VMWare Workstation 6 with latest VMWare
    > additions installed. Win2008 runs flawlessly in this configuration save
    > for the wmiprvse.exe taking up 8-15% of the CPU.
    >
    > Turning off the Windows Management Instrumentation fixes the problem but
    > is not ideal. Turning the WMI back on seems to "fix" the problem however
    > the services "IP Helper" and "Windows Resource Manager" aren't
    > automatically started when the WMI service is turned back on.
    >
    > Turning the IP Helper service back on has no ill effects on the CPU.
    >
    > But turning the Windows Resource Manager on brings the WMIPrvSe.EXE back
    > to the top of the CPU's most used processes.
    >
    > Would leaving the WRM off adversely affect the system?


    Not an expert here, but...

    I recently had a case where there were some documents stuck in a
    non-existent print queue (printer had been removed but user printed to it)
    and the wmiprvse was taking a ton of CPU cycles trying to print to this
    non-existent queue. So was the crss process (or similar). That left the
    system idle process fluctuating between 10 and 20 percent.

    Anyway, deleting the documents from the phantom print queue fixed the issue.

    Something to look at.

    -Frank


Similar Threads

  1. Replies: 8
    Last Post: 08-03-2012, 12:02 AM
  2. Replies: 1
    Last Post: 22-05-2011, 01:34 AM
  3. Installing a function of Windows Server 2008 Server Core
    By SalVatore in forum Tips & Tweaks
    Replies: 2
    Last Post: 28-08-2010, 04:03 PM
  4. Replies: 1
    Last Post: 06-05-2009, 09:09 PM
  5. wmiprvse.exe taking over server using %100 cpu
    By Delil in forum Small Business Server
    Replies: 2
    Last Post: 24-04-2009, 10:21 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,655,890.30241 seconds with 17 queries