Quote from: solarion on May 15, 2014, 11:07:34 PM

Quote from: kevin911 on May 15, 2014, 10:40:27 PM

Quote from: solarion on May 15, 2014, 10:34:40 PM

In a perfect world yes. It's not ck's fault though.

Are you seeing squelching messages in the cgminer output?

i didn't say it was ck's fault, im just asking if there's a solution to this problem if anyone else has come across it as well.
I have been told to use a program called cgwatcher to monitor cgminer & if it zombies it will auto restart cgminer. haven't tested that theory yet, but before i do i thought i would ask if there was any other solution.
When you say squelching messages, what do you mean? i think the only message i have seen is something to do with no response from head then it say's zombie, sorry i didn't really pay much attention, was just concerned the sierra had knocked off & i rapidly restarted everything to get it back up and running

It seems that when the miner is pushed too far, specific cores are "squelched". At least that is the message that cgminer reports. I've not seen one in some while now.

Mine is running comfortably at 604 and has been for a few weeks averaging 1.261Th during that time. I've converted to a .conf file, but the original .bat file simply had this preceding pool information:

"cgminer.exe --hfa-hash-clock 604 --hfa-fan 85"

Your temps seem to be under control, so it seems like you just got a bit of a dud.

ok thank you for your help, do you think running it in linux will make a difference? and il try the .conf file setup as well.
I don't know why i expected any different from hashfast, waited this long and got a dud lol
il also test each board to see if i can locate it down to one board that seems to be causing the issue.
again, thanks for the info, at least now i know its something to do with the sierra