Originally Posted by Inkey
Happy to see you got it working! I went back to square one and just tested idle Vcore with everything in the bios at Auto. Vcore dropped just like it's supposed to so I know there isn't anything interfering.
Then, I tried exactly
what you did and my result was completely different and reverted to what I've been struggling with the entire time. Vcore in the C6H section of HWinfo stays at my P0 volts 99% of the time. I noticed it drop to between .6v &.9v a couple times, but only for a second before jumping back up to the P0 value. Shouldn't it be at idle Vcore all the time?
Should I just.. trust that the idle voltage is what I set for P2? It's bothering me that I'm not seeing the correct values being reported, but at this stage, I just feel like I'm slowly losing my mind and should move on.
All @ Auto (except ram, I guess):
Your bios settings (SOC to 1.1 volts, LLC to level 2, Vcore to offset (auto), P-states all on auto in bios, C-states to enable), default ram speed, with my P0 set in ZenStates and default P1/2:
Ah, yes, I understand your concern. No I would not just trust, I want to SEE a voltage. You will not see voltage changes under the CPU Core Voltage (SVI2 TFN) as they occur with P-state changes with this method of overclocking, which threw me off. You have to look under the Asus Crosshair section in HWiNFO at the Vcore sensor listed there. Just to make sure all things are equal:
I am on 1007 EUFI.
Since you have been tinkering, you might want to do a load optimized defaults, save and reboot.
For me, I then get my memory settings running as I want and stable, before doing any changes beyond that.
After that I did as described in previous post to do my CPU overclocking.
For me it is to easy to change something, and forget I did, and too many variables start coming in to play. So I like to start with "clean slates", and segregate changes to one function or process at a time.
Hope this helps Edited by CeltPC - 4/29/17 at 2:05pm