for you electronics gurus.
- Thread starter porta
- Start date
a lot of boards offer some level of control without even using an enthusuast board and the related board app's:
if you have a reasonably recent board try firing up RM clock, usually you find the cpu isnt running the max VID setting supported, and you can quickly change the current VID up/down with RMclock. eg most athlon X2's run 1.35-1.4v. but all have max VID of 1.45v thats 0.05v boost in windows with no funny apps at all - and usualy this change still works when you raise the v-core in vios to a higher lvl, eg 1.5v because the board applies this as 1.4v(vid) + 0.1v(board adjust). so when you change vid to 1.45 you get 1.55v out.
if you have a reasonably recent board try firing up RM clock, usually you find the cpu isnt running the max VID setting supported, and you can quickly change the current VID up/down with RMclock. eg most athlon X2's run 1.35-1.4v. but all have max VID of 1.45v thats 0.05v boost in windows with no funny apps at all - and usualy this change still works when you raise the v-core in vios to a higher lvl, eg 1.5v because the board applies this as 1.4v(vid) + 0.1v(board adjust). so when you change vid to 1.45 you get 1.55v out.
why would you want to?
you need to up the vcore if your clock is unstable
you find out the clock is unstable when your pc crashes/bluescreens
which means you need to reboot meaning you pass the BIOS entry point where you can have much safer control over the vcore.
Don't see any point tbh, more opportunity to trash your board frankly.
you need to up the vcore if your clock is unstable
you find out the clock is unstable when your pc crashes/bluescreens
which means you need to reboot meaning you pass the BIOS entry point where you can have much safer control over the vcore.
Don't see any point tbh, more opportunity to trash your board frankly.
i was asking for a mate of mine, he is overclocking on LN.
when overclocking he just wanted more control of vcore than whacking it straight up in bios.
point still stand the only time he'll know its unstable is if it crashes. Its not a case of "whacking" it up in the BIOS, he needs to set an FSB, test it.. if it fails up the vcore a notch and test it.
And keep repeating this.
Vcore control in windows will make it no easier.
And keep repeating this.
Vcore control in windows will make it no easier.
says it all - his requirements are more than the usual and I can see how having a live voltage control would be useful - especially if he's trying for suicide shots using a windows based oc programme.
Would be useful to be able to boot up in a controlled manor and then once you're ready, up the voltage and clock the nuts off it!
There might be a way to do it via a variable resistor the way we used to with nb voltages but I've never come across it for the v.core.
this can be achieved with a variable resistor as mentioned - anyone who used an old Iwill KK266 will remember having a row of trimpots stuck to their pci slot, however its oh so easy to blow everythign up like this, if the trimpot is a bit cheap and noisy you can easily crash while changing it.
look for volt mods for the mobo, and if you find reference to a fixed resistor of value x for upping v-core by some other fixed value then replace that with a resistor of x-10% and a pot of ~15% of x givign a variabler ange from 90% thru 105% of x. for fine control.
look for volt mods for the mobo, and if you find reference to a fixed resistor of value x for upping v-core by some other fixed value then replace that with a resistor of x-10% and a pot of ~15% of x givign a variabler ange from 90% thru 105% of x. for fine control.
you have hit the nail right on the head, that is exactly the idea.
thanks to all who replied and will pass on info, as said the electronics part go way over my head.