Weird,  it happened again earlier today where cgminer would run really slowly and produce lost share messages,  and not be responsive to "q". It was not on tagcoin this time,  it was on a different one.  I was able to eliminate processor and system memory overloads as culprits,  and my network connection was ok.

So I thought that perhaps that  my thread concurrency was too high, causing gpu memory overload,  so I dropped it from 24K to the next-lowest appropriate number for my card,  so we will see how that goes...

Also,  any insight on how many days it takes to get credit for TAG coins?

It would be good for each individual user to be able to see how many immature coins are waiting to be credited to them once they fall off of the ledger.  


Edit:  I was typing this with some new info as you responded....I'm actually using Windows 8, I don't really know  how to use linux.  I have been keeping the monitor shut off except when I check cgminer,  I'm not sure if the monitor still uses resources while it is off,  or if it has to be totally unplugged to free them up,  but I do keep it off 99% of the time.  I use a netbook to watch what is going on through your website in regards to my account. Then if I notice a problem,  I go down and actually check the rig through its own monitor.

I:20 seems to lead to a lot more stales,  and I:19 a few more stales, as compared to I:18, while the hashrate will only drop a couple hundred total across six cards with the lower intensity.  Temps go down by 3 to 5 degrees as well, so I kind of like running at the lower intensity.  

Nearmiss is currently fighting off a case of the "sickies" (his son got him sick!) so were a little backed up at the moment, but when we get caught up with it all, you got it.

I hope that my most recent adjustment of lowering my thread concurrency,  on top of lowering my "I' settings, will allow my rig to run 24/7 without issue on hashcows.  

Interestingly enough,  I did see a very slight bump in hash rate after dropping my thread concurrency.

Thinking back, when I was running at I:20, that not only increased stales and temps,  but IIRC it caused a full lockup after a few hours, at some point along the way.

My cards will undervolt,  and I have them set to run at .900 through cgminer.  Cgminer does not report the voltages accurately,  but I did some internet research and found a post somewhere out there stating that despite the reporting inaccuracy,  it will actually adjust the voltages.  I intend to buy a kill-a-watt for testing so I can go through each card and adjust and see for myself in case that info is not correct for my version,  since I upgraded to the newest that will run scrypt (3.7.2 for windows).

I have played around with the engine and memory clocks (using a .7 to 1 ratio) until I found the "best" hash-rates for my cards,  although I may go through them again and see if I can fine-tune that some more, since I can't remember what intensity or thread concurrency I was at when I set them last,  and also I was making changes in 50 Hz whacks.

My temps are pretty good,  right now I'm seeing 68 to 70,  and even when I had the "I" cranked up,  I was seeing 75 to 77.  All of my cards are on risers in a milk crate and each has dual fans built-in,  and I also have three more big 5" a.c. computer style fans controlled by a rheostat blowing down into the cards.

Noob Question to the pool runners about immatures...do we get paid or not get paid on those until they mature?  If we wait until they mature then I would definitely want to see a record of all immatures,  beyond the 30 round ledger.  I always see those tag coins fall off of the list and have yet to see one mature before doing so. Seeing a full record of coins like that would be nice, since as is stands,  we have no simple way of knowing what happens to them once they disappear off of that list. I guess that I could collect them and exchange them myself,  but I am trying to keep things simple,  at least for now.


EDIT: Well the problem occurred again.  I brought up the task manager and then tried to open a browser and locked up the rig so I took a couple of pics with my camera.  Not sure if this will help out,  but maybe someone can tell me what is going on somehow.





I noticed that the CPU was actually pegged at 99% while cgminer was still producing messages,  which I did not notice before.   The last message before cgminer stopped producing messages was "stratum connection to pool 0 interrupted",  although I still had an internet connection to my netbook, and I had not locked up the computer yet.
It's possible that the wired internet connection that is connected to the miner was messed up somehow,  so I recycled my router before rebooting and connecting to the pool.



Hmm,  this is frustrating me.  If anyone has any insight on what could be going on,  that would be great.

EDIT:  Figured that I would post up my most recent config:
(I know gpudyninterval does not do anything for me,  I just haven't deleted it )

{
"pools" : [
   {
      "url" : "--scrypt stratum+tcp://stratum01.hashco.ws:8888",
      "user" : "xxx",
      "pass" : "xxx"
   }
]
,
"intensity" : "18,18,18,18,18,18",
"worksize" : "256",
"kernel" : "scrypt",
"lookup-gap" : "2",
"thread-concurrency" : "22400",
"shaders" : "0",
"gpu-engine" : "1050",
"gpu-fan" : "0-85",
"gpu-memclock" : "1500",
"gpu-memdiff" : "0",
"gpu-powertune" : "20",
"gpu-vddc" : ".900,.900,.900,.900,.900,.900",
"temp-cutoff" : "95",
"temp-overheat" : "85",
"temp-target" : "70",
"api-mcast-port" : "4028",
"api-port" : "4028",
"auto-fan" : true,
"gpu-dyninterval" : "10",
"gpu-platform" : "1",
"gpu-threads" : "1",
"scrypt" : true,
"hotplug" : "5",
"log" : "5",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "2",
"expiry" : "2",
"temp-hysteresis" : "2",
"shares" : "0",
"kernel-path" : "/usr/local/bin"
}

That may be true,  but in my case I think that this is an issue with cgminer disliking connectivity issues, possibly due to the distance between me and the server.  You can see that I have issues with GF and RF errors when I'm hooked up to Hashcows.  I will note that I did not see these GF and RF errors,  nor did I have these connectivity issues when hooked up to Middlecoin.  

I did some searching based on the "stratum connection to pool 0 interrupted" message and found this thread:

https://bt.irlbtc.com/view/188533.0

and decided that I should start running cgwatcher and set it to restart the miner if the accepted shares fall flat after a couple of minutes.  

I had to slightly modify my config as compared to what I posted above as cgwatcher did not like the
"--scrypt" that I had typed in the URL.  

I also set cgwatcher to run automatically, and for it to start the miner automatically on powerup, so I took the cgminer batch file that I had in my startup folder out of there.

So we will see if the cgwatcher helps now.

I guess that I lost three or four hours of mining dicking around with this tonight,  so today will probably be somewhat of a wash for my comparison,  but I do have two full days recorded so far,  after washing the first day out due to starting a bit late and not having any immatures built up.   I want to go for a week before posting any results.  As long I can get this thing running smoothly here on hashcows,  and as long as the guy who I am watching over there on middlecoin,  or someone with identical power to him (and me) keeps running over there,  I'll be able to continue to run my comparison with some degree of accuracy,  and I will report back with some info.

 I don't think that it is causing my issue though,  mainly because I'm not entirely convinced that cgminer is effectively undervolting my cards despite what the one guy that I found who posted about it claims to have seen.  I'm going to pick up a kill-a-watt and do some experimenting with changing the voltages through cgminer.  If it does not seem to make a difference,  I'll try running trixx again,  although I tried trixx when I first started running my rig and seemed to be having trouble with it maintaining my profile with lower voltages.

My issue seems to have to do with connectivity and cgminer getting stuck when there is a problem with that,  just based on what I have seen so far. 

forcefedvr6, I'd bet your issues have to do with a connection reset by hashco.ws when it switches coins. This interferes with cgminer, for whatever reason

The way to work around this, is to load balance to other pool, with a quota. For example:

{
"pools" :
[
   {
      "quota" : "1;stratum+tcp://pool1.us.multipool.us:3342",
      "user" : "Wipeout2097.1",
      "pass" : "x"
   },
   {
      "quota" : "20;stratum+tcp://stratum01.hashco.ws:8888",
      "user" : "Wipeout2097.1",
      "pass" : "x"
   }
]


Above, I'm giving ~96% hash rate to the cows and the rest to some coin. The 1 and 20 after "quota" are arbitrary, but the secondary pool must still have "enough" quota. When hashco.ws disconnects briefly, cgminer handles it gracefully and requests work from the other pool. When it detects the connection becoming alive, it resumes asking most of the work from hashco.ws

The setup above also protects your video cards and psu from stop/start cycles

Then, you should downgrade cgminer. Newer versions resume work from interrupted pools after 5 minutes, while for example cgminer 3.4.3 does so almost immediately

Anything past 3.4.3 you run into the issue of the cgminer throwing a 5 minute cooldown on disconnected pools..  This doesn't affect me because I have a load balance specified.. One pool goes down, the other picks up the slack.  Failover means when one pool crashes it swaps to the other until your original pool comes back up.  All cgminer versions have these options.(there are actually 5)  I did notice your thread concurency was higher than mine, but the fact you're still hashing means you're not above what the cards can handle.. If you're not running a failover pool I highly encourage you to do so..  Downtime is lost money... Even if you're mining something a bit less desireable.

I don't use the config files.. I prefer the hands on Dos 5.0 batch files, but whatever you can do in the config you can do in the batch file so no worries there.

Thank you for the update 

Yes, I do... You are running Winblowz.  Therefore, you are stuck with an max intensity of 13 and not 14-20.

Try BAMT and see your results.

As an example, I get speeds from 640-730kh/sec on my 7950 and one 7970. 

BTW: Go Sapphire all the way.  Solid as a rock at 0.962v and getting 730kh/sec out of it.