Okay, it appears that I have to explain this a few times per day anyways, so lets try a simple mans guide to calculation of VDrop and VDroop. Once you know how your board will apply these vcore voltage drops, you can get to Over clocking!
In image 1, Look at Core Temp, and note the VID field! That is one of the most important things in OCing! That is where your chip starts on the VID voltage scale! The LOWER the better!
1.2375. That means that this chip is programed at the factory to fork over this to the mother board, and it sets the BIOS VCore accordingly!
Then you have intel specification Vdrop. It will lower the In Operating system voltage to something else! In my case, on a p5k-e wifi with LLC enabled.
Take note of the VCore current voltage in both Hardware Monotor, and CPUz. 1.200.
So now we know that in my current configuration my VDrop is exactly .0375
Take note in image 2 that while I am running Primes small FFTs on all the cores, the VCore current value in both HWmonitor and CPUz are down again! In hardware monitor, since its programed to display only 2 decimals, it rounds up to 1.17, but in CPUz, since it has 3 decimals it displays, we get a more precise number. 1.168.
That, my friends in the land of OCing, is the Loaded VCore! That is the most important thing to know how to reach! That decides if you are gonna bomb or not. (and other things, but mostly VCore for now.)
If the LOADED Vcore is a tiny bit to low, Prime 95 will sniff it out! And you'll Bomb out again.
But anyways, VID = Factory BIOS VCore setting while on AUTO.
VDrop is the automatic drop in VCore voltage when you enter an operating system.
VDroop is when the processor is under strain, it has to use more power. At 100% with small FFTs makes your chip use maximum current, and as such, its reduced.
Bios VCore Minus Automatic VDrop Minus Loaded VDroop is your Loaded VCore voltage!
Hope that helps. Once you know what your boards vdrop and vdroop are like, you can decide directly upon a VCore Loaded Voltage and not waste time finding it.
If you found this helpful, please just reply with a smile face, so it hits the top again, just where the noobs start looking!
More about :vdrop vdroop loaded vcore find secret values
I'm lazy! And I like my temps nice and hot! So nope, I sure haven't.
Then again, I am really not to worried about temps and junk.
Maybe, if I havent already had the cores to 90c while running, or maybe if It wasnt at 1.8250 V in the bios when I did it... I'd feel like being close to 65c really mattered!
But since I know better. I dont really care! (enough) to do it.
Hell, had TCase to 116 c. What do you think the cores were at for the whole 10 seconds it took for the AUTO thermal control to kick in? (As in, AUTO thermal control, one they dont tell you about, because you can not disable it or anything. Saves the chips a$$ when its over 85c TCase.)
BUT... comp has been working on me, so I may just do it one day, to see what it does!
I did finally order a new water block for my 1.2000 VID chip! Maybe I can get it up and runnin' on monday and get to working on her.
Yup, but you cant disable the one I am talking about! I ALWAYS have all cpu options off, because they dont do a damn thing anyways but cause trouble.
That does not stop the overheat safeguards from kicking it. The chip will save its own a$$ if it can, if you are insanely beyond specs. Like I tend to be at times!
It did not kick in to control the voltages. Only to kill the Temps. When the voltage VCore was 1.8250, the cores were 80+ in windows idle, yet it didnt shut down. But at 100 TCase, the cores have to be over that, sooo... thats when it kicks in, no matter what you do. And hopefully it doesnt fry in that short period of time it takes for it to realize it's actually on fire.