New Error since last Security update

  • Thread starter Thread starter CTI
  • Start date Start date
C

CTI

Since the latest XP security update I get the following error message:

The instruction at 0x0979b90d referenced memory at 0x08501e90 the memory
could not be read.

Is there a fix for this?
 
CTI wrote:
> Since the latest XP security update I get the
> following
> error message:
>
> The instruction at 0x0979b90d referenced memory at
> 0x08501e90 the memory could not be read.
>
> Is there a fix for this?

99.9% sure it's not related to the update.
 
"Poprivet`" . wrote in message
news:%23WQ9qRrPIHA.6036@TK2MSFTNGP03.phx.gbl...
> CTI wrote:
> > Since the latest XP security update I get the
> > following
> > error message:
> >
> > The instruction at 0x0979b90d referenced memory at
> > 0x08501e90 the memory could not be read.
> >
> > Is there a fix for this?
>
> 99.9% sure it's not related to the update.

Then why did he get it after applying the patch(es)
- O Mighty One Who Offers No Evidence To Back Up His
Terse Reply?

>
>
 
Last edited by a moderator:
CTI wrote:
> Since the latest XP security update I get the following error message:
>
> The instruction at 0x0979b90d referenced memory at 0x08501e90 the memory
> could not be read.
>
> Is there a fix for this?

Open Control Panel, Add/Remove Programs, click "Show Updates", scroll
down to the last six and either look at the support information on each,
or just remove them. If that eliminates the error message, reinstall
fresh copies of the updates, or install one-at-a-time to see which one
causes this. If it was a corrupted download of an update, the reinstall
may correct it.

--
Joe =o)
 
Which updates did you install? What are you doing when you get this error?
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L.ORG http://66.39.69.143/

CTI wrote:
> Since the latest XP security update I get the following error message:
>
> The instruction at 0x0979b90d referenced memory at 0x08501e90 the memory
> could not be read.
>
> Is there a fix for this?
 
Back
Top