Quantcast
Channel: Intel Communities: Message List - Servers
Viewing all articles
Browse latest Browse all 9829

Re: Invalid DIMM population error on S2600CP server board

$
0
0

Dan_Intel wrote:

 

Hi,

The board that you have is an Intel(R) Server Board S2400CP4. Here are our recommendations for this issue:

 

- Make sure that the memory complies with the specifications described on the Technical Product Specification page#3:

 

http://download.intel.com/support/motherboards/server/s2600cp/sb/g26942005_s2600cp_p4000cp_tps_rev19.pdf

 

- Test the board without any memory installed looking for three beep codes, if there are none your board could have defective memory slots.

 

- Test with one memory module installed on the A1 slot only (minimum memory). You can also test with one memory module on slot E1 for the second processor.

 

- If the issue persists, test with validated memory from the following list:

 

Server Products — Memory and Hardware Compatibility

I'm getting 3 beeps whether I insert DIMMs or not. When no DIMMs are inserted, there are three beeps and the error message on the screen as well as the one corresponding to the LED code is "No usable memory".

 

When a DIMM is present in either A1 or E1, there are three beeps and the error message on the screen is "Invalid DIMM population" and the LEDs are lit as follows:

Lower Nibble LEDs (lit green): #1, #2, #3

Upper Nibble LEDs (lit amber): #5, #6, #7

 

As I said, this combination of lit LEDs doesn't seem to be accounted for in the specifications. If anybody can confirm that the LEDs are supposed to be lit this way for a "DIMM population error", I'd appreciate it.

 

At this point, my biggest concern is that this error might be caused by bent pins in the CPU socket. What I noticed about the pins is that they're not very rigid, and they have a bit of springiness to them. I can see how they could be bent easily.


Viewing all articles
Browse latest Browse all 9829

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>