Mouser would you like me to start a general windows annoyances and fix the little buggers section in the Wiki with the following?
Interesting bit of info ...
I have tracked down the cause of the DCOM errors - and this may be of interest to others using Creative SoundBlaster equipment. This seems to be a generic common problem in Creative's drivers, but is more often experienced with Audigy Cards. Here is my summary of the problem and solution:Event Viewer Alert:
Event ID = 7000, PfModNT service failure due to 'missing file'
Also a number of DCOM alerts in the same log referring to various processes that would not startup properly because the service database was locked. These services varied, but "netman" and "iPodService" (installed with iTunes) were a common services to suffer in this way.Background Info:
The process PCI/ISA Device Info. Service belongs to the software PfModNT by Creative Technology Ltd (www.creative.com
PfModNT.sys is located in the folder C:\Windows\System32.
The driver can is started during system startup.
Important: Some malware is hidden as PfModNT.sys, possibly in c:\windows or c:\windows\system32.
The version I have on WindowsXP is straight from the CreativeAudigy driver site, and has the following properties:
File size: 15,840 bytes
This is a typical bug of Creative Audigy 2 drivers (and others in the SB family).
Solution: Open Control Panel > System > Device Manager and select View > All hidden devices.
Scroll down the device list to Non-PnP-Drivers.
Find "PfDetNT" and "PfModNT".
With the right mouse button select "properties" and change
the startup type of PfModNT to "System" and the startup type of PFDetNT to "Demand".
If you are asked to restart you system do it after you have changed both.
You should now find the mysterious PfMonNt error no longer appears amd the service starts properly. I found all the DCOM errors disappeared too so obviously the system was fighting to start PfMonNT when the other processes were asked to start and they couldn't because the PfMonNt problem was blocking access to the service start mechanism. This also explains why the problem DCOM services varied from boot to boot.