There have been many rumors about the N40L supporting 8GB modules which enables the server to use up to 16GB of memory. This would be a great enhancement, especially with the new vSphere 5.1 where many appliances require more physical memory. First of all, the 8GB modules are not supported by HP so upgrade at your own risk.
I picked together all the modules that have been successfully tested with the HP N40L MicroServer:
8 GB Modules
- 1x 8GB: Corsair 8GB DDR3 DRAM 1333MHz 240-pin PC3 10600 (CMV8GX3M1A1333C9)
- 2x 8GB: Patriot Gamer 2 Series 16GB 240-Pin DDR3 SDRAM PC3 10666 (PGD316G1333ELK)
4 GB Modules
- 2x 4GB: Kingston HyperX blu 8GB DDR3-1333 PC3-10600 (KHX1333C9D3B1K2/8G)
- 2x 4GB: PNY Optima DDR3 SDRAM 1333 (MD8192KD3-1333)
- 2x 4GB: Crucial 8GB Kit 240-pin DIMM, DDR3 PC3-10600 (CT1508549)
- 1x 4GB: Kingston 4GB 240-Pin DDR3 SDRAM DDR3 1333 (KVR1333D3N9/4G)
Note the difference between a kit and a single module before buying. Please comment if you can report any other working modules or have problems with the modules above.
Have you had any issues ? I recently upgraded to 16GB on my N40L and I am receiving Pink Screens on reboots when using 5.1 (4.1 works fine)
What errormessage does the PSOD show up? I do not have any issues with 5.1 and 16GB.
I tried both of these on my N40L
1x 8GB: Corsair 8GB DDR3 DRAM 1333MHz 240-pin PC3 10600 (CMV8GX3M1A1333C9)
2x 8GB: Patriot Gamer 2 Series 16GB 240-Pin DDR3 SDRAM PC3 10666 (PGD316G1333ELK)
Neither works, as the system only sees 8gb total
Ny N36L sees both, and presents 16 gb total.
Any ideas why?
I've just upgraded my HP N40L with 2 x 8GB sticks of the Patriot Gamer 2 (8GB Single retail versions)part number PG38G1333EL and they have been working without issue for about a week now.
Im not sure what your issue is but by all accounts the Patriot Gamer 2 sticks should work based on my experience and many others. :neutral:
I also have the Patriot PG38G1333EL.
I saw that BIOS always recognize my 16GB RAM - but Windows Server 2008 R2 sometimes see only 8GB. If you restart 20 times it's about 10 times with 16GB and 10 times with 8GB.
Also I saw that the clock timings in BIOS are completly wrong (CL6 instead of CL9). If I set this manually it doesn't matter - it stays wrong.
BIOS recognize 16GB - Windows Server 2008 R2 doesn't (16 GB installed - 8 GB available).
Any ideas?!?!
Maybe Windows 2008 R2 Foundation which is limited to 8GB of Memory?
No, it's R2 Standard. But in the meantime I found out, that the BIOS "see" sometimes only 8GB instead of 16. It's like a lottery. If you reboot it could be 16GB or just 8GB... Very frustrating... :sad:
Whilst I solved the PSOD by upgrading the bios (downgraded before to test other ram dimms), but I have similar issues with the bios only seeing half the ram most of the time.
It seems that the Microserver only works stable at 16GB when you use ECC ram.
This one works for me flawlessly in an ESXi server without a problem (and I can use all of it without crashes)
Product Code: KVR1333D3E9SK2/16G
Whilst I solved the PSOD by upgrading the bios (downgraded before to test other ram dimms), but I have similar issues with the bios only seeing half the ram most of the time.
It seems that the Microserver only works stable at 16GB when you use ECC ram.
This one works for me flawlessly in an ESXi server without a problem (and I can use all of it without crashes)
Product Code: KVR1333D3E9SK2/16G
Thank you for this information! Before I buy these RAM could you please check if the CL in BIOS is recognized correctly as CL9? Thank you very much.
Bios information is useless I am afraid - see for yourself
http://i49.tinypic.com/34zcen7.png
Unfortunately the server runs ESXi so I cannot run cpuinfo which may give (or not) more info.
But here is what ESXi can read :
Memory Device: #22
Location: "DIMM0"
Bank: "BANK0"
Manufacturer: "Manufacturer00"
Serial: "SerNum00"
Part Number: "ModulePartNumber00"
Memory Array: #20
Form Factor: 0x09 (DIMM)
Type: 0x01 (Other)
Type Detail: 0x0080 (Synchronous)
Data Width: 64 bits (+8 ECC bits)
Size: 8 GB
Speed: 1333 MHz
Inactive Record: #23
Data 00: 7e 13 17 00 00 00 00 00 00 00 00 00 16 00 15 00
Data 10: 01 00 00
Memory Device: #24
Location: "DIMM1"
Bank: "BANK1"
Manufacturer: "Manufacturer01"
Serial: "SerNum01"
Part Number: "ModulePartNumber01"
Memory Array: #20
Form Factor: 0x09 (DIMM)
Type: 0x01 (Other)
Type Detail: 0x0080 (Synchronous)
Data Width: 64 bits (+8 ECC bits)
Size: 8 GB
Speed: 1333 MHz
Hi,
I have an issue with my HP N40L. I bought two Kingston KHX1333C9D3B1K2/8G modules. If I start the device (have ESXi 5.1 on it) there is only 8 GB listet :( Any ideas ?
Cheers Andre
Hi Andre,
can you see the 16GB in your Bios?
There might be also problems with 5.1 and 16GB of RAM. If your Bios shows up 16 GB please try ESXi 5.0
Pingback: VMware ESXi vSphere Home lab Part 1
hey,
used this DIMM Module and work propertly !
TakeMS Arbeitsspeicher 8GB (1333 MHz, CL9) DDR3 RAM
I have a weird solution for keeping the N40L to recognise 16GB all the time:
I have found that having an external hard drive attached to one of the front USB ports causes it to be always detected as 16GB. If I remove the drive, it does the 'lottery' for detecting 8GB /16GB.
Very strange... I hope this helps someone!
Hi Tonyjr
thanks, what you said is correct and now I have a external harddisk dedicated for it.
Cheers
Pentium9394
ich habe mir einen
KVR 1333D3S4R9S/4G Ram für meinen n54l gekauft
Leider funktioniert der Server damit nicht....Warum?
Pingback: [Sammelthread] HP ProLiant N36L/N40L/N54L Microserver - Seite 453
*sigh* ... but it works for me: a root crontab entry like this...
just keep rebooting the box every 15 minutes, until it comes up with non-8GB:
*/15 * * * * /bin/grep -q "MemTotal: 81" /proc/meminfo && /sbin/init 6
i also noticed the influence of USB devices; obviously a timing issue...
plugging in an USB device still is no 100% gurantee for me... thus the hack above.