memory checker

ant31

Hi,
I think one of my memory sticks may well be playing up. Is there any recommended software that can check the memory - either freeware or cheapish shareware?

Ta,

Ant

Joe_Bloggs

You might want to try memtest86 from http://www.memtest86.com/
http://www.memtest86.com/memt31a.zip

It runs from a floppy without troubling your existing operating system.
J_B.

fayraz

Joe_Bloggs wrote:

You might want to try memtest86 from http://www.memtest86.com/
http://www.memtest86.com/memt31a.zip

It runs from a floppy without troubling your existing operating system.
J_B.

That's the best one to use!

-TangleFoot-

Besides memtest86, there's also Microsoft's own Windows Memory Diagnostic. It too is free, and does much the same thing; runs straight from a floppy and repeatedly tests your system's RAM until the computer is rebooted. Any problems found during the scanning process will be displayed on-screen.

Alternatively, if you don't have a floppy drive, you can download a bootable CD-image from here, and burn it to a blank disc using Nero or somesuch; it contains a large number of utilities and diagnostic tools, including both of those already mentioned.

ant31

Thank you all.. here's hoping!

bbb_uk

If you visit MemTest.org, they have an updated version based on memtest86+.

I'm not sure about M$ own memory diagnostic but I advise you read the docs that come with it because if I remember it correctly when you run and then it states it has problems reading/writing to a certain memory location it is recommended you run it again and see if the problem occurs at the same point. If it doesn't it could just be an incompatibility problem with memtext (I'm sure this info is with the docs)

ant31

Have ran memtest86 - cracking bit of software which has shown up some problems. I'll do a few further tests and then dig out the invoice..
Don't ya just love memory with a lifetime warranty

bbb_uk

ant31 wrote:

Have ran memtest86 - cracking bit of software which has shown up some problems. I'll do a few further tests and then dig out the invoice..
Don't ya just love memory with a lifetime warranty

As you say do further tests and make sure the problems it finds are in the approx the same location as it found them first time around. If not, and they're in completely different location just run it again see if its again a completely different location.

I ran it 3 times on a friends computer and everytime it came up with different locations.

If the memory is new then it could be a memory module incompatibility with your system but if its old (in excess of 6 months) and the problems it finds are in different locations it may be an incompatibility with the software. Trying Microsofts one as well.

Ferris

bbb_uk wrote:

As you say do further tests and make sure the problems it finds are in the approx the same location as it found them first time around. If not, and they're in completely different location just run it again see if its again a completely different location.

I ran it 3 times on a friends computer and everytime it came up with different locations.

If the memory is new then it could be a memory module incompatibility with your system but if its old (in excess of 6 months) and the problems it finds are in different locations it may be an incompatibility with the software. Trying Microsofts one as well.

just out of interest bbb, how exactly would you define "the same location"? how do you read the memory addresses thrown up by M$ and memtest?

for example, i ran M$ memory diagnostic overnight two or three times, and each time it found two or three errors in an address where the last four characters were always the same (e.g. xxxx3abc).

similarly, i ran memtest86+ overnight two or three times, and it found errors, again with each failing address ending in the same three or four letters (always in the region 386.1MB), and only on one test (test 8). however, the failing addresses in memtest were completely different to those found by M$.

does that make sense? does that count within your definition of "the same location"?

incidentally, i've had the memory for approx 11 months, and only experienced problems in the last 3 or 4 months.

thanks!

bbb_uk

Ferris wrote:

....similarly, i ran memtest86+ overnight two or three times, and it found errors, again with each failing address ending in the same three or four letters (always in the region 386.1MB), and only on one test (test 8). however, the failing addresses in memtest were completely different to those found by M$.

Unfortunately, I've not used M$ (to be honest I only heard about here on the post) memory tester but you say a completely different memory location - how different and does the M$ test always have problems in the same area as the last time you ran M$ tester?

According to your post, it is sounding like it is the memory as it is always in the region of 386MB but the only way to know for sure is if you could either borrow some memory, or if you're using 2 or more memory modules then just remove one.

Always try and do the memory tests when the computer is cold at least been off for an hour or so as it could be over heating (as posted in this thread) or open the case and have a fan constantly blowing air at the motherboard.

If you've only got 1 memory module and you can't borrow any then, providing your motherboard will support another module, you may have to invest in more memory. If you have 512MB then invest in 256MB (or whatever takes your fancy). You would then remove the 512MB and just use the new 256MB and see if problems still occur with your computer (the crashes, etc). If they do then it could point to a hardware (inc motherboard) problem but your memory won't be wasted as such as you can use it to bring it up to 768MB.

Here are the options you have (cheapest option first):-

1) If you're using 2 memory modules just remove 1 of them, test it few times if problems then swap with the other one you just took out and test that.

2) If you only have 1 memory module then borrow (if poss) some memory and use that instead of your own.

3) If you only have 1 memory module and you can't borrow any then you could backup your harddrive onto CD/DVD using the likes of Norton Ghost, format your harddrive and re-install Windows XP again. This process is time-consuming. After you have re-installed windows, don't install anything else driver wise (hopefully XP will find drivers for the essential items like display - it doesn't matter if it doesn't find sound drivers) but you can install word, etc then fully try out computer by running IE, word, etc.

If you find it doesn't crash anymore then it was a driver/software issue and you then proceed with caution when you install additional software or upgrade the existing drivers, etc - fully testing the computer after each software installation/driver upgrade.

If you find it does carry on crashing then you know for sure it wasn't a driver problem and therefore its hardware - either your memory or even motherboard.

If you choose option 3 then after you have formatted the harddrive and re-installed XP, you will find it runs a lot faster than it does now although it may still crash depending on if it was software/driver related or more hardware related.

4) You go out and buy another or replacement memory.

Remember that option 3 is cheapest if you can't borrow memory or are able to swap memory modules but it is very time consuming.

Let us know which method you plan on doing!

Joe_Bloggs

I have to disagree with bbb_uk to some extent.
Remember much of the advice is meant to be after a memtest86 failure.
You really want your ram to work under normal operating conditions so the tests should be conducted in these circumstances.

Try and retest with extra cooling or when cold to prove heat is the factor by taking the side off and adding a cooling breeze. In many sytems the memory is managed by a memory controller in the North bridge chip on the motherboard. Many have heatsinks and require a good air flow as they would otherwise run hot and fail.

The key thing is to find out what the problem is or to find out if the problem is not solvable.

Get an anti-static wrist band if you are going to change memory modules around. You could be creating faulty ram if you don't take anti-static precautions.

I don't think it's worth backing things up in a system that fails a memory test. Better to disconnect the hard drive and leave things the way they are . Installing an operating system in such circumstances is as prone to memory errors as much as any other process. Only when you pass a memory test should you consider adding a memory hogging operating system.

You can always try underclocking by 10% to see if you can get by with less FSB speed. Upping the ram voltage a little.

Prime 95 is a good way of stressing a system that works compared to Word.
The hardest test is 3D games.

A memory problem could also be a manifestation of a power supply or motherboard problem. These are also affected by heat. You may be able to get more help if you can find out the motherboard make model and version nember. Motherboard voltage/temperature monitoring utilities can also be a valuable diagnostic tool.

J_B.