New To Folding.

check the fahlog.txt file, it will tell you if there was a problem when the client restarted, it may have not liked the saved files and started a new work unit.
 
It started up again....and got to 65% and here's what I got:

[17:02:18] Completed 1625000 out of 2500000 steps (65)
[17:34:06] Gromacs cannot continue further.
[17:34:06] Going to send back what have done.
[17:34:06] logfile size: 28862
[17:34:06] - Writing 29398 bytes of core data to disk...
[17:34:06] ... Done.
[17:34:06]
[17:34:06] Folding@home Core Shutdown: EARLY_UNIT_END
[17:34:09] CoreStatus = 72 (114)
[17:34:09] Sending work to server


[17:34:09] + Attempting to send results
[17:34:13] + Results successfully sent
[17:34:13] Thank you for your contribution to Folding@Home.
[17:34:17] - Preparing to get new work unit...
[17:34:17] + Attempting to get work packet

It started a new one....and it shows in my [H] tag that I have 2 Word Orders done, but I diddn't get any "points" for the second one....any idea what that's about?

 
That probably means your machine is unstable and you should reduce the clock speed. Too bad, but cranking the speed down a bit won't kill you, and it'll give better points and better science in the end.
 
More than 31 hours prime stable on the CPU and overnight memtest on the memory isn't stable enough?

 
Sometimes if the client doesn't exit cleanly you'll lose work. It's a rare occurence, but it does happen. Also, units have set save points as it were, you can modify this setting so that it saves the work it's done more frequently if you so wish. That way you don't lose as much work if you have to reboot. Information on the save interval is here, #13 Checkpoint Interval.

 
If it happens repeatedly it may be a stability issue. There are certain issues that FAH is very sensitive to (one specifically is dual memory controllers for Athlon XPs). Prime95 and memtest might not uncover these problems.

Of course, some WUs do have early ends and it has nothing to do with stability of the box. Just monitor it and see if you can see a pattern to the problem. I found that one of my computers really didn't like the 600 pointers (it worked well with all other WUs) and that when I went single channel with that box everything cleared up.
 
-- for me sometimes I had a good run of early ends.. and I would go through and delete all the files in the folder except the actual console... and just start fresh.. most of the time that helped me out, I am not sure why.. but sometimes it just happens
 
F@H crashed on me last night, but I had full screen visuals up for kicks....so far this test flight is more problematic than stat-fantastic. :( Either way, I'm not just throwing in the towel...I found the check interval which is on a slider, so I moved it one notch to the left, and I have it still running. If worse comes to worse I'll just run 24/7 folding on my Pentium box and leave this one be. :p

 
tsuehpsyde said:
F@H crashed on me last night, but I had full screen visuals up for kicks....
Click to expand...

If you're having problems with the Graphical Client, you might really want to consider moving to the console client and using something like EMIII for the visuals. The graphical client has some known problems with crashing and whatnot.

 
yup.. console client is much more stable....


Keep on Folding!! For the [H]orde!!

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