High Memory Utilization for svchost.exe running WMI

[Guest John Neithercott]

Has anyone else experienced a memory leak caused by the Windows Management

Instrumentation service? I have a seperate copy of svchost.exe

(svchostwmi.exe) running only the Windows Management Instrumentation service.

Usually this service is lumped in with a lot of other services that you

can't just restart (Server, Workstation, etc.). This svchostwmi.exe, if

allowed, will use all of the memory in the system and make the system

unresponsive. This only occurs on some of my Windows 2003 Enterprise 64-Bit

servers (about 6 of them). I currently have a kill script that runs every 4

hours to kill the runaway service. This has been occuring for over a year.

My systems are current on patches. Any ideas?

[Guest Harry Bates]

Re: High Memory Utilization for svchost.exe running WMI

 

Well, looking at what you just wrote, could it be that you are working with

an older version of svchost.exe since the svchostwmi.exe is a version that

you copied and renamed?

 

Harry Bates

Lockheed Martin

 

"John Neithercott" <JohnNeithercott@discussions.microsoft.com> wrote in

message news:9EDD63FE-3ED5-4FEA-9672-1CFC17E97C0F@microsoft.com...

> Has anyone else experienced a memory leak caused by the Windows Management

> Instrumentation service? I have a seperate copy of svchost.exe

> (svchostwmi.exe) running only the Windows Management Instrumentation

> service.

> Usually this service is lumped in with a lot of other services that you

> can't just restart (Server, Workstation, etc.). This svchostwmi.exe, if

> allowed, will use all of the memory in the system and make the system

> unresponsive. This only occurs on some of my Windows 2003 Enterprise

> 64-Bit

> servers (about 6 of them). I currently have a kill script that runs every

> 4

> hours to kill the runaway service. This has been occuring for over a

> year.

> My systems are current on patches. Any ideas?

[Guest John Neithercott]

Re: High Memory Utilization for svchost.exe running WMI

 

No. I just created the copy from the current version of svchost.exe. But

that is a good reminder.

 

"Harry Bates" wrote:

> Well, looking at what you just wrote, could it be that you are working with

> an older version of svchost.exe since the svchostwmi.exe is a version that

> you copied and renamed?

>

> Harry Bates

> Lockheed Martin

>

> "John Neithercott" <JohnNeithercott@discussions.microsoft.com> wrote in

> message news:9EDD63FE-3ED5-4FEA-9672-1CFC17E97C0F@microsoft.com...

> > Has anyone else experienced a memory leak caused by the Windows Management

> > Instrumentation service? I have a seperate copy of svchost.exe

> > (svchostwmi.exe) running only the Windows Management Instrumentation

> > service.

> > Usually this service is lumped in with a lot of other services that you

> > can't just restart (Server, Workstation, etc.). This svchostwmi.exe, if

> > allowed, will use all of the memory in the system and make the system

> > unresponsive. This only occurs on some of my Windows 2003 Enterprise

> > 64-Bit

> > servers (about 6 of them). I currently have a kill script that runs every

> > 4

> > hours to kill the runaway service. This has been occuring for over a

> > year.

> > My systems are current on patches. Any ideas?

>

>

>

[Guest Thee Chicago Wolf]

Re: High Memory Utilization for svchost.exe running WMI

 

>Has anyone else experienced a memory leak caused by the Windows Management

>Instrumentation service? I have a seperate copy of svchost.exe

>(svchostwmi.exe) running only the Windows Management Instrumentation service.

> Usually this service is lumped in with a lot of other services that you

>can't just restart (Server, Workstation, etc.). This svchostwmi.exe, if

>allowed, will use all of the memory in the system and make the system

>unresponsive. This only occurs on some of my Windows 2003 Enterprise 64-Bit

>servers (about 6 of them). I currently have a kill script that runs every 4

>hours to kill the runaway service. This has been occuring for over a year.

>My systems are current on patches. Any ideas?

 

Not sure how applicable it is to your situation but have a look at

this KB article: http://support.microsoft.com/kb/933230

 

- Thee Chicago Wolf