Author Topic: Memory Scan (Read 242 times)

LLv34_Snefens · « **on:** November 11, 2004, 11:14:14 AM »

I suspect I'm suffering from some damaged RAM.
Are there any software out there that will be able to diagnostic if anything is wrong?

eagl · « **Reply #1 on:** November 11, 2004, 11:42:50 AM »

memtest86 installs to a floppy disk or cdrom and is the best way to check all of your memory. Any memory checker that runs under dos or windows will have to skip checking whatever memory is in use at the time. memtest86 uses hardly any memory at all so it checks almost every single bit of memory using various tests and patterns. I've had bad memory that passes a few of memtest86's tests, but some of the more advanced tests proved that the memory was bad.

http://www.memtest86.com

Check out the website as it has a ton of information on testing your memory and other systems in your computer.

llama · « **Reply #2 on:** November 11, 2004, 11:58:56 AM »

Second on eagl's recommendation.

Little known fact - most of the memory vendors are themselves using memtest-86 to verify bad ram. If you contact the vendor and tell them that memtest-86 says the ram is bad at blah blah blah, 4 times out of 5 the conversation stops immediately and you get an RMA number.

These guys could easily be making a buck off this great software too.

-Llama

LLv34_Snefens · « **Reply #3 on:** November 11, 2004, 01:06:17 PM »

Thanks, just the thing I was looking for.

Good news is that I couldn't find any errors with the RAM, bad news is that I then still haven't found what's causing the apparently random Blue SoD.
Got one on the very first entry after new windows install.

indy007 · « **Reply #4 on:** November 11, 2004, 01:47:54 PM »

memtest86 is really good. use it all the time here.

what's the error msg on the bsod?

214thCavalier · « **Reply #5 on:** November 11, 2004, 01:51:54 PM »

Snefens it can also happen if your low volting the Ram in your bios.
Might be worth checking and if you have the option increase the voltage to your ram.
Most ram is going to be ok at 2.8v but i would not advise going above, just try to up it to the next available setting and give it a go.
Another option try your ram in different slots as well.

LLv34_Snefens · « **Reply #6 on:** November 12, 2004, 02:30:21 AM »

The error code given was 0x0000007E

I did some searching on this one and it could be caused by a number of issues (inlcuding bad ram)

After yet another reinstall of windows I soon started getting the error code 0x00000050 instead. This is more specific a ram issue.

I took the twin RAM-blocks out and installed them in the other two ports. After several hours it now seems to be solved whatever it was. (error on the port itself, bad connect, ?)

The plus side is that I found that these two new slots recieve a hellavu lot more air flow from the 120mm CPU fan.
Not that I think it was a heat issue. They should be able to run with just passive cooling at default clocking, right?

I shouldn't have to up voltage as long as I don't overclock, should I?

214thCavalier · « **Reply #7 on:** November 12, 2004, 03:27:38 AM »

Depends on the rated voltage for your ram Snef.
As an example Abit IC7 motherboards had a habit of failing to load a new install of winXP, all you had to do with them was up the ram volts while installing.
Once installed XP however you could reduce the volts again and never have another problem.
Sounds like the slot change has helped tho, so leave the volts alone unless you need to try it.