Server Crashing Problem

cr4zy

<div class="IPBDescription">'Error: Memory cannot be read'</div> System Specs:
2000+ Athlon XP
512 mb DDR
Windows 2000 Pro

The problem I am having is that the server crashes with the error: 'Error: Memory cannot be read'. It used to only happen every few days, but 1.02 seems to do it at least every day. All of my benchmark programs confirm that my memory stick doesn't have any problems so I'm guessing it's some kind of OS problem. I would appreciate any information or help you can give me.

Mellonpopr

wow that's a strange one. I recommend doing a search on the forum and other forums like counter-strike.net and server.counter-strike.net since they have a larger database of issues.

The_Howler

When it crashes, I get a message from Windows that says:

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

Any ideas? Even more sad is that it suspends the program so my watcher program doesn't restart it. I tried disabling the visual notification through Windows but the error still pops up rather than just crashing.

Mellonpopr

definately sounds like some bad ram. if you have multiple ram sticks, take all of them out but one (if your motherboard can support a single stick)
boot and try that.

Keep doing it with each piece of memory until you find the bad or good ones.

If you get the same results as before try a differnt ram slot.. might have a bad one on the motherboard


are you overclocking ?

The_Howler

I have one stick of 512 DDR. I just ran a memory test that writes to each memory address and then reads from the same one. The first time I ran it, the program crashed with a similar error. I ran it again, and it went all the way through with no errors. I'm at a loss. I would assume that if the memory was actually bad, the test would always crash at the same place (ie, when it got to the same part of the memory that was bad). Very strange indeed.....

Mellonpopr

all bets are off when ram goes bad. another sign that memory is bad: try doing some memory intensive operations like making a large zip file or opening a very large zip file. often this will cause errors when ram is bad

cracker_jackmac

<!--QuoteBegin--The Howler+Nov 20 2002, 12:13 PM--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (The Howler @ Nov 20 2002, 12:13 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->I have one stick of 512 DDR. I just ran a memory test that writes to each memory address and then reads from the same one. The first time I ran it, the program crashed with a similar error. I ran it again, and it went all the way through with no errors. I'm at a loss. I would assume that if the memory was actually bad, the test would always crash at the same place (ie, when it got to the same part of the memory that was bad). Very strange indeed.....<!--QuoteEnd--></td></tr></table><span class='postcolor'><!--QuoteEEnd-->
I had a problem like this. My motherboard didn't support the stick size i was using. although i was under the max ram size, the stick wasn't registerable with that motherboard.