Which core holds your C2D overclock back?

[blade52x]

Just wondering, which core ends up being your "failing core" during stress tests. Every time I push for a higher overclock, it's always my second core (Core 1) that fails during Orthos. I'll then voltage tweak until both run for 10+ hours stable. But I think Core 0 could take anywhere from .1-.2V less to run stable. (I never actually testing by shutting the second core off, it doesn't matter since I'll never do that anyway).

So very random question: Which core is your "less equal"?

 

[msg1285]

I guess I get the newb award on this one.

How do you know which core failed?

 

[blade52x]

When Orthos fails there is an error report.

One core's results will just say "execution halted" or something like that, while the other will say "execution halted - fatal error: result returned xxxxxxxx, expected yyyyyyyyy" or something along those lines

 

[(cf)Eclipse]

When Orthos fails there is an error report.

One core's results will just say "execution halted" or something like that, while the other will say "execution halted - fatal error: result returned xxxxxxxx, expected yyyyyyyyy" or something along those lines

and if it is consistantly one core that is failing, that core is holding it back

 

[msg1285]

Kewl thnx for the info.

I'll spend the rest of day making my system fail now

 

[Arcygenical]

Core0 always fails @ 3675mhz for me .

 

[TehQuick]

I dunno which core fails, orthos either crashes to desktop or reboots the computer Strangely enough, another e6600 errors in orthos normally, no reboots or crashes... Both tested in the same mobo, same memory... go figure