How to tell when VCore is to much?

onlyCOpunk

Platinum Member
May 25, 2003
2,533
1
0
Ok for the first time in my life tonight I boosted the vcore of my 2400+ to 1.7 so that I'm able to attain 2200mhz (11x200) I'm constantly monitoring my temps with the program that came with 8RDA+ board, and they seem to be fine. If I force too much voltage into my CPU will it jsut overheat and shut down, or will I get no warning that I put too much in?

Another thing, is voltage really my problem here with my overclock? Before I was using default voltage and I could boot into windows, and my temps were the same as they were at stock speeds, but after a while my computer would reboot itself. Could undervolting be the cause of this. Everything seems to be running fine right now with the voltage up. At first I thought it was the ram, but then I lwoered the multiplyer on the CPU and it runs fine, so I'm figuring it was the voltage.
 

Blooz1

Senior member
Jan 14, 2003
621
0
0
You really don't have to worry about anything at 1.7V....T-Breds are safe up to about 1.85V before things get dicey. I run my 1700 DUT at 1.8V 24/7 without a hiccup.
 

redpriest_

Senior member
Oct 30, 1999
223
0
0
Running my 3000+ at 2.13v. I'm told that's very unsafe, but it was necessary for 2600 mhz. Don't try anything above 1.85v unless you're fine with killing your chip...
 

onlyCOpunk

Platinum Member
May 25, 2003
2,533
1
0
Well I starting using my computer to see how stable it is and after playing Unreal 2 for about 20 minutes it would quit. So while my temps weren't THAT high say 60C for a full load, I figured the vCore must have been too much.
 

redpriest_

Senior member
Oct 30, 1999
223
0
0
Try running Prime95. It heats up the CPU really really quick -- and you'll be able to tell if your CPU can handle it -- I suggest running it for 24 hours and seeing if it boots. If it doesn't you have a stable system.
 

canoner

Senior member
May 26, 2003
465
0
0
My take is 1.8 is quite safe although it does get hotter. I OC on retailed CPU and if it dies, I get a replacement from AMD. Last time my 1500+ died, I got a 1800+.
 

ChampionAtTufshop

Platinum Member
Nov 15, 2002
2,667
0
0
as long as you stay below 1.85volts actual you are ok
1.85 is my upper limit, cuz i wanna keep my cpu lol

but it also depends on the gains...
mine runs fine at 2200mhz at 1.65v
i need 1.8-1.85v to get 2300 or 2350ish
i dont think its worth it lol
 

Shimmishim

Elite Member
Feb 19, 2001
7,504
0
76
Originally posted by: redpriest_
Running my 3000+ at 2.13v. I'm told that's very unsafe, but it was necessary for 2600 mhz. Don't try anything above 1.85v unless you're fine with killing your chip...

:)

i love risk takers like you!!! but wish i had that sort of money to burn on a 3000+ :)

 

onlyCOpunk

Platinum Member
May 25, 2003
2,533
1
0
Originally posted by: canoner
My take is 1.8 is quite safe although it does get hotter. I OC on retailed CPU and if it dies, I get a replacement from AMD. Last time my 1500+ died, I got a 1800+.

I have a retail CPU, so if I burn mine out AMD will replace it under their warranty? And I'm also curious about the temps as my old T-Bird 1.33 used to run idle at about 62C and things never quit with those temps? Would a game quitting or Windows crashing really be from it being undervolted because I would not think that 60C would be too much and cause crashings.

I'm also using the HSF that came in the retail package, maybe someday I will upgrade if I find a good deal, but so far this one has been keeping everything in check stock wise.

 

shelaby

Golden Member
Dec 29, 2002
1,467
0
76
when u guys say stay below 1.85 for tbreds, do u mean 1.85 in bios, or 1.85 actual, cuz some mobos over and under volt, i know mine under volts, in bios i have it at 1.75 but actual is 1.8
 

Shimmishim

Elite Member
Feb 19, 2001
7,504
0
76
Originally posted by: shelaby
when u guys say stay below 1.85 for tbreds, do u mean 1.85 in bios, or 1.85 actual, cuz some mobos over and under volt, i know mine under volts, in bios i have it at 1.75 but actual is 1.8

i would say 1.85 actual... not bios...