MF10 and Corsair Vengeance Pro RGB 3200 stuck at 1.2v...SOLVED

[Trigger5521]

SOLVED...Motherboard scratched near standoff.

Hi guys, having a strange issue with my Maximus Formula X and some new ram I installed. When I enable the XMP profile for this Corsair Vengenance Pro RGB 3200 mem everything applies as expected in the BIOS including DRAM voltage to 1.35v however when I'm booted into windows10 all monitoring software such as Adia64 and HWiNFO64 indicate the DRAM voltage is 1.2. I'm having crashes with my formally stable 5.0ghz OC and I've pretty much convinced it's memory. It doesn't matter if I set the voltage manually or let XMP do it, never changes from 1.2v which of course isn't enough for the 3200mhz OC

Background...prior to getting this new RAM I was 100% stable with G-Skill TridentZ 3400 (F4-3400C16D-16GTZ) and BIOS 1101. I moved my system to a new case only adding new RAM and the updating the BIOS to 1602. I tried putting the TridentZ mem back in and it also will not go past 1.2V. This all seems to point to the new 1602 BIOS. Before I revert back I'd like to see what you guys think or if anyone else has experienced this issue.

Specs:
Intel 8700K
BIOS 1602
Corsair Vengenance Pro RGB (CMW16GX4M2C3200C16W) 2X 8GB
Win10 64bit

Thanks!

[Phillyflyer]

From what I'm gathering here...all you did was swap the board from one case to another and changed out the ram to Corsair vs GSkill....since then neither of the kits will report the correct voltage vs what is set in bios ...correct ??
Bios 1401 onward would have updated the ME Firmware (which is only thing that will not roll back) and should not be related the your issue....I would be more inclined to think that you may have a short somewhere on the board since it was working in a previous case without issue....Either way...the board may have to come out...test on an open bench...see if issue still exists prior to an RMA...
Just a shot in the dark here Bro !!

[Trigger5521]

Phillyflyer wrote:
From what I'm gathering here...all you did was swap the board from one case to another and changed out the ram to Corsair vs GSkill....since then neither of the kits will report the correct voltage vs what is set in bios ...correct ??
Bios 1401 onward would have updated the ME Firmware (which is only thing that will not roll back) and should not be related the your issue....I would be more inclined to think that you may have a short somewhere on the board since it was working in a previous case without issue....Either way...the board may have to come out...test on an open bench...see if issue still exists prior to an RMA...
Just a shot in the dark here Bro !!

Your summary is correct with the addition of updating the BIOS to 1602.

I haven't considered a short but it seems plausible now that you mention it. Still 100% painful to test that theory and I don't have a proper "test" bench to try it out on. I guess I could buy a stock intel air cooler to cool the cpu for a test outside of the case.

Thx

[chevell65]

There were some threads where voltage sticking problems were fixed by toggling the LN2 switch on the board. Man what a pain.

[Trigger5521]

chevell65 wrote:
There were some threads where voltage sticking problems were fixed by toggling the LN2 switch on the board. Man what a pain.

This I can do...will advise.

[Trigger5521]

OK get this snakeyes has also notice from my AIDA64 panel that the VCCSA and VCCIO voltages are out of whack

I have them set in the BIOS VCCSA to 1.25 and VCCIO to 1.2

AIDA reports VCCSA 1.027 and VCCIO 0.968

These voltages are also not responding to BIOS changes, does that indicate a short? or faulty voltage regulator?

[chevell65]

Trigger5521 wrote:
OK get this snakeyes has also notice from my AIDA64 panel that the VCCSA and VCCIO voltages are out of whack

I have them set in the BIOS VCCSA to 1.25 and VCCIO to 1.2

AIDA reports VCCSA 1.027 and VCCIO 0.968

These voltages are also not responding to BIOS changes, does that indicate a short? or faulty voltage regulator?

Normally the VCCSA and the VCCIO voltages show a bit higher voltage compared to what they were manually set at.

Strange voltage problem but I've seen this a few times recently.

[Phillyflyer]

Trigger5521 wrote:
OK get this snakeyes has also notice from my AIDA64 panel that the VCCSA and VCCIO voltages are out of whack

I have them set in the BIOS VCCSA to 1.25 and VCCIO to 1.2

AIDA reports VCCSA 1.027 and VCCIO 0.968

These voltages are also not responding to BIOS changes, does that indicate a short? or faulty voltage regulator?

If the board was working fine prior to the swap...and I would assume that the chip was still in board during the transfer...I would not say that the voltage regulator is faulty unless it happened during the install to new case and was caused by a short of some kind.
Have you tried another version of Aida64 and HWI with same results?...Again...last gasp..shot in the dark.

[Trigger5521]

Tried L2N mode...no effect.
Pulled Battery for 5 mins no change.


So there you have it folks! Drained & disassembled the loop, she's now up and running on the test "Box". No change 1.2v on the DRAM VCCIO 0.968 VCCSA 1.072
She goes back on RMA tomorrow 😞 so sad. Truthfully it only took a couple of hours to break down and will go back together in much less time than the initial build as all the runs are set. Thanks for all of the suggestions guys I will update once I get replacement board back. Cheers!

[Phillyflyer]

Bro....you had nothing to lose by taking board out...at least you know now that infact it was the board....Question remains though....how did a perfectly working board become an RMA during a transfer between cases ?

[edrickjk]

Check your peg to make sure they are all the same length, it can wreak havoc on a board. Had that append to me couple year back,2 board later , a new patch of white hair and me ready to burn the damn thing . Doubt its the issue but better be safe ,good luck with your next board.