Ram

[Guest]

How can I test My RAM to find out if it is bad? When I
get the blie screen of death is says to check for bad or
mismatched RAM.Thanks

 

[Chris Lanier]

Greetings

Memtest86 - A Stand-alone Memory Diagnostic
http://www.memtest86.com/

 

[yet_another_1]

Dr. Harsware or Sisoft Sandra (both are shareware) and maybe
even checkit (if it still exist and has an xp version)
there are ad-hoc utilities designed only to check/test
memory. search on google( keywords ram test)

 

[Rick \Nutcase\ Rogers]

Hi,

If you want to check the memory, there are free programs here:

http://www.simmtester.com/page/products/doc/download.asp
http://oca.microsoft.com/en/windiag.asp

But keep in kind that a thorough test can only be done with test equipment
at a computer shop. At the price of memory today, you may find that the test
costs more than a replacement stick.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!

Associate Expert - WinXP - Expert Zone

 

[Alex Nichol]

How can I test My RAM to find out if it is bad? When I
get the blie screen of death is says to check for bad or
mismatched RAM.

To test - download a free test from www.memtest.com or
www.simmtester.com, which will go on a bootable floppy - boot that and
give it several hours.

Matching is more difficult, as the available testers will tend to tell
you the settings being applied, which will probably be the same for all
the modules. (And those programs will not test the match of multiple
modules) But it *is* a point that Windows is very fussy about

You can get the free Aida 32, enterprise edition from
http://www.aida32.hu/aida-download.php?bit=32
which is an excellent general System Info tool, and its Motherboard -
Chipset page will tell you what modules are present.. If they are say
256 and 256 - two modules, you might try running on just one (slower,
but as a test worth it) -

Start- Run - MSConfig and on the Boot.ini page click Advanced Options.
Check /MAXMEM and set alongside for the size of just the one module.
OK and exit to boot with just the one in use. If that does not give a
BSOD< then matching (or a problem in the second module) is likely -
about all you can do then is swap them over physically and try just the
other on its own.