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

special_exit

G

gnewbury

[H]ard|DCer of the Month - September 2007
Joined
May 4, 2001
Messages
2,544
Been running and had to shut machine down without going in and killing the client by hand, W2K.
Got message:

[19:02:21] Assembly optimizations on if available.
[19:02:21] Entering M.D.
[19:02:51] Checkpoint corrupt.
[19:02:51]
[19:02:51] Folding@home Core Shutdown: SPECIAL_EXIT
[19:02:56] CoreStatus = 65 (101)
[19:02:56] Core internal error: SPECIAL_EXIT
[19:03:01]
And it dumped the workunits after 8 steps and reloaded.
Happened 4 times.
Anybody else have this problem ?
 
About once a month I check log files and I see one of those. Sometimes it's a bad WU, sometimes your just pushing your CPU too hard, or it's running hot. If everything has been stable you can also have a bad download which can cause it too. Back the CPU down if your OC'd and try again, and check those temps :D

Fold on

BillR
 
The only thing special about those kind of exits is that they get you especially pissed off. I haven't seen them in a long time and I seem to remember that they were random...in addition ot BillR's ideas, maybe a bad WU or bad core?
 
It's on a dually PIII 1Ghz and only happened when the core was shut down w/o a Cntrl-C.
Usually if the system is given the shutdown command, and the client is running, an elegant shutdown is accomplished. Since I'm running v4 with the special flag I'm thinking it's the new version of the core.
 
You must log in or register to reply here.
Back
Top