>> Is it normal for wbem logs to constantly report repeated errors?
> Are you saying these errors in the wmi log files are meaningless?

I looked up what happens if I kill this service and I'm even more confused.

While the filemon.exe log does not show the failure which exists inside the
wmiprov.log and wbemess.log files, filemon does implicate the process which
is constantly being called as "wmiprvse.exe" (whatever that is).

Looking this up, I find wmiprvse.exe is a Windowx XP SP2 Windows Management
Instrumentation (WMI) process which is not supposed to be killed according
to http://www.auditmypc.com/process/wmiprvse.asp

Process Library & Answers that Work imply this service essential to XP:
http://www.processlibrary.com/directory/files/wmiprvse
http://www.answersthatwork.com/Taskl...tasklist_w.htm

It may be useful to note my anti-virus software has been running and is up
to date even though this intermittent daily Windows XP lockup has been
occurring for weeks.

Are you sure that killing the wmiprvse service will solve the problem
intimated by the constant errors in the WBEM log files?