Difference between revisions of "User:SVANDUSEN"
Jump to navigation
Jump to search
Line 134: | Line 134: | ||
'''3. Observe boot-up process''' | '''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). | + | ::*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. | ::*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. | ||
Line 224: | Line 224: | ||
:::::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. | :::::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 | + | :::::*Power off at the switch on the power supply |
:::::*Remove the suspected stick. | :::::*Remove the suspected stick. | ||
:::::*Restart the testing process and monitor MemTest again for failures. | :::::*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 - ''' | ||
+ | |||
+ | ::::*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. | ||
|- | |- | ||
| Pair the Device || | | Pair the Device || |
Revision as of 13:29, 7 July 2010
RAM (Memory) Testing
SVANDUSEN 19:13, 26 May 2010 (UTC)
RAM is a deceptively simple device to test. It appears to be simply a matter of gathering, sorting,loading,removing, labeling, and storing; repeated over and over again. In actuality, there are a multitude of details and issues involved that would take far more space to cover than is alloted here. 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.
|