2nd request

  • Thread starter Thread starter not a techie
  • Start date Start date
N

not a techie

Not sure if this is proper to do, but my original question went unanswered,
then a zillion others appeared, burying mine! I was worried no one would ever
see it!!
Repeat question....
At first I got this message when I tried to open an email attachment. Now
it's happening when I try to open the net. I have to restart my computer to
get on the net. Can anyone please help me solve this?? This is the error
message:
The instruction at "0x00f02d22" referenced memory at “0x00f02d22â€. The
memory could not be “readâ€.
Click on OK to terminate the program.

Appreciate any and all help!

Sorry if I breached ettiquette here!
 
"not a techie" <notatechie@discussions.microsoft.com> wrote in message
news:9817C504-A86A-4C8D-A4EA-104A31190A87@microsoft.com...
> Not sure if this is proper to do, but my original question went
> unanswered,
> then a zillion others appeared, burying mine! I was worried no one would
> ever
> see it!!
> Repeat question....
> At first I got this message when I tried to open an email attachment. Now
> it's happening when I try to open the net. I have to restart my computer
> to
> get on the net. Can anyone please help me solve this?? This is the error
> message:
> The instruction at "0x00f02d22" referenced memory at "0x00f02d22". The
> memory could not be "read".
> Click on OK to terminate the program.
>
> Appreciate any and all help!
>
> Sorry if I breached ettiquette here!

No breach of ettiquete!

You might have a flawed memory chip or a marginal
contact. Open your PC, then remove your RAM
module(s) and put it/them back in again. If the problem
persists then you may have to ask your friendly computer
dealer to try a new memory module.
 
Thanks Pegasus, but, did you notice my name "not a techie"? Take my what and
do what with it??
I take it I have to open up the back of cpu and look for something. What
does it look like and can I screw it up??

Thanks again!

"Pegasus (MVP)" wrote:

>
> "not a techie" <notatechie@discussions.microsoft.com> wrote in message
> news:9817C504-A86A-4C8D-A4EA-104A31190A87@microsoft.com...
> > Not sure if this is proper to do, but my original question went
> > unanswered,
> > then a zillion others appeared, burying mine! I was worried no one would
> > ever
> > see it!!
> > Repeat question....
> > At first I got this message when I tried to open an email attachment. Now
> > it's happening when I try to open the net. I have to restart my computer
> > to
> > get on the net. Can anyone please help me solve this?? This is the error
> > message:
> > The instruction at "0x00f02d22" referenced memory at "0x00f02d22". The
> > memory could not be "read".
> > Click on OK to terminate the program.
> >
> > Appreciate any and all help!
> >
> > Sorry if I breached ettiquette here!
>
> No breach of ettiquete!
>
> You might have a flawed memory chip or a marginal
> contact. Open your PC, then remove your RAM
> module(s) and put it/them back in again. If the problem
> persists then you may have to ask your friendly computer
> dealer to try a new memory module.
>
>
>
 
Look at the manual that came with your pc (personal computer) and it'll show
you how to open the case and where the RAM is located.

"not a techie" <not a techie@discussions.microsoft.com> wrote in message
news:87C04E0A-B4A7-443F-B834-551DE5AFC598@microsoft.com...
: Thanks Pegasus, but, did you notice my name "not a techie"? Take my what
and
: do what with it??
: I take it I have to open up the back of cpu and look for something. What
: does it look like and can I screw it up??
:
: Thanks again!
:
: "Pegasus (MVP)" wrote:
:
: >
: > "not a techie" <notatechie@discussions.microsoft.com> wrote in message
: > news:9817C504-A86A-4C8D-A4EA-104A31190A87@microsoft.com...
: > > Not sure if this is proper to do, but my original question went
: > > unanswered,
: > > then a zillion others appeared, burying mine! I was worried no one
would
: > > ever
: > > see it!!
: > > Repeat question....
: > > At first I got this message when I tried to open an email attachment.
Now
: > > it's happening when I try to open the net. I have to restart my
computer
: > > to
: > > get on the net. Can anyone please help me solve this?? This is the
error
: > > message:
: > > The instruction at "0x00f02d22" referenced memory at "0x00f02d22". The
: > > memory could not be "read".
: > > Click on OK to terminate the program.
: > >
: > > Appreciate any and all help!
: > >
: > > Sorry if I breached ettiquette here!
: >
: > No breach of ettiquete!
: >
: > You might have a flawed memory chip or a marginal
: > contact. Open your PC, then remove your RAM
: > module(s) and put it/them back in again. If the problem
: > persists then you may have to ask your friendly computer
: > dealer to try a new memory module.
: >
: >
: >
 
not a techie wrote:
> Thanks Pegasus, but, did you notice my name "not a techie"? Take my what and
> do what with it??
> I take it I have to open up the back of cpu and look for something.

Yes:

> What does it look like

A long narrow circuit board (or two), on the motherboard, with a bunch
of chips lined up.

This is a pic of memory sticks, but not necessarily the type you use,
just the first page I selected:
http://www.crucial.com/store/listmodule.aspx?family=SDRAM&tabid=SDRAM,+PC133

> and can I screw it up??

Yes, so:

- Shut down the computer.
- Turn power strip off, but leave the computer plugged in. If no power
strip, unplug the computer.
- Open the case.
- Don't wear a sweater, don't move around excessively. Touch the case
occasionally.
- Remove the memory stick/s by depressing the two plastic levers at
either end of the stick.
- Press it back in being careful not to bend the stick excessively.

Close the case, plug back in, and try again.

> "Pegasus (MVP)" wrote:
>
>> "not a techie" <notatechie@discussions.microsoft.com> wrote in message
>> news:9817C504-A86A-4C8D-A4EA-104A31190A87@microsoft.com...
>>> Not sure if this is proper to do, but my original question went
>>> unanswered,
>>> then a zillion others appeared, burying mine! I was worried no one would
>>> ever
>>> see it!!
>>> Repeat question....
>>> At first I got this message when I tried to open an email attachment. Now
>>> it's happening when I try to open the net. I have to restart my computer
>>> to
>>> get on the net. Can anyone please help me solve this?? This is the error
>>> message:
>>> The instruction at "0x00f02d22" referenced memory at "0x00f02d22". The
>>> memory could not be "read".
>>> Click on OK to terminate the program.
>>>
>>> Appreciate any and all help!
>>>
>>> Sorry if I breached etiquette here!
>> No breach of etiquette!
>>
>> You might have a flawed memory chip or a marginal
>> contact. Open your PC, then remove your RAM
>> module(s) and put it/them back in again. If the problem
>> persists then you may have to ask your friendly computer
>> dealer to try a new memory module.

--
Joe =o)
 
not a techie wrote:
> Not sure if this is proper to do, but my original question went unanswered,
> then a zillion others appeared, burying mine! I was worried no one would ever
> see it!!
> Repeat question....
> At first I got this message when I tried to open an email attachment. Now
> it's happening when I try to open the net. I have to restart my computer to
> get on the net. Can anyone please help me solve this?? This is the error
> message:
> The instruction at "0x00f02d22" referenced memory at “0x00f02d22â€. The
> memory could not be “readâ€.
> Click on OK to terminate the program.
>
> Appreciate any and all help!
>
> Sorry if I breached ettiquette here!
>
>


Such memory errors are very often indicative of defective RAM.
Start with testing the RAM. You might try MemTest86:
http://www.memtest86.com/ It's free. Then you can download and use the
hard drive maufacturer's diagnostic utility to test the hard drive.


--

Bruce Chambers

Help us help you:
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot
 
You guys are the best! Thanks so much. I'll see what I can do
Thanks again!

"Bruce Chambers" wrote:

> not a techie wrote:
> > Not sure if this is proper to do, but my original question went unanswered,
> > then a zillion others appeared, burying mine! I was worried no one would ever
> > see it!!
> > Repeat question....
> > At first I got this message when I tried to open an email attachment. Now
> > it's happening when I try to open the net. I have to restart my computer to
> > get on the net. Can anyone please help me solve this?? This is the error
> > message:
> > The instruction at "0x00f02d22" referenced memory at “0x00f02d22â€. The
> > memory could not be “readâ€.
> > Click on OK to terminate the program.
> >
> > Appreciate any and all help!
> >
> > Sorry if I breached ettiquette here!
> >
> >
>
>
> Such memory errors are very often indicative of defective RAM.
> Start with testing the RAM. You might try MemTest86:
> http://www.memtest86.com/ It's free. Then you can download and use the
> hard drive maufacturer's diagnostic utility to test the hard drive.
>
>
> --
>
> Bruce Chambers
>
> Help us help you:
> http://www.catb.org/~esr/faqs/smart-questions.html
>
> They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety. ~Benjamin Franklin
>
> Many people would rather die than think; in fact, most do. ~Bertrand Russell
>
> The philosopher has never killed any priests, whereas the priest has
> killed a great many philosophers.
> ~ Denis Diderot
>
 
On Dec 13, 12:17 pm, Bruce Chambers <bchamb...@cable0ne.n3t> wrote:

> The philosopher has never killed any priests, whereas the priest has
> killed a great many philosophers.
> ~ Denis Diderot

Welcome to my killfile, moron.
 
On 15 Dec 2007 01:06:05 -0600, Plato <|@|.|> wrote:

> =?Utf-8?B?bm90IGEgdGVjaGll?= wrote:
> >
> > At first I got this message when I tried to open an email attachment. Now
>
> Dont open email attachments unless you are expecinging theml


That statement implies that it is safe to open attachments that you
are expecting. That is *not* true.

Even if you are expecting an attachment from your best and most
-trusted friend, if your friend is infected with a virus and doesn't
know it, the attachment may also be infected, and if you open it, you
are at risk of getting infected. Running an anti-virus program reduces
the risk, but does *not* eliminate it.

The safest rule, and the one that I follow myself, is not to open
E-mail attachments at all.

--
Ken Blake, Microsoft MVP Windows - Shell/User
Please Reply to the Newsgroup
 
Ken Blake, MVP wrote:
>
> > > At first I got this message when I tried to open an email attachment. Now
> >
> > Dont open email attachments unless you are expecinging theml
>
> That statement implies that it is safe to open attachments that you
> are expecting. That is *not* true.
>
> Even if you are expecting an attachment from your best and most
> -trusted friend, if your friend is infected with a virus and doesn't
> know it, the attachment may also be infected, and if you open it, you
> are at risk of getting infected. Running an anti-virus program reduces
> the risk, but does *not* eliminate it.
>
> The safest rule, and the one that I follow myself, is not to open
> E-mail attachments at all.

I save them to a folder, then scan them first.




--
http://www.bootdisk.com/
 
Plato wrote:
> Ken Blake, MVP wrote:
>>>> At first I got this message when I tried to open an email attachment. Now
>>> Don't open email attachments unless you are expecting them.
>> That statement implies that it is safe to open attachments that you
>> are expecting. That is *not* true.
>>
>> Even if you are expecting an attachment from your best and most
>> -trusted friend, if your friend is infected with a virus and doesn't
>> know it, the attachment may also be infected, and if you open it, you
>> are at risk of getting infected. Running an anti-virus program reduces
>> the risk, but does *not* eliminate it.
>>
>> The safest rule, and the one that I follow myself, is not to open
>> E-mail attachments at all.
>
> I save them to a folder, then scan them first.

That's a very good practice. The only addition, and I suspect you do
this, I wait a week so my a/v definitions have a chance to catch up to
any malware recently created.

Maybe we shouldn't warn so many people.. we need someone to find and
report the malware so the a/v companies can find it in-the-wild. Just
kidding, but someone's going to fall for it!

Actually I save the whole email and open the questionable attachment
later. It recently paid off when an email, supposedly from one of my
brothers, had a subject about "Trip Plans". We had recently discussed
vacationing together, so it seemed plausible. There was an attached
..zip file. I opened the file and saw that it contained a. executable.
That seemed strange, so I moved the email to my "Purgatory" folder, and
emailed my brother about the .zip file. I never got an answer, and
about five days later I started to open the email again to look at the
header, etc., and Avast! went crazy, warning that a virus had been
detected. Conditions were just right, and I almost fell for that one.

--
Joe =o)
 
On 16 Dec 2007 00:18:04 -0600, Plato <|@|.|> wrote:

> Ken Blake, MVP wrote:
> >
> > > > At first I got this message when I tried to open an email attachment. Now
> > >
> > > Dont open email attachments unless you are expecinging theml
> >
> > That statement implies that it is safe to open attachments that you
> > are expecting. That is *not* true.
> >
> > Even if you are expecting an attachment from your best and most
> > -trusted friend, if your friend is infected with a virus and doesn't
> > know it, the attachment may also be infected, and if you open it, you
> > are at risk of getting infected. Running an anti-virus program reduces
> > the risk, but does *not* eliminate it.
> >
> > The safest rule, and the one that I follow myself, is not to open
> > E-mail attachments at all.
>
> I save them to a folder, then scan them first.


That's fine, and certainly good to do. However, people should be aware
that that *reduces* the risk; it doesn't eliminate it. Anti-virus
programs are never perfect, and can not be perfect.

To repeat, the safest rule is not to open E-mail attachments at all.

--
Ken Blake, Microsoft MVP Windows - Shell/User
Please Reply to the Newsgroup
 
On Sun, 16 Dec 2007 10:09:56 -0500, Elmo <elmogeek@iglou.invalid>
wrote:

> Plato wrote:
> > Ken Blake, MVP wrote:
> >>>> At first I got this message when I tried to open an email attachment. Now
> >>> Don't open email attachments unless you are expecting them.
> >> That statement implies that it is safe to open attachments that you
> >> are expecting. That is *not* true.
> >>
> >> Even if you are expecting an attachment from your best and most
> >> -trusted friend, if your friend is infected with a virus and doesn't
> >> know it, the attachment may also be infected, and if you open it, you
> >> are at risk of getting infected. Running an anti-virus program reduces
> >> the risk, but does *not* eliminate it.
> >>
> >> The safest rule, and the one that I follow myself, is not to open
> >> E-mail attachments at all.
> >
> > I save them to a folder, then scan them first.
>
> That's a very good practice. The only addition, and I suspect you do
> this, I wait a week so my a/v definitions have a chance to catch up to
> any malware recently created.


That's good to do, and reduces the risk still further. But again, it
doesn't eliminate it.

--
Ken Blake, Microsoft MVP Windows - Shell/User
Please Reply to the Newsgroup
 
Ken Blake, MVP wrote:
>
> > > The safest rule, and the one that I follow myself, is not to open
> > > E-mail attachments at all.
> >
> > I save them to a folder, then scan them first.
>
> That's fine, and certainly good to do. However, people should be aware
> that that *reduces* the risk; it doesn't eliminate it. Anti-virus
> programs are never perfect, and can not be perfect.
>
> To repeat, the safest rule is not to open E-mail attachments at all.

Grin. I dont even save email attachements from my Mom. No matter what...






--
http://www.bootdisk.com/
 
Elmo wrote:
>
> >> The safest rule, and the one that I follow myself, is not to open
> >> E-mail attachments at all.
> >
> > I save them to a folder, then scan them first.
>
> That's a very good practice. The only addition, and I suspect you do
> this, I wait a week so my a/v definitions have a chance to catch up to
> any malware recently created.

I cant argue with that. I suppose I am very conservative, and in the
first place dont even download most attachements.










--
http://www.bootdisk.com/
 
Back
Top