Memory could not be "read"/"written"

The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of seriousness.
My OS is WinXPPro SP2 running on IBM T23 with 1.2GB memory. A solution
would be appreciated.

Do a Google search for memtest86 and run it to see if your memory is ok.

"Chas" wrote:

The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of seriousness.
My OS is WinXPPro SP2 running on IBM T23 with 1.2GB memory. A solution
would be appreciated.

Chas wrote:

The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of seriousness.
My OS is WinXPPro SP2 running on IBM T23 with 1.2GB memory. A solution
would be appreciated.

Are the address references in the error message always the same
("0x01cddd51" for both)?

The reference is circular, in that it implies that an instruction was
trying to read itself. That in turn indicates a possible programming
error in an application program or device driver.

Try shutting down various background tasks and utilities that you may
have running on the computer and see if that changes things.

Is there any consistency in terms of the programs that you are
changing from or to when the error happens?

Changing programs would normally involve substantial changes to the
screen contents. Have you checked for updated video drivers?

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how to achieve "error free RAM." I'd love to take the seriousness out of my problem. If it has nothing to do with Microsoft, I would think they would jump all over the chance to help solve a problem that everyone seems to think is an OS problem (refer to the high number of requests for assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

"Ron Martell" wrote:

Chas wrote:

The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of seriousness.
My OS is WinXPPro SP2 running on IBM T23 with 1.2GB memory. A solution
would be appreciated.

Are the address references in the error message always the same
("0x01cddd51" for both)?
NO. THEY ARE USUALLY DIFFERENT AND MOST EVENTS HAVE DIFFERENT ADDRESSES. I'M A USER AND NOT A DEVELOPER SO MY USUAL FRUSTRATED RESPONSE IS TO TRY TO RECOVER MY WORK RAHTER THAN WORRY ABOUT THE PROBLEM. HOWEVER, THE PERSISTENCE OF THE PROBLEM HAS FINALLY CAPTURED MY ATTENTION.
The reference is circular, in that it implies that an instruction was
trying to read itself. That in turn indicates a possible programming
error in an application program or device driver.

Try shutting down various background tasks and utilities that you may
have running on the computer and see if that changes things.

Is there any consistency in terms of the programs that you are
changing from or to when the error happens? I HAVEN'T BEEN ABLE TO FIND A PATTERN. I AM USUALLY WORKING WITH POWERPOINT, EXCEL, AND WORD OPEN AT THE SAME TIME WITH DATA TRANSFERS GOING BETWEEN. THE PROBLEM SEEMS TO OCCUR WHEN I TRY TO MAKE A TRANSFER "TOO QUICKLY" BEFORE THE PROGRAM I WAS IN HAS STOPPED PROCESSING(???). THE PROBLEM HAD NEVER OCCURRED UNTIL AFTER I INSTALLED THE WXP SP2 PACKAGE. NOW IT OCCURS FREQUENTLY.

Changing programs would normally involve substantial changes to the
screen contents. Have you checked for updated video drivers? i HAVE THE LATEST VIDEO DRIVER AVAILABLE FROM IBM FOR MY T23.

Good luck
THANKS FOR YOUR HELPFULNESS. CHAS
Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

First of all, you do not "achieve" error free Ram. It either is or isn't.
You determine whether yours is or not by running a test such as
memtest86.exe. Ram that is not error free is not a Microsoft problem. The
message you saw is most likely a hardware error. Before proceeding further,
test your memory with one of the many such programs around. If yours is
error free, then post again.
Jim

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive) and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

Thanks for the suggestion. I ran memtest86 through 4 cycles. No errors were
found. Thanks for the suggestion. I now know the problem is not caused by
Ram memory errors.

"Vincent Isabelle" wrote:

Do a Google search for memtest86 and run it to see if your memory is ok.

"Chas" wrote:

The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it would
seem that MS would take a reply and solution with some degree of seriousness.
My OS is WinXPPro SP2 running on IBM T23 with 1.2GB memory. A solution
would be appreciated.

I bought the IBM (at the time) "state of the art" T23 laptop with the full
deck of IBM RAM memory, designed, I assume, by IBM and "certified to work for
the T23" computer and guaranteed for three years (and by no means, cheap).
As I stated in my initial posting, I had no problems until after I updated my
WINXPPro to WinXP SP2. Since I wasn't interested in how cheaply I could get
my product, I went for the "best and most dependable" equipment I could find.
I'm sure I got what I paid for. Now that I have encountered a problem, I'd
like to solve the problem, not defend my past choices that brought me to this
point. By the way, after running memtest86 through 4 cycles, my Ram is
apparently "error free" since all the tests registered without errors each
time. Obviously, now, "error free Ram" is not my problem.
Any helpful suggestions would be appreciated.
Chas

"Richard Urban" wrote:

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive) and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

I have also started getting this error over the last couple of days. Mine
reads...

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

I can understand your frustration at the inane replies you appear to have
received so far. Have you managed to find a fix for it yet? Let me know if
you do. Or if anyone out there actually knows how to fix this problem,
rather than just coming up with inane red herring ideas...

Mary

"Chas" wrote:

I bought the IBM (at the time) "state of the art" T23 laptop with the full
deck of IBM RAM memory, designed, I assume, by IBM and "certified to work for
the T23" computer and guaranteed for three years (and by no means, cheap).
As I stated in my initial posting, I had no problems until after I updated my
WINXPPro to WinXP SP2. Since I wasn't interested in how cheaply I could get
my product, I went for the "best and most dependable" equipment I could find.
I'm sure I got what I paid for. Now that I have encountered a problem, I'd
like to solve the problem, not defend my past choices that brought me to this
point. By the way, after running memtest86 through 4 cycles, my Ram is
apparently "error free" since all the tests registered without errors each
time. Obviously, now, "error free Ram" is not my problem.
Any helpful suggestions would be appreciated.
Chas

"Richard Urban" wrote:

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive) and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

Thanks for your supportive response. Ron Martell's reply was informative but
did not produce a solution. Vincent Isabelle's suggestion eliminated a
possible source of the problem - a bit like "Did you make sure your power was
plugged in?" I can search with a bit more confidence now that I know my
memory doesn't have any errors. At least I know now that I don't have to
purchase "expensive" RAM from Mr. Urban's crucial.com site. However, I still
don't know how to solve the problem. Did your problem begin after the SP2
update or is that simply a coincidence in my case?
Chas

"Mary" wrote:

I have also started getting this error over the last couple of days. Mine
reads...

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

I can understand your frustration at the inane replies you appear to have
received so far. Have you managed to find a fix for it yet? Let me know if
you do. Or if anyone out there actually knows how to fix this problem,
rather than just coming up with inane red herring ideas...

Mary

"Chas" wrote:

I bought the IBM (at the time) "state of the art" T23 laptop with the full
deck of IBM RAM memory, designed, I assume, by IBM and "certified to work for
the T23" computer and guaranteed for three years (and by no means, cheap).
As I stated in my initial posting, I had no problems until after I updated my
WINXPPro to WinXP SP2. Since I wasn't interested in how cheaply I could get
my product, I went for the "best and most dependable" equipment I could find.
I'm sure I got what I paid for. Now that I have encountered a problem, I'd
like to solve the problem, not defend my past choices that brought me to this
point. By the way, after running memtest86 through 4 cycles, my Ram is
apparently "error free" since all the tests registered without errors each
time. Obviously, now, "error free Ram" is not my problem.
Any helpful suggestions would be appreciated.
Chas

"Richard Urban" wrote:

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive) and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

Hi... I know the other respondees were trying to be helpful but as you
pointed out in one of your posts, this problem seems to be affecting quite a
few people... and there are a few recent posts which is very suspect. I have
had my PC for a few years now and upgraded to the SP2 software ages ago and
not had this problem before. At first I ignored it but today it really
annoyed me so I had a search round the Knowledge Base and then the forum,
where I found your post amongst others. In my case I can't understand what
would have triggered this problem as I am using my PC in the way I always
have and have not installed any new software (that I'm aware of!), so it's a
bit of a mystery. Until I saw all the posts here I did wonder if it was a
virus of some sort but I run AVG software daily and that's not picked
anything up. Do Microsoft actually read through these posts do you think?
Not sure how to go about bringing it to their attention. Although I did come
across Article 899811 in the Knowledge Base... you might want to check it out
if you haven't already... I wonder whether this 'Hotfix' of theirs applies
regardless of the address returned in the error message, in which case maybe
that's the way to go. Let me know what you think if you do have a read of it.

Mary

"Chas" wrote:

Thanks for your supportive response. Ron Martell's reply was informative but
did not produce a solution. Vincent Isabelle's suggestion eliminated a
possible source of the problem - a bit like "Did you make sure your power was
plugged in?" I can search with a bit more confidence now that I know my
memory doesn't have any errors. At least I know now that I don't have to
purchase "expensive" RAM from Mr. Urban's crucial.com site. However, I still
don't know how to solve the problem. Did your problem begin after the SP2
update or is that simply a coincidence in my case?
Chas

"Mary" wrote:

I have also started getting this error over the last couple of days. Mine
reads...

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

I can understand your frustration at the inane replies you appear to have
received so far. Have you managed to find a fix for it yet? Let me know if
you do. Or if anyone out there actually knows how to fix this problem,
rather than just coming up with inane red herring ideas...

Mary

"Chas" wrote:

I bought the IBM (at the time) "state of the art" T23 laptop with the full
deck of IBM RAM memory, designed, I assume, by IBM and "certified to work for
the T23" computer and guaranteed for three years (and by no means, cheap).
As I stated in my initial posting, I had no problems until after I updated my
WINXPPro to WinXP SP2. Since I wasn't interested in how cheaply I could get
my product, I went for the "best and most dependable" equipment I could find.
I'm sure I got what I paid for. Now that I have encountered a problem, I'd
like to solve the problem, not defend my past choices that brought me to this
point. By the way, after running memtest86 through 4 cycles, my Ram is
apparently "error free" since all the tests registered without errors each
time. Obviously, now, "error free Ram" is not my problem.
Any helpful suggestions would be appreciated.
Chas

"Richard Urban" wrote:

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive) and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

Your description of the problems you are having is somewhat similar to mine.
However, mine don't appear to have any connection to Internet 6. I am
usually switching between MS Word, Excel, and Powerpoint when I have the
problem. I don't know that they cause it, because there is a lot of
background activity as well. I read the article to which you refer but
decided to observe their caution about using the fix since my problem did not
appear to be associated with Internet 6. I think the address must be
incidental, because the address specification in my messages seem to change
from one time to the next. I think the problem must be related to some kind
of floating program instruction. That's just a guess, but I can't think of
any other possibility that makes any kind of sense. I hope some
knowledgeable person gets into this however, because it is incredibly
frustrating and also quite costly in time and effort when I lose work.
Chas

"Mary" wrote:

Hi... I know the other respondees were trying to be helpful but as you
pointed out in one of your posts, this problem seems to be affecting quite a
few people... and there are a few recent posts which is very suspect. I have
had my PC for a few years now and upgraded to the SP2 software ages ago and
not had this problem before. At first I ignored it but today it really
annoyed me so I had a search round the Knowledge Base and then the forum,
where I found your post amongst others. In my case I can't understand what
would have triggered this problem as I am using my PC in the way I always
have and have not installed any new software (that I'm aware of!), so it's a
bit of a mystery. Until I saw all the posts here I did wonder if it was a
virus of some sort but I run AVG software daily and that's not picked
anything up. Do Microsoft actually read through these posts do you think?
Not sure how to go about bringing it to their attention. Although I did come
across Article 899811 in the Knowledge Base... you might want to check it out
if you haven't already... I wonder whether this 'Hotfix' of theirs applies
regardless of the address returned in the error message, in which case maybe
that's the way to go. Let me know what you think if you do have a read of it.

Mary

"Chas" wrote:

Thanks for your supportive response. Ron Martell's reply was informative but
did not produce a solution. Vincent Isabelle's suggestion eliminated a
possible source of the problem - a bit like "Did you make sure your power was
plugged in?" I can search with a bit more confidence now that I know my
memory doesn't have any errors. At least I know now that I don't have to
purchase "expensive" RAM from Mr. Urban's crucial.com site. However, I still
don't know how to solve the problem. Did your problem begin after the SP2
update or is that simply a coincidence in my case?
Chas

"Mary" wrote:

I have also started getting this error over the last couple of days. Mine
reads...

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

I can understand your frustration at the inane replies you appear to have
received so far. Have you managed to find a fix for it yet? Let me know if
you do. Or if anyone out there actually knows how to fix this problem,
rather than just coming up with inane red herring ideas...

Mary

"Chas" wrote:

I bought the IBM (at the time) "state of the art" T23 laptop with the full
deck of IBM RAM memory, designed, I assume, by IBM and "certified to work for
the T23" computer and guaranteed for three years (and by no means, cheap).
As I stated in my initial posting, I had no problems until after I updated my
WINXPPro to WinXP SP2. Since I wasn't interested in how cheaply I could get
my product, I went for the "best and most dependable" equipment I could find.
I'm sure I got what I paid for. Now that I have encountered a problem, I'd
like to solve the problem, not defend my past choices that brought me to this
point. By the way, after running memtest86 through 4 cycles, my Ram is
apparently "error free" since all the tests registered without errors each
time. Obviously, now, "error free Ram" is not my problem.
Any helpful suggestions would be appreciated.
Chas

"Richard Urban" wrote:

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive) and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads, apparently
depending on whether it was "reading" or "writing". From the volume of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea how
to achieve "error free RAM." I'd love to take the seriousness out of my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests for
assistance on this problem.) Please, th4e steps to the solution. Thanks!
Chas

It is up to you, but the IBM T23 computer (2001) was NOT designed for
Windows XP. Windows XP uses the RAM much more aggressively than the older
operating systems do.

I wish I had a hundred bucks for every computer I serviced that ran just
fine with Windows 98, Windows ME or Windows 2000, and then crapped out when
trying to load (or work with) Windows XP. I would go on a nice 15 day
vacation to some foreign country.

In a vast majority of the cases, new RAM solved the problem.

But as I have said - it's up to you..................

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...
I bought the IBM (at the time) "state of the art" T23 laptop with the full
deck of IBM RAM memory, designed, I assume, by IBM and "certified to work
for
the T23" computer and guaranteed for three years (and by no means, cheap).
As I stated in my initial posting, I had no problems until after I updated
my
WINXPPro to WinXP SP2. Since I wasn't interested in how cheaply I could
get
my product, I went for the "best and most dependable" equipment I could
find.
I'm sure I got what I paid for. Now that I have encountered a problem,
I'd
like to solve the problem, not defend my past choices that brought me to
this
point. By the way, after running memtest86 through 4 cycles, my Ram is
apparently "error free" since all the tests registered without errors each
time. Obviously, now, "error free Ram" is not my problem.
Any helpful suggestions would be appreciated.
Chas

"Richard Urban" wrote:

Replace the RAM with RAM that is "certified" to work with your system, or
your money back.

Many RAM manufacturers have this guarantee, as long as you buy the RAM
indicated as being "of choice" compatible when running the RAM
configurator
on their web page.

Yes, this type of RAM is more expensive (sometimes much more expensive)
and
many people want to go cheap. They get what they pay for.

WWW.crucial.com



--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"Chas" wrote in message
...


"Richard Urban" wrote:


"Chas" wrote in message
...
The instruction at "0x01cddd51" referenced memory
at "0x01cddd51". The memory could not be "read"
This note appears frequently, and always at the most inopportune
time
(generally when I'm switching from one program to the other and just
before I
have saved my work). The system always freezes or reloads,
apparently
depending on whether it was "reading" or "writing". From the volume
of
requests for assistance on this problem, (some dating from 2004) it
would
seem that MS would take a reply and solution with some degree of
seriousness.


Error free RAM will take the seriousness out of your problem! It has
nothing
to do with Microsoft.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

Oviously I don't know as much as you thought I knew. I have no idea
how
to achieve "error free RAM." I'd love to take the seriousness out of
my
problem. If it has nothing to do with Microsoft, I would think they
would jump all over the chance to help solve a problem that everyone
seems to think is an OS problem (refer to the high number of requests
for
assistance on this problem.) Please, th4e steps to the solution.
Thanks!
Chas