• 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.

F@H question

Markfw

Markfw

Moderator Emeritus, Elite Member
I have 3 Barton 2500's @ 192 mhz (almost 3200 speeds, they all seem to like that but won;t run 200)

2 of them are running the windows regular client, and run fine.

The third is one of my dedicated F@H machines. At 200 it will pass everything but won;t run F@H console with the flags all set, it locks up (forcesse and advmethods and one other). The I turn off all the flags, and it works ! It will work at stock speed with the flags, but overclocked only without the flags (shuttle an35 ultra nforce2 mobo). Can anybody else confirm this ? And wouldn;t it run better OC'ed to 192 or 200 than with the flags on ?

I want to get the most out of my dedicated servers.
 
Even if you run with the flags off, you're still likely to encounter instability when overclocked beyond a stable point. Every so often the core will exit due to abnormal termination (or something like that, it will say "simulation instability encountered"). It's better to run a lower overclock with flags, and make sure that it's pretty stable (that means no simulation instability within a week or so), than a higher overclock that appears to be "stable" at the moment without flags.

Note, however, that it is possible to get a simulation instability every few months due to errors in the WU itself, rather than one's own system. At least that's what I was told some time ago - somebody correct me if I'm wrong. 😱 😉
 
Yes, I ran memtest for hours, and everything works perfectly, but OC'ed with flags on, it locks up in 1-2 minutes EVERY TIME, without them its been running at 193 FSB for 30 minutes !
 
Originally posted by: Hyperfocal
Check for heat issues as well. I had a lot of lockups on my Linux box until I installed a better HSF.
Click to expand...

It has a Thermaltake 84 (I think), anyway its running 44c and perfectly stable with NO command line additions for 1 1/2 hours. Never would make it over 2 minutes at anything but stock with the parameters added.

Any thoughts ??
 
Originally posted by: Markfw900
Yes, I ran memtest for hours, and everything works perfectly, but OC'ed with flags on, it locks up in 1-2 minutes EVERY TIME, without them its been running at 193 FSB for 30 minutes !
Click to expand...

-forceSSE
On machines with an AMD processor, Core_78 gives priority to 3DNow over SSE -- this overrides that.

SSE must be more efficient and work the processor harder than 3DNow! causing temps to rise.
Check how long it takes to finish a few steps without the flag.
Then lower the OC, add the flag and time a few steps. Compare results.

The advmethods flag only affects which WUs you get. It does nothing to the core.
-advmethods
Request to be assigned work units from new projects, before they are broadly released to the rest of Folding@home. As among the first to try out new advanced simulations, you may wish to post any observations (positive or negative), questions, or issues at the user Forum.

So your problem may be with only certain WUs

Thanks
 
When I start F@H, I see this as part of the beginning text:


Warning:
By using the -forceSSE flag, you are overriding program
safeguards that monitor the stability of SSE
instructions on your system. If you did not intend
to do this, please restart the program without
-forceSSE. If work units are not completing fully,
then please discontinue use of the flag.

I"m thinking they are trying to tell you that wierdness may occur using this flag!

I don't remember where I read it, but I think I have seen it stated that overclocked systems are much more likely to have difficulties like this.

Remember that because one (or several) apps. will run, it doesn't mean you are stable at that O/C. Isn't the definition of unstable that some (or all) apps. won't run?

I suspect that no matter how attractive it is to reach a certain benchmark, you may find that if apps aren't running properly, your stability is in question.

back it down a bit and you will probably not see the same issue.

As a side note, DC projects make great stability testers because they frequently aren't written with as much error recovery capability as more mainstream applications.

-Sid
 
I ran a AN35 with Barton 2500 OCd to 12x200 for a year or so with no issues using the force SSE and the advmethods flags. not sure what you problem might be but you are better off dropping the OC till you stop the lockups.

is your cpu multi unlocked ? is your ram PC3200 ?

try swaping the ram from another rig and see if it still locks up.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top