Memory could not be "read"/"written"

[Guest]

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

 

[christine.gaspar]

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

 

[Guest]

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

 

[vzwstore]

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

 

[Richard Urban]

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!

 

[Guest]

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?

 

[coachpaul]

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

 

[soloman1980]

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.

 

[dbstew]

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.