Internet explorer has encountered a problem and needs to close

G

Guest

I have a laptop running windows xp pro, with service pack 2, and internet
explorer 6.0.2900.2180
I can open internet explorer ok, and enter a website, but if i want to go to
another page on the same website and sertainly a secure page then I get the
error message:- Internet explorer has encountered a problem and needs to
close - If you were working on somthing the information you were working on
might be lost
The error signature is:-
Appname: Iexplore.exe
Appver: 6.0.2900.2180
Modname: unknown
Modver: 0.0.0.0
Offset: 53454e49
This is stopping me working on the internet, I have had to wright this on
another computer because when I press new the error message comes up because
it is going to a secure page.
I have tried several remedies I have found in these discussion groups
without success.
Can anyone help ??
 
F

Frank Saunders, MS-MVP IE/OE

Green Dragon said:
I have a laptop running windows xp pro, with service pack 2, and internet
explorer 6.0.2900.2180
I can open internet explorer ok, and enter a website, but if i want to go
to
another page on the same website and sertainly a secure page then I get
the
error message:- Internet explorer has encountered a problem and needs to
close - If you were working on somthing the information you were working
on
might be lost
The error signature is:-
Appname: Iexplore.exe
Appver: 6.0.2900.2180
Modname: unknown
Modver: 0.0.0.0
Offset: 53454e49
This is stopping me working on the internet, I have had to wright this on
another computer because when I press new the error message comes up
because
it is going to a secure page.
I have tried several remedies I have found in these discussion groups
without success.
Can anyone help ??

" I have tried several remedies I have found in these discussion groups
without success."
Not very informative.

First eliminate any spyware.
What You Should Know About Spyware
http://www.microsoft.com/athome/security/spyware/devioussoftware.mspx

CAUTION!!!!! Removing some spyware can damage the Winsock stact. Before
you try to remove spyware using any of these programs , download a copy of
LSP-Fix - a free program to repair damaged Winsock 2 stacks (all Windows
versions)
http://www.cexx.org/lspfix.htm
Winsockfix for W95, W98, ME, NT, 2000, XP
http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
Directions here: http://www.tacktech.com/display.cfm?ttid=257
WinXP:
Get WinSockxpFix
http://www.spychecker.com/program/winsockxpfix.html
How to Reset Internet Protocol (TCP/IP) in Windows XP
http://support.microsoft.com/kb/299357
In WinXP SP2: You can fix Winsock by going to Start | Run and typing
CMD
In the command window type
netsh winsock reset

See
Dealing with Unwanted Malware, Parasites, Toolbars and Search Engines
http://mvps.org/winhelp2002/unwanted.htm

Note that AdAware and SpyBot S & D will each catch some things the other
won't. Also, each needs to be updated with the program's update function
before every use, even when just downloaded. There's also a lot more to do
than just those two programs. CWShredder is also available here:
http://www.intermute.com/products/cwshredder
**Post your HijackThis log to
http://forums.spywareinfo.com/
http://forums.tomcoyote.org/
http://castlecops.com/forum67.html
http://www.wilderssecurity.com/ or the Spyware forum at
http://forum.aumha.org/viewforum.php?f=30 for expert analysis, not here.**
Alternative download pages for Ad-Aware, Spybot, HijackThis and CWShredder
may be found on this page:
http://aumha.org/a/parasite.htm.

See this link for information about malware:
http://arstechnica.com/articles/paedia/malware.ars

If nothing there helps, please post back to this thread.

--
Frank Saunders, MS-MVP, IE/OE
Please respond in Newsgroup only. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com./athome/security/protect/default.aspx
http://defendingyourmachine.blogspot.com/
 
R

Robert Aldwinckle

Offset: 53454e49
I have tried several remedies I have found in these discussion groups
without success.

Such as?

The symptom is obviously due to third-party interference.
E.g. your crash offset when interpreted as ASCII characters
spells SENI Does that give you a clue?

If you were interested you could probably get more such clues
from the Stack Back Trace and the Raw Stack Dump for the
crashing task in drwtsn32.log (search up from the bottom and
look for FAULT -> ) Normally that prefixes the crash address
but in your case the crash address is bogus. Still I think that XP
preserves that formatting convention even though there isn't
any valid data to associate with it. (Previous OS did not do this;
in that case you could search (up) for an EIP= prefix to the crash
address and then similarly page down to find the sections about
the Stack.)


HTH

Robert Aldwinckle
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top