Error message: "The memory could not be 'read' "

[speeddude2000]

Hey,

whenever i try to close a program, it closes, then pops up with a windows error message. It's annoying...anyone know how to fix it?

Here's a screenshot.

I tried a few google searches, but the only thing that was somewhat useful was an article explaining something about memory buffers being too large in windows 2000. I'm using windows XP.

[GaryRouth]

Hi speeddude2000

I've put a few links below for you to check out, just to keep things as thorough as possible in your troubleshooting. But from what I've seen so far, it seems that the likeliest cause is a spyware-type infection. If you have AdAware, SpyBot, and a decent antivirus scanner, boot into Safe Mode & run each of those on as "thorough" settings as the scanners will allow (definitely "scan within compressed files", etc.).....

When done, visit http://housecall.trendmicro.com (you might have to temporarily allow it's ActiveX control to download just long enough to run the scan). This scanner is very up-to-date - choose the selection to run both the antivirus and the antispyware at the same time. A nice added feature of the scans is that they list any identified MS Windows or MS Office based vulnerabilities, and offer advice on how to grab the updates you need for those (basically you go to Windows Update & then to Office Update).

It's not often related to either failing (or loose) memory modules, but it can't hurt to check that. And if you are overclocking, try stock timings for a bit. Some folks found that disabling HyperThreading helped - but that sounds more like a workaround than a true repair.


spyware complication
http://www.experts-exchange.com/Web/..._21103256.html

IE6 configuration issue
http://www.mcse.ms/message1256636.html

list of various fixes
http://castlecops.com/postt97038.html

Best of luck
. . . Gary

[P.S. -- sometimes spyware removal can damage Internet connectivity. Just in case, you might want to download LSPfix and WinsockXPfix and have them handy in case you need them. I don't have those links with me at the moment, but a quick Google should find them pretty quickly]

[TristanGoodchildIII]

I'm experiencing the same problem and unfortunately the links provided above didn't fix the problem. It seems that microsoft is aware of it and there is a hotfix available, but you need to contact them directly to fix it. It appears that they will address this issue in the next SP release. Check out the link below for more info...


http://support.microsoft.com/default...b;en-us;840114