• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

folding beta 3.25

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Ben721

Official X-Hour Man
Joined
Feb 3, 2002
I heard there are still some issues with overclocked Tbred B's, but I've yet to have a problem, but then again I only have a 400mhz overclock.
 

grv

Member
Joined
Aug 13, 2002
Location
Guilderland, NY
emericanchaos said:
yeah the new beta fixes the SSE issue with instability in AMD's.

It's my understanding that the 3.25 beta makes it possible to keep sse cooking all the time, but does not fix the stability issue, per se.

I have two tbreds (2400+) on which I can't use sse right now, even with the beta client, because I will always eventually lock up. Different MB's and everything.

My 2100+ pally has sse on and it just keeps chugging along. Actually, with sse it is faster on gromacs than the 2400+ rigs.:eek:

Does anyone know if the new core will address any of the stabilty issues? I'm looking at a new box, and as of now, it makes more sense for me to just spring for a pally instead of a tbred. Cheaper, and faster until this gets fixed. Also - any 2100+ I get would be a pally, right?
 

muddocktor

Retired
Joined
Nov 1, 2001
Location
New Iberia, LA
Actually, it's the newest version of the FahCore_78.exe that addresses the instability issues with using the SSE extentions with some XP and MP procs. It preferentially starts folding by using the 3DNow! extentions instead of SSE extentions and will fold around 15-20% slower while using 3DNow!. Only a small percentage of AMD procs seem to be affected by this so if you have an XP that folds reliably while using the SSE extentions, you can force the core to use SSE instead of 3DNow!. The 3.25 beta client was brought out so that forcing the use of SSE would stay persistant while folding multiple WU's, which the 3.24 version wouldn't do. The 3.24 client would only do the first WU after starting it with SSE being forced and would revert to using 3DNow! on subsequent WU's, so Stanford came out with the beta 3.25 client to get around this problem. The way that you switch the use of extentions(for now at least) is to use the -forceasm flag in your startup shortcut on the beta 3.25 client.

Personally, I have run into this problem with 1 proc of my farm not liking the way that Stanford is using the SSE extentions and will hard lock, even at stock speeds and relaxed mem timings. It is the only XP that I'm having any particular problems with using the SSE extentions, so I keep it using 3DNow! and I upped the overclock to near max for that proc to help make up the folding speed difference.

grv, the proc I am having problems with is an oem XP2400 and my Tbred 2100 doesn't seem to have any particular problems with SSE and neither do the 3 Tbred A XP1700 or the Tbred B XP1700 in my farm.