SysFader: iexplore.exe Application Error

[Guest]

When clicking on certain links on websites, seemingly just links that open to
articles, I get the following message:

SysFader: iexplore.exe Application Error

The instruction at "0x0c41fdb3" referenced memory at "0x00000044." The
memory could not be "read."

I recently upgraded to IE 7 and also removed Norton SystemWorks and added
Lavasofts Anti-Virus/Spam/Adware package.

Thanks so much.

 

[Guest]

Yes, I have a similar prob that cropped up a couple of days ago....get an
error message "0x0571f3d3 referenced memory at "0x00000004". The memory could
not be read...this appears after passwords to read/access articles have been
accepted.Would love to hear from anyone who can help.Cheers

 

[Guest]

I too had this problem crop up over this past weekend. I hadn't turned on my
computer for a few days and, now, about 20% of the time the browser crashes
right when I load my homepage. If I switch my homepage to another page, then
it doesn't crash - I may not have tested it thoroughly enough, though.

In any case, I checked my Transition Effects settings (Display Properties >
Appearance Tab > Effects... and I noticed something odd: The Fade Effect was
listed in the drop-down menu, but the check box was neither checked nor
unchecked. It's one of those half-checked check boxes, like when you select
multiple cells in Excel when some of them share a property and some don't. I
clicked it until the Fade Effect was back to checked.

I've tried open Internet Explorer a number of times now and the problem
doesn't seem to be cropping up anymore. I don't know if this is the answer,
but check your Fade Effect settings and see what's there.

Good luck

 

[jack]

several things it can be, in my case

I went to IE Tools, Internet Options, Advanced Tab, uncheck 'Enable
Page Transitions' under the 'Browsing' section

it stopped immediately and hasn't been back.

Sometimes it is spyware issue.

 

[Guest]

I have this identical and annoying problem occurring on several web sites.
It's costing me time and money! It seems to me there should be a quicker way
to find the answer to the problem. I hope someone has the answer.

 

[VanguardLH]

Same situation and solved by removing Java 6 updates 7 & 16. I kept Java
6 update 15.

You think sqwk77 is still monitoring that 3-year old thread?