FEATURED Kingston HyperX FURY 16GB DDR4-2666 CL15 - HX426C15FBK4/16

[Woomack]

Today I will present memory which is already for couple of months on our market but is for sure interesting - HyperX FURY 4x4GB DDR4-2666 CL15 1.20V - PN: HX426C15FBK4/16

I was already testing 32GB DDR4-2400 which was overclocking good but I wanted to take a look at higher clocked 16GB version and Kingson gave me that chance.









Below you can check how ASUS Rampage V Extreme sees memory profiles. As you see "standard" SPD profile is exactly the same as XMP so it's probably the most user friendly memory on the market. Simply, you install memory and it's working as declared. If motherboard has no issues to read SPD profile, then is no need to set anything else in BIOS.



Also screenshot at default settings DDR4-2666 15-17-17-35 CR2 1.20V:

 

[Woomack]

2750 15-15-15-35 1N 1.20V






3000 15-15-15-35 1N 1.30V





3200 15-15-15-35 1N 1.35V





3333 was losing 1-2 memory sticks from time to time. Like one reboot and all 16GB was visible but next and board saw only 8-12GB.

CPU-Z valid @3333 16-18-18 1.35V - http://valid.canardpc.com/gg0a62

 

[MetalRacer]

I was looking at the Fury's yesterday but went with the Predators instead. Are these Samsung IC's?

Looking forward to OC results.

 

[Woomack]

All earlier Kingstons were Hynix. 2 other Fury which I was testing were also Hynix the same as Predators. These 2666 Fury arrived last friday and I had no time to test them yet. I will let you know soon.

 

[Woomack]

I added couple of results to the 2nd post. Generally it looks really good. I have to check if I can make it work @3333 stable and how tight I can set voltages at 3000 and 3200.

 

[Woomack]

I've finally added photos to the 1st post. Probably I will add something to OC results soon too.

 

[JDMStanced]

how do you know when 3333 was losing 1-2 memory sticks? i would like to check mine too

 

[Woomack]

1. when you enter BIOS then on some boards is list of occupied banks - it shows what is missing ( OC timing tabs or 1st tab with general info on ASUS/ASRock boards )
2. while you start PC then on first screen ( if you don't have any welcome screen enabled in BIOS ) board is showing available memory but on new platforms it's passing so fast you can barely see anything
3. when you run benchmark like AIDA64 ( even trial ) then you clearly see that bandwidth is ~10GB/s lower than it supposed to be

CPUZ usually shows all memory sticks even if something is missing. The same Windows sometimes is showing all memory sticks but sometimes is info that usable is less like you have 16GB but usable is 12GB.

I have problems like that mainly on X99 and earlier on X79. On Z8x/Z9x it was also happening but was related to socket issues and usually 2 memory slots were not working at the same time.

 

[JDMStanced]

1. when you enter BIOS then on some boards is list of occupied banks - it shows what is missing ( OC timing tabs or 1st tab with general info on ASUS/ASRock boards )
2. while you start PC then on first screen ( if you don't have any welcome screen enabled in BIOS ) board is showing available memory but on new platforms it's passing so fast you can barely see anything
3. when you run benchmark like AIDA64 ( even trial ) then you clearly see that bandwidth is ~10GB/s lower than it supposed to be

CPUZ usually shows all memory sticks even if something is missing. The same Windows sometimes is showing all memory sticks but sometimes is info that usable is less like you have 16GB but usable is 12GB.

I have problems like that mainly on X99 and earlier on X79. On Z8x/Z9x it was also happening but was related to socket issues and usually 2 memory slots were not working at the same time.

that's interesting. i recently OCed my Crucial Ballistix elite 16gb 1644(1844?) to 2133.
On aida64, i see that free available ram is 12319 mb.. so it looks like i lost some Ram for OCing?

 

[Woomack]

It's different for DDR3 and DDR4 platforms. Ballistix memory generally doesn't like high clocks. Most of these kits can't make more than 2000-2133 but can run at tighter timings. In this case try changing memory slots or try higher VCCSA or memory voltage.