Nope, even though the closing error went away again even after signing in, it
came back yet again when I posted the last message, and all the Roboforn
addons are still showing disabled. What is it about posting a message that
would change thngs?

"DCL" wrote:

> Okay, well after submitting the last post I closed IE7... and got the closing
> error again. After some trial and error, it appears it is coming from
> Roboform, after I use the fill forms to sign in here. As noted previously,
> even though I disabled addons via run, the ones I normally use still appeared
> to be active including Roboform. Now, I have disabled them via IE7's
> tools>manage addons, and for the moment I am not getting the closing error.
> What is interesting is that the Roboform fill still is working, and I use it
> to sign in.
>
> I guess I will see what happens after I post this message...
>
> "DCL" wrote:
>
> > Robin and Robert, Thank you, thank you. Disabling the addons in the manner
> > you noted did fix the error when closing IE7. I am not sure what was
> > disabled, because when I go into Tools>Manage Addons now I do not see
> > anything disabled that I had not already disabled, and so far the ones I
> > normally use seem to work.
> >
> > Robin, after fixing the IE7 closing error and following your method, I
> > installed KB927891-v3-x86-ENU.exe which appeared to install fine. Next I
> > followed your examples for installing the MU update. This did not work. I
> > still get the same error. I did not try installing it via safe mode yet, but
> > will give it a try tonight after work. I will let you know how that goes.
> >
> > Again, thank you both for your time. I relish not having that error box show
> > up every time I close IE7 !
> >
> > "Robert Aldwinckle" wrote:
> >
> > > (cross-post added to IE NG)
> > > "DCL" <DCL@discussions.microsoft.com> wrote in message
> > > news:917EED85-357C-451A-B9BB-60DD9E269566@microsoft.com
> > > ....
> > > > Every time I close IE7 I get an error saying: "The instruction at 0x43666454
> > > > referenced at 0x00000148 could not be read."
> > >
> > > Interpreting the crash "address" as ASCII yields: CfdT
> > > It could be a coincidence but I suspect it represents stack corruption.
> > > Depending on the byte order it was stored by it may be seen
> > > as a permutation of those letters elsewhere in a dump. Etc.
> > >
> > > Usually we guess that this is a symptom of interference by third-party
> > > programs and with IE7 suggest that you try running first with No Add-ons
> > > e.g. Run... iexplore.exe -nohome -extoff and see if closing that
> > > causes the symptom. Then try being selective about which Add-ons
> > > you leave enabled in order to figure out which one might be the problem
> > > cause. Etc.
> > >
> > > Good luck
> > >
> > > Robert Aldwinckle