AOL program error report

[PSRumbagh]

About 50% of my boot-ups produce the error message that AOL 9.1 has
encountered a problem and needs to close down, send or don’t send error
report. The detailed Error message text file that is generated is very large
and contains about 227 KB. All .exe and .dll files mentioned in the report
reference AOL as the program's vendor. I can’t tell if AOL has really
closed down but it comes up within 1 or 2 seconds (normal speed) when I click
on the AOL Icon. I am using WinXP home edition with SP3 on a Compaq Presario
V2000 laptop.

Contacting AOL many times results in no answer except their standard canned
answer: uninstall their software (AOL 9.1) and reinstall it. This action
does nothing to solve the problem. Sending AOL and Microsoft the 227 KB text
file error report results in no action, like they are not interested. The
details (e.g. checksum, software version, software vendor, pe_checksum ...
etc.) in the error report don’t mean much to me as I am not a programmer. I
have some of the error reports saved on disc and could email them to anyone
interested. What to do next?

 

[Malke]

About 50% of my boot-ups produce the error message that AOL 9.1 has
encountered a problem and needs to close down, send or don?t send error
report. The detailed Error message text file that is generated is very
large
and contains about 227 KB. All .exe and .dll files mentioned in the
report
reference AOL as the program's vendor. I can?t tell if AOL has really
closed down but it comes up within 1 or 2 seconds (normal speed) when I
click
on the AOL Icon. I am using WinXP home edition with SP3 on a Compaq
Presario V2000 laptop.

Contacting AOL many times results in no answer except their standard
canned
answer: uninstall their software (AOL 9.1) and reinstall it. This action
does nothing to solve the problem. Sending AOL and Microsoft the 227 KB
text
file error report results in no action, like they are not interested. The
details (e.g. checksum, software version, software vendor, pe_checksum ...
etc.) in the error report don?t mean much to me as I am not a programmer.
I
have some of the error reports saved on disc and could email them to
anyone
interested. What to do next?

Uninstall AOL and leave it uninstalled. Make sure the uninstall also removes
all the AOL services, too. Run>services.msc [OK] to be sure. It is
unnecessary to use AOL software - which has *always* been buggy - to access
AOL mail. Just open a regular browser, go to www.aol.com, and sign in.

Malke

 

[Gerry]

Please post a copy here of the Error Report as it appears in Event
Viewer,

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[mikeyhsd]

it is very possible a timing problem.

access the properties and tell AOL to not start with windows.
then using scheduled tasks tell AOL to start delayed after logon.


(e-mail address removed)



About 50% of my boot-ups produce the error message that AOL 9.1 has
encountered a problem and needs to close down, send or don’t send error
report. The detailed Error message text file that is generated is very large
and contains about 227 KB. All .exe and .dll files mentioned in the report
reference AOL as the program's vendor. I can’t tell if AOL has really
closed down but it comes up within 1 or 2 seconds (normal speed) when I click
on the AOL Icon. I am using WinXP home edition with SP3 on a Compaq Presario
V2000 laptop.

Contacting AOL many times results in no answer except their standard canned
answer: uninstall their software (AOL 9.1) and reinstall it. This action
does nothing to solve the problem. Sending AOL and Microsoft the 227 KB text
file error report results in no action, like they are not interested. The
details (e.g. checksum, software version, software vendor, pe_checksum ....
etc.) in the error report don’t mean much to me as I am not a programmer. I
have some of the error reports saved on disc and could email them to anyone
interested. What to do next?

 

[Ed.]

Try opening AOL and on the Icon Toolbar at the top,
Click on the Settings Icon.
Click on Start-up Settings.
Uncheck "Enable Fast Start".
See if that helps.
it is very possible a timing problem.

access the properties and tell AOL to not start with windows.
then using scheduled tasks tell AOL to start delayed after logon.


(e-mail address removed)



About 50% of my boot-ups produce the error message that AOL 9.1 has
encountered a problem and needs to close down, send or don’t send error
report. The detailed Error message text file that is generated is very large
and contains about 227 KB. All .exe and .dll files mentioned in the report
reference AOL as the program's vendor. I can’t tell if AOL has really
closed down but it comes up within 1 or 2 seconds (normal speed) when I click
on the AOL Icon. I am using WinXP home edition with SP3 on a Compaq Presario
V2000 laptop.

Contacting AOL many times results in no answer except their standard canned
answer: uninstall their software (AOL 9.1) and reinstall it. This action
does nothing to solve the problem. Sending AOL and Microsoft the 227 KB text
file error report results in no action, like they are not interested. The
details (e.g. checksum, software version, software vendor, pe_checksum ...
etc.) in the error report don’t mean much to me as I am not a programmer. I
have some of the error reports saved on disc and could email them to anyone
interested. What to do next?