Opteron 170 - burn in weaker cpu0 core ?

[eva2000]

arrrrrrrrgh dam thy weaker cpu0 core



what's best way to burn in cpu0 core ??? any success stories with helping along a weaker core to catch up to it's better half ???

[biohead]

with or without IHS?

[eva2000]

with IHS as i never take it off too risky and looses resale value heh

[Plywood99]

This has worked for me several times. Use CPUBurn set to K7 and high priority. Run it on core 0 overnight. Leave machine off for 8 hours or so. Try SuperPi again. It should run longer. Continue till it completes SuperPI.

This has worked for me on claws, winnies, and my opty. Only difference is I run Prime for the testing instead of SuperPi.

I use this technique to lower voltage on my cpu's...

[eva2000]

thanks Plywood99 never used cpuburn as i use cpuburnin which is different ... will try CPUBurn/K7 and see how it goes

[mag|c]

eva be sure to bring us news on the burn in effect, and good luck to you! (fingers crossed)

[jetjaguar]

This has worked for me several times. Use CPUBurn set to K7 and high priority. Run it on core 0 overnight. Leave machine off for 8 hours or so. Try SuperPi again. It should run longer. Continue till it completes SuperPI.

This has worked for me on claws, winnies, and my opty. Only difference is I run Prime for the testing instead of SuperPi.

I use this technique to lower voltage on my cpu's...

u use cpuburn at stock clock speeds ?

[shuRe]

with IHS as i never take it off too risky and looses resale value heh

probably bad contact with the core0 then.

[jetjaguar]

my 1 core can do 2800 no prob .. other core needs alot of vcore to

[tommo123]

hopefully this will help with my 3800+ X2.

2.75 is stable on both cores, but @ 2.80, the first core craps out on superPI

[don_vercetti]

this CPUBurn sure seems to stress the CPU hard, it's good and simple as well. I'm going to leave it running all tomorrow, and see if it has any effect.

[Kunaak]

the cool thing about burning in dual cores... is you can burn one core, and still use the PC while the other core is working away.
I been doing this for 2 days now, straight, haven't turned my PC off or anything, just set Affinity to core 1 in my case, and then let it go...
I use sisoftsandra for burning in a CPU though.

[s7e9h3n]

AFAIK, the OS is run on CPU0 - so that in itself can make that particular core more unstable during benches. I guess the ideal thing to do would be to split up the processes running in windows....

[Plywood99]

u use cpuburn at stock clock speeds ?

Not at stock. I set clock at just above stable. For instance say prime stable at 2800, but 2850 craps out after about an hour or so. Run cpuburn overnight at 2850. Shut down computer for a few hours. Now try prime again.

On my opty 148 I could run SuperPi 32m and 3d benches at 3050mhz no problem, even gaming was not a problem. But Prime would crap out after about fifteen minutes with cpu set at 2900mhz. This is with voltage set at 1.61 in the bios.

I ran CpuBurn k7 set on high priority for two nights. Now cpu is prime stable, and passes occt no problem. So I drop voltage a bit and run prime, not stable. I repeat my burnin process till stable at lower volts.

Doing this I have went from 1.61v to 1.575v and cpu is rock stable, passing all tests. My goal of course is over 3ghz 24 hour prime stable at under 1.6volts...

[eva2000]

nice Plywood99... guess i need to run it longer than i have now

still burning in cpu0 with cpuburn k7 while cpu1 completed 8.75hrs of cpuburn

[afireinside]

probably bad contact with the core0 then.

It's one die...

I've had my 165 a week now and still can't get over 2850mhz. Haven't tried prime since it failed after an hour and a half but it's been 100% stable over that. 2880mhz core 1 fails no matter what voltage, probably getting to hot. I've been running games and dual D2OL and prime and all kinds of crap 24/7 since I got it and haven't gained a damned thing.

[Ket]

everything has its physical limit and no manner of torture will bring it higher.

[eva2000]

Man i hope for my sake ya wrong LOL


cpu0 = cpuburn K7
cpu1 = stressprime

[eva2000]

Doing so cpu burn in to help cpu0 core along seems to be the weaker one of the two cores at the higher clocking end

changed to dual CpuBurn K7 @2700mhz



APC UPS reported system power draw with 2nd BFG 7800GTX card added = 355 watts

Opteron 170 CCBWE 0544XPMW cooled by Corsair Hydrocool 200EX
DFI NF4 UT SLI-DR R.AB0 623-2BTA bios
2x BFG 7800GTX SLI with 81.94 beta drivers
4x 80GB Hitachi 7K80 SATAII Raid 0 OS drive
1x 250GB Maxtor Maxline Plus II PATA
Pioneer DVD Burner
Floppy drive
650W Silverstone SLI PSU

[Supertim0r]

burn in helped ?

[eva2000]

don't know yet.. gonna leave it running for as long as i can before seeing if it helps hehe

wish me luck

[amrgb]

There's little you can do (if anything) to make your weaker core to catch up with the better one.

Core 0 of my X2 3800 is at least 150Mhz weaker than core 1. I can prime core 1 at 2850 and core 0 only at 2700. Actually I don't know how good is core 1 because windows crashes before prime fails on core 1.

I've started with a Big Typhoon -> water -> no IHS+water

I gained 150Mhz on core 0, but the difference between core0 and 1 remained the same.

In fact it's a shame. You and I are unfortunate, because if ou disable one core at windows boot.ini, it will always disable core 1. So no way to disable the weaker core 0 to bench on core 1.

[s7e9h3n]

AFAIK, the OS is run on CPU0 - so that in itself can make that particular core more unstable during benches. I guess the ideal thing to do would be to split up the processes running in windows....

I'm not sure if anybody caught my post, but here it is again - lol....

[don_vercetti]

have got any proof of that?
Besides, going through windows and disabling services everytime you just want to overclock a bit further than is 100% stable seems fairly pointless. Better just to run a burn-in. Which, incidentally, has done my core0 some good (now seems to be more stable (i.e. can run prime for half an hour, could only do 6 mins before) with 1.55v@2750mhz after just a few hours of CPUBurn)

[Plywood99]

Eva2000, when I say I ran CpuBurn for two nights, I don't mean 48 hours straight. But 2nights each about 7-8 hours while sleeping, shutting system down while I go to work.

Just wanted to clarify...