- Joined
- Feb 15, 2014
- Messages
- 20,194
Not really. It's small in a system with several spinning disks.Is there a big difference in power consumption between 1.5 V and 1.35 V modules? Let's assume I want two 8 GB modules.
Not really. It's small in a system with several spinning disks.Is there a big difference in power consumption between 1.5 V and 1.35 V modules? Let's assume I want two 8 GB modules.
My motherboard X10SL7-F already is populated with 16 GB (2x8) of Kingston KVR1333D3E9SK2/16G CL9 1.5V. I want to add 16GB more to it. What ram should i go with?
In e-mail conversations with affected forum members, Kingston stated that using two Kingston DIMMs in the second pair of slots along with two of the Supermicro-verified Hynix DIMMs in the first pair of slots allowed for 32GB to be used.
I do not recommend this solution for anyone and am frankly surprised Kingston suggested it. However, those who have tried it say it works. If you are on a tight budget, currently own 16GB of Kingston RAM and would like to step up to 32GB, consider this solution.
Kingston's suggested solution seems to have worked for me for many months. Why are you recommending against it?
Mostly because it's hacky and nobody really guarantees that it'll work.Kingston's suggested solution seems to have worked for me for many months. Why are you recommending against it?
Mostly because it's hacky and nobody really guarantees that it'll work.
Sure, but I don't want to be the guy who gets the blame if it doesn't work.It doesn't seem particularly hacky. We know that there's some problem related to the bus length and timing. This isn't really all that different from other situations where populating DIMM modules in slots further away require memory speeds to be reduced; it's basically just turning that on its end.
Nobody really guarantees that any memory configuration will work under all circumstances. When you get the Supermicro list, for example, all it really means is that it's been tried and tested and - hopefully - that someone actually looked at it to see that things weren't actually running on the bleeding edge of fail.
Well, my thoughts on the matter are more or less the following:I'm not demanding that anyone suggest Kingston. I'm just being realistic here. This **** happens to everyone sooner or later.
I certainly wasn't recommending Kingston -- and in fact the /EF modules which they suggested relegating to the second pair of slots and using Hynix in the first pair of slots were discontinued long ago.Well, my thoughts on the matter are more or less the following:
- Kingston lost a lot of credibility with this story (which was probably an honest mistake and bureaucratic corner-cutting) and the V300 SSD story (which amounts to bait-and-switch). Had it been just the first debacle, it wouldn't have bothered me nearly as much.
- I don't feel comfortable suggesting Kingston RAM for X10 boards, because it's quite likely that there's still a lot of bad stuff in stock. Assuming Kingston's current QVL is accurate
- The Hynix + Kingston solution sounds like it might be operating rather close to the edge of what is acceptable, so sticking to a different brand seems to be the better choice.
I certainly wasn't recommending Kingston -- and in fact the /EF modules which they suggested relegating to the second pair of slots and using Hynix in the first pair of slots were discontinued long ago.
But are you suggesting that if anyone already has two of the 8GB /EF modules and wants 32GB of RAM, they should start over with 32GB of modules that are on Supermicro's QVL and sell off, or find another use for, the Kingston modules?
I finally completed a proper migration of this document to the Resources section. The original changelog follows below:
Update 2014-09-04 - Clarified Kingston's e-mail conversation and their current claims of compatibility (Special thanks to Z300M for the info!) and clarified only DDR3 Intel processors are affected by the 8GB UDIMM limitation.
Update 2 2014-09-04 - Clarified that Supermicro never listed Kingstom RAM as compatible (Special thanks to jgreco for the reminder and...