I beg your pardon! Net leaches? Hmmph

Same problem here

Specs:
3.06 ghz P4
512mb DDR RAM
64mb intel graphics card
WinXP w/SP1


I get this message when playing Half life 2, and counter strike 2. Im pretty sure its not a game bug.

Ive heard several rumours of it being a memory leak, and until now i was sure it was to do with windows not allocating the memory properly. Ive tried all the hardware test and blah-d-blah. still no luck. Im in desperate need of help!

My error message is:

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

Click on OK to terminate the program.

I think it is one of problems:

Graphics card
Memory allocation
Virtual memory
Memory leakage.

Help, please!

Hi

Ive been getting the error message The instructions at "0x004052a3" referenced memory at "0x00001518" the memory could not be read.

I was getting this when playing Call of Duty (United offensive) after playing for about 10 mins. But the other day had it a couple of times when online.

System specs
AMD XP2800+
Gigabyte GA-7VT600L
Radeon AIW 9800pro
1GB PC3200 memory
Windows XP home

Any help would be appreciated as Activision said update to latest drivers which I have anyway.

Thanks
Ian

If you are getting it after some time, e.g. 10 minutes, then I should think it is a memory leak/vitural memory problem - your memory is filling up.

But I think the problem is with the game you are playing - not with Windows. Your game's software probably keeps on grabbing more and more memory without releasing or reusing previously used memory. AFAIK games are memory hogs.

You might try looking at your game's executable in the Processes tab of Windows Task Manager while you are playing to see if its Mem Usage keeps on growing. You could also look in the Performance tab of WTM to see if CPU Usage and/or PF Usage keep growing while you are playing the game.

Have had same problem, after i bought new mainboard, CPU, memory 1GB and grapich card, after uppdating all drivers and so on, same old same old. Then i got the bright idea to uppgrade my BIOS, And after that the problem was gone.
It had som memory fix in it.

I just ran into this as well (on WIN2K, SP4) and found that it seems to be related (in my case anyway) to the Microsoft Indexing Service. After I disable it it seems to have stopped the errors, tho I'm not sure if it has to do with stopping the service or taking it off of 'instant update'. Either way it wasn't doing what it was supposed to, which is index in the background when your computer is idle.

Try this for more: http://ask-leo.com/cidaemon.html

Good luck - thanks for the background footwork. Frustrating error.

PH

Hello All,

These pesty memory errors sure can create havoc on anyones pc...Thru past experiences, I have found a quick fix for them by doing the following...

1. Have your Windows Xp CD in your Cd Drive and go to:

http://www.updatexp.com/scannow-sfc.html

2. The main reason for using this utility is when you suspect there may be a problem with a Windows XP system file.

Perhaps you get a dialog box appear informing you of a problem with a .dll file, or your program will just not load! It is therefore worth checking to see if there are any corrupt system files using scannow sfc.

To do this simply go to the Run box on the Start Menu and type in:

sfc /scannow

This command will immediately initiate the Windows File Protection service to scan all protected files and verify their integrity, replacing any files with which it finds a problem.

This will fix all memory errors and hopefully, help all you fine folks out...

Good Luck!!!

Hello All,

These pesty memory errors sure can create havoc on anyones pc...Thru past experiences, I have found a quick fix for them by doing the following...

1. Have your Windows Xp CD in your Cd Drive and go to:

http://www.updatexp.com/scannow-sfc.html

2. The main reason for using this utility is when you suspect there may be a problem with a Windows XP system file.

Perhaps you get a dialog box appear informing you of a problem with a .dll file, or your program will just not load! It is therefore worth checking to see if there are any corrupt system files using scannow sfc.

To do this simply go to the Run box on the Start Menu and type in:

sfc /scannow

This command will immediately initiate the Windows File Protection service to scan all protected files and verify their integrity, replacing any files with which it finds a problem.

This will fix all memory errors and hopefully, help all you fine folks out...

Good Luck!!!

You should run [COLOR=Blue]sfc /scannow[/COLOR] regularly, say once a week. I do.

I had a similar problem my error message was;
The instructions at "0x7c9105f8" referenced memory at "0x02630010". The memory could not be "read".
Also I noticed when I was surfing the web and open up a new window by right clicking on a link and selecting "Open in New Window" that my address bar was blanked and I could not type anything in it.
I removed a program called new.net from "Add or Remove programs" in my control panel and it seemed to have fixed both problems.

sometimes its like people forget what the process of elimination is.. its not SP2 obviously cause i get this same garbage and i have win2k.. its not memory cause ive tested my memory with memtest86 and i got 0 errors.. its not caused by explorer or your favorite game.. cause ive gotten this with almost every application on my computer.. so we can rule all those out simply by just one person.. another thing ide like to add like someone else said earlier.. it seems to happen when closing the app.... somebodys gotta know what is causing this...

The way I'd start pinpointing the problem is to download Filemon, Pmon, Process Explorer and Regmon from Sysinternals and monitor which files and registry entries affect this.

it sounds to me like its an incompatabilty with your RAM/mobo possibly the frequency is not in sync with your cpu

i dont know a lot about hardware but finally an idea that sounds pretty good...

Um, this thing actually causes some blue screens for me, does this mean that my memory could be bad, and I should return it for replacement?

i found a way to fix it on my machine!!! :angel:


it had been bugging me for months, every time i closed IE i used to 2 of those error boxes in a row, but the simple solution was to go into internet options, advanced, and uncheck the box called "enable third party browser extensions". now the error has disappeared. i dont know if that will work when other programs cause the error, but if its just IE, try that.

if ude look up a couple of replies i kinda already said something about the memory thing.. process of elimination...


doesnt explain the other applications.. but im giving that a try..

:knock: I have 3 users on a network who get the following error when trying to forward an email that contains an attachment:
The instruction at "0x61e52c66" referenced memory at "0x00000000". The memory could not be "read".

Once either user clicks OK to terminate, Outlook crashes with:
Outlook.exe has generated errors and will be closed by Windows. You will need to restart the program.

I'm in the process of reviewing logs but the oddity here is that it does not happen when trying to forward every attachment or even a specific type of attachment. In their cases, the error appears when they try to forward an attachment that comes from a specfic user.

All three are running W2K, SP4. The Outlook is Outlook2000, SP3. According to the users, it just started happening about a week ago.

Any ideas on this one?

I had the same problem you had, I fixed it by un-installing service pack 2 for windows, hope this helps.

well i reinstalled everything and i still got it a couple of times... so im guessing its got something to do with the motherboard.. ive always suspected there was something wrong with my motherboard....