Memory problems
See this section to resolve issues related to memory.
Common memory problems
Multiple memory modules in a channel identified as failing
Complete the following procedure to solve the problem.
- Reseat the memory modules; then, restart the server.
- Remove the highest-numbered memory module of those that are identified and replace it with an identical known good memory module; then, restart the server. Repeat as necessary. If the failures continue after all identified memory modules are replaced, go to step 4.
- Return the removed memory modules, one at a time, to their original connectors, restarting the server after each memory module, until a memory module fails. Replace each failing memory module with an identical known good memory module, restarting the server after each memory module replacement. Repeat step 3 until you have tested all removed memory modules.
- Replace the highest-numbered memory module of those identified; then, restart the server. Repeat as necessary.
- Reverse the memory modules between the channels (of the same processor), and then restart the server. If the problem is related to a memory module, replace the failing memory module.
- (Trained technician only) Install the failing memory module into a memory module connector for processor 2 (if installed) to verify that the problem is not the processor or the memory module connector.
- (Trained technician only) Replace the system board.
Displayed system memory is less than installed physical memory
Complete the following procedure to solve the problem.
- Make sure that:- No error LEDs are lit on the operator information panel. 
- No memory module error LEDs are lit on the system board. 
- Memory mirrored channel does not account for the discrepancy. 
- The memory modules are seated correctly. 
- You have installed the correct type of memory module. 
- After changing or replacing a memory module, memory configuration is updated accordingly in the Setup Utility. 
- All banks of memory are enabled. The server might have automatically disabled a memory bank when it detected a problem, or a memory bank might have been manually disabled. 
- There is no memory mismatch when the server is at the minimum memory configuration. 
 
- Reseat the memory modules, and then restart the server. 
- Check the POST error log: - If a memory module was disabled by a systems-management interrupt (SMI), replace the memory module. 
- If a memory module was disabled by the user or by POST, reseat the memory module; then, run the Setup Utility and enable the memory module. 
 
- Re-enable all memory modules using the Setup Utility, and then restart the server. 
- (Trained technician only) Install the failing memory module into a memory module connector for processor 2 (if installed) to verify that the problem is not the processor or the memory module connector. 
- (Trained technician only) Replace the system board. 
Invalid memory population detected
- Invalid memory population (unsupported DIMM population) detected. Please verify memory configuration is valid.
- See Memory module installation rules and order to make sure the present memory module population sequence is supported.
- If the present sequence is indeed supported, see if any of the modules is displayed as “disabled” in Setup Utility.
- Reseat the module that is displayed as “disabled,” and reboot the system.
- If the problem persists, replace the memory module.