![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
-
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.
Early Ends
- Thread starter MTXR
- Start date
Krayzie135
Gawd
- Joined
- Jul 27, 2005
- Messages
- 641
you usually get an "early end" if your comp isnt stable, happened to me before when i was overclocking and didnt check for complete stability.
Kvothe
[H]ard|DCer of the Month - October 2006
- Joined
- Sep 27, 2004
- Messages
- 8,712
Early ends are most commonly the result of PC instability, whether it be too high of an overclock, bad memory, even just overheating. Normally when getting early ends, we suggest you step back, make sure your box is Prime95 and Memtest stable, then start recrunching.
Now if you're running with the -advmethods flag, you will sometimes recieve WU's from Stanford that aren't as stable and those will bomb out with an early end regardless of the above variables. Either way we recommend you make sure your box is stable then fire them back up.
As for the [H]bowl, getting your client running 24-7 is really going to be the only way to compete. We've based the calculations and scoring on a total week of folding, and you just can't get as much done if it's not up and running.
Now if you're running with the -advmethods flag, you will sometimes recieve WU's from Stanford that aren't as stable and those will bomb out with an early end regardless of the above variables. Either way we recommend you make sure your box is stable then fire them back up.
As for the [H]bowl, getting your client running 24-7 is really going to be the only way to compete. We've based the calculations and scoring on a total week of folding, and you just can't get as much done if it's not up and running.
Also another question.
Lets say you overclock, and are at X speed when you are done with a game. So lets say you are on a break waiting for the next game, and overclock to Z speed. Can you use Z speed for the next game? Would you be disquailified, or lose points?
Lets say you overclock, and are at X speed when you are done with a game. So lets say you are on a break waiting for the next game, and overclock to Z speed. Can you use Z speed for the next game? Would you be disquailified, or lose points?
Kvothe
[H]ard|DCer of the Month - October 2006
- Joined
- Sep 27, 2004
- Messages
- 8,712
Nope, a restart doesn't count as an early end, an early end is only counted when the WU you have encounters instability and crashes. If you restart properly and the client closes cleanly, any WU you're working on should pick right back up where it left off.
As for overclocking, you can run it at whatever speed you'd like for however long as you'd like. There won't be a gap in the games though, so the opportunity for OC changes is going to be at the expense of folding time. Thats why we're alloting for a 1 week break in period, so that people can get OC's figured out and setup.
If you want to sqeak out more speed during the contest you're more than welcome to, as that may be what you need to do to pull out a win.
As for overclocking, you can run it at whatever speed you'd like for however long as you'd like. There won't be a gap in the games though, so the opportunity for OC changes is going to be at the expense of folding time. Thats why we're alloting for a 1 week break in period, so that people can get OC's figured out and setup.
If you want to sqeak out more speed during the contest you're more than welcome to, as that may be what you need to do to pull out a win.
OK, 'splain me this Lucy 
... I've been running FAH on 2 console threads as services for 3 months on my main WinXP P4 box with 1GB ram (minor overclock, always stable). One thread runs big packets but no advmethods, the other thread runs big packets + advmethods and always pulls successful QMD's using the 5.04 client for the last month. All of a sudden at 4am (i.e. it's cooler) it starts cranking early end units (at 0% finished), reloads, repeats... I've got over 135 early end units with 0 points (in about 16 hours) before I discover it & shut it down. The other thread continues rock solid producing 600 pointers.
Any ideas why the QMD thread is shutting down ?
... I've been running FAH on 2 console threads as services for 3 months on my main WinXP P4 box with 1GB ram (minor overclock, always stable). One thread runs big packets but no advmethods, the other thread runs big packets + advmethods and always pulls successful QMD's using the 5.04 client for the last month. All of a sudden at 4am (i.e. it's cooler) it starts cranking early end units (at 0% finished), reloads, repeats... I've got over 135 early end units with 0 points (in about 16 hours) before I discover it & shut it down. The other thread continues rock solid producing 600 pointers.Any ideas why the QMD thread is shutting down ?
RPhArrow said:OK, 'splain me this Lucy
Any ideas why the QMD thread is shutting down ?
You could be running into ram trouble maybe....600 pointer eats a lot of ram and a QMD eats even more ram than that....i'm just guessing though.
Yeah -- RAM overload was my first guess too... So I'm trying to figure out how to remove all traces of only one thread.. Easy to remove the one folder , but how do I fix registry to remove service on one thread only (without messing up the good 600 pointer thread) ?Mayhem33 said:You could be running into ram trouble maybe....600 pointer eats a lot of ram and a QMD eats even more ram than that....i'm just guessing though.
If I can get the one bad thread cleanly removed, I can start it anew with different configuration for ram (and 5.02 client if necessary).
BAH - I don't have this problem on Foldix ! But none of them are pulling down QMD's either
Kvothe
[H]ard|DCer of the Month - October 2006
- Joined
- Sep 27, 2004
- Messages
- 8,712
If you're referring to removing one of the services, those can be found at HKLM\SYSTEM\ControlSet001\Services\FAH@C:+.... You should have two of them, one for the QMD session, and one for the other, you'll just need to remove one of the two keys and reboot and thats the extent of reg cleanup you'll need.
Ahh -- Thanks p[H]antom, I was looking in all the wrong places (what does the key at HKLM\Software\Pandegroup\Folding@Home\5.03 do ?)p[H]ant0m said:If you're referring to removing one of the services, those can be found at HKLM\SYSTEM\ControlSet001\Services\FAH@C:+.... You should have two of them, one for the QMD session, and one for the other, you'll just need to remove one of the two keys and reboot and thats the extent of reg cleanup you'll need.
Kvothe
[H]ard|DCer of the Month - October 2006
- Joined
- Sep 27, 2004
- Messages
- 8,712
If you see a huge number of WU's and very few points on an update, something like say 20 WU and 20 points, thats a pretty good sign that there's problems. If you check the FAHlog.txt and FAHlog-prev.txt in your F@H directory, you can search through them for early end. If you see that, then you absolutely have problems, and should back off and stress test, etc.