OCUK Foldign@home

BOTH MY WORK UNITS HAVE STOPPED THERE BOTH ORANGE IN FAHMON AND IVE STOPPED AND STARTED THE PROCESSES AND RELOADED THE CLIENTS IN FAHMON. ANY IDEAS
 
Are you sure they've stopped?

FahMon shows orange sometimes just after a checkpoint or restart.

Have a look in task manager, if both cores are using 50% each, you're fine. If not, please post the logs for both clients :)

Stan :)
 
StevenG said:
BOTH MY WORK UNITS HAVE STOPPED THERE BOTH ORANGE IN FAHMON AND IVE STOPPED AND STARTED THE PROCESSES AND RELOADED THE CLIENTS IN FAHMON. ANY IDEAS
Click to expand...
all mine go a bit like that after midnight GMT for some reason - I take it as a sign I should have gone to bed :p

Another shortcoming of FahMon's guesswork I'm afraid - like Stan said if it's using the CPU still then there's nothing to worry about.
 
THERE FINE NOW :D another 622 points have been added to my name :D and soon another 622 points will. the next one i got was 266
 
fahsig.php
nevermind its updated since lol
 
Last edited:
I dumped a 574 pointer this morning and it hasn't been credited yet - even though several "lesser" Wus completed since have been.

It happens sometimes, you will get your points - eventually :p (as will I).

Stan :)
 
nope i wont.

[07:29:28] Quit 101 - Fatal error: NaN detected: (ener[13])
[07:29:28]
[07:29:28] Simulation instability has been encountered. The run has entered a
[07:29:28] state from which no further progress can be made.
[07:29:28] This may be the correct result of the simulation, however if you
[07:29:28] often see other project units terminating early like this
[07:29:28] too, you may wish to check the stability of your computer (issues
[07:29:28] such as high temperature, overclocking, etc.).
[07:29:28] Going to send back what have done.
[07:29:28] logfile size: 42057
[07:29:28] - Writing 42620 bytes of core data to disk...
[07:29:28] ... Done.
[07:29:28]
[07:29:28] Folding@home Core Shutdown: EARLY_UNIT_END
[07:29:31] CoreStatus = 72 (114)
[07:29:31] Sending work to server

EDIT: POINTS APPEAR ON THIS SITE http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&username=StevenG[OCUK] JUST NOT IN SIG
 
Last edited:
That's an EUE, an Early Unit End. In this case I'd guess that it means that the WU you got was flawed and could only be crunched so far. If this is *** case it's not your fault.
The other possibility is that your machine errored and it damaged *** WU so that it could not finish properly. If this is the case it is your machine's fault and it suggests that there is instability, especially in overclocking.

Keep a watchful eye on the machine for a week or so. If you have no more EUEs you're fine. :)
 
You must log in or register to reply here.
Back
Top Bottom