Fuck CGWatcher.
...Do you have a better solution for that stubborn card that decides to get SICK or DEAD randomly?...
Developing a stable config file will solve that type of problem.
Ummmm, yeah that's all fine and good... but what is your solution for this scenario?
5850 works at 350kh/s for about 12-24 hours and then randomly goes SICK immediatley losing 350kh/s on your hashrate...
You can "stabilize" it by reducing the intensity to 14 and getting 270kh/s for 24hrs with no problems or you can use CGWatcher to restart the miner and get the GPU running at 350kh/s again within a minute. Sorry but I would rather do the latter and "stabilize" at 80kh/s more.
Not a good explanation. Sorry, bud, but you are another person who is "fuck this" or "fuck that" without actually offering a valid explanation.
Miners are fucking stupid and this thread is proof.
Well now we are just thread-jacking and getting way off-topic, but that guys post is validation enough as why not to run CGWatcher. CGWatcher is a piece of shit. I'm no Einstein, but I'm not fucking stupid either. I agree that cutting the balls off by selecting a lower intensity is fucking stupid. It's also fucking stupid to wring the shit out of your cards until they end up "sick" and "dead", and to rely on a re-start to straighten everything out until it happens again. Throwing shares away to re-boot because I overheated my cards or constantly running at a sub-par speed are not my ideas of a stable and optimized system. All but one of my single-core 7950s are set to I-19 and average ~630 kh/s each, and throttle back and forth between ~620 and ~640. I have one set to I-18 so I can periodically use my monitor while mining without locking up the rig. That one throttles between ~600 and 620 Khs. Temps almost never go above 74 degrees and fan speeds almost never go above 3400 rpm on any of my cards. Most of the time they run lower in terms of temp and fan speed. I could squeeze a liiiiittle more hash out of them if I wanted periodic lock-ups, but what's the point since I stopped having sick/dead cards (your temps are too high, you are killing your fans/cards) or hard locks (indicates gpu engine and/or mem clocks and/or T.C. settings are too high), once I tuned my config. Why do I need CGWatcher again? Why do I need a program that would consistently NOT work properly and consistently NOT activate CGMiner if I decided to reboot or the power went out? A simple BIOS setting and a cgminer batch file in the start-up menu addresses those conditions. And forget about setting CGWatcher up for quota work across multiple pools, those settings were good for what, one go-around, iirc. It didn't take me too long to figure out that CGWatcher was basically an all-around pain-in-the-ass, barely-serviceable band-aid for a poorly tuned config file. CGMiner gives you all of the tools that you need to maximize your hash rate as well as to avoid sick/dead cards/hard locks at the same time. It took me a little longer to figure out which version of CGMiner has a dead-balls accurate quota function, but yeah, it does that too.
odd 
