JSI Tip 7193. Corrupted Windows XP system files cause event IDs 1000, 4609, or 1000 in the Application event log.

If your system files are corrupted, you may receive any of the following in the Application event log entries:

Event Source: Application ErrorEvent Category: NoneEvent ID: 1000Date: MM/DD/YYYYTime: HH:MM:SSUser: N/ADescription: Faulting application explorer.exe, version 6.0.2600.0, faulting module shlwapi.dll,             version 6.0.2600.0, fault address 0x00003193.Event Type: ErrorEvent Source: Application ErrorEvent Category: NoneEvent ID: 1000Date: MM/DD/YYYYTime: HH:MM:SSUser: N/ADescription: Faulting application iexplore.exe, version 6.0.2600.0, faulting module browseui.dll,              version 6.0.2600.0, fault address 0x0000d09b.Event Type: ErrorEvent Source: VSSEvent Category: NoneEvent ID: 8193Date: MM/DD/YYYYTime: HH:MM:SSUser: N/ADescription: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.Event Type: ErrorEvent Source: EventSystemEvent Category: (50)Event ID: 4609Date: MM/DD/YYYYTime: HH:MM:SSUser: N/ADescription: The COM+ Event System detected a bad return code during its internal processing.             HRESULT was 8007043C from line 44 of d:tcomcom1xsrceventstier1eventsystemobj.cpp.             Please contact Microsoft Product Support Services to report this error.             For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

To resolve this problem, repair the Windows XP installation from your CD-ROM. See Reinstall Windows XP by Starting Your Computer from the Windows XP Compact Disc.