BonzaiDuck
Lifer
OK here's the story.
I have this absolutely great system -- 2700K @ 4.7, G.SKILL DDr3-1866 "GXM" 2x8GB=16GB @ 9-10-9-28 CR=1. SSD dual-boot Win7/Win10. 2x GTX 970 OC'd to core-clock 1480, memory 7500 in SLI.
Never any problems; event-logs all blue; never misses a beat or a lick.
I decided I wanted just a bit more RAM than 16GB, because at one time my RAM usage went up to 75-80%. I'd placed the order for more RAM before I discovered that unloading a program would get the memory settled back to about 55-60%. The reason RAM usage is this high either way derives from using 4GB for caching disks.
The "GXM" RAM is labeled as "RipJaws X." But there are several RipJaws X kits: some now coded as "GBXL," others coded as "GBXM."
I would have been better off, I think getting a 2x2GB GBXM kit with the same timings and speed: 9-10-9-28 and 1866. Instead, I picked a GBXM kit of 2x4GB with tighter timings: 8-9-9-24 @ 1866. Knowing GSKILL, I was sure I could simply loosen the timings on the 8GB kit to match those on the original 16GB kit.
And -- I can. But I was hoping to run these at CR=1. And so I set the timings for that command rate.
Then I booted into HCI Memtest 64. As soon as it begins to run the "long" test for the first 100% coverage, there are some 152 errors that pop up.
So I imagined a possibility that the VCCIO and possibly even the VDIMM were too low to sustain CR=1. Went into BIOS; changed CR to 2. Now the HCI Memtest-64 program seems to show the RAM behaving as it ought, but it's going to take time to test these. Perhaps would have been better to test the new modules separately, but I have a broken latch in a socket for one of the original modules, the stick needs to be levered out with a screwdriver, and I figured to just install all four modules, test, and cross my fingers.
I would only guess this is a likely outcome for filling all slots: you might need to bump the voltages slightly to obtain CR=1.
At this point, I can't tell if I should send the new modules back for RMA replacement. I should just wait and see how a few passes at HCI Memtest-64 goes.
Any thoughts?
I have this absolutely great system -- 2700K @ 4.7, G.SKILL DDr3-1866 "GXM" 2x8GB=16GB @ 9-10-9-28 CR=1. SSD dual-boot Win7/Win10. 2x GTX 970 OC'd to core-clock 1480, memory 7500 in SLI.
Never any problems; event-logs all blue; never misses a beat or a lick.
I decided I wanted just a bit more RAM than 16GB, because at one time my RAM usage went up to 75-80%. I'd placed the order for more RAM before I discovered that unloading a program would get the memory settled back to about 55-60%. The reason RAM usage is this high either way derives from using 4GB for caching disks.
The "GXM" RAM is labeled as "RipJaws X." But there are several RipJaws X kits: some now coded as "GBXL," others coded as "GBXM."
I would have been better off, I think getting a 2x2GB GBXM kit with the same timings and speed: 9-10-9-28 and 1866. Instead, I picked a GBXM kit of 2x4GB with tighter timings: 8-9-9-24 @ 1866. Knowing GSKILL, I was sure I could simply loosen the timings on the 8GB kit to match those on the original 16GB kit.
And -- I can. But I was hoping to run these at CR=1. And so I set the timings for that command rate.
Then I booted into HCI Memtest 64. As soon as it begins to run the "long" test for the first 100% coverage, there are some 152 errors that pop up.
So I imagined a possibility that the VCCIO and possibly even the VDIMM were too low to sustain CR=1. Went into BIOS; changed CR to 2. Now the HCI Memtest-64 program seems to show the RAM behaving as it ought, but it's going to take time to test these. Perhaps would have been better to test the new modules separately, but I have a broken latch in a socket for one of the original modules, the stick needs to be levered out with a screwdriver, and I figured to just install all four modules, test, and cross my fingers.
I would only guess this is a likely outcome for filling all slots: you might need to bump the voltages slightly to obtain CR=1.
At this point, I can't tell if I should send the new modules back for RMA replacement. I should just wait and see how a few passes at HCI Memtest-64 goes.
Any thoughts?