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

0 points????

B

[BRO]Alaskan

Gawd
Joined
May 14, 2005
Messages
954
on 1-27 I did over 600wu and got 0 points. My points lately have gone in the toilet. I went from 700ppd to 260ppd. Any idea what could cause this. I rebooted all of the computers and no change
 
EARLY_END_UNITS. Check your FAHLOG.txt in the folding folder. If you see anything that looks like EARLY_END_UNIT, you've got problems, usually due to unstabel hardware/overclocking.
 
Check the each box/client has its own unique id.
Thats normally the reason for folding a full protien for zero points.
Have you cloned/copied FAH between boxen.

From the top of the FAHlog.txt file.

[17:48:27] - User name: Tigerbiten (Team 33) <- Check right name/team.
[17:48:27] - User ID: 205AFBF023F2CB0E <- Different one for each box.
[17:48:27] - Machine ID: 1 <- Different is more than 1 client on a box.

Have you given it enough time to work through the system.
It can take over 3 hours if a server is down.

Ps. The badge goes just above the sig. not in it.

Luck......... :D
 
If you manually edited the client.cfg files in something like notepad or wordpad, there's a good chance they got messed up and the client reset them to the default (Anonymous, team 0). Like Tigerbiten said, check your log files.

 
poddo said:
EARLY_END_UNITS. Check your FAHLOG.txt in the folding folder. If you see anything that looks like EARLY_END_UNIT, you've got problems, usually due to unstabel hardware/overclocking.
Click to expand...

poddo hit the nail on the head, as after looking at your stats page you've turned in an obscene number of WU's with next to nothing to show for it. Normal course of action is to stop the F@H client, and check the logs for the early ends, then apply a healthy dose of Memtest86, and Prime95 to remove any stability questions. If the rig in question is otherwise running properly, but F@H is screaming like this, its very probably an obscure memory error or a bunk OC. Good Luck getting it fixed!


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