[Milkman]

what's happening is the client downloads a wu, almost all have been gromacs 200-500 frame ones and it will engage the core for a few mins then sends results and gets a new work packet, each one is different and I don't really seem to be finishing any frames before it send them again, what's going on with this?

-mamer

[Tismedt]

There have been a couple threads about this lately
http://forum.oc-forums.com/vb/showth...hreadid=198180
http://forum.oc-forums.com/vb/showth...annot+continue

Check those out. Is this your situation?

[Milkman]

Well I did find something interesting, I was running the text console and added Fah as a service, I recently changed to the gui version and just checked the task manager and found core 65 still running as a service, once I cleared that the core stays engaged.

[Milkman]

Well after getting myself all freaked out I finally figured it out, what I found was that the overclock wasn't completly stable, I backed down the overclock and reinstalled the console version with the -advmethods -forceasm switches and all three machines are chewing on Gromacs as I type this, lesson learned about stability!!

[Lonely Raven]

I thought those were planned ends to Work Units that were, well
just at the end?

I'm sure the overclock could have had something to do with it,
but I posted about this a week ago after seeing a few end
early on a machine that had been solid and unchanged for 2
months now...

I still hope we got points for them.