• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Error

B

bradyapba

Gawd
Joined
Nov 30, 2004
Messages
923
Now having another problem... got an error about 30% through a WU. THis has never happened before. This system has been rock solid stable for weeks. I am getting temps of about 55C on the CPU, but its been that hot for awhile, and I didn't think it was too high.. but maybe it is on a venice core 3000?

I am OC'd to 2500, but i have had it higher with no problems.

Sohuld I be concerned? Could it be a one time thing?

The next WU it downloaded, was running REAL slow.. amber core, that usually gets about 8 min a frame... its now running at 17....

Not sure what to do, except maybe turn down the OC....

I am going to WC.. parts starting arriving today... that may solve the issue.

thanks for any possible opinons!

Chris


Hres the Error


22:22:18] Completed 1500000 out of 5000000 steps (30)
[22:35:39] + Working...
[22:49:46] Quit 101 - Fatal error:
[22:49:46] Step 1544994, time 3089.99 (ps) LINCS WARNING
[22:49:46] relative constraint deviation after LINCS:
[22:49:46] max 0.000769 (between atoms 972 and 974) rms 0.000040
[22:49:46]
[22:49:46] Simulation instability has been encountered. The run has entered a
[22:49:46] state from which no further progress can be made.
[22:49:46] This may be the correct result of the simulation, however if you
[22:49:46] often see other project units terminating early like this
[22:49:46] too, you may wish to check the stability of your computer (issues
[22:49:46] such as high temperature, overclocking, etc.).
[22:49:46] Going to send back what have done.
 
K, step 1, are you running the -advmethods switch? If so, buggy proteins come with the territory, but if its doing it on alot of them, then there's a larger problem.

First, back off the OC and stress test your rig, Prime95, Memtest86, anything that stresses it and will detect errors. If these aren't stable, there there's not a chance of F@H being stable. Hopefully between the two, you'll be able to narrow down the problem component.

If it's prefectly stable at stock, and once you get your W/C setup, if you want to OC, start gradually and go a few MHz at a time so that you can find the sweet spot where things are stable and won't crash.

 
Its has been rock solid at 2500 mhz. No problems ram prime, and mem test for 24 no errors. I have been folding for weeks on this PC with no problems.

It looks like i am running that -advmethods switch. In EMIII under extra launch commands - its listed.... so i assume im using it... im gonna guess thats the problem?

What does it do, and how do you stop using it?

Thanks,

Chris
 
Well you're only running -advmethods if that switch is checked. Are you running graphical or console?

If you're running the console service mode, check your Services under Administrative tools and see if Path to executeable line constains -advmethods.

The -advmethods switch essentially alerts Stanford that you're willing to run new beta proteins. There's two things about doing this though, these proteins are potentially buggy and can eat tons of memory and such, but on the flip side, they offer huge point bonuses.

If you're running the service mode, I recommend using this tool as it makes editing the parameters of your service a snap.

Before you do that though, I'd recommend backing off the OC and re-stability testing, just in case. F@H tends to be very sensitive to any sort of computational error that Prime or Memtest may not even find.

 
You must log in or register to reply here.
Back
Top