Discussion on:

Check your RAM with MemTest

I'm getting neither the utility nor the website for this company. Too bad, it sounded usefull too.

I had no problem getting to the HCI corporate site from the link in the article (http://hcidesign.com/memtest/).

If you reloaded the page and it still didn't work, you need to verify that your local DNS database is both current _and_ uncorrupted.

Why waste your time checking your RAM?
Windows itself is a pretty good memory test.
If Windows will crank and run, then more than likely your memory is O.K.
I personally would never bother to check anybody's memory unless there were some sort of problems with the operation of the computer.

On a new box or chip a test is great. Also when you suspect a memory problem. Some NT blue screen could be a bad driver or bad memory.

I have seen too much random behaviour on win machines that is very hard to diagnose.

Random reboots, Odd memory size (123 megs??),
just odd stuff.

The last thing you usually think of is your memory. Testing it is usually not a bad idea and can rule out that part of the subsystem as part of the problem.

One of the first rules of computing. Remove and Rule out everything until you get to the lowest common denominator and work from there.

Good advice, another is a basic training word of advice: The basics are usaully overlooked and are the simplist of the solution to oncoming problems which are linked to the first. Like a domino effect.

Beg your pardon... The last thing I trust is Redmonds "expertise". Why complaining about a free utility that can point out problems ans save you alot of time? Not a waste of time, but GAIN of time! The link in the article worked just fine here.

Checking RAM is essential, I carry out RAM tests before rolling out PC's, Servers etc. It isn't good should a PC for example that has been rolled out start experiencing faults because of bad memory and so on leaving an IT Dept blue in the face. I recommend performing such an action.

I recently discovered the value of using software to test the RAM in a machine. I found a program called Memtest86 (www.memtest86.com) that, like the software mentioned in the article, is also free. The thing I like about Memtest86 is that it is platform independent. A boot diskette can be created that can be used to check any machine. Because it is not confined to running it Windows, it can do a more thorough test. After having used it to find bad memory in my manager's laptop, I highly recommend it because it works! My manager was getting strange memory related error mesages in Win2K -- they disappeared after I replaced the bad memory. It's also worth mentioning that I tested the replacement memory before giving him his machine back.

Once you identify that one of the faulty chips is bad, you still don't know which one and need to run the same test again?! This doesn't sound like the best service we could give to the people who use these boxes on a daily basis. It does sound like the start of a regular preventative maintenance plan.

One night you start the test on your computers (or a manageable portion of them). Before the computers are needed, you take inventory of which ones had faulty memory and replace those with known good memory modules, taking the questionable modules down to the lab for subsequent testing the conventional way... in hardware designed for that purpose. Modules that pass can be set aside for later use -- say the next time that your software indicates faulty memory...

Linux users can obtain source-code for a memory tester at http://www.qcc.sk.ca/~charlesc/software/memtester/

We use "QuickTech Pro" at our shop. Since you actually boot from the diagnostic diskette, you can test (almost) the entire range of RAM addresses.
Recently we have had a whole series of NT Workstations that blue screen due to stuck bits in the RAMchips.
Had we not had the disgnostic software, we would have been chasing our tails trying to find out what was causing the problems.

I periodicly have run accross troubles with the blue sceen terror. The same memory address coming up would indicate a bad memory
chip. This self test would definetly confirm my suspicions. Thanks for the resource, it will save time and my clients money beyound any doubt.
Robin D. Thompson

I use the Diagnostics program that came with Norton SystemWorks 2001. It is easy to use and fairly fast for a RAM tester. By swapping sticks of RAM and comparing the pass or fail results, I can determine if a system has a bad RAM slot or just bad RAM.

While the software is not free, it also is very extensive in its testing. I had a batch of workstations come in and out of the 11, 5 had bad memory chips. I contribute them to bad ESD handling while assembling the machines. Without QuickTech Pro,I would not have been able to tell what the problem was since it was very sporadic and seemingly random (ahhh, RANDOM access memory). The software also checks system board elements, hard drives, COM and LPT ports, as well as other things. For any serious PC Tech, I highly recommend it. The developer is Ultra-X Incorporated at www.uxd.com....and no I don't get any commission nor own stock.

We recently purchased 50 new Dell Win 2000 Optiplex computers. When booting some of the computers get a blue screen virtual memory dump. We ahve t turn computer off sometimes one or two starts before getting the operational system to work. Any thoughts. It does not occur all the time. Infrequent maybe one out every 20 starts???? Just a wild guess. But about 40 % of our computers have experienced this problem

I have found an excellent memory tester. It's easy to use and very reliable and free.
Memtest86 can be found at:
http://www.teresaudio.com/memtest86/

I don't think it helps TechRepublic to introduce a freeware Windows-based tester, telling the reader that it cannot test the memory directly (which also means that it's impossible to directly determine where the bad RAM module is)... This program'sability to test RAM is unreliable at best, a complete sham at worst. At least it's free, it's not worth a penny.

Yet alone running a diagnostic while choosing to use the same computer at the same time (?!)... That's lunacy. Any computer suspect of being unstable should not be used for production work. Using diagnostic programs which can't access the hardware directly is just as ludicrous.

Somehow somewhere there's got to be a reliable memory checker that produces tangible results. (and it's easy to determine which RAM module is bad, if you know the location of the faulty segment... Even old-day DOS testers, limited to 64mb or whatever, access memory directly and tell the person who initiated the test what was wrong and effectively where.)

I have found memory testing invaluable for tricky workstation problems. We have had one instance of high quality RAM with a 'sticky bit'. One bit that occasionaly will not set or reset. I used DocMemory from www.simtester.com and DocMemory found thefaulty bit at pass 19 then again at pass 26 etc.

I suggest using a memory test product if you are having weird system crashes or application failures.

I had a brand new Compaq DP using NT that blue screened and behaved erratically. It turned out the Kingston RAM installed by CDW at purchase was bad. I was suprised at bad "name brand" ram having problems. I agree - it the PC is acting strange, test the RAM,

If your not testing the entire memory, and especially if it can't point to the bad Simm ... whats the point? THis is like a computer version of 'twiddle your fingers ..' ....

I can still remember the days of the old IBM PC, XT and AT. Even with the miniscule amount (by today's standards) of RAM in those machines, hardware parity checking on the motherboard was considered essential. It was simply not good engineering practice to assume that each and every bit was OK when a fault with any one of them could crash the machine. As far as I can tell, the situation has not only not changed in the slightest, but has become even more important with the voluminous amounts of memory we deal with now; every bit has to work, for every bit can be a part of a machine instruction code, or important piece of data. If it's wrong, you have corrupted your data or you're executing the wrong instruction. IMHO, implementing error detection, if not full blown detection and automatic correction, is vital if the machine is even remotely involved in a vital application. Just running a diagnostic occasionally doesn't cut it. Pros know this.

A well written article, however the question of 'how often'? was not answered. I am intrigued enough to try the product.


Regards Des

One of the best memory testers out there is from a builder of hardware based ram test units. There are flavors for all OS'es but it boots from a floppy and does some really in-depth testing.

I've recently had several PC's come in the shopthat had unusual symptoms, but the usual "in Windows" and "Dos" based testing didn't give me any indication as to the cause of the problems. When I ran DocMem in the burn in mode it showed 2 memory modules that were intermittently giving back bad data.

Following is the link to their site:
http://www.simmtester.com
SimmTester

Go get it!