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!

[Snakeyes]

Phillyflyer wrote:
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 ?

Very interesting question. I have seen this happen only once before when hard tubing became popular replacing flexible tubing. In that case the builder put some extra pressure in inserting the tubes into the connecting ends and as a result created flex in the motherboard which in turn caused connection issues. This risk is apparently more common than we realize, especially when dealing with hard tubing that is protruding at right angles to the motherboard surface. In that particular case, motherboard standoffs were not properly tightened and a few were missing.

I do not believe that is the case in Ian's build. It's a pity, since he put together an absolutely awesome looking system. Looking forward to a post of his rebuilt system.

[Trigger5521]

Well ASUS found the cause and I'm embarrassed to say it looks as though it's my own fault. They traced the fault to a scratch on the back of the motherboard, right next to a standoff. I must have nicked the board installing it in the new case. Never had this happen to me before, oh well live and learn. Lesson here is to be super careful around the stand off because a very small scratch can ruin a good board. See attached. Thanks again to everyone for all ideas to try, great forum!

Replacement board is in (at my own expense of course) everything is running perfect 5GZ OC with memory volting properly.

[Phillyflyer]

Trigger5521 wrote:
Well ASUS found the cause and I'm embarrassed to say it looks as though it's my own fault. They traced the fault to a scratch on the back of the motherboard, right next to a standoff. I must have nicked the board installing it in the new case. Never had this happen to me before, oh well live and learn. Lesson here is to be super careful around the stand off because a very small scratch can ruin a good board. See attached. Thanks again to everyone for all ideas to try, great forum!

Replacement board is in (at my own expense of course) everything is running perfect 5GZ OC with memory volting properly.

So....I guess it was a short afterwards ...glad to see that the issue was resolved .

[Snakeyes]

Boy, you rebuilt that fast. Glad all is good and your system looks awesome.