IE quite memory error

  • Thread starter Thread starter ComPCs
  • Start date Start date
C

ComPCs

Have just 'cleaned' a machine that was grotesquely infected with all low
life forms of spyware, malware, trojans etc.

However, prior to the 'cleanse', when quitting IE6 (XP Home) the
following error occurs ...

The instruction at ?0x0683458d? referenced memory at ?0x683458d?. The
memory could not be ?read?. Click on Ok to terminate the program

I've cleaned the machine to the best of my ability, and it is definitely
running far better than it was - I hit it with NOD32, ad-aware, S,S&D,
HijackThis, CWShredder, SpywareBlaster, WinPatrol plus Trends online
scanner!

A lot of crap was found, but, the IE6 error is still occurring.

I've googled and can find no reference to the error whatsoever.

I suspect there is still something 'quirky' on the machine, as it does
instigate a dial-up as soon as the GUI loads, but aside from that, an
the error, it runs sooooo smoooooooothly now.

Can anyone throw any light on the error, or how I can go about repairing
IE6 under XP Home?? (URL's on "how to" are fine, i'll blag it from there
on in, but I haven't found anything yet that I find what I feel is
appropriate)

I've tried the Firefox 'conversion' approach, but user not interested as
familiarity is the key, and she wants to stick with IE ... *sigh ...
 
From: "ComPCs" <[email protected]>

|
| Have just 'cleaned' a machine that was grotesquely infected with all low
| life forms of spyware, malware, trojans etc.
|
| However, prior to the 'cleanse', when quitting IE6 (XP Home) the
| following error occurs ...
|
| The instruction at ?0x0683458d? referenced memory at ?0x683458d?. The
| memory could not be ?read?. Click on Ok to terminate the program
|
| I've cleaned the machine to the best of my ability, and it is definitely
| running far better than it was - I hit it with NOD32, ad-aware, S,S&D,
| HijackThis, CWShredder, SpywareBlaster, WinPatrol plus Trends online
| scanner!
|
| A lot of crap was found, but, the IE6 error is still occurring.
|
| I've googled and can find no reference to the error whatsoever.
|
| I suspect there is still something 'quirky' on the machine, as it does
| instigate a dial-up as soon as the GUI loads, but aside from that, an
| the error, it runs sooooo smoooooooothly now.
|
| Can anyone throw any light on the error, or how I can go about repairing
| IE6 under XP Home?? (URL's on "how to" are fine, i'll blag it from there
| on in, but I haven't found anything yet that I find what I feel is
| appropriate)
|
| I've tried the Firefox 'conversion' approach, but user not interested as
| familiarity is the key, and she wants to stick with IE ... *sigh ...

Did you install WinXP SP2 which brings IE to SP2 level ?
 
ComPCs said:
Have just 'cleaned' a machine that was grotesquely infected with all low
life forms of spyware, malware, trojans etc.

However, prior to the 'cleanse', when quitting IE6 (XP Home) the
following error occurs ...

The instruction at ?0x0683458d? referenced memory at ?0x683458d?. The
memory could not be ?read?. Click on Ok to terminate the program

I've cleaned the machine to the best of my ability, and it is definitely
running far better than it was - I hit it with NOD32, ad-aware, S,S&D,
HijackThis, CWShredder, SpywareBlaster, WinPatrol plus Trends online
scanner!

A lot of crap was found, but, the IE6 error is still occurring.

I've googled and can find no reference to the error whatsoever.

I suspect there is still something 'quirky' on the machine, as it does
instigate a dial-up as soon as the GUI loads, but aside from that, an
the error, it runs sooooo smoooooooothly now.

Can anyone throw any light on the error, or how I can go about repairing
IE6 under XP Home?? (URL's on "how to" are fine, i'll blag it from there
on in, but I haven't found anything yet that I find what I feel is
appropriate)

I've tried the Firefox 'conversion' approach, but user not interested as
familiarity is the key, and she wants to stick with IE ... *sigh ...

Check for BHO's and do a repair on the TCP/IP stack.
Something's still in there ... most likely a trojan.
 
Check for BHO's and do a repair on the TCP/IP stack.
Something's still in there ... most likely a trojan.

Bizarrely enough, it *only* does it if the user exits IE6 when in her
Yahoo mail portal.

If she navigates away from such, and goes, say, to the BBC site, and
then closes the browser, no error message.

???
 
Back
Top