MAP | 1240: |
| Memory | Problem | Resolution |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
Purpose | of | This | MAP |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
Note: |
| The |
| firmware checkpoint that sent you | here | could | be | one |
| of | the | following: | |||||||||||||
E122, E213, E214, E220 or E3xx. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||||||||
These | checkpoints |
| are | referred | to | as | "a | memory | checkpoint" | in |
| this | MAP. |
|
| ||||||||||
Use | this | MAP | to | trouble shoot | a | problem | during | the | memory | test | when | the | system | ||||||||||||
stops | at |
| a memory checkpoint and no error | code | is | displayed | on the | system | console. | ||||||||||||||||
General | Memory | Information |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |||
Be | sure |
| to | unplug | the | power | cable | before | removing | or | installing | the | memory |
| modules | ||||||||||
to avoid damage to them. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||
Model | 150 |
| memory | modules | do not | need | to | be | installed | in | pairs | and | can | be | installed | ||||||||||
in any slot on the system board. There is | no | requirement that |
| one | slot | be | installed | ||||||||||||||||||
before | the | other. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Refer to “Memory Modules” on page
Note: | If the | symptom | changes, | check | for loose | cards, | cables, and obvious |
problems. If | you do | not find | the | problem, go | to “MAP | 1540: Minimum Configuration” | |
on | page |
|
|
|
|
|
|
Step 1240-1
1. Ensure that the diagnostics and the operating system are shut down.
2. Power off the system. Refer to "Powering Off the System".
3. Remove and
4. Power on the system. Refer to "Powering On the System".
Does the system stop with a memory checkpoint displayed on the operator panel?
NOReseating the memory modules has corrected the problem.
Go to"MAP 0410: Repair Checkout" in theDiagnostics Information for
Multiple Bus Systems.