BSOD with Corsair Vengeance Pro 2400mhz 32gb

Fiddy4

Commendable
Feb 22, 2016
2
0
1,520
Hello, I've done countless searches and trial/error trying to find the cause and course of action to fix my issue here with this new memory I've purchased... I'm hoping this great community can lead me to a solution!

My system:

CPU: i7 4790K OC'd to 4.6ghz
Mobo: MSI z97 Gaming 7
GPU: Asus Strix GTX 970
PSU: EVGA 850 G2

The memory in question:

Corsair Vengeance Pro Series 2400mhz, I'm using 2 kits of 2x8 16gb, 32gb total.

I am aware that some people warn of problems using "un-matched" sets, but countless people claim there should be no issue as long as you use the same modules and run the same timings, so I hope this isn't the case.

I have a 4x4gb set of Kingston Hyper X genesis memory that can run 100% stable on the system, so this makes me believe it's an issue with the Corsair set.

I would really like to have the Corsair set work in my build, not only because they LOOK so damn sexy, but the capacity and speed are an obvious upgrade over my old set of Kingston's (which are blue in color and I'm vain, doesn't match the black/red theme I've got going on)

With the Corsair RAM installed, the PC will boot and act normally, even run for some time on Aida 64 stress testing with no issues... But will randomly BSOD while gaming, browsing the web, and live streaming on Twitch.tv...

My Chrome browser will often fail to load pages as well - it won't crash, but it will show a page that says "Oops! Failed to load" or something like this.

Please, let me know what additional information I can provide if you would like to assist me in sorting this out. I can post my OC voltages / settings etc. and try to reproduce the BSOD and provide the information on the BSOD (or dump files if you can educate me on where to find those and the relevant information required).

P.S. I am using the X.M.P. profiles, and manually setting the DRAM voltage to 1.65.

I've also tried to down-clock the RAM to 2133, 1866, 1600 etc.. This has made the crashes less frequent but they still exist.

Thank you so much for the help!


 
Solution
Hey, thanks for the reply Tradesman1!

I actually ran another series of Memtest86, first with all 4 which revealed errors... And then individually until I found the problematic stick. So, problem solved! I have one stick producing tens of thousands of errors in Memtest, so I'll have to RMA.

Forgot to update my thread, but thanks for the suggestion!

Fiddy4

Commendable
Feb 22, 2016
2
0
1,520
Hey, thanks for the reply Tradesman1!

I actually ran another series of Memtest86, first with all 4 which revealed errors... And then individually until I found the problematic stick. So, problem solved! I have one stick producing tens of thousands of errors in Memtest, so I'll have to RMA.

Forgot to update my thread, but thanks for the suggestion!
 
Solution