• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

What's your voltage? [retired sticky]

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

What's your voltage? (closest value)

  • Below 1.75

    Votes: 774 37.6%
  • 1.75

    Votes: 382 18.6%
  • 1.8

    Votes: 240 11.7%
  • 1.85

    Votes: 331 16.1%
  • 1.9

    Votes: 101 4.9%
  • 1.95

    Votes: 68 3.3%
  • 2.0

    Votes: 52 2.5%
  • Over 2.0

    Votes: 111 5.4%

  • Total voters
    2,059
1900+ 1.64Gz 1.775v 43.5-48C 12x136

FSB 40C @136

Somebody here has a 1600+ running faster
at lower volts than my water-cooled 1900+.
This one is rock solid, though, and fairly
quiet for the power.

-Bob
 
I got my 1GHz Athlon clocked 100% stable at 1.47GHz and I'm using 1.975Vcore with the Volcano 7+. Even under the hottest room temperatures, my cpu never exceeds past 45c.


DS-Master
 
maybe it's not really a minivan

I doubt that heat is what is causing problems
with my XP1900+ when run over 1.64Ghz
12 x 136 FSB or 12.5 x 133, 45C. Maybe I should
look at linux and the VIA chips. When I last
tried to go higher my errors were virtual
paging kernel oops and in the boot messages
there was "Unrecognized VIA south bus".
Now I have up to date source code and
should try again. I have hard drive recognition
problems even with kernel append= specific
instructions as to which bios number i.e.
0x80 or 81 or 82 or 84 or 84 or 86 is drive
/dev/hda. I don't know if the raid chip
is recognized.

Meanwhile slightly paraplegic linux is running
stable and serving my network. I can't do
things that crash it all the time but I should
find out if new source code keeps the kernel
up with faster settings. HTC code updated.

Gotta go to get nvidia kernel source, too.
Some is in there but there are some others
with documentation and utilities for OC'ing
nvidia, 2 or 3 nvidia packages http://www.debian.org

-Bob
 
I'm running an Athlon MP 1.2GHz @ 1.67GHz (9.5x176MHz) with the voltage of 2.1V (MBM showing 2.11-2.16V). It's aircooled with a Taisol CGK760 with a 120mm fan 12V @ 24V. :D
 
I miss my 8KHA+... I wrecked it a week after I repaired it (replaced a defect mosfet and resistor). I connected a device that i used to bypass the overcurrentprotection wrong way :( . I actually ran my MP with 2,38V on that board, but only @ 1,2GHz.
 
Had an unlocking accident.. so my AthlonXP 1700+ (default 11.0X) is locked at 7.0X, so the vcore is set to 1.725! So basically I'm running a 937MHz AthlonXP! :(

Tried cleaning off the conductive ink (which I guess I can't see with my naked eyes), again and again with no avail!
 
1.85v on a soyo dragon ultra, xp1600 running 147fsb x 12.5@1838mhz. its stable, up 4 degrees from stock, and cooled with air.
 
1.8 vcore - 1700+ Unlocked running at 1600 mghz 266 bus ,air cooled will boot as 1900+ but unstable even with 1.85(highest available) vcore.

MSI K7T266 RU
GEFORCE 3Ti
 
Although I'm now running at stock speed an vcore, the proc is just extremely hot now. I'm gonna do something about it and winter is coming, so I'm hope that I'll be able to go to 1400+ @ 1.85v. I selected 1.85, coz that's the core voltage I'll be running soon enough...
 
I'm at 1.85 volt on a athlon xp 1800+ (done with pencil trick because my current mobo abit kt133a (to be replaced soon) doesn't support user changable voltage. Managed to get the thing to run at 1850 at this voltage though. It too bad that there was only a 5% perfomance differance from at 1533 though because of the pc133 ram.
 
my parents computer (tbird 1000/100 AVIA w/ abit nv7 133-r) does 1580 mhz at only 1.8v (the highest the board goes on a locked cpu). Can't run it for long at this speed though because of the poor heat sink (50 C at 1000, shows about 75 right after booting at 1580 and is rising so it has to be shut down but when I tried it with my own tt volcano 7+ it did only 47 C and was stable)
 
Running this 1.4 Athlon at 1.5 with a vcore of 1.80...Have had some trouble getting accurate readings on what the vcore actually was, but MBM5 solved my dilemma...:rolleyes:
 
Back