wmiprvse.exe application error ???

[Guest Jessica]

For the past week when I turn on on my computer I get the following

Application Error: wmiprvse.exe

 

Instruction at 0x03b19020 memory could not be written 0x0000000 click ok to

debug or cancel to terminate the program

 

I have no idea what "program" it is referencing and I do not know how to fix

it.

Help! Thanks...

[Guest nass]

RE: wmiprvse.exe application error ???

 

 

 

"Jessica" wrote:

> For the past week when I turn on on my computer I get the following

> Application Error: wmiprvse.exe

>

> Instruction at 0x03b19020 memory could not be written 0x0000000 click ok to

> debug or cancel to terminate the program

>

> I have no idea what "program" it is referencing and I do not know how to fix

> it.

> Help! Thanks...

 

http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsxp.help_and_support&tid=dbf129b3-03f4-4108-8c53-16520387c2dc&cat=en_US_4fae9fed-da91-4a2a-9d2b-5dc71973d43c&lang=en&cr=US&sloc=en-us&m=1&p=1

MS:: <Quote>

Stopping and Starting the WMI Service

 

If you are experiencing problems with the WMI service you might need to

manually stop and restart the service. Before doing so you should enable

WMI’s verbose logging option. This provides additional information in the WMI

error logs that might be useful in diagnosing the problem. To enable verbose

logging using the WMI control, do the following:

1.Open the Computer Management MMC snap-in and expand Services and

Applications.

2.Right-click WMI Control and click Properties.

3.In the WMI Control Properties dialog box, on the Logging tab, select

Verbose (includes extra information for Microsoft troubleshooting) and then

click OK.

Alternatively, you can modify the following registry values:

•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging to 2.

•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging File Max Size

to 4000000.

After enabling verbose logging try stopping the WMI service by typing the

following

Open a run command prompt:

net stop winmgmt

 

If the net stop command fails you can force the service to stop by typing

this:

winmgmt /kill

 

Important. If you are running Windows XP or Windows Server 2003 the WMI

service runs inside a process named Svchost; this process contains other

services as well as WMI. Because of that, you should not try to stop

Svchost;

if you succeed, you’ll stop all the other services running in that process

as

well. Instead, use net stop winmgmt or winmgmt /kill in order to stop just

the WMI service.

 

You can then restart the service by typing the following command:

net start winmgmt

 

If the service does not restart try rebooting the computer to see if that

corrects the problem.

If it does not, then continue reading.

MS:: </Quote>

 

"WMI Diagnosis Utility"

http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx

 

Systems that have changed the default Access Control List permissions on the

%windir%\registration directory may experience various problems after you

install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC

http://support.microsoft.com/kb/909444

Also you can download the DiagWMI from here and some good solutions on the

page:

http://windowsxp.mvps.org/repairwmi.htm.

HTH.

Let us know.

nass

---------

http://www.nasstec.co.uk