Memory could not be "read"/"written"

I am going to pay more attention to exactly when it happens and what
applications are running when it does. It's always about finding a pattern
with these things so the problem can be re-created. IE was the application I
was using yesterday but because it happens intermittently I really can't
remember if that was the case on previous occasions. To be honest I'm hoping
it will just go away but that's just wishful thinking on my part, I know.
Mary


"Chas" wrote:

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

I strongly suggest that you not try the "fix" described in the KB article. I
became so frustrated with the recurring memory problem that I decided to
"take the risk" that the fix might solve my problem as well since no one
seems to know what's causing the problem anyway. Unfortunately, it didn't
solve my problem, but did create other problems that I'm still trying to sort
out and correct. Fortunately I had a restore available so it wasn't a total
disaster. Microsoft did acknowledge that they are aware of the problem, but
"just wait until a fix comes out." At times like this, Linux doesn't look so
bad after all.
Chas

"Mary" wrote:

I am going to pay more attention to exactly when it happens and what
applications are running when it does. It's always about finding a pattern
with these things so the problem can be re-created. IE was the application I
was using yesterday but because it happens intermittently I really can't
remember if that was the case on previous occasions. To be honest I'm hoping
it will just go away but that's just wishful thinking on my part, I know.
Mary


"Chas" wrote:

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

Thanks for letting me know about the not so hot Hotfix! Hope you have
managed to sort the new problems you were left with after applying it. How
annoying, not to mention time-consuming, for you. I will leave well alone
until MS finally issue a fix. It does seem it's causing you more chaos than
me. All very strange.
Mary

"Chas" wrote:

I strongly suggest that you not try the "fix" described in the KB article. I
became so frustrated with the recurring memory problem that I decided to
"take the risk" that the fix might solve my problem as well since no one
seems to know what's causing the problem anyway. Unfortunately, it didn't
solve my problem, but did create other problems that I'm still trying to sort
out and correct. Fortunately I had a restore available so it wasn't a total
disaster. Microsoft did acknowledge that they are aware of the problem, but
"just wait until a fix comes out." At times like this, Linux doesn't look so
bad after all.
Chas

"Mary" wrote:

I am going to pay more attention to exactly when it happens and what
applications are running when it does. It's always about finding a pattern
with these things so the problem can be re-created. IE was the application I
was using yesterday but because it happens intermittently I really can't
remember if that was the case on previous occasions. To be honest I'm hoping
it will just go away but that's just wishful thinking on my part, I know.
Mary


"Chas" wrote:

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

"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.

Hey Chas & Mary,

I unfortunately have the same irritating problem.
My problem occurs at shutdown or restart only, and usually involves my PCI
wireless adapter software (Linksys WMP54GS).
I have about 5 of these windows, all specifying different memory locations,
appear sequentially upon shutdown/restart.

I also have a problem with the program ccApp, which always delays in closing
upon shutdown/restart. I always have to select "End Now" to hasten the
process.

Anyway, I've also run the memtest utility (error-free), as well as several
Adware detection utilities and Norton AntiVirus on a daily basis.
Nothing found....nothing corrected as of yet.

I am growing endlessly weary of this utter annoyance.
I sure hope I can eventually pinpoint the problem.

If it is indeed an OS issue w/ SP2, I surely hope they rectify the problem
ASAP.
I have Win XP Media Center Edition 2005 (with all rollup updates/Microsoft
updates applied).

I check for Norton updates on a daily basis.

My Linksys driver (as well as all others) are the most up-to-date (this I
can verify because I just re-formatted my drive and performed clean installs
of the OS and ALL programs and drivers).

All relevant drivers were downloaded and installed yesterday.
I have no unknown devices listed in the device manager utility.

Here's to hoping we can find a solution to this irritating setback.

Stephen T.


"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.

Hi Stephen

It's obvious this problem is not application specific. I have not had the
problem since my last post but really have no idea why it started or why it
stopped!
The only additional housekeeping I have carried out is to run a product
called Housecall http://housecall.trendmicro.com/. It detected entries both
Ad-aware, Spybot and my AVG virus scanner missed. Whether this is a
coincidence I have no idea but at least I cleared out more rubbish from my PC.
In the meantime I think after Chas' (bad) experience of applying the only
relevant fix I could find in the Knowledge Base we just have to be patient
and if it is an OS problem presumably the nice microsoft people will come up
with the goods one day.
Mary

"Stephen T." wrote:

Hey Chas & Mary,

I unfortunately have the same irritating problem.
My problem occurs at shutdown or restart only, and usually involves my PCI
wireless adapter software (Linksys WMP54GS).
I have about 5 of these windows, all specifying different memory locations,
appear sequentially upon shutdown/restart.

I also have a problem with the program ccApp, which always delays in closing
upon shutdown/restart. I always have to select "End Now" to hasten the
process.

Anyway, I've also run the memtest utility (error-free), as well as several
Adware detection utilities and Norton AntiVirus on a daily basis.
Nothing found....nothing corrected as of yet.

I am growing endlessly weary of this utter annoyance.
I sure hope I can eventually pinpoint the problem.

If it is indeed an OS issue w/ SP2, I surely hope they rectify the problem
ASAP.
I have Win XP Media Center Edition 2005 (with all rollup updates/Microsoft
updates applied).

I check for Norton updates on a daily basis.

My Linksys driver (as well as all others) are the most up-to-date (this I
can verify because I just re-formatted my drive and performed clean installs
of the OS and ALL programs and drivers).

All relevant drivers were downloaded and installed yesterday.
I have no unknown devices listed in the device manager utility.

Here's to hoping we can find a solution to this irritating setback.

Stephen T.


"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.

Hi All,
I have been having this problem at my work computer, as well. The
numbers change, but it happens over and over again. I was convinced it
was a hardware problem on my horrible Dell. For me, it happens when I
try to copy files from one folder to another, and then sometimes when I
try to open a folder. It has also happened to me when I am opening a
file (so far only in Adobe Illustrator and Photoshop) or placing an
image file into an Illustrator file. Once it happens within a folder,
I can never open that folder again without the message coming up again
and my computer freezing.

I am running Windows XP Home Edition, which is the OS that came with
the computer. I've only been having this problem over the last six
months. It's a particularly debilitating problem, though. I was
contemplating brining in the Geek Squad people (they are my personal
heroes) but your posts make me wonder if maybe it is an OS thing.

Christine

Hi Christine

It's not a hardware problem, we are all running on different equipment.
While it's the same error message the program that generates it appears to be
different for all of us, so it can't be the individual applications. Which
leaves the OS or some sort of virus/spyware hijack. If you look at Chas'
post of 3 April, he was told Microsoft are aware of the problem and to wait
for a fix. So everything seems to point to the OS. It would be nice to know
what kicked it off, in your case 6 months ago, in mine last week. Then you
would know whether it is worth getting your geek squad heroes to re-install
windows on your desktop at work, especially if it's causing you a lot of
problems.
Mary


" wrote:

Hi All,
I have been having this problem at my work computer, as well. The
numbers change, but it happens over and over again. I was convinced it
was a hardware problem on my horrible Dell. For me, it happens when I
try to copy files from one folder to another, and then sometimes when I
try to open a folder. It has also happened to me when I am opening a
file (so far only in Adobe Illustrator and Photoshop) or placing an
image file into an Illustrator file. Once it happens within a folder,
I can never open that folder again without the message coming up again
and my computer freezing.

I am running Windows XP Home Edition, which is the OS that came with
the computer. I've only been having this problem over the last six
months. It's a particularly debilitating problem, though. I was
contemplating brining in the Geek Squad people (they are my personal
heroes) but your posts make me wonder if maybe it is an OS thing.

Christine

I have this exact issue. I believe this occurs if you install the
linksys adapter BEFORE you install the software. I tried uninstalling
the software, uninstalling the card from the device manager, removing
the card, installing the software, installing the card... still get the
wmp54gs memory can not be read and ccApp has to be killed.

Searching linksys is futile and their live assistance is even more
futile.

If anyone find this information useful and is able to ascertain a fix,
please email me. I don't read this group often if ever unless I'm
looking for a fix.
Howie

Norton is not going to detect it's own file (CCapp) as a problem. If it did,
Norton would be shut down when the problem was treated.

Get rid of Norton and use another antivirus to eliminate the problem.

--
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!

"Stephen T." wrote in message
...
Hey Chas & Mary,

I unfortunately have the same irritating problem.
My problem occurs at shutdown or restart only, and usually involves my PCI
wireless adapter software (Linksys WMP54GS).
I have about 5 of these windows, all specifying different memory
locations,
appear sequentially upon shutdown/restart.

I also have a problem with the program ccApp, which always delays in
closing
upon shutdown/restart. I always have to select "End Now" to hasten the
process.

Anyway, I've also run the memtest utility (error-free), as well as several
Adware detection utilities and Norton AntiVirus on a daily basis.
Nothing found....nothing corrected as of yet.

I am growing endlessly weary of this utter annoyance.
I sure hope I can eventually pinpoint the problem.

If it is indeed an OS issue w/ SP2, I surely hope they rectify the problem
ASAP.
I have Win XP Media Center Edition 2005 (with all rollup updates/Microsoft
updates applied).

I check for Norton updates on a daily basis.

My Linksys driver (as well as all others) are the most up-to-date (this I
can verify because I just re-formatted my drive and performed clean
installs
of the OS and ALL programs and drivers).

All relevant drivers were downloaded and installed yesterday.
I have no unknown devices listed in the device manager utility.

Here's to hoping we can find a solution to this irritating setback.

Stephen T.


"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.

Hi,

Cristine, I'm sorry you're having problems but I must admit being relieved
to finally know that someone else is having the same 'version' of this issue
as I am - especially the part about the files/folders. Do they become
"corrupted, truncated" or some other 'bonus' error once the memory fails?

I started having the error within a few days of purchasing my new computer -
at first sporadically and in apparently random programs (which is still
happening) but over the past few weeks it's become a regular occurance with
Photoshop.

I understand that more memory intensive programs are going to be more likely
to trigger these sorts of problems but this is a brand new computer and while
it isn't a 'golden machine', it was bought specifically for it's capacity to
handle all of my publishing software. It's definitely an XP OS issue.

Now does anyone have a suggestion as to how we get MS to take it seriously?

" wrote:

Hi All,
I have been having this problem at my work computer, as well. The
numbers change, but it happens over and over again. I was convinced it
was a hardware problem on my horrible Dell. For me, it happens when I
try to copy files from one folder to another, and then sometimes when I
try to open a folder. It has also happened to me when I am opening a
file (so far only in Adobe Illustrator and Photoshop) or placing an
image file into an Illustrator file. Once it happens within a folder,
I can never open that folder again without the message coming up again
and my computer freezing.

I am running Windows XP Home Edition, which is the OS that came with
the computer. I've only been having this problem over the last six
months. It's a particularly debilitating problem, though. I was
contemplating brining in the Geek Squad people (they are my personal
heroes) but your posts make me wonder if maybe it is an OS thing.

Christine

Chiming in on my same problem - memory referencing itself. I am running
XP on a Dell Inspiron 5100 and have been trouble free for years. This
memory problem just started a few weeks ago. Is this a trend with you
too?

In my case it only happens at startup referencing 0X745A6EBF. The debug
option does nothing and when I click OK , within 3 seconds XP wants to
send Microsoft an error report, referencing an unnamed Module. And I
cannot break past it to get into Windows. I click OK and it repeats the
error report dialog box.

My only option is to restart windows, pressing F8 to select reboot from
a previous configuration that works. This seems to work, but is a pain.

Lets keep each other posted when any of us figures this out.

.... Paul

Hi,I googled and knew that this problem is really common. My computer
is IBM X31 designed for XP. Do you have any applicable solution?
The MS did not give a useful response to the "memory could not be read"
problem.

coachpaul wrote:
Chiming in on my same problem - memory referencing itself. I am running
XP on a Dell Inspiron 5100 and have been trouble free for years. This
memory problem just started a few weeks ago. Is this a trend with you
too?

In my case it only happens at startup referencing 0X745A6EBF. The debug
option does nothing and when I click OK , within 3 seconds XP wants to
send Microsoft an error report, referencing an unnamed Module. And I
cannot break past it to get into Windows. I click OK and it repeats the
error report dialog box.

My only option is to restart windows, pressing F8 to select reboot from
a previous configuration that works. This seems to work, but is a pain.

Lets keep each other posted when any of us figures this out.

... Paul

Hi all:
Having same problems, only at shut down. Using XP on a Compag also using a
Belkin wireless system. Mine is referenced to 0X00040000. I get the chance
to cancel or debug when I get the message. No matter which way I go it
restarts my comp. Takes a couple of trys but eventually it shuts down. I will
also keep checking back to see if solution became available.

" wrote:

Hi,I googled and knew that this problem is really common. My computer
is IBM X31 designed for XP. Do you have any applicable solution?
The MS did not give a useful response to the "memory could not be read"
problem.

coachpaul wrote:
Chiming in on my same problem - memory referencing itself. I am running
XP on a Dell Inspiron 5100 and have been trouble free for years. This
memory problem just started a few weeks ago. Is this a trend with you
too?

In my case it only happens at startup referencing 0X745A6EBF. The debug
option does nothing and when I click OK , within 3 seconds XP wants to
send Microsoft an error report, referencing an unnamed Module. And I
cannot break past it to get into Windows. I click OK and it repeats the
error report dialog box.

My only option is to restart windows, pressing F8 to select reboot from
a previous configuration that works. This seems to work, but is a pain.

Lets keep each other posted when any of us figures this out.

... Paul

Hi all:
Having same problems, only at shut down. Using XP on a Compag also using a
Belkin wireless system. Mine is referenced to 0X00040000. I get the chance
to cancel or debug when I get the message. No matter which way I go it
restarts my comp. Takes a couple of trys but eventually it shuts down. I will
also keep checking back to see if solution became available.

" wrote:

Hi,I googled and knew that this problem is really common. My computer
is IBM X31 designed for XP. Do you have any applicable solution?
The MS did not give a useful response to the "memory could not be read"
problem.

coachpaul wrote:
Chiming in on my same problem - memory referencing itself. I am running
XP on a Dell Inspiron 5100 and have been trouble free for years. This
memory problem just started a few weeks ago. Is this a trend with you
too?

In my case it only happens at startup referencing 0X745A6EBF. The debug
option does nothing and when I click OK , within 3 seconds XP wants to
send Microsoft an error report, referencing an unnamed Module. And I
cannot break past it to get into Windows. I click OK and it repeats the
error report dialog box.

My only option is to restart windows, pressing F8 to select reboot from
a previous configuration that works. This seems to work, but is a pain.

Lets keep each other posted when any of us figures this out.

... Paul