Same memory kits but they show different speeds

[Dive5885]

Not sure why this shows different speeds?

 

Both kits are the exact same.

 

Any ideas? 

[airdeano]

the week/year shows that the version has changed.

might also be noted on the module itself by version (i know corsair does this).

[Dive5885]

2 minutes ago, airdeano said:

the week/year shows that the version has changed.

might also be noted on the module itself by version (i know corsair does this).

So in other words its normal and the memory isn't defective? 

 

I was just confused when I saw that. 

 

[airdeano]

just makes booting a nightmare as which XMP profile will be used?

booting 2133 or 2400 with what CAS, tRAS, tRC. this is what purchasing memory at a later date can pop-up.

and some might wonder why their machines don't perform properly. identical =/= identical NOT.

 

once in XMP selection then it seems to be an equal footing.

[Dive5885]

2 minutes ago, airdeano said:

just makes booting a nightmare as which XMP profile will be used?

booting 2133 or 2400 with what CAS, tRAS, tRC. this is what purchasing memory at a later date can pop-up.

and some might wonder why their machines don't perform properly. identical =/= identical NOT.

 

once in XMP selection then it seems to be an equal footing.

It only showed one XMP profile in the bios. 

 

3200, 16-18-18-38 1.35V

 

[airdeano]

but the JDEC is what is different and this is solved during memory training. on POST, the system may boot multiple tims to find what memory compatibility may have to resort to to boot/run. when the systems is at 'default' what speeds are you seeing?

[Sakkura]

18 minutes ago, airdeano said:

just makes booting a nightmare as which XMP profile will be used?

booting 2133 or 2400 with what CAS, tRAS, tRC. this is what purchasing memory at a later date can pop-up.

and some might wonder why their machines don't perform properly. identical =/= identical NOT.

 

once in XMP selection then it seems to be an equal footing.

The XMP profile appears to be the same, the newer kit just has faster JEDEC profiles in SPD. This helps performance a little for those people who forget to enable XMP.

[Dive5885]

21 minutes ago, airdeano said:

but the JDEC is what is different and this is solved during memory training. on POST, the system may boot multiple tims to find what memory compatibility may have to resort to to boot/run. when the systems is at 'default' what speeds are you seeing?

With no xmp enabled, it boots up without any issues. 

 

Speed shows 2133

[Dive5885]

32 minutes ago, Sakkura said:

The XMP profile appears to be the same, the newer kit just has faster JEDEC profiles in SPD. This helps performance a little for those people who forget to enable XMP.

Even with xmp off, the speed is 2133?

[ProximaOfZeal]

@Dive5885 the system always uses JEDEC specs of the weakest module when set to automatic (default). Since XMP is the same, there shouldn't be any problem with XMP enabled.

[Dive5885]

2 hours ago, ProximaOfZeal said:

@Dive5885 the system always uses JEDEC specs of the weakest module when set to automatic (default). Since XMP is the same, there shouldn't be any problem with XMP enabled.

Its interesting that this could even happen lol 

 

So far I have had zero issues. Everything runs fine with XMP on or off. 

[porina]

CPU-Z only lists limited SPD profiles. If you want to see more, try Thaiphoon Burner. It might be they are the same, apart from the additional 1200 speed profiles on the newer module.