>EVENT LOG MESS<

[Wayne B.]

Would anyone out there be able to point me in the right
direction to find out what needs to be done to stop these
errors and warnings from coming up on a relative's XP Home
that I have been given to troubleshoot. If anybody
recognizes any of these and are familiar with correcting
these problems, please pass on some info. It would be much
appreciated. THANX N ADVANCE. Wayne B.

Event Type: Warning
Event Source: EventSystem
Event Category: (54)
Event ID: 4353
Date: 3/12/2004
Time: 12:30:10 PM
User: N/A
Computer: FRESH
Description:
The COM+ Event System attempted to fire the
EventObjectChange::ChangedSubscription event but received
a bad return code. HRESULT was 80040201.

=========================================

Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354
Date: 3/12/2004
Time: 12:30:10 PM
User: N/A
Computer: FRESH
Description:
The COM+ Event System failed to fire the
ChangedSubscription method on subscription {D789AB02-5B9F-
11D1-8DD2-00AA004ABD5E}-{00000000-0000-0000-0000-
000000000000}-{00000000-0000-0000-0000-000000000000}. The
subscriber returned HRESULT 80040206

====================================

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 3/12/2004
Time: 12:30:10 PM
User: N/A
Computer: FRESH
Description:
The COM+ Event System detected a bad return code during
its internal processing. HRESULT was C0000005 from line
44 of d:\nt\com\com1x\src\events\tier1
\eventsystemobj.cpp. Please contact Microsoft Product
Support Services to report this error.

=========================

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 3/12/2004
Time: 11:23:24 AM
User: N/A
Computer: FRESH
Description:
Faulting application explorer.exe, version 6.0.2800.1106,
faulting module toolbar.dll, version 2.1.1.858, fault
address 0x0000435b.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 65 78 70 ure exp
0018: 6c 6f 72 65 72 2e 65 78 lorer.ex
0020: 65 20 36 2e 30 2e 32 38 e 6.0.28
0028: 30 30 2e 31 31 30 36 20 00.1106
0030: 69 6e 20 74 6f 6f 6c 62 in toolb
0038: 61 72 2e 64 6c 6c 20 32 ar.dll 2
0040: 2e 31 2e 31 2e 38 35 38 .1.1.858
0048: 20 61 74 20 6f 66 66 73 at offs
0050: 65 74 20 30 30 30 30 34 et 00004
0058: 33 35 62 0d 0a 35b.. s

 

[Kaylene aka Taurarian]

http://www.jsiinc.com/subo/tip7100/rh7193.htm
7193 » Corrupted Windows XP system files cause event IDs 1000, 4609, or 1000 in
the Application event log.

 

[Guest]

Great, now how do you un-corrupt the files

----- Kaylene aka Taurarian wrote: ----

http://www.jsiinc.com/subo/tip7100/rh7193.ht
7193 » Corrupted Windows XP system files cause event IDs 1000, 4609, or 1000 i
the Application event log

 

[Adrian Grigorof]

Do the following and hope for the best:
- scan your system for viruses/worms/trojans (if you don't have any, use
http://housecall.trendmicro.com/ and the trojan scanner listed at
http://www.eventid.net/links.asp).
- run chkdsk against all your drives
- reinstall the latest service pack
- obtain all the updates from Microsoft (Windows Update)

See also:
http://www.eventid.net/display.asp?eventid=1000&source=application
http://www.eventid.net/display.asp?eventid=4609&source=