What's new
Carbonite

South Africa's Top Online Tech Classifieds!
Register a free account today to become a member! (No Under 18's)
Home of C.U.D.

Advice Needed: Enabling XMP with 2 identical modules from different manufacturers

Vecta_ZA

Member
Rating - 100%
3   0   0
Joined
Oct 5, 2017
Messages
25
Reaction score
0
Points
1,315
Age
39
Location
Northern Suburbs, Cape Town
Hi All

I bought 2x Kingston HyperX Fury 16GB DIMM's (HX426C16FB4/16) as individual pieces and even after BIOS updates and loading the XMP profile, Windows 10 does not recognise the kit at 2666MHz.

After checking CPU-Z I noticed that the one module is manufactured by Samsung and the other by Micron.

Might this be the cause for XMP failing to load correctly and if so, is there a workaround?

My CPU and mobo:
Ryzen 1600X (1st Gen, Summit Ridge)
Asrock Fatal1ty AB350 Gaming-ITX/ac - updated to UEFI 4.60


 
This may not be helpful at all, but I suggest just selling both and getting a kit with the exact same modules.

1st gen Ryzen and a B350 board was a RAM nightmare at launch, not to mention my OCD kicking in even reading your story.

Edit: I actually spoke too soon without looking at the pictures. Based on the pictures I'm seeing they are running at 2666... still the OCD part remains.

Basically how it works is: The DDR part stands for Double Data Rate, meaning it can send and receive data twice per clock cycle, so what you are reading is the speed of SDRAM, but since it can send twice the data per clock cycle (being DDR SDRAM) it is effectively 2x the speed. So 1333x2 = 2666.

@Vecta_ZA
 
Last edited:
This may not be helpful at all, but I suggest just selling both and getting a kit with the exact same modules.

1st gen Ryzen and a B350 board was a RAM nightmare at launch, not to mention my OCD kicking in even reading your story.

Edit: I actually spoke too soon without looking at the pictures. Based on the pictures I'm seeing they are running at 2666... still the OCD part remains.

Basically how it works is: The DDR part stands for Double Data Rate, meaning it can send and receive data twice per clock cycle, so what you are reading is the speed of SDRAM, but since it can send twice the data per clock cycle (being DDR SDRAM) it is effectively 2x the speed. So 1333x2 = 2666.

@Vecta_ZA

Sorry for the OCD inducing post 😄

I understand DDR, and this is the contentious issue as I didn't want to make a long winded post about why I'm asking this in the first place.

This all started from Reddit posts where it was advised that the one way to know whether XMP is active is to check your Task Manager - Memory tab, where the speed should state 2667MHz.

Aside from Redditors, a friend of mine who has an Intel laptop with a single 8GB DDR4 DIMM has his Task Manager - Memory tab displaying a speed of 2667MHz. The inconsistency is frustrating, because Windows 10 as the common denominator here surely cannot display two different sets of results purely because of the chipset manufacturer?

Without labouring the point any further; how then are you supposed to know whether XMP is active?
 
Hi @Vexta_ZA what you could potentially try is to insert only the one Micron stick (I state Micron as the timings with the Samsung stick may be a little too tight) in the bios load the xmp settings and boot into Windows to check that the XMP is active. Best is to use CPUz but also taken your system the Zentimings application works great. Now after you've booted into WIndows and confirmed that the memory timings is set and running well then shut down and unplug the computer then insert the second (Samsung) stick of memory. If the timings on the memory is the same, then both should run fine, but you can trick it by first just using one stick of memory.
 
What you can also try go is maybe leave xmp off and just Seth the ram to 2666 and see what windows and the apps show once you boot.
 
Thanks for your help everyone.

After many benchmarking and in-game testing was performed over the weekend, the performance gain coming from the 32GB upgrade is enough to be more than satisfactory.

XMP is enabled in my BIOS, so I'll trust in @AinsleyHarriott's advice that there's nothing further to be concerned about.
 

Users who are viewing this thread

Back
Top Bottom