Originally Posted by liquidfluidity;15521178
Yeah , I figured that if I turned vdroop back on, I'd have to raise my vcore to compensate. I do a lot of odd stuff from gaming to video conversion and editing so I like to have hyper-threading enabled. I'll raise my vcore to around 1.24v and see what happens. I understand the voltage spike but it shouldn't go above the 1.248v it goes to now, should it(with vdroop disabled). Is it just the harshness on the components when the voltage spikes that is the main worry/fear when there is no vdroop?
I'm not sure I entirely understand, so let me clarify...
Under load your vcore will drop slightly (vdrop). What vdroop does is increase voltage under load to compensate for vdrop so you'll have basically the same vcore under load as under no load. Great idea, but the problem is that going from full load to no load (vice versa? don't remember
) there can be a tiny space in time when vdroop hasn't stopped compensating so you can potentially get a huge spike in voltage for an extremely short period of time. That's why it's recommended to disable vdroop.
I knew all this stuff a while back so sry if this isn't entirely right. There were similar issues with LLC.
With vdroop off, your vcore will go down below the target vcore during load. Thus you have to compensate and set your vcore higher than you want. Run prime95 or something and see what cpu-z says your vcore is under load.
*edit* Doubting myself again, I looked it up and I think I'm getting it mixed up with LLC...
I'll come back after I get home and check my bios
.Edited by drjoey1500 - 10/31/11 at 12:27pm