PDA

View Full Version : possibly defective 2nd core?



Emperor
06-25-2006, 11:56 PM
i am running a opteron 170 and i noticed when i try priming, most of the time it's the core 0 that fails first while the other core runs for a while longer.

not that core 1 actually ran for 8hrs w/o errors but core 0 fails much faster, sometimes within 20secs

4Qman
06-26-2006, 12:02 AM
Are you overclocking the chip?

Shark-357
06-26-2006, 12:05 AM
If u are overclocking its normal that one core i weaker then the other ..

Emperor
06-26-2006, 12:05 AM
yes yes

trying to prime at 3.0ghz

Emperor
06-26-2006, 12:13 AM
EDIT. the cores take turns to fail within 30secs.

right now, the reverse of the first post is happening

4Qman
06-26-2006, 12:38 AM
Its not defective mate, your pushing the core past what it can handle. Either cool it better/increase the juice or lower the clock.

What cooling are you running dude?

Emperor
06-26-2006, 01:02 AM
Its not defective mate, your pushing the core past what it can handle. Either cool it better/increase the juice or lower the clock.

What cooling are you running dude?
i am using water cooling and i;ve been trying vcores frm 1.56v to 1.65, every vcore possible. still refuses to prime.

i mean, i've seen many 170 users with the same batch and stepping having 3ghz prime stable or faster.

4Qman
06-26-2006, 01:12 AM
OK, depends on what temps your hitting as this can cause it to fail, my old 146 would fail once it got a little toasty.

Id maybe try 2.8/2.9 and if this passes then maybe its other factors thats causing your chip not to hit 3ghz.

r3w4
06-26-2006, 01:32 AM
Seems like other factors since the cores take turns failing. Emperor you really didn't give any information about the system and specs.

Emperor
06-26-2006, 01:57 AM
oops....

anyway

my ambient is ard 25-27deg, being in a tropical island.
idle temps hover ard 32-34degC
load(eg, F@H, utorrent) ard 40degC

somehow i get this when priming,

ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Possible hardware failure, consult readme.txt file, restarting test.
ERROR: ILLEGAL SUMOUT
Maximum number of warnings exceeded.
Torture Test ran 0 minutes 55 seconds - 0 errors, 100 warnings.
Execution halted.

what's illegal sumout?

taemun
06-26-2006, 03:18 AM
what's illegal sumout?

Quick summary: it means that your chip is either too hot, or clocked too high. Or both :)

As someone said ^^^^ decrease your clocks, or increase your cooling. Or move to the arctic :woot:

farksy
06-26-2006, 03:38 AM
I get this error when i undervolt.

ripken204
06-26-2006, 06:24 PM
have u tried any other overclokcing? plz dont tell me u just started overclocking to 3.0 right away. try 2.8 first and just go up little by little

r3w4
06-26-2006, 07:58 PM
Your load temp is good so try increasing vcore, based on what farksy said.

einCe
06-27-2006, 01:40 AM
ram capable?

Emperor
06-27-2006, 05:22 AM
i've tried overclocking , 200mhz at a time. but last prime stable clocks were 2.9ghz

alexio
06-27-2006, 05:26 AM
i've tried overclocking , 200mhz at a time. but last prime stable clocks were 2.9ghz

Sounds like you have hit the max of your chip if anything more than 1.56v doesn't help. Bummer, but OC's are never quarantied. If you take off the IHS it will probably hit arround 3GHZ though, but that's your choice ;)