• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ack, lost most of a folded 600pt'r

had a 600 pt'r die around 75% of the way through while I was jacking with my OC, on a positive note, increased my clock speed on the beast a smidge, my memory is holding me back though.

2500+ barton (original core, over 2yrs. old)
running at 202x10.5 now 1.75Vcore mem@83% dual channel
was running 166x12.5 @ 1.70Vcore 1:1 mem dual channel

46Mhz boost.

 
At least you'll get partial points for what part of the WU that you did (as long as you got the "simulation instability encountered, going to send back what's done" message, and not some other worse one).

As an aside, I was having problems (incomplete WUs like this) with F@H on my system a while back but didn't have time to troubleshoot, so I was down to 1.6GHz. This evening I went back to 1.8GHz with a bit more voltage, but I'm not sure how much I'm going to be able to push this Tbred 1700+. Maybe it's about time for an upgrade... 😉
 
I hate that when it is my own fault that I screw up a bunch of points.

Just in case you don't know and for others that might not know:

The log file "FAHlog.txt" is started anew (after a restart) after it gets over 50KB.

It is renamed to "FAHlog-Prev.txt" before a new one is started.
 
My memory/KT400 chipset holds me back too..

I'm running 172 x 12.5 (2150MHz) and that seems to be the limit of my poor ol' system's incompetence.

I can't really think about an A64 upgrade for some time because I blew my $$ on new video cards.... but thank God for the 2500+ Bartons. If I'm going to be stuck with old stuff.... I'm glad this is it.

-Sid

 
$#@&, I just lost a WU to overclocking. I guess bumping the voltage from 1.6V stock to 1.7V wasn't enough; I'll have to try a little more. 🙁

I really want a new processor, but I really want even more to do a major upgrade (hopefully including dual dual-core Opterons), so spending on frivolous stuff right now isn't an option if I want to attain that goal. 😱
 
Are we going to have to sign you guys up for our next meeting of:

It Just Won't Go Any Faster Anonymous?

😛
 
Couple of days ago my OCed to the edge box started making beeping songs.

There wasn't much dust but blew it out and left the side off, no more beeps.

It was crunching a BigWU AND a QMD ExtraBigWU (which uses like 212,400K and a Peak Mem Usage of 327,508K)
 
Remember that the limiting factor could be the motherboard.

AMD 1700+ (stock 1.4 ghz).

Abit Nforce2 performance mobo ( whatever it was called NF7-s?) = 2.1 ghz

Asus A7n8x mobo = 1.6 ghz..

sigh. why did that abit have to die.

Both were rock solid stable [same processor just diff mobo. It's funny how one mobo can make a 500 mhz difference in the overclock. and yes, i've tried everything on the asus 😛

Also I love my Abit Ic7-max 3 but i jumped the gun and bought it when if first came out with the 'not so stable' voltages..so while its a 200 dollar board at the time it's the first-gen and as such i can't get it over 3.22 ghz for extended periods of time (as in weeks). Had it at 3.45 ghz for a while but I didn't like it crashing once or twice a week...then again it could have just been that bad ram stick 😉
 
no, it's actually my memory. If I relax the settings it runs fine,

shuttle kn31-n (rock solid performer)
2x512MB Kingston valueram pc2700 spd 7-2-2-2.5, fastest it will run is 168Mhz at spd, unless underclocking to 133 it won't run at anything below spd timings.

my system got buggy anyway, I had to go back to 166x12.5.
 
Back
Top