Added memory, can't overclock (i5 2500k)

Insomniator

Diamond Member
Oct 23, 2002
6,294
171
106
Hey everyone --

Added 2x8GB Kingston Fury PC1800 to this:

i5 2500k
Asus Maximus IV Gene-Z Z68
2x4GB GSkill Sniper PC1600


I've been at an automatic 4.2 OC with no issues for a few years, but after adding this memory I get a code 55 error (no memory) unless I set everything to default 'balanced' values. I've tried manually setting the memory to 1600 but still get no boot.

Any tips?

Looks like with everything on auto the timings for each stick are different, and the Kingston PC18000 sticks are running at PC14200. Should I set everything manually to easy values?
 
Last edited:

BonzaiDuck

Lifer
Jun 30, 2004
16,654
2,034
126
Hey everyone --

Added 2x8GB Kingston Fury PC1800 to this:

i5 2500k
Asus Maximus IV Gene-Z Z68
2x4GB GSkill Sniper PC1600


I've been at an automatic 4.2 OC with no issues for a few years, but after adding this memory I get a code 55 error (no memory) unless I set everything to default 'balanced' values. I've tried manually setting the memory to 1600 but still get no boot.

Any tips?

Looks like with everything on auto the timings for each stick are different, and the Kingston PC18000 sticks are running at PC14200. Should I set everything manually to easy values?

Sometimes I had mixed RAM of one manufacture -- specifically G.SKILL -- knowing that they came out of the same factory (I hope) and that they overlapped in SPD/JEDEC with a perfect match of timings. I'd set the timings to the common SPD profile.

But you've thrown in a kit of Kingstons with a set of G.SKILL. With that board, I would've thought you'd be eager to leave automatic OC behind. To me, it's just a feature providing a means for quick assessment of OC capability.

If the Kingstons have better timings and lower voltage than the G.SKILLs, dump the smaller kit. In fact, I'd dump the smaller kit even for Kingstons of the same voltage, high speed and looser timings. Even Masters of the Universe have a hard time using a full 16GB.

But just one more. It may be that Kingston is on the Maximus IV QVL list -- I can't say. On the other hand, and over the years, I've seen all kinds of Maximus users using G.SKILLs. Why didn't you just get another 2x4 kit of the same?
 
Last edited:

Insomniator

Diamond Member
Oct 23, 2002
6,294
171
106
I already had 4x4GB of the G.SKILL but with wanted more memory with the VMware lab build I'm learning/following. The 2x8 Kingston was a tigerdirect deal that might end up being free if the rebates actually work so i said what the hell.

And yeah, using that board for an auto oc is kinda overkill. Just got lazy and didn't want to tweak it myself -- haven't been using the PC for anything very intense anyway.

I'll check out the QVL list and keep trying. Thanks!
 

ShintaiDK

Lifer
Apr 22, 2012
20,378
146
106
Auto OC is terrible. Just set the memory to standard and manually OC the CPU with voltage/multiplier.

And make sure you check for BIOS updates.
 

Charlie98

Diamond Member
Nov 6, 2011
6,298
64
91
Auto OC is terrible. Just set the memory to standard and manually OC the CPU with voltage/multiplier.

And make sure you check for BIOS updates.

When I first started OC'ing on my Gigabyte board, the OC presets were horrible... far easier to set it yourself, and a greater chance of success. With Z68, GB pumped up the bclk... which is a no-no with Sandy onward.

OP, I feel your pain, however... I replaced my low-end Gigabyte board with that same board... and was a bit put back by all the OC adjustments that board offers... Jeepers! :eek:
 

BonzaiDuck

Lifer
Jun 30, 2004
16,654
2,034
126
Like I said, I spent many days -- at least hours -- recording information about the processor so I could more quickly find my overclocks and use the stock monitored voltages as a reference. I also wanted to use the AI Overclocking as an initial reference, and it gave me of an idea of an absolutely certain clock speed with voltages I thought were uncomfortable for me. I think with the Sandy Bridge, it was 1.44V, just to overclock the bCLK and multiplier to get a speed of ~4.4 Ghz.

It's an interesting concept, and I found a use for it. But I stopped using it the first day I ran it.