X99 Memory/Overclock issue

[RadHatter]

Just finished building my first Intel HEDT system.  I got a CPU through Intel Retail Edge a while back and finally got all the parts lined up.

MOBO - ASRock Taichi x99

CPU - Intel 6850k

GPU - ASUS Striix GTX1060 6GB

RAM - 32gb Corsair Vengeance DDR4 3000 (4x8gb)

PSU - Corsair 750w

AIO Cooler - Corsair H110i

 

I'm having a weird issue while trying to get a stable overclock.  The memory defaults to 2133, and if I set the multiplier to 42 I can do 4.2Ghz at ~1.32 Vcore with temps staying below 85 during Prime95 max heat,never crashing, and never rising above about 60-65 while gaming.  It seems perfectly stable but I would like to run the memory at its rated 3000 speed since I paid a premium for it.

The first thing I did was to set the XMP Profile.  The memory jumps to the right speed, but the BCLK automatically changes to 125 which throws my CPU overclock off and makes me alter the BCLK/PCIE ratio.  The closest I can get without messing with the BCLK is 4.125Ghz or 4.250Ghz.  Both of those frequencies crash during prime with the memory at XMP speeds, and upping the Vcore past 1.34-1.35 nets way too much heat to be useful.

I went back into the UEFI, changed the BCLK back to 100, the multiplier back to 42, and then manually altered the memory divider to get to 3000Mhz on the memory. Everything appears to work great, its stable again, but when I go into system properties it only shows 24GB.  CPU-z can see all 4 sticks and Corsair LINK is still running the RGB colors, but one stick always disappears from Windows.  I shuffled the memory sticks around, they all work individually, and it isn't always the same slot that it loses it either so I don't think it is a bad board.  I upped the memory to 1.4v (from a stock 1.35) but it didn't seem to make a difference.  I manually changed all the DRAM timings to match the XMP profile but that didn't change anything either.  As long as I go back to the XMP profile or reset the BIOS the last stick magically reappears, it just doesn't like the non XMP profiles.

At the end of the day I am guessing it is just a voltage issue, I know the VCCSA is a potential candidate but there is no VCCSA label in the UEFI.  Is it just named something different? I don't want to start turning any more knobs without some advice.  I tried to add a little to the CPU cache voltage and it ended up spiking the VCore to like 1.45 (for about 4 seconds before I stopped it) and now I'm afraid to mess with anything else.

My old 3570k was literally just a multiplier tweak and one bump of the offset, and my DDR3 was set it and forget it at XMP speeds.  I knew x99 could be picky but I've never had a BIOS with so many settings before and can't really afford to be damaging a 2000 dollar PC.

[Ordinarily_Greater]

maybe VCCSA is named VCCIO in the UEFI?

[RadHatter]

Just now, Ordinarily_Greater said:

maybe VCCSA is named VCCIO in the UEFI?

Thank you! I am at work right now but that sounds familiar.  I'll definitely test it out when I get home, still definitely open to other suggestions but I am hopeful that this is the right answer.

[Ordinarily_Greater]

Just now, RadHatter said:

Thank you! I am at work right now but that sounds familiar.  I'll definitely test it out when I get home, still definitely open to other suggestions but I am hopeful that this is the right answer.

i guess this thread adresses your problem

 

[RadHatter]

I found that thread but there was a lot of questioning whether or not to manually adjust VCC and their general consensus was "let xmp do it" which doesn't work for me. Worst case scenario I can accept 4.0 as my overclock or run the ram at 2666 instead but I would like to try and get everything working "as intended"

[Ordinarily_Greater]

20 hours ago, RadHatter said:

I found that thread but there was a lot of questioning whether or not to manually adjust VCC and their general consensus was "let xmp do it" which doesn't work for me. Worst case scenario I can accept 4.0 as my overclock or run the ram at 2666 instead but I would like to try and get everything working "as intended"

ok i will try to find a solution, wait have you tried to search a different naming scheme in the UEFI

[DocSwag]

IIRC the haswell e and broadwell e IMCs weren't as good as the newer ones.

 

You could try raising VCCIN a little bit; that might help though I'm not too sure. If that doesn't work, you may have to result to lowering CPU frequency a bit to hit the memory frequency.

[RadHatter]

Thank you guys for your help! You guys both pointed me in the right direction, got all the ram recognized at its XMP rated speeds and I have the CPU at 4.25Ghz @ 1.33 Vcore.  Hovers in the low 70s in Prime95 SmallFFT and between 60-65 for prime blend test after running each for 6 hours last night. I feel pretty comfortable with the temp, voltages, and stability that I am seeing at this point.  I was just being dumb, the VVCSA was labeled as "CPU System Agent" should have been obvious, I was just moving too quickly through the menus without reading all the descriptions.

[Ordinarily_Greater]

7 hours ago, RadHatter said:

Thank you guys for your help! You guys both pointed me in the right direction, got all the ram recognized at its XMP rated speeds and I have the CPU at 4.25Ghz @ 1.33 Vcore.  Hovers in the low 70s in Prime95 SmallFFT and between 60-65 for prime blend test after running each for 6 hours last night. I feel pretty comfortable with the temp, voltages, and stability that I am seeing at this point.  I was just being dumb, the VVCSA was labeled as "CPU System Agent" should have been obvious, I was just moving too quickly through the menus without reading all the descriptions.

great then! i hope you enjoy it!