Read & Write Errors

  • Thread starter Thread starter Me2Ewe
  • Start date Start date
M

Me2Ewe

Can someone tell me what the following error message means:

The instruction at "0x6a2a2fec" referenced memory at "0x0000000c". The
memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.



I have has a few others also here is an example:

Error Message When Shutting Down
Aspnet_state.exe-Application Error

The instruction at "0x6a2a2fec" referenced memory at "0x00000000".

The memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.

Errors After Booting Up
iTouch.exe - Application Error

The instruction at "0x008c286b" referenced memory at "0x0006442a".

The memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.



iTouch.exe - Application Error

The instruction at "0x77c2ba4e" referenced memory at "0x000641bc".

The memory could not be "written".

Click on OK to terminate the program.

Thanks for any help you can give me

B
 
Me2Ewe said:
Can someone tell me what the following error message means:

The instruction at "0x6a2a2fec" referenced memory at "0x0000000c". The
memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.
Click to expand...
run a ram test or try different RAM
 
Me2Ewe said:
Can someone tell me what the following error message means:

The instruction at "0x6a2a2fec" referenced memory at "0x0000000c". The
memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.



I have has a few others also here is an example:

Error Message When Shutting Down
Aspnet_state.exe-Application Error

The instruction at "0x6a2a2fec" referenced memory at "0x00000000".

The memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.

Errors After Booting Up
iTouch.exe - Application Error

The instruction at "0x008c286b" referenced memory at "0x0006442a".

The memory could not be "read".

Click on OK to terminate the program.

Click on CANCEL to debug the program.



iTouch.exe - Application Error

The instruction at "0x77c2ba4e" referenced memory at "0x000641bc".

The memory could not be "written".

Click on OK to terminate the program.

Thanks for any help you can give me

B
Click to expand...

If you are getting these types of errors randomly and involving different
applications (as you describe) then I'm inclined to suspect a problem with
faulty memory.

Microsoft has a free tool to diagnose these problems. It's available at
http://oca.microsoft.com/en/windiag.asp (requires creation of a boot disk
because the tool cannot run while Windows is running... instructions are on
the web page) - If the tool reports any failures, it's probably time to
replace one or more memory modules in your computer. You can easily do this
yourself if you are comfortable with PC hardware, otherwise it's a fairly
routine job for a qualified tech.

This is just a hunch based on my experience with these types of errors.
Other possible causes include corrupted system files and problems with the
hard drive.
 
Wed, 7 Dec 2005 19:57:11 -0500 from <"Colin Nash [MVP]" <cnash x@x
mvps.org>>:
Microsoft has a free tool to diagnose these problems. It's available at
http://oca.microsoft.com/en/windiag.asp (requires creation of a boot disk
because the tool cannot run while Windows is running... instructions are on
the web page) - If the tool reports any failures, it's probably time to
replace one or more memory modules in your computer.
Click to expand...

Between this and www.memtest.org, which do the experts think is
better?
 
Stan Brown said:
Wed, 7 Dec 2005 19:57:11 -0500 from <"Colin Nash [MVP]" <cnash x@x
mvps.org>>:

Between this and www.memtest.org, which do the experts think is
better?

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://OakRoadSystems.com/
"If there's one thing I know, it's men. I ought to: it's
been my life work." -- Marie Dressler, in /Dinner at Eight/
Click to expand...


I find the Microsoft one easier to use, and the documentation on the
Microsoft web site is probably easier for a less experienced user to
understand (the main memtest page is mostly full of talk about their project
team, their license agreement and lists of chipsets, while Microsoft's
actually attempts to describe how to use the tool and the suggested method
of troubleshooting.) That said, I think both tools are at the same level of
reliability.
 
Thanks for the info already, but it didn't work I didn't run Mutest I did
run windiagand it showed no errors in about 3 seconds. So it must be
something else.
It shows up every time I shut down.
 
Stan said:
Wed, 7 Dec 2005 19:57:11 -0500 from <"Colin Nash [MVP]" <cnash x@x
mvps.org>>:



Between this and www.memtest.org, which do the experts think is
better?
Click to expand...

I use both. They're both pretty good although memtest86 gets updated
frequently. I've seen RAM pass one but not the other.

Steve N.
 
Me2Ewe said:
Thanks for the info already, but it didn't work I didn't run Mutest I did
run windiagand it showed no errors in about 3 seconds. So it must be
something else.
It shows up every time I shut down.
Click to expand...

3 seconds is not nearly long enough, I usually run it for at least 5-10
minutes. Some errors don't show up until the system heats up some.

Steve N.
 
The error test ran all night [6+ hrs] & showed all was well, but now when I
shut down the following appears:



Microsoft Visual C++ Runtime Library

Runtime Error!

Program: C:\Program Files\Common Files\Symantec Shared\ccEvtMgr.exe



R9025



-Pure Virtual Function Call



Close



Thanks

Bruce
 
Thu, 8 Dec 2005 19:27:04 -0500 from <"Colin Nash [MVP]" <cnash x@x
mvps.org>>:
I find the Microsoft one easier to use, and the documentation on the
Microsoft web site is probably easier for a less experienced user to
understand (the main memtest page is mostly full of talk about their project
team, their license agreement and lists of chipsets, while Microsoft's
actually attempts to describe how to use the tool and the suggested method
of troubleshooting.) That said, I think both tools are at the same level of
reliability.
Click to expand...

Thanks! I'll bear it in mind for the future.

For my recent troubles, I ended up using memtest, just because it was
easier to download and burn to a disk. Since my own computer was
flaky, I had to use a public computer where we couldn't install any
programs, which ruled out the Microsoft one.
 
Back
Top