Faulting application wmiprvse.exe, version 5.2.3790.3959, faulting module ntdll.dll,

http://www.file.net/process/wmiprvse.exe.html

You might want to download some spyware scanning software like SpyBot S&D to make sure you dont have any infections.

Is the server freezing up/crashing?  Have you had any NIC problems?  You may want to switch out nic(s) with a new one to see if you get the same errors.

The two posts would have guided the person who posted the question in a direction to resolve this.  I believe some points should be awarded for the suggestions.  I believe one of the posts solved the solution and that is why there was no response.

Your posts are good troubleshooting but not necessarily leading to a solution I am afraid.
Noone knows what had gone wrong with the asker's OS. Although you had reasonable suggestions without the asker they can hardly be called answers..

Points in EE are for answers - sometimes when the Asker does not return you cannot help much but this is not a reason for saving the question unsolved in the database

"...You may want to switch out nic(s) with a new one to see if you get the same errors."

I guess I would have to disagree as suggestions turn into solutions.  It almost sounds like you are saying that people should becareful where they decide to post suggestions and offer up their time since there is no reward if the person asking the question doesn't respond.  Sounds like a silly policy and a deterent.  But, keep the points, delete the question, whatever you have to do.  Lesson learned.  Thanks Venabili.

>>there is no reward if the person asking the question doesn't respond.
Nope. I am just saying that the idea is to save answers. And that sometimes the Askers never return and the questions CANNOT be answered... and no matter that I hate this, I cannot recomend acceptance

Sometimes the question is clear and the solutions are solutions. In cases like thjis one, the askers NEED to work with the experts...

Sorry for the late response.  I have not being in town or available since I posted my issue.  Actually what resolved the issue was putting more RAM into the server and expanding the paging file.  Once I did that the errors went away.  I tried the suggestion provided, but those actually did not work till someone at a confernece shared their own nightmares with this issue.

Sorry for such a late post , but i am new to the site and have a client with the exact same problem as above. They have 4gb RAM in the server and i have increased the page file, but it did not correct the errors. Were there any other solutions?

Anyone ever resolve this?

kentastic > I would post a new question so we can help you with it.

Another possibility for this issue is that WMI needs to be re-registered.
See http://groups.google.com/group/microsoft.public.windows.server.sbs/msg/17fba053e482d2ea

TechSoEasy