OK, That'll get me back to the exact settings used earlier. (actually, looking back, the Vcore was at 1.275, not 1.30, but I can work with that on the next step up.)
V dimm down to 2.10, 5,5,5,15 timings.
FSB freq - 200
PCIE freq - 100
Processor freq mult - 13X
cpu-nb link speed - auto
cpu volt - 1.30
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
FSB freq - 204
PCIE freq - 100
Processor freq mult - 13X
cpu-nb link speed - auto
cpu volt - 1.30
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
just for reference, the last wu came in at 40:44, but it ranges from 40:01 to the high 40 min mark.
You know...I read many articles about this Core #2 issue on the AMD site. I thought most of them had trouble getting a 100Mhz OC or so before the problem appeared. I've already made it WAY past that point, and think that my processor would be considered "one of the good ones". Also, most appeared to be having it using the AM2 mobo, which doesn't have 4 phase power (independent control for NB, SB, Dimm, and CPU) that the newer AM2+'s have (like this one). So, Memory freq and voltage are seperate for CPU freq (fsb). I also saw were they were running the FSB up to 220 and such instead of keeping it down. This meant all manner of trouble with HT that this board doesn't suffer from. Also, they appeared to be using DDR2 800 ram. Perhaps they were using undersized PSU's also, causing the core volts to become erratic??? I don't know, but am willing to play around with it.
Hmmm, OK it locked up. screen freeze, not the funky cpu stuff I saw earlier. What now? I've rebooted back into linux. Saw no prompt about "OC failure, enter bios" message.
Not sure what happened. I restarted again, got the OC failure message, entered Bios and my V CPU was at 1.275.
Anyhooo, I upped the V CPU to 1.3125, change FSB to 200, Multi to 13.5. 2.7 Ghz
FSB freq - 200
PCIE freq - 100
Processor freq mult - 13.5X
cpu-nb link speed - auto
cpu volt - 1.3125
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
OK, appeared to start normally. gkrellm started, but when I click Boinc and boinc manager, I got the empty box, but the cursor still moves, tried to open konsole, but displayed nothing. Can't select anything with the mouse.
FSB freq - 200
PCIE freq - 100
Processor freq mult - 13.5X
cpu-nb link speed - auto
cpu volt - 1.325
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
OK then be that way. Upped FSB to 204 or 2.754 Ghz
FSB freq - 204
PCIE freq - 100
Processor freq mult - 13.5X
cpu-nb link speed - auto
cpu volt - 1.325
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
And, both Boinc and Boincmanager, started normally.
OK, I think I'm about there. Boinc and the system stopped responding. CPU3 went to 0%, but the manager was in the way of cpu 0 and 1, cpu 2 was at 100%. rebooting and plan to resize the manager if I can to see all 4 cores.
OK, That'll get me back to
)
OK, That'll get me back to the exact settings used earlier. (actually, looking back, the Vcore was at 1.275, not 1.30, but I can work with that on the next step up.)
V dimm down to 2.10, 5,5,5,15 timings.
FSB freq - 200
PCIE freq - 100
Processor freq mult - 13X
cpu-nb link speed - auto
cpu volt - 1.30
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
OK, only upped FSB to 204 for
)
OK, only upped FSB to 204 for 2.652 Ghz.
FSB freq - 204
PCIE freq - 100
Processor freq mult - 13X
cpu-nb link speed - auto
cpu volt - 1.30
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
just for reference, the last wu came in at 40:44, but it ranges from 40:01 to the high 40 min mark.
You know...I read many
)
You know...I read many articles about this Core #2 issue on the AMD site. I thought most of them had trouble getting a 100Mhz OC or so before the problem appeared. I've already made it WAY past that point, and think that my processor would be considered "one of the good ones". Also, most appeared to be having it using the AM2 mobo, which doesn't have 4 phase power (independent control for NB, SB, Dimm, and CPU) that the newer AM2+'s have (like this one). So, Memory freq and voltage are seperate for CPU freq (fsb). I also saw were they were running the FSB up to 220 and such instead of keeping it down. This meant all manner of trouble with HT that this board doesn't suffer from. Also, they appeared to be using DDR2 800 ram. Perhaps they were using undersized PSU's also, causing the core volts to become erratic??? I don't know, but am willing to play around with it.
Hmmm, OK it locked up.
)
Hmmm, OK it locked up. screen freeze, not the funky cpu stuff I saw earlier. What now? I've rebooted back into linux. Saw no prompt about "OC failure, enter bios" message.
Not sure what happened. I
)
Not sure what happened. I restarted again, got the OC failure message, entered Bios and my V CPU was at 1.275.
Anyhooo, I upped the V CPU to 1.3125, change FSB to 200, Multi to 13.5. 2.7 Ghz
FSB freq - 200
PCIE freq - 100
Processor freq mult - 13.5X
cpu-nb link speed - auto
cpu volt - 1.3125
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
OK, appeared to start
)
OK, appeared to start normally. gkrellm started, but when I click Boinc and boinc manager, I got the empty box, but the cursor still moves, tried to open konsole, but displayed nothing. Can't select anything with the mouse.
Upped V cpu to 1.325. FSB
)
Upped V cpu to 1.325.
FSB freq - 200
PCIE freq - 100
Processor freq mult - 13.5X
cpu-nb link speed - auto
cpu volt - 1.325
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
Booted ok after journal
)
Booted ok after journal recovery.
Just clicked Boinc and gkrellm shows 100% all cores.
then started Boinc manager. Still running at this point.
But then last time it got a dozen wus done before it got funky.
OK then be that way. Upped
)
OK then be that way. Upped FSB to 204 or 2.754 Ghz
FSB freq - 204
PCIE freq - 100
Processor freq mult - 13.5X
cpu-nb link speed - auto
cpu volt - 1.325
cpu-nb volt - auto
dram volt - 2.10
Mem freq 533/1066
2T, 5,5,5,15
And, both Boinc and Boincmanager, started normally.
OK, I think I'm about there.
)
OK, I think I'm about there. Boinc and the system stopped responding. CPU3 went to 0%, but the manager was in the way of cpu 0 and 1, cpu 2 was at 100%. rebooting and plan to resize the manager if I can to see all 4 cores.