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 Error
Event Category: None
Event ID: 1000
Date: MM/DD/YYYY
Time: HH:MM:SS
User: N/A
Description: Faulting application explorer.exe, version 6.0.2600.0, faulting module shlwapi.dll,
             version 6.0.2600.0, fault address 0x00003193.


Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: MM/DD/YYYY
Time: HH:MM:SS
User: N/A
Description: Faulting application iexplore.exe, version 6.0.2600.0, faulting module browseui.dll,
              version 6.0.2600.0, fault address 0x0000d09b.


Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: MM/DD/YYYY
Time: HH:MM:SS
User: N/A
Description: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.


Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: MM/DD/YYYY
Time: HH:MM:SS
User: N/A
Description: The COM+ Event System detected a bad return code during its internal processing.
             HRESULT was 8007043C from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.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.



Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish