Re: [newbie] Testing for bad RAM-solved and update
RR! Run from that shop. FAST. Don't look back. Not all ram is the same, there are different types with different internal funtionality. Windows does not, as a rule, use ram as agressivley as Linux does. Just "popping" the ram in to test it is not enough. The bios needs to be set for optimum or even acceptable use on some sticks. If you are concerned about the validity of your ram, take it to a vendor that has a test box. The box is a device designed for one purpose only.. Testing ram. It will run all portions of the stick through the paces, and provide a result in about 1-2 minutes. Not every computer tech or shop will have one of theses puppies, they cost $2k to $5k us. If the memory is indeed faulty, the chances are it will not pass tesing on one of these devices. Bill Ries-Knight - Original Message - From: Linux Tests [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 28, 2001 6:37 PM Subject: Re: [newbie] Testing for bad RAM-solved and update It might have been just as easy for the tech to wave the RAM back and forth in the air a few times - lightly touch it to his forehead - chant "Ibeebeebeeeboo" five times - blinking the lights off and on with the other hand while twirling about ... He'd have come to the same conclusion ... On Mon, 26 Feb 2001, you wrote: I took the suspect ram sticks back to the shop where I bought them and the ##tech put it in a windows box and booted it up. It booted right up, so they ##said the memory was tested ok. They gave me an exchange anyway, but I ##thought it interesting that their test was to boot it and let the bios test ##tell them if it was ok. That's fine i'm back to 256M and it was instantly ##recognized in LM7.2 on boot. Dennis M. ##-Original Message- ##From: [EMAIL PROTECTED] ##[mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWO ##Sent: Thursday, February 22, 2001 8:45 AM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ##This is the funny thing about my situation, no crashes, no weird things ##going on, I just can't get linux to recognize my ram. The system doesn't ##even seem to run any slower, transfers of web pages and searches are as fast ##as ever. I am thinking motherboard, so I will try suggested test of putting ##the ram in another box and see if it causes problems there. Two of the ##sticks are only a couple of months old and I should be able to exhchange ##them if I can determine good or bad. ##-Original Message- ##From: [EMAIL PROTECTED] ##[mailto:[EMAIL PROTECTED]]On Behalf Of Mark Johnson ##Sent: Wednesday, February 21, 2001 8:58 AM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ##Naa, I can't believe this, I have a 256 stick that crashed three computers ##continuously and it counted up in the bios just fine in all three. This 128 ##stick isn't quite so ruthless on me but linux apps keep crashing on me left ##and right and weird things like the logout won't work sometimes in X... ## ##-Original Message- ##From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]] ##Sent: Tuesday, February 20, 2001 2:20 PM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ## ##I've been told by local computer techs that if your bios sees the ram at ##bootup ,( in other words detects it and counts it off on the first screen ##that shows your primary and secondary IDE devices and you can hit del to ##get to bios) then the ram memory is good and should be functional. I am not ##a technician so I am relying on their advice. ## ##BM__MailData-Original Message- ##From: [EMAIL PROTECTED] [ ##mailto:[EMAIL PROTECTED] ##mailto:[EMAIL PROTECTED] ] On Behalf Of Mark Johnson ##Sent: Tuesday, February 20, 2001 1:31 PM ##To: LinuxNewbie (E-mail) ##Subject:[newbie] Testing for bad RAM ## ##I am suspicious that my RAM is bad. Is there anyway in linux that I can ##confirm this? ## ## ## Content-Type: text/html; name="Attachment: 1" Content-Transfer-Encoding: 7bit Content-Description:
Re: [newbie] Testing for bad RAM-solved and update
On Monday 26 February 2001 16:01, you wrote: I took the suspect ram sticks back to the shop where I bought them and the tech put it in a windows box and booted it up. It booted right up, so they said the memory was tested ok. They gave me an exchange anyway, but I thought it interesting that their test was to boot it and let the bios test tell them if it was ok. That's fine i'm back to 256M and it was instantly recognized in LM7.2 on boot. Dennis M. First off I'm glad you have your memory problem solved and I'll bet it was an incompatibility, however if any of the Tech's that work for me ever used the method you just described to troubleshoot a memory problem they would be in the unemployment line... In my shop we have an SP3000 for testing Simms and Dimms and as a standard practice if they test good we exchange the memory with another brand and always make sure we are matching the same speed.. My advice find a better shop with professional Tech's. Scott Faulkner This is the funny thing about my situation, no crashes, no weird things going on, I just can't get linux to recognize my ram. The system doesn't even seem to run any slower, transfers of web pages and searches are as fast as ever. I am thinking motherboard, so I will try suggested test of putting the ram in another box and see if it causes problems there. Two of the sticks are only a couple of months old and I should be able to exhchange them if I can determine good or bad. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Johnson Sent: Wednesday, February 21, 2001 8:58 AM To: '[EMAIL PROTECTED]' Subject: RE: [newbie] Testing for bad RAM Naa, I can't believe this, I have a 256 stick that crashed three computers continuously and it counted up in the bios just fine in all three. This 128 stick isn't quite so ruthless on me but linux apps keep crashing on me left and right and weird things like the logout won't work sometimes in X... -Original Message- From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 20, 2001 2:20 PM To: '[EMAIL PROTECTED]' Subject: RE: [newbie] Testing for bad RAM I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. BM__MailData-Original Message- From: [EMAIL PROTECTED] [ mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject:[newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this? Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: 7bit Content-Description:
Re: [newbie] Testing for bad RAM-solved and update
It might have been just as easy for the tech to wave the RAM back and forth in the air a few times - lightly touch it to his forehead - chant "Ibeebeebeeeboo" five times - blinking the lights off and on with the other hand while twirling about ... He'd have come to the same conclusion ... On Mon, 26 Feb 2001, you wrote: I took the suspect ram sticks back to the shop where I bought them and the ##tech put it in a windows box and booted it up. It booted right up, so they ##said the memory was tested ok. They gave me an exchange anyway, but I ##thought it interesting that their test was to boot it and let the bios test ##tell them if it was ok. That's fine i'm back to 256M and it was instantly ##recognized in LM7.2 on boot. Dennis M. ##-Original Message- ##From: [EMAIL PROTECTED] ##[mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWO ##Sent: Thursday, February 22, 2001 8:45 AM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ##This is the funny thing about my situation, no crashes, no weird things ##going on, I just can't get linux to recognize my ram. The system doesn't ##even seem to run any slower, transfers of web pages and searches are as fast ##as ever. I am thinking motherboard, so I will try suggested test of putting ##the ram in another box and see if it causes problems there. Two of the ##sticks are only a couple of months old and I should be able to exhchange ##them if I can determine good or bad. ##-Original Message- ##From: [EMAIL PROTECTED] ##[mailto:[EMAIL PROTECTED]]On Behalf Of Mark Johnson ##Sent: Wednesday, February 21, 2001 8:58 AM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ##Naa, I can't believe this, I have a 256 stick that crashed three computers ##continuously and it counted up in the bios just fine in all three. This 128 ##stick isn't quite so ruthless on me but linux apps keep crashing on me left ##and right and weird things like the logout won't work sometimes in X... ## ##-Original Message- ##From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]] ##Sent: Tuesday, February 20, 2001 2:20 PM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ## ##I've been told by local computer techs that if your bios sees the ram at ##bootup ,( in other words detects it and counts it off on the first screen ##that shows your primary and secondary IDE devices and you can hit del to ##get to bios) then the ram memory is good and should be functional. I am not ##a technician so I am relying on their advice. ## ##BM__MailData-Original Message- ##From: [EMAIL PROTECTED] [ ##mailto:[EMAIL PROTECTED] ##mailto:[EMAIL PROTECTED] ] On Behalf Of Mark Johnson ##Sent: Tuesday, February 20, 2001 1:31 PM ##To: LinuxNewbie (E-mail) ##Subject: [newbie] Testing for bad RAM ## ##I am suspicious that my RAM is bad. Is there anyway in linux that I can ##confirm this? ## ## ## Content-Type: text/html; name="Attachment: 1" Content-Transfer-Encoding: 7bit Content-Description:
Re: [newbie] Testing for bad RAM-solved and update
On Wed, 28 Feb 2001, you wrote: It might have been just as easy for the tech to wave the RAM back and forth in the air a few times - lightly touch it to his forehead - chant "Ibeebeebeeeboo" five times - blinking the lights off and on with the other hand while twirling about ... He'd have come to the same conclusion ... On Mon, 26 Feb 2001, you wrote: I took the suspect ram sticks back to the shop where I bought them and the ##tech put it in a windows box and booted it up. It booted right up, so they ##said the memory was tested ok. They gave me an exchange anyway, but I ##thought it interesting that their test was to boot it and let the bios test ##tell them if it was ok. That's fine i'm back to 256M and it was instantly ##recognized in LM7.2 on boot. Dennis M. ##-Original Message- RONTF, that is funny.. My mental image of the testing of the ram will never be the same, it will always have a shaman a ram and ewe in the image, : 0 ) -- Dennis M. registered linux user # 180842
Re: [newbie] Testing for bad RAM-solved and update
On Tue, 27 Feb 2001, you wrote: On Monday 26 February 2001 16:01, you wrote: I took the suspect ram sticks back to the shop where I bought them and the tech put it in a windows box and booted it up. It booted right up, so they said the memory was tested ok. They gave me an exchange anyway, but I thought it interesting that their test was to boot it and let the bios test tell them if it was ok. That's fine i'm back to 256M and it was instantly recognized in LM7.2 on boot. Dennis M. First off I'm glad you have your memory problem solved and I'll bet it was an incompatibility, however if any of the Tech's that work for me ever used the method you just described to troubleshoot a memory problem they would be in the unemployment line... In my shop we have an SP3000 for testing Simms and Dimms and as a standard practice if they test good we exchange the memory with another brand and always make sure we are matching the same speed.. My advice find a better shop with professional Tech's. Scott Faulkner Thanks, I will try to take your advice. I have not looked around that much since this place is only about a mile from my house and I can buy OEM stuff there when I am building or upgrading something. I'll check with folks in my office about a good tech shop. I ran the memtest86 on the other 2 computers and they checked out ok. Again, thanks for the advice, I'll try. -- Dennis M. registered linux user # 180842
Re: [newbie] Testing for bad RAM-solved and update
On Tue, 27 Feb 2001, you wrote: On Monday 26 February 2001 16:01, you wrote: I took the suspect ram sticks back to the shop where I bought them and the tech put it in a windows box and booted it up. It booted right up, so they said the memory was tested ok. They gave me an exchange anyway, but I thought it interesting that their test was to boot it and let the bios test tell them if it was ok. That's fine i'm back to 256M and it was instantly recognized in LM7.2 on boot. Dennis M. First off I'm glad you have your memory problem solved and I'll bet it was an incompatibility, however if any of the Tech's that work for me ever used the method you just described to troubleshoot a memory problem they would be in the unemployment line... In my shop we have an SP3000 for testing Simms and Dimms and as a standard practice if they test good we exchange the memory with another brand and always make sure we are matching the same speed.. My advice find a better shop with professional Tech's. Scott Faulkner Thanks, I would love tobe able to do that, but, always a but, My other choices are considerably farther away, and I'm not sure if they are any better. I don't know, Gateway and CompUSA are the next choice, although I will start checking with some of the computer literate folks in my office to see if I can find another tech source. Thanks for the advice. -- Dennis M. registered linux user # 180842
RE: [newbie] Testing for bad RAM-solved and update
Title: RE: [newbie] Testing for bad RAM I took the suspect ram sticks back to the shop where I bought them and the tech put it in a windows box and booted it up. It booted right up, so they said the memory was tested ok. They gave me an exchange anyway, but I thought it interesting that their test was to boot it and let the bios test tell them if it was ok. That's fine i'm back to 256M and it was instantly recognized in LM7.2 on boot. Dennis M. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWOSent: Thursday, February 22, 2001 8:45 AMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM This is the funny thing about my situation, no crashes, no weird things going on, I just can't get linux to recognize my ram. The system doesn't even seem to run any slower, transfers of web pages and searches are as fast as ever. I am thinking motherboard, so I will try suggested test of putting the ram in another box and see if it causes problems there. Two of the sticks are only a couple of months old and I should be able to exhchange them if I can determine good or bad. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark JohnsonSent: Wednesday, February 21, 2001 8:58 AMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM Naa, I can't believe this, I have a 256 stick that crashed three computers continuously and it counted up in the bios just fine in all three. This 128 stick isn't quite so ruthless on me but linux apps keep crashing on me left and right and weird things like the logout won't work sometimes in X... -Original Message-From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]]Sent: Tuesday, February 20, 2001 2:20 PMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this?
RE: [newbie] Testing for bad RAM-solved and update
The techs who fed you the line about the bootup memory test are drones. They have no idea about what they are talking about. There are numerous incompatibilities between motherboards and certain memory strip configurations. I recently ran into an interesting one, wherein certain Crucial/Micron strips would ALWAYS crash WinME (strangely not Win2K) or Linux when installed on Intel 815 and VIA Apollo based motherboards. These same strips worked fine on BX based motherboards. Memory test programs continually reported no problems whatsoever. Testing revealed that the data lines would not "come ready" fast enough for the 815 and VIA chipsets after a strobe. Ironically Crucial/Micron is big on touting it's reliability factor... right. A very simple and faily good indicator of problems is to use DOS's Himem with the /TESTMEM option. I.E. Make a DOS boot disk and add this line to the config.sys after placing himem.sys on the disk... DEVICE = HIMEM.SYS /TESTMEM:ON This is surprisingly good in catching memory problems which will foul up Linux and would have most likely demonstrated problems with the memory you had. It's not foolproof but I've seen it catch things that even hardware testers and good test suites do not. -JMS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWO Sent: Monday, February 26, 2001 11:01 AM To: '[EMAIL PROTECTED]' Subject: RE: [newbie] Testing for bad RAM-solved and update I took the suspect ram sticks back to the shop where I bought them and the tech put it in a windows box and booted it up. It booted right up, so they said the memory was tested ok. They gave me an exchange anyway, but I thought it interesting that their test was to boot it and let the bios test tell them if it was ok. That's fine i'm back to 256M and it was instantly recognized in LM7.2 on boot. Dennis M.
Re: [newbie] Testing for bad RAM
http://www.uxd.com/ abe Mark Weaver wrote: abe wrote: regrettably that tech is misinformed. In my time as a pc repair tech I saw many sticks of ram that passed the boot test put were infact bad. Quick tech pro is one of the best memory testers you'll find. It actually test's most of the hardware in your system. Quick tech can identify a single bad sector in ram. Good luck Abe "Myers, Dennis R NWO" wrote: I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this? Abe, Where does one find and buy a copy of this amazing program? -- Mark "If you don't share your concepts and ideals, they end up being worthless," "Sharing is what makes them powerful."
Re: [newbie] Testing for bad RAM
abe wrote: regrettably that tech is misinformed. In my time as a pc repair tech I saw many sticks of ram that passed the boot test put were infact bad. Quick tech pro is one of the best memory testers you'll find. It actually test's most of the hardware in your system. Quick tech can identify a single bad sector in ram. Good luck Abe "Myers, Dennis R NWO" wrote: I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this? Abe, Where does one find and buy a copy of this amazing program? -- Mark "If you don't share your concepts and ideals, they end up being worthless," "Sharing is what makes them powerful."
RE: [newbie] Testing for bad RAM
Title: RE: [newbie] Testing for bad RAM well that is sort true,, if you bios is set to fast boot, the chances are that it is not doing a full test of the ram,,, You would be better of booting from a floppy with something like microscope or PCcheckit... and do a full test with that. regards Frank -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Myers, Dennis R NWOSent: Wednesday, 21 February 2001 4:20 AMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this?
RE: [newbie] Testing for bad RAM
Title: RE: [newbie] Testing for bad RAM Naa, I can't believe this, I have a 256 stick that crashed three computers continuously and it counted up in the bios just fine in all three. This 128 stick isn't quite so ruthless on me but linux apps keep crashing on me left and right and weird things like the logout won't work sometimes in X... -Original Message-From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]]Sent: Tuesday, February 20, 2001 2:20 PMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this?
RE: [newbie] Testing for bad RAM
Title: RE: [newbie] Testing for bad RAM This is the funny thing about my situation, no crashes, no weird things going on, I just can't get linux to recognize my ram. The system doesn't even seem to run any slower, transfers of web pages and searches are as fast as ever. I am thinking motherboard, so I will try suggested test of putting the ram in another box and see if it causes problems there. Two of the sticks are only a couple of months old and I should be able to exhchange them if I can determine good or bad. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark JohnsonSent: Wednesday, February 21, 2001 8:58 AMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM Naa, I can't believe this, I have a 256 stick that crashed three computers continuously and it counted up in the bios just fine in all three. This 128 stick isn't quite so ruthless on me but linux apps keep crashing on me left and right and weird things like the logout won't work sometimes in X... -Original Message-From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]]Sent: Tuesday, February 20, 2001 2:20 PMTo: '[EMAIL PROTECTED]'Subject: RE: [newbie] Testing for bad RAM I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this?
Re: [newbie] Testing for bad RAM
Just test the stick. I know a place that sells memory testers, but yuo can do it the software way of through hardware switching. First, remove the old stick and use just the new one. Now recompile the kernel. Recompiling a kernel is one of the most memory sensitive things you can do. If that works then so far so good. Now put in your new stick only and compile again. If it fails then new stick is broken. Now both together. If it fails then the sticks are incompatable. - Original Message - From: Heather [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 21, 2001 8:24 PM Subject: Re: [newbie] Testing for bad RAM On this subject of RAM incompatibility... I have a stick of RAM that someone gave me to boost me up past 64mb. When I first installed it it would do ok, but then it would get where sometimes it would show on boot up and others it wouldn't then (in evil windows since i haven't put it back after installing LM) my computer started popping up more errors and illegals than it ever had before. When I pulled the RAM it went back to normal (for windows). Is there a way for me to find out if the 2 sticks are just incompatible or if the 1 stick is just borked up?
Re: [newbie] Testing for bad RAM
Actually RAM Stress Test is able to correctly identify bad modules better than Quick Tech Pro. This is a 35 K program that was originally shareware until the owners figured out that it is better than using a $25,000 darkhorse tester ;-) Micron even tried to purchase the code because they realized that compatibililty of memory modules and timing can also be tested with RST. http://www.uxd.com I've used RST for several years - and have been able to stop all DOA shipments of RAM (company I worked for shipped GB of memory daily plus built systems with GB of memory.). On Wed, 21 Feb 2001, you wrote: ##regrettably that tech is misinformed. In my time as a pc repair tech I ##saw many sticks of ram that passed the boot test put were infact bad. ##Quick tech pro is one of the best memory testers you'll find. It ##actually test's most of the hardware in your system. Quick tech can ##identify a single bad sector in ram. ## ##Good luck ## ## ##Abe ## ## ## ## "Myers, Dennis R NWO" wrote: ## ## I've been told by local computer techs that if your bios sees the ram ## at bootup ,( in other words detects it and counts it off on the first ## screen that shows your primary and secondary IDE devices and you can ## hit del to get to bios) then the ram memory is good and should be ## functional. I am not a technician so I am relying on their advice. ## ## -Original Message- ## From: [EMAIL PROTECTED] ## [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson ## Sent: Tuesday, February 20, 2001 1:31 PM ## To: LinuxNewbie (E-mail) ## Subject: [newbie] Testing for bad RAM ## ## I am suspicious that my RAM is bad. Is there anyway in linux that I ## can ## confirm this?
Re: [newbie] Testing for bad RAM
Sorry, I respectfully disagree with some of this. A techs time is too expensive to go through BIOS settings. Always stick with the BIOS defaults. Period. DO NOT make changes to your BIOS. Plus simplify the testing process. Keep the BIOS at default. Use RST - and OS independent tester - which will test compatibility issues for the complete system as well as locate any bad memory modules. In less than 3 minutes you will know if the memory is bad. http://www.uxd.com Don't waste your time swapping and pulling etc. Just get the program and be happy.(No, I'm not affiliated with Ultra-X. I just happen to use the program) On Wed, 21 Feb 2001, you wrote: ##On Wednesday 21 February 2001 02:24 pm, Heather wrote: ## On this subject of RAM incompatibility... ## ## I have a stick of RAM that someone gave me to boost me up past 64mb. ## When I first installed it it would do ok, but then it would get where ## sometimes it would show on boot up and others it wouldn't then (in ## evil windows since i haven't put it back after installing LM) my ## computer started popping up more errors and illegals than it ever had ## before. When I pulled the RAM it went back to normal (for windows). ## Is there a way for me to find out if the 2 sticks are just ## incompatible or if the 1 stick is just borked up? ## ##Not really. The only way to actually test ram is on a _very_ ##expensive, purpose built machines that very few people would ever have ##access to (lab equipment). What is more important to understand is ##just how much ram can be affected by other parts of the system. ##Particularly the motherboard, cpu, cache, etc. The best ram test apps ##like 'memtest86', actually test the whole system, so the appearance of ##errors are not necessarily due to bad ram. Also important to ##consider, is that ram is very heat and voltage tolerant, especially ##when compared to the other system components. IOW's, it's usually not ##the culprit. ## ## Most often there's no problem mixing ram sizes or "labels" (eg pc66, ##100, 133, etc). I've got two 128mb sticks, one pc100, one pc133 ##that'll run 'memtest86', L2 disabled, together for an extended time at ##155 mhz with -0- error at 3.55V. So is my pc100 mislabeled? No, ram ##is what it'll do with -0- errors over time. But I digress ## ## First check your bios settings. The settings easiest on the ram are ##the 'slow' settings. (eg, cas3-3-3, precharge disabled, no ECC for ##sdram). Then most ram problems can often be solved by moving the sticks ##to different slots and/or changing the order they're installed in. ##Sometimes just reseating the ram cures the problem. Next most likely ##culprit is the motherboard. A stick of pc66 ram that will run without ##errors at 133mhz (twice it's rated speed) in one motherboard, might not ##work reliably at all in a different (lesser) motherboard even at it's ##default 66mhz. It's just another situation that illustrates how ##important it is to base a system on a good quality motherboard and a ##good power supply. Many of the better motherboards (eg, Asus, Soyo, ##Abit, Epox, MSI, etc) provide more than the standard IO voltage to the ##ram by default (about +10%). This greatly enhances ram stability and ##performance at, or even far above it's manufacturers rating. ## ##So what'a you do? Try reseating (clean the contacts), swappin ##around, tryin in other motherboards (ie, see if it works in a different ##system), give it some more voltage (if you've got a good motherboard). ##'memtest86' is a good check in that you can toggle the L2 cache off/on. ##Many cache error problems often get blamed on the ram. If none of that ##fixes the problems, then give the ram to somebody you don't like ;) ##. and try again with a better motherboard/power supply and some new ##ram ;
Re: [newbie] Testing for bad RAM
256 MB sticks are especially tricky in terms of timings and quality. It isn't surprising to find 256 MB modules fail on one board and pass on another brand. Almost all of the original Corsair 256 MB modules failed after a few months of operation. This qualty issue was common with many other brands too. n Wed, 21 Feb 2001, you wrote: Naa, I can't believe this, I have a 256 stick that crashed three computers ##continuously and it counted up in the bios just fine in all three. This 128 ##stick isn't quite so ruthless on me but linux apps keep crashing on me left ##and right and weird things like the logout won't work sometimes in X... ## ##-Original Message- ##From: Myers, Dennis R NWO [mailto:[EMAIL PROTECTED]] ##Sent: Tuesday, February 20, 2001 2:20 PM ##To: '[EMAIL PROTECTED]' ##Subject: RE: [newbie] Testing for bad RAM ## ## ## ##I've been told by local computer techs that if your bios sees the ram at ##bootup ,( in other words detects it and counts it off on the first screen ##that shows your primary and secondary IDE devices and you can hit del to ##get to bios) then the ram memory is good and should be functional. I am not ##a technician so I am relying on their advice. ## ##BM__MailData-Original Message- ##From: [EMAIL PROTECTED] [ ##mailto:[EMAIL PROTECTED] ##mailto:[EMAIL PROTECTED] ] On Behalf Of Mark Johnson ##Sent: Tuesday, February 20, 2001 1:31 PM ##To: LinuxNewbie (E-mail) ##Subject:[newbie] Testing for bad RAM ## ##I am suspicious that my RAM is bad. Is there anyway in linux that I can ##confirm this? ## ## ## Content-Type: text/html; name="Attachment: 1" Content-Transfer-Encoding: 7bit Content-Description:
Re: [newbie] Testing for bad RAM
cool. I'll check it out. Quick Tech Pro is made by the same people. I like it because it can test more then just memory. Besides, I've seen it identify single bad sectors. Pretty impressive and saves a lot fo time/money in a production environment. Abe Linux Tests wrote: Actually RAM Stress Test is able to correctly identify bad modules better than Quick Tech Pro. This is a 35 K program that was originally shareware until the owners figured out that it is better than using a $25,000 darkhorse tester ;-) Micron even tried to purchase the code because they realized that compatibililty of memory modules and timing can also be tested with RST. http://www.uxd.com I've used RST for several years - and have been able to stop all DOA shipments of RAM (company I worked for shipped GB of memory daily plus built systems with GB of memory.). On Wed, 21 Feb 2001, you wrote: ##regrettably that tech is misinformed. In my time as a pc repair tech I ##saw many sticks of ram that passed the boot test put were infact bad. ##Quick tech pro is one of the best memory testers you'll find. It ##actually test's most of the hardware in your system. Quick tech can ##identify a single bad sector in ram. ## ##Good luck ## ## ##Abe ## ## ## ## "Myers, Dennis R NWO" wrote: ## ## I've been told by local computer techs that if your bios sees the ram ## at bootup ,( in other words detects it and counts it off on the first ## screen that shows your primary and secondary IDE devices and you can ## hit del to get to bios) then the ram memory is good and should be ## functional. I am not a technician so I am relying on their advice. ## ## -Original Message- ## From: [EMAIL PROTECTED] ## [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson ## Sent: Tuesday, February 20, 2001 1:31 PM ## To: LinuxNewbie (E-mail) ## Subject: [newbie] Testing for bad RAM ## ## I am suspicious that my RAM is bad. Is there anyway in linux that I ## can ## confirm this?
Re: [newbie] Testing for bad RAM
I second this. Quick Tech is the program that I recommend. It is available from http://www.uxd.com as was mentioned below. It is amazing. Well worth the money. Worth its weight in gold actually. Although I do disagree with always keeping BIOS defaults. Definately keep them for ram timings and speeds but other settings need to be adjusted to achive stable peak performance from your hardware. As an example: An Asus A7V (if you have no usb devices) will boot twice as fast with "legacy USB Support" disabled and it is enabled by default. Abe "I test more ram and motherboards in an afternoon then most people touch in their entire lives" olson ;-) Linux Tests wrote: Sorry, I respectfully disagree with some of this. A techs time is too expensive to go through BIOS settings. Always stick with the BIOS defaults. Period. DO NOT make changes to your BIOS. Plus simplify the testing process. Keep the BIOS at default. Use RST - and OS independent tester - which will test compatibility issues for the complete system as well as locate any bad memory modules. In less than 3 minutes you will know if the memory is bad. http://www.uxd.com Don't waste your time swapping and pulling etc. Just get the program and be happy.(No, I'm not affiliated with Ultra-X. I just happen to use the program) On Wed, 21 Feb 2001, you wrote: ##On Wednesday 21 February 2001 02:24 pm, Heather wrote: ## On this subject of RAM incompatibility... ## ## I have a stick of RAM that someone gave me to boost me up past 64mb. ## When I first installed it it would do ok, but then it would get where ## sometimes it would show on boot up and others it wouldn't then (in ## evil windows since i haven't put it back after installing LM) my ## computer started popping up more errors and illegals than it ever had ## before. When I pulled the RAM it went back to normal (for windows). ## Is there a way for me to find out if the 2 sticks are just ## incompatible or if the 1 stick is just borked up? ## ##Not really. The only way to actually test ram is on a _very_ ##expensive, purpose built machines that very few people would ever have ##access to (lab equipment). What is more important to understand is ##just how much ram can be affected by other parts of the system. ##Particularly the motherboard, cpu, cache, etc. The best ram test apps ##like 'memtest86', actually test the whole system, so the appearance of ##errors are not necessarily due to bad ram. Also important to ##consider, is that ram is very heat and voltage tolerant, especially ##when compared to the other system components. IOW's, it's usually not ##the culprit. ## ## Most often there's no problem mixing ram sizes or "labels" (eg pc66, ##100, 133, etc). I've got two 128mb sticks, one pc100, one pc133 ##that'll run 'memtest86', L2 disabled, together for an extended time at ##155 mhz with -0- error at 3.55V. So is my pc100 mislabeled? No, ram ##is what it'll do with -0- errors over time. But I digress ## ## First check your bios settings. The settings easiest on the ram are ##the 'slow' settings. (eg, cas3-3-3, precharge disabled, no ECC for ##sdram). Then most ram problems can often be solved by moving the sticks ##to different slots and/or changing the order they're installed in. ##Sometimes just reseating the ram cures the problem. Next most likely ##culprit is the motherboard. A stick of pc66 ram that will run without ##errors at 133mhz (twice it's rated speed) in one motherboard, might not ##work reliably at all in a different (lesser) motherboard even at it's ##default 66mhz. It's just another situation that illustrates how ##important it is to base a system on a good quality motherboard and a ##good power supply. Many of the better motherboards (eg, Asus, Soyo, ##Abit, Epox, MSI, etc) provide more than the standard IO voltage to the ##ram by default (about +10%). This greatly enhances ram stability and ##performance at, or even far above it's manufacturers rating. ## ##So what'a you do? Try reseating (clean the contacts), swappin ##around, tryin in other motherboards (ie, see if it works in a different ##system), give it some more voltage (if you've got a good motherboard). ##'memtest86' is a good check in that you can toggle the L2 cache off/on. ##Many cache error problems often get blamed on the ram. If none of that ##fixes the problems, then give the ram to somebody you don't like ;) ##. and try again with a better motherboard/power supply and some new ##ram ;
RE: [newbie] Testing for bad RAM
Title: RE: [newbie] Testing for bad RAM I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this?
Re: [newbie] Testing for bad RAM
On Tuesday 20 February 2001 14:19, you wrote: Hi Dennis, I've been told by local computer techs that if your bios sees the ram at bootup ,( in other words detects it and counts it off on the first screen that shows your primary and secondary IDE devices and you can hit del to get to bios) then the ram memory is good and should be functional. I am not a technician so I am relying on their advice. Find some new Techs... :) this is totally false, being a Tech myself with over 18 years experience I know for a fact that you can indeed have a system with either bad ram or incompatiable ram and the system will still post.. BIO's does not check or test each and every register on a stick of ram this can only be accomplished by either using a dedecated ram tester ( most repair shops have one ) or the less reliable method is PC-Check or one of it's many clones.. One of the other gotcha's with newer systems is ram module incompatibilitys two different manufactures modules installed and one being either of a different speed or just plain incompatiable and these problems 99% of the time do not show up until an OS is loaded and the ram is fully utilized... Regards, Scott -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mark Johnson Sent: Tuesday, February 20, 2001 1:31 PM To: LinuxNewbie (E-mail) Subject: [newbie] Testing for bad RAM I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this? Content-Type: text/html; charset="iso-8859-1"; name="Attachment: 1" Content-Transfer-Encoding: quoted-printable Content-Description:
Re: [newbie] Testing for bad RAM
On this subject of RAM incompatibility... I have a stick of RAM that someone gave me to boost me up past 64mb. When I first installed it it would do ok, but then it would get where sometimes it would show on boot up and others it wouldn't then (in evil windows since i haven't put it back after installing LM) my computer started popping up more errors and illegals than it ever had before. When I pulled the RAM it went back to normal (for windows). Is there a way for me to find out if the 2 sticks are just incompatible or if the 1 stick is just borked up?
[newbie] Testing for bad RAM
I am suspicious that my RAM is bad. Is there anyway in linux that I can confirm this?
