In theory, speedstep seems like a great Idea: Lower the multi AND the Vcore when processor useage is below X %. Wall the multi (and the Vcore, but not in that order) when the task calls for it.
Would make worry about Vdroop etc... a thing of the past.
I know there is a "lag" when it kicks in / out etc..., but I don't really mind that, because I can't detect it.
Anyway, on this MB, if you enable speedstep, you have no Vcore control. But using CrystalCPUid, it works pretty well, but on my system it can only basically kick the Vcore to "low" or "high" (what you set in bios). "Low" seems to be about 1.1 V according to speedfan.
So it works great so far, but in Crystal you have all these discrete voltage choices - anybody get exact voltages to work, or is your system only doing the "hi / lo" thing ? While this works pretty good, I just wondered if anyone has gotten it to work like it looks like it should work.
Would make worry about Vdroop etc... a thing of the past.
I know there is a "lag" when it kicks in / out etc..., but I don't really mind that, because I can't detect it.
Anyway, on this MB, if you enable speedstep, you have no Vcore control. But using CrystalCPUid, it works pretty well, but on my system it can only basically kick the Vcore to "low" or "high" (what you set in bios). "Low" seems to be about 1.1 V according to speedfan.
So it works great so far, but in Crystal you have all these discrete voltage choices - anybody get exact voltages to work, or is your system only doing the "hi / lo" thing ? While this works pretty good, I just wondered if anyone has gotten it to work like it looks like it should work.
Last edited: