Memory tester: Difference between revisions

Content deleted Content added
Software testers: display needed usually
Importing Wikidata short description: "Computer memory testing equipment"
 
(41 intermediate revisions by 21 users not shown)
Line 1:
{{Short description|Computer memory testing equipment}}
{{Cleanup|date=April 2009}}
{{refimprove|date=May 2020}}
'''Memory testers''' are specialized test equipment used to test and verify [[Volatile memory|memory modules]] typically in [[SIMM]] or [[DIMM]] configurations. It detects functional failures of memory modules.
{{use dmy dates|date=December 2021|cs1-dates=y}}
{{use list-defined references|date=December 2021}}
'''Memory testers''' are specialized test equipment used to test and verify [[Volatile memory|memory modules]] typically in [[SIMM]] or [[DIMM]] configurations. It detects functional failures of memory modules.
 
== Types ==
Memory module testers can be broadly categorized into two types, [[computer hardware|hardware]] memory testers and [[software]] [[diagnostic program]]s that run in a [[Personalpersonal computer|PC]] environment. Hardware memory testers have more sophisticated and comprehensive test features built into the tester as compared to software diagnostic testing programprograms. Software diagnostic does allow for detection of possible problems when memory modules are already installed on the computer system.
 
Memory module testers can be broadly categorized into two types, [[hardware]] memory testers and [[software]] [[diagnostic program]]s that run in a [[Personal computer|PC]] environment. Hardware memory testers have more sophisticated and comprehensive test features built into the tester as compared to software diagnostic testing program. Software diagnostic does allow for detection of possible problems when memory modules are already installed on the computer system.
 
=== Hardware testers ===
High-end [[automatic test equipment]] (ATE) Class Memory testers are used by most OEM memory chip manufacturers such as Samsung, Hyundai, Micron…etc. They are typically priced starting at one million dollars per system. This equipment must be operated by well trained semiconductor engineers. ATE Class Memory testers are built with very complex test algorithms to detect memory faults during the final stages of memory chip packaging.
 
Mid-range memory testers typically priced under $26,000 ,<ref>http://www.pcstats.com/articleview.cfm?articleID name=1174<"AMT"/ref>, and are commonly found in memory module manufacturing assembly houses. These testers are built to support mass volumes of memory module testing. They are also used for detecting assembly faults caused by mis-soldering and cross-cell contamination after chips are assembled onto [[Printed circuit board|PCB]] or SIMM cards. These memory testers are usually docked onto an automatic handling system for high volume production testing, thus eliminating manual intervention by an operator.
High-end automatic test equipment (ATE) Class Memory testers are used by most OEM memory chip manufacturers such as Samsung, Hyundai, Micron…etc. They are typically priced starting at one million dollars per system. This equipment must be operated by well trained semiconductor engineers. ATE Class Memory testers are built with very complex test algorithms to detect memory faults during the final stages of memory chip packaging.
 
Mid-range memory testers typically priced under $26,000 <ref>http://www.pcstats.com/articleview.cfm?articleID=1174</ref>, and are commonly found in memory module manufacturing assembly houses. These testers are built to support mass volumes of memory module testing. They are also used for detecting assembly faults caused by mis-soldering and cross-cell contamination after chips are assembled onto [[Printed circuit board|PCB]] or SIMM cards. These memory testers are usually docked onto an automatic handling system for high volume production testing, thus eliminating manual intervention by an operator.
 
Low-end memory testers are usually relatively low cost ranging from $1000 – $3000. Their main features are portability, ease of use and relatively small size. They are typically used by the service industry especially by computer service technicians, RMA departments, memory reseller/brokers/ and wholesalers for verifying and testing memory modules that fails in PC system or before going into PC. Quality and features of this range of memory testers varies greatly depending on the manufacturer. A good memory tester is built with features comparable with high-end ATE and medium range memory tester. The key is to provide a simple to use tester at an affordable price that is still effective in capturing most memory faults and failures.
 
=== Software testers ===
Memory diagnostic software programs (e.g., [[memtest86]]) are low-cost or free tools used to check for memory failures on a PC. They are usually in the form of a bootable software distribution on a [[floppy disk]] or [[CD-ROM]]. The diagnostic tools provide memory test patterns which are able to test all system memory in a computer. Diagnostic software cannot be used when a PC is unable to [[boot-up|start]] due to memory or [[motherboard]]. While in principle a test program could report its results by savingsending them to a storage device (e.g., floppy disc) or printer if working, or by sound signals, in practice a working display is required.
 
==== {{anchor|Worm test}}Worm memory tests ====
Memory diagnostic software programs are low-cost or free tools used to check for memory failures on a PC. They are usually in the form of a bootable software distribution on a [[floppy disk]] or [[CD-ROM]]. The diagnostic tools provide memory test patterns which are able to test all system memory in a computer. Diagnostic software cannot be used when a PC is unable to [[boot-up|start]] due to memory or [[motherboard]]. While in principle a test program could report its results by saving them to a storage device (e.g., floppy disc) or by sound signals, in practice a working display is required.
Some stronger memory tests capable of detecting subtle timing problems are implemented as [[self-modifying code|self-modifying]], [[dynamic self-relocation|dynamically self-relocating]] and potentially self-destructive memory [[helpful worm|worm]]s called ''worm memory test'' (or ''worm test'').<ref name="Vector"/><ref name="Wilkinson_2003"/><ref name="Steinman_1986_Worm"/><ref name="Steinman_1986_Toolbox"/>
 
== Detected faults ==
Memory testers are designed to detect two types of faults that affect the functional behavior of a system ( memory chip, logic chips or PCB board).: TheyNon-Permanent arefaults and Permanent faults.
 
*=== Permanent faults ===
Memory testers are designed to detect two types of faults that affect the functional behavior of a system ( memory chip, logic chips or PCB board). They are
Permanent faults affect the logic values in the system permanently, these faults are easier to detect using a memory tester. Examples include:
* Non-Permanent faults
* Permanent faults
 
* Incorrect connections between [[integrated circuit]]s, boards….boards, etc. (e.g. missing connections or shorts due to solder splashes or design fault)
Non-Permanent faults occur at random moments. They affect a system's behavior for an unspecified period of time. The detection and localization of non-permanent faults are extremely difficult with a memory tester. Sometimes non-permanent faults will not affect the system's operation during testing.
* Broken component or parts of components
* Incorrect IC Maskmask, (Manufacturing problem)
* Functional design errors (logical function that had to be implemented, is designed incorrectly).
* Defective storage cell
 
There=== are two types of nonNon-permanent faults : ===
Non-Permanent faults occur at random moments. They affect a system's behavior for an unspecified period of time. The detection and localization of non-permanent faults are extremely difficult with a memory tester. Sometimes non-permanent faults will not affect the system's operation during testing.
* Transient fault
* Intermittent fault
 
There are two types of non-permanent faults: Transient fault and Intermittent fault.
Transient faults are hard to detect, and there are no well defined faults to detect. Errors in RAM introduced by transient faults are often called software errors, the following examples are possible factors that will contribute to transient faults :
 
Transient faults are hard to detect, and there are no well defined faults to detect. Errors in RAM introduced by transient faults are often called software errors, the following examples are possible factors that will contribute to transient faults :
*[[Cosmic Ray]] ([[UV light]])
 
*[[Alpha Particle]] (Dust)
* [[Cosmic Rayray]] ([[UV light]])
*[[Pollution]]
* [[Alpha Particleparticle]] (Dust)
*[[Humidity]]
* [[TemperaturePollution]]
* [[PressureHumidity]]
* [[VibrationTemperature]]
* [[Pressure]]
*[[Power Supply]] fluctuations
* [[Vibration]]
*[[Electromagnetic interference]]
* [[Power Supplysupply]] fluctuations
*[[Electrostatic discharge|Static electrical discharges]]
* [[Electromagnetic interference]]
*[[Ground loop (electricity)|Ground loops]]
* [[Electrostatic discharge|Static electrical discharges]]
* [[Ground loop (electricity)|Ground loopsloop]]s
 
Intermittent faults are caused by non-environmental conditions such as:
*Loose connections
*Deteriorating or aging components
*Critical Timing
*[[Electrical resistance|Resistance]] and [[capacitance]] variation
*Physical irregularities
*Noise (noise disturbs signals in the system)
 
* Loose connections
Permanent faults affect the logic values in the system permanently, these faults are easier to detect using a memory tester. Examples include:
* Deteriorating or aging components
* Critical Timingtiming
* [[Electrical resistance|Resistance]] and [[capacitance]] variation
* Physical irregularities
* Noise (noise disturbs signals in the system)
* [[Row hammer]] susceptibility
 
== See also ==
*Incorrect connections between [[integrated circuit]]s, boards….etc (e.g. missing connections or shorts due to solder splashes or design fault)
* [[memtest86]]
*Broken component or parts of components
* [[Power-on self-test]] (POST)
*Incorrect IC Mask, (Manufacturing problem)
* [[NOP slide]]
*Functional design errors (logical function that had to be implemented, is designed incorrectly.
* [[Apple Worm]]
 
== References ==
{{Reflist}}|refs=
<ref name="AMT">{{cite web |title=Innoventions Ramcheck Advanced Memory Tester - PCSTATS.com |website=www.pcstats.com |url=http://www.pcstats.com/articleview.cfm?articleID=1174}}</ref>
 
<ref name="Vector">{{cite book |title=The Worm Memory Test |publisher=[[Vector Graphic]] |date=2015-10-21<!-- upload date --> |orig-date= |url=http://deramp.com/downloads/vector_graphic/software/manuals/Worm.pdf |access-date=2021-12-13 |url-status=live |archive-url=https://web.archive.org/web/20190515181617/http://deramp.com/downloads/vector_graphic/software/manuals/Worm.pdf |archive-date=2019-05-15}} (3 pages) (NB. From a [[Vector Graphic 3]] service manual.)</ref>
 
<ref name="Wilkinson_2003">{{cite web |title=The H89 Worm: Memory Testing the H89 |author-first=William "Bill" Albert |author-last=Wilkinson |date=2003 |orig-date=1996, 1984 |work=Bill Wilkinson's Heath Company Page |url=https://www.heco.wxwilki.com/h89worm.html |access-date=2021-12-13 |url-status=live |archive-url=https://web.archive.org/web/20211213130013/https://www.heco.wxwilki.com/h89worm.html |archive-date=2021-12-13 }}</ref>
 
<ref name="Steinman_1986_Worm">{{cite journal |title=The Worm Memory Test |author-first=Jan W. |author-last=Steinman |___location=West Linn, Oregon, USA |journal=[[Dr. Dobb's Journal of Software Tools for the Professional Programmer]] |publisher=[[M&T Publishing, Inc.]] / [[The People's Computer Company]] |publication-place=Redwood City, California, USA |department=The Right to Assemble (TRTA) |volume=11 |issue=9 |id=<!-- |number=-->#119. ark:/13960/t74v34p9p {{CODEN|DDJOEB}} |issn=1044-789X |date=1986-09-01 |pages=114–115 (662–663) |url=https://archive.org/details/dr_dobbs_journal_vol_11/page/662/mode/1up |access-date=2021-12-13 }} [https://ia803109.us.archive.org/13/items/dr_dobbs_journal_vol_11/dr_dobbs_journal_vol_11.pdf] (2 pages)</ref>
 
<ref name="Steinman_1986_Toolbox">{{cite book |title=Dr. Dobb's Toolbook of 68000 Programming |chapter=III. Useful 68000 Routines and Techniques, 16. The Worm Memory Test |author-first=Jan W. |author-last=Steinman |___location=West Linn, Oregon, USA |publisher=[[Brady Book]] / [[Prentice Hall Press]] / [[Simon & Schuster, Inc.]] |publication-place=New York, USA |date=1986 |pages=341–350 |lccn=86-25308 |isbn=0-13-216649-6 |chapter-url=http://www.bytesmiths.com/Publications/Worm%20Memory%20Test%20-%20Steinman_1986-01-01-1.pdf |access-date=2021-12-13 |url-status=live |archive-url=https://web.archive.org/web/20211213202006/http://www.bytesmiths.com/Publications/Worm%20Memory%20Test%20-%20Steinman_1986-01-01-1.pdf |archive-date=2021-12-13}} (1+5+10+1 pages)</ref>
 
}}
 
[[Category:Computer_memoryComputer memory]]
[[Category:Utility software types]]