Hyper x auto OC??

[RyanFawcett]

So im running a single stick of this: http://www.kingston.com/dataSheets/HX421C14FB_8.pdf

 

Kingston advertise automatic OC'ing up to 2666, all im seeing however is stock 2133.

 

This is my mobo: https://www.asus.com/uk/Motherboards/Z170I-PRO-GAMING/

 

Any ideas? thanks in advanced!!

[The_Baguettes]

I'm sorry but I don't see the auto overclock on the HyperX page.

[RyanFawcett]

http://www.amazon.co.uk/gp/product/B00TY6A56U?psc=1&redirect=true&ref_=oh_aui_detailpage_o01_s00

[The_Baguettes]

This is what I see

[RyanFawcett]

.

[MageTank]

I will also point out that in that Amazon link, it says auto overclocking for X99, not Z170. Besides. You can always manually overclock it if you want. 

[Nena Trinity]

Try to set it to 2400MHz and enable XMP if it works you are good!

[MageTank]

19 minutes ago, Nena360 said:

Try to set it to 2400MHz and enable XMP if it works you are good!

Why would that work? It's rated XMP is 2133mhz. Setting it to 2400 and then enabling XMP would undo the 2400mhz.

[Nena Trinity]

Just now, MageTank said:

Why would that work? It's rated XMP is 2133mhz. Setting it to 2400 and then enabling XMP would undo the 2400mhz.

That is funny my 1866MHz RAM ran nicely in 2133MHz with XMP enabled...

[MageTank]

10 minutes ago, Nena360 said:

That is funny my 1866MHz RAM ran nicely in 2133MHz with XMP enabled...

That's not the point. Did you enable XMP first (which sets the timings up) and then increase clock speed to 2133? Or did you set the clock speed, and load XMP afterwards? Loading XMP afterwards will load the XMP profile, including its raw speed. Changing it from 2133 to 1866 in your case. The order of operations is very important in this specific scenario.

[Nena Trinity]

1 minute ago, MageTank said:

That's not the point. Did you enable XMP first (which sets the timings up) and then increase clock speed to 2133? Or did you set the clock speed, and load XMP afterwards? Loading XMP afterwards will load the XMP profile, including its raw speed. Changing it from 2133 to 1866 in your case. The order of operations is very important in this specific scenario.

XMP first!

[MageTank]

1 minute ago, Nena360 said:

XMP first!

Okay, that is a big difference, lol. If he were to dial in 2400, then load XMP, it would just load in at 2133. However, your method is not exactly concrete, and you probably got lucky. Changing the clock speeds also impacts RTL and IO-L. Meaning if you load XMP, and it manually enters those values, changing the clock speed to 2400mhz might result in a no-POST. If he needs the speed, he is better off leaving things on auto, and changing the speed of his memory, while letting his board auto train the rest of the timings. He can probably just dial in 1.35V, enter 2666mhz, and be perfectly fine in doing so.

 

I personally don't recommend it, because changing raw speed without touching timings is the most inefficient way of getting bandwidth out of memory, but hey, to each their own.

[Nena Trinity]

Just now, MageTank said:

Okay, that is a big difference, lol. If he were to dial in 2400, then load XMP, it would just load in at 2133. However, your method is not exactly concrete, and you probably got lucky. Changing the clock speeds also impacts RTL and IO-L. Meaning if you load XMP, and it manually enters those values, changing the clock speed to 2400mhz might result in a no-POST. If he needs the speed, he is better off leaving things on auto, and changing the speed of his memory, while letting his board auto train the rest of the timings. He can probably just dial in 1.35V, enter 2666mhz, and be perfectly fine in doing so.

 

I personally don't recommend it, because changing raw speed without touching timings is the most inefficient way of getting bandwidth out of memory, but hey, to each their own.

I guess so it auto changed to CL11 from CL9 but besides that not much really...