Accidentally bought slightly mismatched RAM, potential issue?

[Chaoticlusts]

Hey

Got sick of random low memory warnings and decided to grab an extra 8GB of RAM... Found what I *thought* was the same model as my original pair (It's been so many years....gotta love Sandy Bridge )..

Turns out my original pair was G.Skill F3-12800CL9D-8GBSR2 and I bought G.Skill F3-12800CL9D-8GBSR. From what I can see the only spec difference is the originals run at 1.25v and the new ones run at 1.5v.

What I'm wondering is if this is going to cause issues at all? As it stands my system has decided to drop them to 1333 rather than 1600 for some reason, gonna look into that in a second. I was trying to make sure I had a matching 4 set so speed wasn't affected (gaming system) seems like I may have stuffed that up (been one of those months >_<).

Worth attempting a return/biting the bullet and grabbing 2x8gb or not an issue at all really?

Any help would be greatly appreciated ^_^

Thanks

 

[Elixer]

It will run with the timings of the slowest stick, and the voltage will be the same for all sticks.

As for if it makes a difference, it depends, if the 1.5v is required to get those sticks up to speed, and running lower makes them error out.

So, first thing you should do is leave everything default, and run memtest86+. If that passed, then, set the timings to what you want, and test again, if no errors, good, if you get errors, then you know you will have issues at the timings you set them at.

 

[Chaoticlusts]

Cheers for the quick response

Will do ^_^ Well thankfully the timings are identical according to the specs (both 9,9,9,24,2) haven't had a chance to reset yet and dig into the bios to see why it dropped the speed but yeah I assume it's running them at 1.25v. According to the spec sheet for the old 1.25v ones they can run at 1.5v as a 'speed voltage' so hopefully all will match up then >_<

*edit*

Well it refused to so much as boot above 1333 at first (Despite both sets happily running memtest at 1600+1.5v by themselves... >_<) ...But apparently clearing the cmos was the answer...so booted and running memtest atm hopefully will be stable