A long shot?

  • Thread starter Thread starter Chuck Davis
  • Start date Start date
C

Chuck Davis

A club member, Windows XP SP2 and all updates, says that 6 or 8 times a day,
no matter which program he is running, a box opens that says: "The
instruction at "0xO1ac397e" referenced memory at "0x01d8c3e8" the memory
could not be read.

He claims to have run an online memory check and chkdsk with no problems. I
suggested a virus or malware and he claims he has McAfee up to date and no
problems reported. He has run both Ad-Aware and I forget the other one that
he mentioned.

Any guesses?

Thanks in advance.
 
Chuck said:
A club member, Windows XP SP2 and all updates, says that 6 or 8
times a day, no matter which program he is running, a box opens
that says: "The instruction at "0xO1ac397e" referenced memory at
"0x01d8c3e8" the memory could not be read.

He claims to have run an online memory check and chkdsk with no
problems. I suggested a virus or malware and he claims he has
McAfee up to date and no problems reported. He has run both
Ad-Aware and I forget the other one that he mentioned.

Any guesses?

Thanks in advance.
Click to expand...

Use a better memory tester and the hard disk drive manufacturer's diagnostic
tools to really test.
 
Chuck, Microsoft has a Memory Checker and you can also download MemTest.
They are both free. Also, I would
delete the Page File and clean out the Prefetch Folder in C:\Windows.
 
Chuck Davis said:
A club member, Windows XP SP2 and all updates, says that 6 or 8 times a
day, no matter which program he is running, a box opens that says: "The
instruction at "0xO1ac397e" referenced memory at "0x01d8c3e8" the memory
could not be read.

He claims to have run an online memory check and chkdsk with no problems.
I suggested a virus or malware and he claims he has McAfee up to date and
no problems reported. He has run both Ad-Aware and I forget the other one
that he mentioned.

Any guesses?

Thanks in advance.
Click to expand...

Most frequently this is caused by one of three scenarios:

1. Bad RAM. The ram has a bad register.

2. Mis-matched RAM modules; RAM with different SPD timings that causes
errors in RAM intensive DATA transfers. The RAM may pass diagnostic
testing, but the timing issue creates access violations which generate the
message displayed.

3. Occasionally. this can be an indicator of a hard drive that is about to
fail.

Note: This error can also occur on a overclocked system.


Bobby
 
NoNoBadDog! said:
Most frequently this is caused by one of three scenarios:

1. Bad RAM. The ram has a bad register.

2. Mis-matched RAM modules; RAM with different SPD timings that causes
errors in RAM intensive DATA transfers. The RAM may pass diagnostic
testing, but the timing issue creates access violations which generate the
message displayed.

3. Occasionally. this can be an indicator of a hard drive that is about to
fail.

Note: This error can also occur on a overclocked system.


Bobby
Click to expand...

I agree with Bobby. The only thing he did not mention is that
#2 and #3 can occur RANDOMLY to all intents and purposes!
 
Back
Top