Am i safe???

U

UberPooner

Limp Gawd
Joined
Jul 21, 2005
Messages
435
Hi, i recently oc'd my processor. it is a amd 4000+ and i got it to 2.6 ghz.
its using this fan http://www.newegg.com/Product/Product.asp?Item=N82E16835106068

and rite now when im doing nothing its at 38c. im not sure how high it gets when im playing games. the multiplier is x12 and the HTT is at 217 so i get 2604mhz. and the voltage is at 1.5v. so now i am wondering if this is an ok clock to keep my processor at? if not what would be the best settings. also im using EVERST to read the temps.
 
you need to look at what your load temp is. That heatsink kind of looks like a "smaller" takeoff of the famous XP-90. Idle doesn't mean a whole lot temp wise (this can be argued too...some may say that your cpu is idle more than it is under load so the cooler you keep it the majority of the time will prolong it's life.), but the stress under load is what will make or break the cpu when overclocked. The cooler it is under stress, the less likely it will be to "break" under the stress (which is why you see a lot of people watercooling or phase-change cooling their highly oc'd cpus).

I never looked up the specs on a 4000+ and don't have the time to right now, but what's the stock voltage on it?

I have a Winchester 3200+ and I can run it at 2.6Ghz with about 1.67v on the core, however I have a lapped XP-90 heatsink and the temp doesn't get above 50c under load.
 
Stock voltage is 1.35

i was playing guildwars and using itunes and i opend up windows task manager and it said it was at 100%, and i checked the temps and they were around 48-51. how is that?
 
51's a tad high. But nothing unsafe. Warmer temperatures might raise that to unsafe (55+) levels.
 
try something real intensive...like Prime or SuperPi. Those are most often used to stress test a cpu at an overclocked speed. They tend to generate the most amount of heat also. Just because task manager reads 100% doesn't mean that the cpu's being stressed 100%. Prime and Superpi are known for pushing cpu's to their limits.

run those and see what you're load temps are. They may be higher or lower. if they're higher, I'd get better cooling if you want to continue to run at that speed/voltage.

btw...did you max out the clocks on the stock voltage? My a64 clocked another 300Mhz on stock voltage before I had to bump it. After that I had to raise the voltage drastically to get decent stable results.
 
nst6563 said:
try something real intensive...like Prime or SuperPi. Those are most often used to stress test a cpu at an overclocked speed. They tend to generate the most amount of heat also. Just because task manager reads 100% doesn't mean that the cpu's being stressed 100%. Prime and Superpi are known for pushing cpu's to their limits.

run those and see what you're load temps are. They may be higher or lower. if they're higher, I'd get better cooling if you want to continue to run at that speed/voltage.

btw...did you max out the clocks on the stock voltage? My a64 clocked another 300Mhz on stock voltage before I had to bump it. After that I had to raise the voltage drastically to get decent stable results.
Click to expand...

hay, no i did not really max out the clocks on my stock voltage. but i think im going to try that to reduce the temp. but how would i no that it is clocked to high for the voltage? would it not load windows or what?
 
also ive been running Prime and ive passed the 1024k and the 8k self tests so far (and its still running) and my temp hasent gotten above 51c.
 
I thought at one point there was a sticky on the A64 overclocking...but here's a quick n' dirty of it.

If your clock speed is too high for the voltage it's set it a few things tend to happen. One is that it stops after the initial POST sequence. Another would be that windows doesn't fully load, displaying errors that it can't find files or just plain BSOD (dropping the clocks back down normally fix this...so don't think you'll have to be reloading windows all the time...but if you can make an image with ghost or driveimage or something it could save some headache b/c the chance is always there that it'll corrupt windows and need a reinstall). It could even load into windows and run an 8k superpi and not fail...until you run the 1million or let it prime for a while. This is the reasoning behind the extensive testing at each speed step.

set your voltages to stock. raise the bus speed. This is where people vary in methods. I immediately raise mine by 10 or 20 b/c most A64's I've messed with easily handle another 10-20mhz on the fsb/htt on stock voltage. Load windows, run some tests, prime some, run superpi, monitor temps.
If everything runs fine, reboot and raise the clock a bit more and repeat the tests. Eventually you will get to a point where you'll have to raise the voltage. When that comes, raise it one setting at a time and then run the tests again.

When you've reached what you think is the max clock speed at the desired voltage...run superpi at the highest setting and let it prime for a while...like overnight or something. If it never crashes in those two in an 8 hour period of time, chances are it's stable and safe to run those speeds.

chances are, time and patience will yield you a faster and cooler cpu ;)
 
nst6563 said:
I thought at one point there was a sticky on the A64 overclocking...but here's a quick n' dirty of it.

If your clock speed is too high for the voltage it's set it a few things tend to happen. One is that it stops after the initial POST sequence. Another would be that windows doesn't fully load, displaying errors that it can't find files or just plain BSOD (dropping the clocks back down normally fix this...so don't think you'll have to be reloading windows all the time...but if you can make an image with ghost or driveimage or something it could save some headache b/c the chance is always there that it'll corrupt windows and need a reinstall). It could even load into windows and run an 8k superpi and not fail...until you run the 1million or let it prime for a while. This is the reasoning behind the extensive testing at each speed step.

set your voltages to stock. raise the bus speed. This is where people vary in methods. I immediately raise mine by 10 or 20 b/c most A64's I've messed with easily handle another 10-20mhz on the fsb/htt on stock voltage. Load windows, run some tests, prime some, run superpi, monitor temps.
If everything runs fine, reboot and raise the clock a bit more and repeat the tests. Eventually you will get to a point where you'll have to raise the voltage. When that comes, raise it one setting at a time and then run the tests again.

When you've reached what you think is the max clock speed at the desired voltage...run superpi at the highest setting and let it prime for a while...like overnight or something. If it never crashes in those two in an 8 hour period of time, chances are it's stable and safe to run those speeds.

chances are, time and patience will yield you a faster and cooler cpu ;)
Click to expand...
:D http://www.hardforum.com/showthread.php?t=795444
 
You must log in or register to reply here.
Back
Top