SVANDUSEN Scratch Page

CPU (Processor) Testing
SVANDUSEN 19:13, 26 May 2010 (UTC)

{|fontsize="14" border=".05" fontweight="bold" cellpadding=".5" width="100%" {|fontsize="8" cellpadding=".5" border=".05" font-weight="bold" cellpadding=".5" 1. Socket Type 2. Obvious Physical Damage
 * align="left" padding=".5"|CPUs are the "brains of the computer system. This is where all of the information and instructions are gathered from, processed, and redistributed to the other components of the system.  The following will be a description of a VERY RUDIMENTARY TEST to determine the viability of a CPU to function in a system.  In actuality, there are a multitude of details and issues involved that would take far more space to cover and time to perform than is practical in these circumstances.  This is a very basic overview of the essentials that are necessary to get through the process.  For more information please consult other experienced volunteers, instructors, or research such sources as Wikipedia or forums on Google.
 * align="left" padding=".5"|CPUs are the "brains of the computer system. This is where all of the information and instructions are gathered from, processed, and redistributed to the other components of the system.  The following will be a description of a VERY RUDIMENTARY TEST to determine the viability of a CPU to function in a system.  In actuality, there are a multitude of details and issues involved that would take far more space to cover and time to perform than is practical in these circumstances.  This is a very basic overview of the essentials that are necessary to get through the process.  For more information please consult other experienced volunteers, instructors, or research such sources as Wikipedia or forums on Google.
 * width="10%" align="center"|STEPS
 * width="90%" align="center"|NOTES AND DETAILED INSTRUCTIONS
 * Collect ||CPUs will accumulate in two areas:
 * Advanced Testing Incoming Rack - there is a covered, foam lined bin on the rack labeled "Incoming CPUs".All CPUs extracted from systems by System Evaluation or other departments and CPUs that have come to the store as customer returns are supposed to be brought and deposited in this container. CPUs extracted in Advanced Testing during Motherboard triage should be deposited here as well.
 * Receiving - there is a box on the top shelf of their rack, next to 'Unsorted Memory' labeled 'CPUs'. In theory, all processors with pins are supposed to be brought immediately to us by Receiving, however, exceptions do occur.  Other types of CPUs may gather there as well.
 * '''At least once a day (preferably twice to three times) the contents of these collection points should be gathered and evaluated.
 * Pre-test Evaluation and Storage || Evaluate the collected CPUs as follows:
 * '''At least once a day (preferably twice to three times) the contents of these collection points should be gathered and evaluated.
 * Pre-test Evaluation and Storage || Evaluate the collected CPUs as follows:
 * Pre-test Evaluation and Storage || Evaluate the collected CPUs as follows:
 * Intel 478 and 775 - Retain in Pre-test Storage.
 * AMD 754, 939, AM2/AM2+/AM3, Phenom - Retain in Pre-test Storage.
 * Intel other than 478 or 775 (e.g.. 370, slot processors, etc.) - Automatic Recycle.
 * AMD other than 754, 939, AM2/AM2+/AM3 (e.g., 462 [socket A], socket 5, socket 6, etc.) - Automatic Recycle.
 * Non-Intel or AMD (e.g., Cryix, VIA, etc.) - Automatic Recycle.
 * Non-desktop system processors (e.g., laptops, servers [Intel Xeon, AMD 940, etc.], etc.) - Automatic Recycle.
 * Primarily this will be bent pins.
 * This will only occur with PGA (Pin Grid Array) processors; socket 478s, 754s, 939s, AM2s, etc.
 * This is not necessarily a sign to recycle the processor. Many can be rescued.  A determination will be made at the actual time of testing.
 * This step of evaluation is primarily to determine whether there is an inordinate amount of damage occurring prior to their arrival in Advanced Testing so that the sources can be advised and corrective steps taken.

Put the sorted processors into Pre-test Storage in TARDIS. 3. Sort by Speed
 * Very rarely ... there will be signs of scorching; indicating that a major thermal event has taken place sometime during the life of the processor. Again, this is not necessarily a sure indicator that the processor should be recycled unless the damage is obviously severe. This is a judgment call that experience will teach.
 * This is basically in the same place as the tested processors; on the self, in trays or other containers, in places designated be socket type.
 * SDRAM -
 * PC 66 - Automatic Recycle.
 * PC 100 - Automatic Recycle.
 * PC 133 - Set aside to sort by capacity.


 * DDR -
 * PC 1600 (200 MHz) - Automatic Recycle.
 * PC 2100 (266 MHz) - Set aside to sort by capacity.
 * PC 2700 (333 MHz) - Set aside to sort by capacity.
 * PC 3200 (400 MHz) - Set aside to sort by capacity.


 * DDR2 -
 * PC2 3200 (400 MHz) - Set aside to sort by capacity.
 * PC2 4200 (533 MHz) - Set aside to sort by capacity.
 * PC2 5300 (667 MHz) - Set aside to sort by capacity.
 * PC2 6400 (800 MHz) - Set aside to sort by capacity.
 * PC2 8500 (1066 MHz) - Set aside to sort by capacity.
 * PC2 9600 (1200 MHz) - Store in TARDIS until a test board is available.

4. Sort by Capacity
 * SDRAM -
 * 32 thru 128 MB - Automatic Recycle.
 * 256, 512 MB, & 1 GB - Stack by capacity in designated area on table (orange label) to be loaded into test board.


 * DDR -
 * 128, 256, 512 MB, & 1 or 2 GB - Stack by capacity in designated area on table (orange label) to be loaded into test board.


 * DDR2 -
 * 256 & 512 MB, 1 or 2 GB - Stack by capacity in designated area on table (orange label) to be loaded into test board.

5. Unspecified speed and/or capacity
 * Frequently RAM will not be labeled as to speed or capacity by the manufacturer. In such cases it is necessary to determine these characteristics by other means.


 * SDRAM -
 * Insert RAM into the test device in front of monitor (SIMM Check II).
 * Push red button(On/Off) to power on.
 * Wait for screen to display "INNOVENTIONS".
 * Press blue button (F1).
 * If display ("Basic Test") indicates speed less than 133 MHz - Automatic Recycle.
 * If display ("Basic Test") indicates capacity less than 32X64 (256 MB - see chart on test device for other equivalents) - Automatic recycle.
 * If display goes past "Basic Test" - press blue F1 button until "Basic Test" is displayed.
 * If display will not hold on "Basic Test" or error message is displayed - Automatic recycle.
 * If speed and capacity can be determined, and both meet specification -
 * Press red button (On/Off) to turn off test device.
 * Remove RAM.
 * Label with speed and capacity.
 * Stack in designated area on table (orange label) to be loaded into test board.


 * DDR & DDR2 -
 * Use a test board. Several boards give an accurate reading regarding capacity and speed (see also "Loading & Testing).
 * Load a single stick.
 * Power on at the power supply.
 * Wait until the system enters "MemTest".
 * Read the capacity and speed from the display.
 * Power off at the power supply.
 * Remove the stick.
 * Label and stack in designated area on table (orange label) to be loaded into test board.
 * Research online. Several websites dealing in RAM specifications have been bookmarked and other websites can be accessed by "Googling" using the manufacturer and or model/part number (if available).
 * Locate a website.
 * Locate the RAM in question in the website.
 * Note the capacity and speed in the specifications.
 * Label and stack in designated area on table (orange label) to be loaded into test board.
 * Ask an instructor. Some of them know ways to determine information by examining the imbedded chips.

6. "Kit of 2"
 * Some manufacturers, especially Kingston and Super Talent have a marketing ploy of packaging RAM in pairs totaling a specific capacity, usually 512 MB and 1 or 2 GB. In these cases, each stick has only one half of the total capacity; eg. a 1GB "Kit of 2" consists of two 512 MB sticks.
 * This will be indicated somewhere on the label, either as a distinct statement as such or, in the case of Kingston, within the model number; eg. KVR400x64C3AK2/1G. In this case the "400" indicates the speed, the "1G" indicates the total capacity of the kit, and the "K2" indicates that the stick is part of the kit.  The actual capacity of the stick in this example is one half of 1 GB or 512 MB.
 * Both halves of such kits are not always present when they come into our possession but they are testable separately.
 * When labeling such sticks after testing, treat each one as a separate stick and label it with its actual individual capacity (see "Labeling and Routing").
 * Test || Test the sorted RAM in the wall-mounted test boards as follows:
 * Test || Test the sorted RAM in the wall-mounted test boards as follows:

1. Select -Select the RAM to be loaded according to the following criteria:


 * Must all be of the same type.
 * Must all be of the same speed.
 * May be of mixed size; ie. 256 and 512, etc.
 * Should be balanced by size across channels (all test boards are "Dual Channel"); ie. 512 MB in channel 1 and 256 MB in channel 2 (see "Load").
 * Should be all of the same brand or paired by brand, if possible, for compatibility and to resolve "latency" issues (particularly with DDR2).
 * Balance and brand can be worked around if single sticks are all that are available (see "Boot Up").

2. Load - Load the RAM into the test boards as follows:


 * Be aware ---
 * Banks (the slots into which the sticks are inserted) are designated 0, 1, 2, & 3 moving from inboard [closest to the CPU] to outboard [farthest from the CPU]).
 * Channels consist of two banks (all test boards are dual channel but will operate in single channel mode).


 * Banks may be color coded; ie. two black and two blue.
 * Clips on the banks (hinged plastic parts at the ends of the banks that hold the sticks in place) may be color coded; ie. two black and two white.
 * Some boards may have a separation between pairs of banks, some do not.
 * Some boards may alternate color coded banks or clips; ie. blue-black-blue-black, or pair them; ie. blue-blue-black-black.
 * In any case, Channels are always composed of pairs of banks. Either the banks themselves or the clips will be of matching color.
 * Intel cpu boards will nearly always match banks 0 and 2 as channel 1 or A, and banks 1 and 3 as channel 2 or B.
 * AMD cpu boards will nearly always match banks 0 and 1 as channel 1 or A, and banks 2 and 3 as channel 2 or B.
 * Load from inboard to outboard.
 * Load largest capacity inboard to smallest outboard; eg. 1 GB in banks 0 and 2 and 512 MB in banks 1 and 3 or 512 MB in bank 0, 256 MB in bank 1, and 128 MB in bank 2.


 * Insert the stick into the bank.


 * Align the notches on the stick with the "key" (the small bar) in the groove of the bank.
 * Make sure that both ends of the stick are in the groove of the bank.
 * Press firmly and evenly until the stick moves completely into place along its entire length and the clips click into place in the notches at the end of the stick securing it in place.
 * Manually check all clips to confirm that all are closed properly and the stick is securely in place.


 * Power on using the switch on the power supply and, if necessary, the power button switch attached to the test board.


 * Set the KVM channel to the corresponding number or letter of the test board (orange label w/ arrow on power supply).

3. Observe boot-up process


 * The system should go through a boot up process appropriate to that particular board and its corresponding BIOS version and arrive at the Dynamic Host Configuration Protocol (DHCP followed by a spinning slash mark), indicating that it is booting from the network.


 * Changes in total RAM capacity, lack of balance across channels, or issues peculiar to a particular board (eg. "System Fan Not Functioning") may result in the appearance of a prompt message directing you to hit a function key (F1, F2, or F4), ESC, or "any key". in order to continue. Do so. The system should then continue on to DHCP.


 * Some boards, for whatever reason, may require you to pass through the BIOS. Simply hit the key indicated by the prompt message, hit ESC, and then hit Enter.  The system should then continue on to DHCP.


 * Following the completion of DHCP the system should arrive at a program called MemTest without any additional manipulation.

4. Observe MemTest


 * This will be a blue screen with white lettering (occasionally monochrome) that will provide information about the RAM being tested (and the CPU as well).


 * A box (outlined in white, dotted lines) in the upper right hand corner will indicate "Pass %", "Test %", "Test #", "Testing", and "Pattern" ('''"Testing" and "Pattern" are not relevant for now). This will indicated what point in the progress of each pass and test has been achieved.


 * A line labeled "Settings", beginning on the far left of the screen, will provide information about RAM speed and "latency" (latency is not relevant for now). RAM speed is not present in all versions of MemTest.


 * A row of column headings will appear about halfway down the screen and extend all the way across. Only "WallTime", "Cached", and "Pass" are relevant.


 * WallTime indicates how much time has elapsed since MemTest began.
 * Cached indicates how much total RAM has been loaded onto the board.
 * Pass indicates what pass the testing process is on.

5. Monitor MemTest


 * Indications of Failure - 


 * No video, sometimes accompanied by a series of beeps or video is distorted -


 * The system will not boot up or show any other video signal or-
 * The video is streaked, broken up into blocks, completely fragmented into dancing pixels, or wildly discolored.
 * One or more sticks may be bad and/or incompatible; ie. ECC. See "Remedies"


 * "Red Screen" -


 * The most common indicator of failure.
 * The bottom half of the screen turns red, a new set of column headings appears, the section fills with data and may begin scrolling rapidly. See Remedies.
 * Usually occurs within the first two tests of the first pass but may, occasionally, happen much deeper in the testing process.
 * One or more sticks have failed. See "Remedies".


 * "WallTime" is frozen -


 * The clock stops ticking ... period.
 * This may happen very early in the testing process or may occur much deeper.
 * One or more sticks have failed. See "Remedies".


 * "Cached" column indicates a different total capacity than the known amount physically loaded -


 * The total capacity of RAM indicated by this column must equal the known total capacity of the RAM physically loaded onto the board.
 * If not ... this indicates that the system is not reading all of the RAM that has been loaded.
 * It is permissible for the speed indicated by MemTest to differ from the speed indicated on the stick (it will simply run at a slower speed ... this is not optimal but acceptable).
 * This may NOT be a problem with the RAM. This may be a problem with one or more of the banks on the test board.
 * One or more sticks and/or banks have failed. See "Remedies."


 * Remedies - 


 * This can be tedious, time consuming, and tricky, but with the technology available it is the only way.


 * Red Screen -  here there is an important clue.


 * A new row of column headings will appear above the red area (the bottom half of the MemTest screen). Only Test, Pass, and Failing Address are relevant here.


 * Test and Pass will indicate at what point in the testing process the failure occurred. If it occurs early (eg. pass 0, test 1), all well and good.  If it occurs deeper in the testing process, it may be that a failing stick will begin testing well and then fail, making it more difficult to identify.
 * Failing Address is in two parts which indicate the pattern (not relevant here) and the point in the total capacity at which the failure occurred.


 * Moving from outboard to inboard, subtract the capacity of each stick from the total until you are in the range at which the failure occurred, eg. four sticks of 256 MB RAM for a total of 1 GB have been loaded. A failure occurs at 368.2 MB on pass 0, test 1.  The failure has occurred between 512 MB, and 256 MB.  Subtracting 256 MB for each of the two outboard sticks (banks 3 & 2) leaves 512 MB. The failure occurred at a point below this capacity.  The failure occurred at a point greater than 256 MB, the capacity of the first inboard stick (bank 0).  Therefore, it is most likely that the stick in bank 1 is the stick that failed.
 * Power off at the switch on the power supply
 * Remove the suspected stick.
 * Restart the testing process and monitor MemTest again for failures.


 * No Video or Cached column indicates lower total capacity than physically loaded.


 * This may simply be a matter of the sticks not being seated properly, or the system does not recognize the RAM in the order in which it was loaded, or it has compatibility issues with brands, latency, etc., OR it has some other problem all its own and refuses to give you any indication as to what it might be.
 * Power off at the switch on the power supply.
 * Remove and re-seat all of the sticks.
 * Change the order, re-balance the load across the channels, reverse the channel position by pairs, etc.
 * Restart the test process and monitor MemTest again for failures.


 * WallTime freezes or the location steps for Red Screen, No Video, or Cached column differential don't resolve the issue.


 * Unfortunately ... it's strictly trial and error from here on.
 * Power off at the switch on the power supply.
 * Remove the suspected stick or sticks, singly or in pairs.
 * Restart the testing process and monitor MemTest again for failures.


 * Repeat as necessary until issues are resolved.


 * If a bad bank or other system failure is suspected for any reason - 


 * Power off at the switch on the power supply.
 * Remove all RAM sticks.
 * Test each bank with a known good RAM stick.


 * If all banks pass, all well and good. If not, power down, remove, stick or sticks, mark the suspected bank or banks with a label, and notify an instructor.
 * If something other than a bad bank or banks is suspected, ie. video or network issues, ask an instructor.

6. For the duration of the testing process - 


 * Check on the progress of the testing process.


 * The time necessary to complete the testing process can vary greatly, depending on the capacity and speed of the RAM that has been loaded, the FSB (Front Side Bus) speed of the CPU or other factors specific to the test board. The time can be less than one hour, with low capacity and/or high speed, or can take an incredibly long time with high capacity and/or low speed (eg. 2 GB of SDRAM at 133 MHz can take nearly 24 hours).  Generally an average load of around 1 GB  of DDR or DDR2 will take between 2.5 and 3.5 hours.
 * A complete testing process consists of three passes, labeled 0-2.
 * Each pass consists of 'eight tests, labeled 1-8.
 * MemTest will continue to run indefinitely until is manually discontinued.
 * If the pass number is 3 or greater, the testing process is complete.


 * Watch for indications of failure, as indicated above, and correct as necessary.

'''7. Repeat these steps for each test board as long as there is RAM to be tested.

8. Do NOT load any boards after 5:00P.
 * Label & Route ||After the testing process has been completed, label and route the tested RAM as follows:
 * Label & Route ||After the testing process has been completed, label and route the tested RAM as follows:

1. Unload the test boards -.


 * Power off at the switch on the power supply.


 * Remove all RAM sticks and take them to the table to be labeled.


 * If possible, remove any old, handwritten labeling to avoid confusion.

2. Label as follows:


 * SDRAM - capacity and speed only. Eg. 256/133.


 * DDR & DDR2 - type and capacity and speed. Eg. DDR2 512/667.
 * DDR and DDR2 have more subtle visual cues (other than the label) and can be easily confused by after-testing users such as build. Therefore, it is highly advisable to make them as distinguishable as possible.


 * Kit of 2 -


 * Label each stick with its true capacity and speed. Eg. a 1GB kit of 2 - each stick would be labeled as 512 MB with the speed.
 * If you have both halves of such a kit, make a small nonstick paper strip label, write "Kit of 2" and "xxx MB (or GB) each" on it, wrap it around the kit, and rubber band it together.

3. Route as follows -


 * The two boxes on the table labeled, "Tested RAM SDRAM & DDR" and "Tested RAM DDR2" -


 * Place the vast majority of the labeled RAM in the appropriate slots in these two boxes (see Store for exceptions).
 * This will be harvested regularly by build and occasionally by the store to fill their needs.


 * TARDIS -


 * The boxes on the table will populate quite rapidly.
 * As they fill (usually once a week or more), empty the slots into the appropriate static free bags in the blue bins on the shelf in TARDIS.
 * As the bags fill, tape them shut and place them in the RAM Overstock bin on the top shelf.
 * Replace the bag with an empty one labeled with type, capacity, speed (in MHz) and PC or PC2 code (PC 2100, PC 2700 ... PC2 4200, PC2 5300 ... etc.)
 * These will be harvested by build and the store to meet their needs.


 * Store -


 * Some tested RAM should be taken directly to the store (do not put in the outgoing "Store" box on the rack shelf next to the TARDIS door).


 * SDRAM -
 * 1GB/133


 * DDR -


 * 1GB/any speed.
 * 512/400 - pairs (or more ) of quality brands (Hynix, Nanya, Samsung, etc.). Leave singles in the box for build.


 * DDR2 -


 * 1 or 2 GB/any speed.
 * 256 or 512/667 or higher.


 * All PAIRED & BUNDLED Kit of 2 sets.


 * Any sticks, paired or not, any capacity and speed, with "heat spreader" technology ... metal plates over the embedded chips that run the length of the stick on one or both sides.

POWER OFF ALL TEST BOARDS AT THE SWITCH ON THE POWER SUPPLY WHETHER THE TESTING PROCESS IS COMPLETE OR NOT!
 * End of DAY ||
 * End of DAY ||