Anyone had this happen?

[Bleep]

Flushed all my machines last night and when I went to update tonight I found that one of the Clients had hung up--did not restart after flushing so lost a whole days cracking with one of my machines >wimper--cry--whine< glad to get that off my chest.
Bleep

 

[Russ]

I have that problem on one of my Linux boxes (node 9). Every now and then, the client will simply die right after a flush. I've never been able to figure out why. I thought I had it solved a while back, but it re-materialized.

Russ, NCNE

 

[Slahr Dzhe]

I give my boxes a hug (new age computing trouble shooting technique) at least once a week. I find that this helps them keep thier mind(cpu) on what they are supposed to be doing.

SD

 

[Kilowatt]

Overclocking will do that sometimes under Linux.
It'll screw something up, while everything else seems OK.

 

[Bleep]

This is the first time that this has happened, I am running win 98 but a very old client, it is a GUI client I probably would do a few more blocks a day with a newer client but I like the graphing and logging features of the one I am using. Happened on my celron 533 with a mild overclock. I will try the Hug thing though maybe even a Kiss, should I put my tounge in the floppy drive slot??
Bleep

 

[dennilfloss]

I had the client hang up yesterday for 45 minutes at 96% of a packet with nothing else but Explorer, ZoneAlarm and Norton Antivirus running in the background. When I minimized it and restored the window, it resumed at normal speed.

 

[MWalkden]

No Bleep, but inside there is a 12 volt power lead.....

You'll have to keep an eye on that client, sounds like the OC may be causing it. If it continues to happen I would look at some BIOS changes for a fix. Since the clients use about 2K of memory, I would look there first, increase timing, CAS or a wait state. Good luck!