Is 1.7v vcore safe ???

Is 1.7v vcore safe ???
I have Thermaltake Silent Boost K8 Heatsink & Tagan Tg-480 (480W) power supply. Temperature - OC at 217 FSB (1:1) - 44-47C
Athlon 3200 (2210 MHz - NC core, no OC)
- MSI K8N NEO Platinum (1.4 bios)
- 2x 512Mb PC3200 Geil Ultra (2-3-3-6 1T at stock)
- MSI 6800GT
- WD Caviar 80GB SATA 8Mb cache
- Tagan Tg-480 (480W)
- SB Audigy 2 ZS
- Other standar stuff
- Win XP + SP2
- Dx: 9.0c
- ForceWare: 66.70
What is the highest safe voltage for Athlon 64 CPU???

1.7 is unsafe for such a, shall we say, modest heatsink/fan combo that you are using.
The Thermaltake Silent boost cools no better than the AMD stock HSF; it's just quieter.
I'm running 1.7 right now, with a much better heatsink, and even that's not very safe. So I toss on cool and quiet into the mix, so it's only running 1.7 while playing games...and even that's not safe...I expect to fry my cpu w/in a few months so I have an excuse to upgrade
If you're planning to keep your current HSF setup, you should drop to 1.55V.

Similar Messages

PT880 with 2.4A (no not that A, the other :-D)

ok, i'm wanting to kno if this is a good idea
PT880 (i've red review so far as much, this thing looks like it kicks ass)
and a 2.4A prescott (533 bus).
my plan, take this 2.4A all the freakin way... 3.4 preferrably (stock vCore, safe OC)
problems i would like to kno about:
is the PCI bus locked? i've read that the SATA takes a hit from OCing, and i will have this thing from a 133FSB, to preferrably a maybe a 185x18=3330 or so.
this is quite a bit if the PCI (SATA???) isn't locked
i plan on using my 120 and one of my 80s (thru a PATA-SATA converter board) on the SATA. leaving the IDE for DVDburner, DVDrom, and other 80 gig, (maybe another 52x burner cuz DVDburner burns CDs at 40x. hey, they r 20 bucks...)
is there any other, general... problems with this board?
i know about the prescott, and bios upgrade thingy, i'm not really worried about it, because i have access to northwoods to upgrade (flash), if anything gives me problems
ANY other problems? seems like a SHWEET board, but i was also looking at a ABIT PT880 board, and man did it suck, nobody has one that is stable.
thank you for all your info, and btw, all the puters we sell at the shop, are all MSI :-D MSI for goodpeople, and like biostars for rude people and cops :-D
j/k j/k j/k cops r nice people

yes :D thats why i considered this board, very good performancewise (almost catching 875), but not too much speedwise overclocking, yet plenty of options, PERFECT for maxed out prescott 133mhz CPU... thank you
BUUUUUUUUT... very good question... is SATA locked, or not, why is it that these SATAs get knackered when overclocking, AND does it only happen >200 FSB, i don't really plan on ever getting to 200FSB, because that would leave me at around 3.6ghz, which would probably be my max... i would have to do some interesting cooling modifications to get that high, (not that this chip couldn't take it heh heh heh heh) but 3.6ghz is more of an overclock than i can imagine getting, seeins how i'd end up spending about 200-250 clams on this thing, including some more than sufficient PC3200 (with tight timings). 3.4ghz is kickass for 250 bucks.
is this SATA a problem with ANY board? or just this PT880? i am running the promise SATA controller on my K7N2DeltaILSR right now, (using PATA-SATA adapters) but i am running stock... so i wouldn't notice any instabilities... (this MSI couldn't handle the duron heh heh heh heh)
shuttle AN35 Owns... but no SATA to test my theory :(
an experienced SATA board OCer perhaps able to answer question?
thank you in advance...
EDIT: pg5555: InYourOpinion, which? Soltek, Gigabyte, or MSI? i know the Abit is junk...

Which pin to measure vCore on MS-7125?

I think I found it (shows 1.621v on digi MM with bios set to 1.62v) but it is strange, top of pin looks like correct vcore, bottom of pin reads 1.585v. Each end of the pin shows uber-stable voltage (~0.001v). now I have the case closed but IIRC, it's in the top row of pins at the top edge of the board, directly north of the CPU, third pin from the right if facing the board. Correct pin?
thanks in advance

B&G,
I do not have a 7125 but the links below depict where to find Vcore and Vddr on a 7025. Your set up should be similar.
Look here for Vcore location: http://www.xtremesystems.org/forums/attachment.php?attachmentid=23902&stc=1
Be extremely carefull taking Vcore readings at that location, pin shown will be Vcore, short stubby pin next to it (middle) carries 12 volts, and the one next to it carries your Vddr voltages (2.xx Volts). Shorting any two of these pins together will ruin your day and your motherboard.
You can also obtain Vddr from here: http://xtremesystems.org/forums/showthread.php?p=583463
This location is a bit safer since pins next to it do not carry different voltages.
Good luck,

With a Zalman 7000Acu cooler, how high vcore is too high???

I'd like to overclock a little with my Neo2, but since I don't have an accurate temp reading in my bios, it will be tricky.
I have an fx-53 w/zalman cooler and how high can I raise the vcore while still playing it safe...
I was thinking i'll raise it to 1.6v and get the best I can out of that.

Yep I can confirm 1.8v makes a funny smell

Vcore adjustment on 645 Combo-L?

Hi,
I am commissioning my new PC.Currently consisting off:
645Combo-L motherboard
1.7 G Celeron
256 MB PC2100 DDR.
20GB Seagate HD
Generic PCI graphics board.
The system passes POST and will boot up DOS, but the system is to unstable to allow an install of W2k or even W98.
The Celeron Packaging states 1.75V, but the BIOS health monitor gives the Vcore as 1.69V, which seems away to low for the Celeron and may be the reason for the instability.
How can I adjust this? I can only successfully run DOS, but there appears to be no DOS software for this adjustment.
MSI seem only to provide Windows software for Vcore adjustment.
Is there any way forward?
Your advice will be most welcome.
Codger

Thanks Assaf for pointing out my error regarding voltage.
That blows away my theory as to the cause of my system instability.
I am using the "safe" BIOS defaults ie FSB=100 PC2100 = 133
and CPU clock = 1.7GHz.
I have changed the memory,the HD, the HD cables and the power supply, without resolving my problem. I don't have access to a spare Celeron to try, but what are the chances of a Celeron that passes POST and can load up DOS from a W98 boot floppy, being faulty in such a way that it crashes when installing Windows?
regards
Codger

Boris_m - can you hack AMIBIOS to allow more CPU Vcore Voltage?

I saw you talking about all kinds of BIOS mods and tweaks... so i was thinking - can u mod the AMIBIOS 3.31a (the one that comes with my 645 MAX2-LRU) so that it would be exactly the same only it would allow, lets say, up to 1.7V CPU Vcore instead of 1.6V ?
I would owe you my life if you could :D

Quote
Originally posted by EmAzY
lolz hehe u made it sound like easy and safe to do so...
hehe did u do the mod yourself also and did it help.. coz your 1.8 is only at 2.4ghz... did u try pushing it higher.
Yes i did the mod myself and of coz it helped. Highest i could go was 149 fsb coz my ram is limiting me :(
And by the way, most of the 1.8a processors need at least 1.65v to get to 133fsb. Of coz if u r lucky, u might get those gd ones which will run @ 133fsb @ default vcore :P

Found a solution for Locked VCORE/Prescott

As much as I hate "Core Center" ( the first versions were just to " Buggy" for my taste) it seems the latest version has supplied a solution to my problem of not being able to adjust the Vcore with my Prescott
My board ( 865 Neo 2 LS) has had the Vcore locked since Bios version 2.0
( 2.0 and up are the only versions that support the prescott microcode)
When overclocking I hit a brick wall at 3.59 ( sometimes this was unstable) and knew that it was just a matter of being able to raising the Vcore just a tad( don't want to " smoke that Prescott )
Well the latest version of Core center has allowed me to adjust the Vcore . I set it at 1.5 ( which seems to be the limit that some of the people over at the overclockers .com agree is safe) and I am happy to report that I have been able to hit 3.71 for two days now stable
I have run a battery of tests such as Sandra , PC mark etc in an effort to see how stable it is and have not had a problem yet
Video Encoding ussually brought my system to it's knees , now I not only can do this but I can run several other programs while encoding
my temps have only increased 2C so far.
I am going to try and continue to inch up my FSB some more and see how far I can push this 2.8E ( If I am gone for awhile you know what happened )
Dave

lol with my board i send 1.6vcore to keep over 3.95 stable.

MOVED: MS-7125...which pin to measure Vcore?

This topic has been moved to AMD64 nVidia Based board.
MS-7125...which pin to measure Vcore?

B&G,
I do not have a 7125 but the links below depict where to find Vcore and Vddr on a 7025. Your set up should be similar.
Look here for Vcore location: http://www.xtremesystems.org/forums/attachment.php?attachmentid=23902&stc=1
Be extremely carefull taking Vcore readings at that location, pin shown will be Vcore, short stubby pin next to it (middle) carries 12 volts, and the one next to it carries your Vddr voltages (2.xx Volts). Shorting any two of these pins together will ruin your day and your motherboard.
You can also obtain Vddr from here: http://xtremesystems.org/forums/showthread.php?p=583463
This location is a bit safer since pins next to it do not carry different voltages.
Good luck,

Safe xp2100 temps??

Ok, since my new xp2500 would not oc hardly at all, I put my old xp2100 back in.
I have it oced to 2250MHz- seems stable. Loaded it with Prime95 and the cpu temp seemed to peak at 52-53c, while the MB is seemed to peak at 43c. I have my vcor set to 1.8 which is probably actually a bit higher because of the MB. My FSB is 180x12.5. Are these temps safe? Also, if these temps seem a bit high, what kind of cooling solution would you suggest. I currently have Thermaltake XaserIII with seven case fans and I believe its a Thermaltake Volcano CPU fan. I dont want water cooling, but what about other fans or set-ups?

ok, i bumped my fsb to 195 and changed the multiplier to 12. I am running cooler now but Prime95 pukes on me in two minutes. CPU Stability 5.0 and 3dMark2001 run without a hitch. So my question is- Should I adjust my ram timings to make the sytem more stable? I think I am at 8-4-4-3 now. If so, any suggestions on where to start?

Adjusting the vcore voltage to get more power

wat wud be a safe voltage 4 me to rise it 2 at the moment its at 1.64v wat wud be the highest i cud go wit out burning out the cpu

Quote
Originally posted by balewolf
Raising your Vcore does not give you more power
lmao voltage is power to the cpu raise it is force fed more their for it can go to a higher clock speed. peewee2004 check your temps i thk some go up to 1.8 aslong as the temps stay under control.
GO ahead and lyao, he asked about raising vcore for more power. not raising vcore to clock higher for more power. I should have posted: Raising Vcore alone does not give you more power. My bad.

Limited vcore 990FXA-GD65

I have a 990FXA-GD65 and from what I can tell there is a revision 1.0, 2.0, and 3.0. What is the best, most accurate way of finding out the revision of the board? Also, do any of the beta bioses allow more voltage adjustment? The vcore can only be set to 1.45v in the bios, it can go higher in AMD Overdrive. I'd like to not use overdrive anymore but the board doesnt allow enough Vcore adjustment for me to do so.

Its been a BIOS restriction for a long time, and it was introduced when the FX8000 series were launched.
These CPUs start spiking to over 200Watt TDP when overclcoking. The board was designed before these CPUs were launched and thus the VRMs are not safe at those power requirement levels. To protect the VRMs from burning up, the restriction was added.

785GTM-E45 vcore reset when resume

I currently have the vcore set to 1.34x in the bios since auto puts it over 1.45. When I resume from S3 the vcore resets itself to auto.
Nothing is overclocked, it is all at default speeds except my memory which is running at 800mhz.
I read about the high auto vcore, but it shouldn't be resetting to auto on resume.
BIOS is version 8.8, that latest I was able to find.

Quote from: wlahdone on 02-March-11, 08:42:05
If your intention is to keep the CPU with low voltages ,you could do the opposite and Enable CnQ ONLY ,to keep the CPU at low voltages dinamically.
And the real measurement is made with a multimeter at the VRM coil outputs on the back of the mobo.
The voltages you see are software reads.
I plan to use CnQ, but CnQ is used to lower power usage while you are using the computer. When not in use I'd prefer it to sleep to save even more energy. I would just shut it down but it is a media PC and I would to be able to turn it on with my remote.
I'm aware the software voltages are not accurate. In the BIOS the "safe settings" for vcore are between 1.447 and 1.456 with Auto being between 1.453 and 1.456. So it isn't just software readings. I considered that the sensor could be doing something weird on resume and reading wrong, but running prime95 for 5-10 mins after a resume shows temps several degrees higher than before the sleep/resume.

Safe OC level for AMD 64 3200+ Clawhammer?

My current computer set up consists of the K8T NEO FIS2R and the AMD 64 3200+ Clawhammer (2.0ghz 1MB L2 cache) core. While I understand that the K8T is not particularly conducive to overclocking because of the lack of an AGP/PCI lock, I'd still like to net a little extra performance and try my hand at overclocking the CPU. However, as I understand it, overclocking the CPU can be potentially more dangerous than overclocking, say, a GPU, so I was wondering what a safe OC level for my A64 3200 Clawhammer on the K8T might be? I plan to follow safe OC procedures (slowly bump up FSB or whatever its called now since its integrated, and then stress test), but I'd like to know what not to try to exceed. I'm thinking maybe 200 mhz boost within safe limits, making it 2.2 instead of 2.0?
Oh btw, I use an SATA HDD, if that should be taken into account. I've heard something about data corruption?

From what I've noticed, the Athlon64's seem to overclock fairly well. I've got a 3000+ (runs at the same clock speed as yours, just has half the cache) running at 2.15 GHz just fine, even when simultaneously undervolted to 1.4V (conventional wisdom says that when overclocking you're supposed to have to RAISE the voltage to achieve stability, but I was able to lower mine and still be stable, which would seem to say something about how well the CPU handles the overclocking). So while in general overclocking a CPU may be fairly risky, I'd say that the Athlon64 is an exception...you'll probably hit problems with your memory/PCI and AGP devices/SATA controller long before you're stressing to CPU to a dangerous level (all thanks to that missing PCI/AGP lock, of course).
Anyways, with any luck you should be able to hit a 220 MHz FSB just fine, just don't push it too far past this because as you correctly mentioned, people have reported issues with the SATA controller becoming unreliable above 220 MHz FSB, and this *can* cause your HDD's to become corrupted, which is probably something you don't want.
Other than that, just watch for any drastic changes in your temp readings while overclocking...if the CPU's running temp jumps by like 10 or 15 degrees from its temp at stock speeds, of if you have to raise the vcore voltage in order to keep the system stable, you may want to consider easing off a bit.

Powerup Edition: Vcore (Auto) setting bug

Last night I decided to push my pc by overclocking it a bit. This was only to test and report back to the board. I like the settings that are in my signature, they keep my pc quiet (I have EIST, C1 and smart fan enabled), and it is fast enough to handle any games or apps that I use.
Anyway, I disable all the fancy stuff and start overclocking. Basically I adjusted my voltages and dividers in the bios, and then tweaked my fsb and cpu multiplier using windows based apps...
After I was all done, I undid everything and put my system back to what you see in my signature. Well, I use Everest UE to check how my system is running and found a disturbing bug..
I had set my Vcore (core voltage) back to Auto, but my system was still running at almost 1.5v, and even though my computer had no load, C1 did not kick in and lower my voltage either. But EIST did reduce my multiplier from 9x to 6x, which confirmed that my system truly was at idle.
After many starts and restarts (all of which did nothing to fix the problem), I finally turned my computer off and also turned off the power switch on my power supply. My original thought was to open up my pc and reset my bios, but instead I decided to wait a minute or so and boot up my pc, sometimes that clears up problems... Well, i worked, my Vcore (on Auto) and C1 (enabled) worked as it should. Since this could be a real bug, I went into my bios, rasied my Vcore to 1.5, booted into windows, confirmed that my pc was indeed running at Vcore 1.5, and then rebooted, set my Vcore to Auto, and again rebooted into Windows. I found that my Vcore was still 1.5v and that C1 would not kick in at low load. I had to again, turn off my power supply to get Auto to work correctly.
Anyway, I don't know if MSI actually reads these forums but this is a worrysome problem. There are many users that test the waters of overclocking when they first get a new pc. So they do the normal things like push the core voltage over its rated setting, then decide that thier pc is too noisy or running too hot. So then they boot back into the bios, put settings back on default or Auto.and decide to try it again another day. With this bios your Vcore will stay stuck on whatever its last setting was before you put it on auto. For many, that setting might be the highest overclock they tried that day, meaning thier Vcore could well be stuck at close to 1.5v rather than the ~1.35v (or lower) that they should be getting on auto.
So please, if you have tried overclocking and then set your Vcore back to auto, double check and make sure your cpu isn't getting too much voltage and that C1 is working proplerly and lowering your voltage at low loads.
Be safe and have fun...

Quote from: Vaniireq on 25-October-06, 00:09:23
Thanks for the welcome to your forums.
One or two quick comments also...
I am (well was) into overclocking for years, I stopped because I found I was wasting more time tweaking than actually using my computer for fun stuff. My post wasn't intended for heavy overclockers but for the beginner that wants to get some extra performance out of their computer but didn't know where to start. So if we can let's leave this message thread for what it was intended to be in its title "Simple overclocking".
As for the 4-4-4-12 in my sig ....
yes that is what I am running my memory at ...
I am well aware that the new bios likes to change memory settings, so I manually take control of my memory settings..
So for dimitri and Planet X, I recommend using Memset3.0, this will allow you to override your bios memory settings.
You can find it here:
http://www.overclock.net/intel-memory/120402-memset-3-0-a.html
(let me know if it helped)
@smokinkane I realize that "a 320fsb overclock, that is easily accomplished" and that, my friend, was the whole point of my post, you know how (share this with others), there are many that read this board that don't know where to start.
If I get some free time I will try and see how hard I can push the fsb with my stock equipment.
Anyway, as I mentioned in my post, I have only had this board a couple of days, so I don't know yet what it can and can't do. If you have specific problems or questions, start a new thread, so everyone can work on the problem.
Be safe and have fun...
Good post as described in the headline "simple overclock".

Max safe CPU Voltage?

I am in the middle of OC'ing my system. So far I am doing pretty good. I can get up to 252 clock generator x 9.5X CPU multiplier at 4X HT multiplier. (I currently got my memory at 133 3-6-6-11: I'll tweak this a little bit later.)
To get this I have my CPU Voltage at 1.7V. Running Prime95 with option #2, I can keep my CPU temp below 55C.
My question is, is this voltage too high? I understand that voltage will raise the temperature, and that it will decrease the life expectancy some, but is there some other problem? Is this really safe? Or should I reduce the voltage?https://forum-en.msi.com/images/msi/smilies/confused2.gif

Increasing Vcore increases the gate voltage on the transistors inside which lowers the on resistance allowing the transistors to drive their signal lines harder and thus faster. Increasing Vcore also means the signal lines need to swing farther (voltage wise) than they did before. As you continue to increase Vcore the on resistance of the transistors improves less and less as other limiting factors in the transistor take over, however the signal lines still need to swing more and more as vcore goes up. It's like being able to speed a runner in a race up, but when you do the race also gets longer. At some point the runner is going as fast as he can but the race keeps getting longer so it actually takes him longer to finish.
You want to find that sweet spot where he finishes the race the quickest.
The other problem with increasing Vcore is increasing the temperature of the die because of all the heat generated. The hotter it gets, the more the asphalt melts and the slower the runner will go. You don't want it to get to hot or things slow down.
Increased Vcore also brings a pair of failure mechanisms with it, one is just that the heat can't be removed quickly enough and when the silicon gets hot enough the currents from thermally generated carriers cause a runaway condition and the chip just melts down. This happens fast.
The slow failure mechanism is electromigration, where the currents are so high in the metal interconnect wires on the die that the metal starts to flow. Eventually the wires break. This happens slowly.
Always use the lowest Vcore you can that will give you the performance you want. In other words, err on the low side.

Is 1.7v vcore safe ???

Similar Messages

Maybe you are looking for