HP Compaq Elite 8100 SFF 16GB Memory Upgrade

[Tropick]

Hi all,

So I recently bought a bunch of new hardware to install in my aging Elite 8100. Upgrading the i5-650 to an i7-870, 8GB (2x4GB) DDR3-1333 to 16GB (4x4GB) DDR3-1333 memory, and an Nvidia Geforce GT 620 to an Nvidia Geforce GT 1030 (GDDR5). I installed everything and booted it back up and it seemed to be just fine! Loaded right into Windows 7 64-bit with no problems at all. I pulled up Speccy to check everything, and it's detecting the i7-870 and the GT 1030 just fine. However, it's only reporting 8 of the 16GB of memory installed.

I've read a couple posts with people experiencing this same problem when they occupy all 4 of the Elite 8100 SFF's memory slots. However what I can't seem to figure out is WHY this problem exists. Reading the installation guide for the 8100 SFF, it explicitly states that in order to get 16GB of system memory, you must use 4x4GB sticks of non-ECC, CL9, DDR3-1333. Exactly what I'm using to upgrade the machine with. I am using a matched, 4-stick set of VisionTek VTK 4G PC3-10600 CL9 1333 memory. When I occupy slots 2 and 4 (the black slots, channel A), it detects 8GB, 4GB in both slot 2 and 4. When I occupy slots 2,4 and 3 (both black slots and the white slot further from the CPU, channel A and half of channel B) It only detects 4GB in slot 3. And, as expected, when only slots 1 and 3 (the white slots, channel B) are occupied, the system fails to boot, sounding a 5-beep post code for using the wrong memory channel first. Additionally I have verified that all 4 sticks of memory are functional by putting them in another machine and running memtest86+ for an hour.

So what gives? I have a sinking feeling in my stomach that this is a memory density issue and I just wasted 60 bucks on this kit. However before I shelf another set of memory I want to make sure I'm not doing something obviously incorrect. Anyone have any ideas? Could this be a motherboard issue? BIOS? Anything helps.

Thanks!

[Paul_Tikkanen]

Hi:

If you can't figure it out, buy four of these...I think it is memory brand/type issue.

https://www.newegg.com/patriot-4gb-240-pin-ddr3-sdram/p/N82E16820220480?Item=N82E16820220480

These work in the 8000 Elite CMT I have, which uses the same memory as the 8100 Elite.

I am surprised the GT 1030 works in the 8100 Elite.

I thought those needed a UEFI BIOS to work.  So that is good to know in case someone asks.

I have one of those in my 8200 Elite CMT which does have a UEFI BIOS.

Pretty low risk on the memory as they will take returns...

We want to ensure your holiday shopping this year is hassle-free. That’s why we’re automatically extending our return policies on almost every product! For purchases placed between November 1, 2019 and December 24, 2019 you will have until January 31, 2020 to return your product. There's nothing additional that you have to do!
Return for refund until: January 31, 2020

https://kb.newegg.com/knowledge-base/return-policy/#53

[Tropick · Accepted solution]

Thank you so much for the quick reply, however I was able to find the problem! You're not going to believe this. After (a last ditch effort) inspection of the memory slots on the board, I found that the upper rightmost pin on the XMM3 slot looked bent if not broken off completely. After looking up the pinout of DDR3 modules, I found out that it was a Vss power pin and that there was no way any memory would ever work in the slot without fixing that pin first. So with a dead slot on my hands and nothing to lose I proceeded to (again, in a last ditch effort) stuff a tiny ball of 28AWG copper wire into the minuscule opening in the top of the pin hole and out the inside edge of the slot. I figured if I could just get the darn module pin to make contact with the slot pin there was at least some chance that I would have a working memory module again. A few moments later my jaw proceeded to hit the floor as the BIOS successfully identified all 16GB of memory. I'm a little speechless right now as this is probably the sketchiest, most macgyver fix I have ever successfully attempted in my entire IT career.

As a quick disclaimer to anybody getting any ideas, this is obviously a very slapdash fix. I never would have attempted to repair the machine like this had it not been a personal project that I was perfectly fine with losing. Always back up your data and never mess with something like this if you aren't ready to lose it. I got super, super lucky that this worked and didn't end up just setting my workbench on fire.

[Paul_Tikkanen]

You're very welcome.

Glad you were able to fix the problem.