The 41E90F3E-56C1-4633-81C3-6E8BAC8BDD70 part of the GUID mentioned in the event is the COM EventSystem itself (COMSVCS.DLL) it is not that useful in narrowing down the problem. The second GUID, if exists, may point to the application causing this.
Various GUIDs encountered for this event:
- 6295DF2D-35EE-11d1-8707-00C04FD93327 = Mobsync
- D3938AB0-5B9D-11D1-8DD2-00AA004ABD5E = SENS Subscriber for EventSystem EventObjectChange events. A support forum thread indicated that an instance of this problem was fixed by uninstalling and reinstalling MS Office and .NET Framework.
- 42EB8D03-5548-4667-A2A4-73395F61 BDC8 = Microsoft Message Queuing - See ME331697
- 58FC39EB-9DBD-4EA7-B7B4-9404CC6ACFAB = Dr. Watson (debugger)
- 7E89FF0B-F649-4F9A-A9C3-F05DFAAA3DA1 = Microsoft SMS advanced client (C:\WINNT\system32\CCM\CcmExec.exe). If combined with Error code 80070005
, see ME298095
There may be different error codes reported in the event description as well. These codes, like the GUIDs may help identifying the problem:
- Error code 8000401A
- This may be recorded when the computer is started by there is no connection to the domain controller (for example when starting a laptop at home). See also the suggestions for event id 4100.
- Error code 80070424
- A service is not installed properly.
- Error code 80070422
- Service disabled.
- Error code 80070005
- Access denied