207 Memory Initialization Error

[Mike Mayr]

I am getting a 207 Memory Initialization Error on Processor 2 DIMM 2 and DIMM 3. Whenever I have 2 processors in the machine. The DIMM slots filled are: A, B, C, D, E, F on both processors and the DIMMs are Kingston 4GB Quad Rank DIMMS. Any ideas? I have eliminated the system board, and rotated DIMMs/CPUs.

[Erdogan Temur]

Server model ?

[Mike Mayr]

Ooops sorry I forgot that - DL380G6

[Erdogan Temur]

Hi Mikde,

Memory configration and model for chech the below link.

https://community.hpe.com/hpeb/attachments/hpeb/itrc-264/105674/1/361938.pdf

Kingston :((( I do not recommend you to use

Regards.

[Axeblokie]

I'm having the same problem, with the same server a DL380 G6, on slot 6 and 9 on one machine, and just slot 6 on another.
Slots A, B and C populated on both CPU's.
I'm using HP memory, as listed on the compatibility list, part number 500656-B21.

I've performed a BIOS update in the vain hope that it would work, alas it did not.
Out of 27 servers, 2 of them have this error, yet the other 25 are fine.

Any ideas??

[Mike Mayr]

Mine turned out to be 3 DOA system boards - the last one I put in fixed it. The 3rd system board gave me the same issue but on CPU 2. That's when I noticed that several pins in the socket itself were bent - check your sockets. I have run into similar issues on 2 other DL380G6s since then - again bent CPU sockets fresh out of the bag.

[bbelle]

This happened to me on a bl460c G7 and all i had to do to correct it is shutdown the server, re-seed the DIMM chips and it booted fine without error.

[Rebecca Huang]

I have run in this on multiple servers - DL380G6 being the most common - and the majority have been damaged CPU sockets on the system board - I am a HP Services CE and work on Proliants on an almost daily basis since I started this thread. If you run into this issue take a flashlight and magnifying glass to the system board and look into the CPU sockets. Look for bent pins, if I am wrong, you've lost a few minutes - if i am right, get a new system board.

[Joshua Post]

Thank you for this thread.  We had the same error messages on one new BL490 G7 server.  Reseating the memory modules resolved the error for us.

[brandaoHPPRO]

How you reset the memory modules ?

I have the same problem with a BL460c G7

Thanks for the help

[Abelder]

Solved it by looking into the processor socket, mine was realy messed up. Had a diagonal line from left to right with bend pins

was on a HP DL 380 G7.

[Juergen_V]

Same problem on two processor DL380 G7. Impacts on both sockets. Multiple Memory 207-Errors.

[HuguoArnaud]

Morning all I have the same error on DL 380 G8. I have reseat the module memory, but error persit. I don't know how to do!

[Cresswell Williams]

Hi Experts

I have the exact same issue on a BL680c G7 even with I25 08/04/2012 ROM installed..... Could this be a fualty DIMM or System Board?

[PhiLoSW]

Hello,

I can confirm that so far every similar issue I had on 380G6/g7 has been related to the processor socket.

But think more broadly, when "bent pin" is mentioned.

I just (30 minutes ago) had the case that when upgrading CPUs on a DL380 G6 from X5570 to X5670 I got faulty dim socket reports on A,D and G of Proc 1. I was worried that the processor was busted and switched them, but it still was on Proc 1 side.

Then I took a strong light and a magnifying glass and found that two tiny (I'd guess <= 0.3mm) pieces of fluff had lodged onto two of the pins.  (Sorry, not a sterile environment here).

Apparently that was enough to either make or block an electrical connection in a way that was not intended. I blew the socket out with air (Giotto Rocket Blower), reseated the CPU. Now memory is fine and the server is currently looping through memory tests without any error or problem.

regards

martin

[Amdrezm]

you can clean slot memory and work fine....   i have the same problem... clean slot  and solved

[Mike Texter]

Same issue here using Kingston DIMMs, we had 16x 32GB in a DL380G9, only the error message said "207- memory initialization failed on." and I had 64GB less of memory than I should have. 

It's supposed to call out the slot and processor, but in this case it didn't.  After re-seating, cleaning, shuffling DIMMs around, etc I found out that I had 2 bad DIMMs. 

Interestingly, if we shuffled these DIMMs into their own separate pairs, they would each disable their own respective pair making us short by 128GB of memory total.  Seems like the same pair failed simultaneously, which is either ridiculously unlucky or the system shorted them out or something.  Still not sure.