I'm currently running cgwatcher 1.3.0.2 on cgminer 3.3.4. here's some of the output
Mining duration.................. 24 hrs, 12 min, 31 sec
Current total hashrate........... 62.55264 Gh/s
Current average hashrate......... 62.53938 Gh/s
Accepted shares.................. 38984
Rejected shares.................. 184
Stale shares..................... 0
Discarded work................... 6283
Local work....................... 1663309
Getworks......................... 3224
Getwork failures................. 0
Hardware Errors.................. 9160
I've tried everything I can think of to reduce the hardware errors 19% seems a little high. I've direct connect to modem, reboot modem, direct connect to pc via usb (as opposed to using an active usb extension), changed pools, switched to bfgminer (although i'm not certain I'm comparing apples to apples with their errors), reinstalled zadig and reinstalled the drivers for the single...and that's about all I could think to do. I don't know what's acceptable or really what the hardware errors even mean. Is this something I should take to BFL? I don't see anything goofy in the miner.log
[8/28/2013 7:59:12 AM] CGMiner (3196): Process found; started at 8/28/2013 7:52:56 AM using "Default" profile on port 4028.
[8/28/2013 7:59:12 AM] CGMiner (3196): Pool 0 ( pool ) status is ALIVE
[8/28/2013 7:59:12 AM] CGMiner (3196): Current pool is Pool 0 (pool )
[8/28/2013 7:59:12 AM] CGMiner (3196): Network difficulty is now 65,750,060.
[8/28/2013 7:59:17 AM] CGMiner (3196): GPU0 (ATI Radeon HD 4800 Series) status is UNKNOWN
[8/28/2013 7:59:17 AM] CGMiner (3196): BAS0 status is ALIVE
I was thinking maybe it had something to do with using the NoGPU exe of cgminer but even with the regular binary I still can't get below 15% error rate. Any suggestions? And, milone, if you have any ideas you might consider putting a threshold in to the watcher. If your error rate is above X (commonly acceptable percentage) suggest some changes or diagnostics to get that number down to an acceptable level. If that can even be done. I just know when I see that big red number of hardware errors I want to click on it and find out what the problem is.
Any advice would be appreciated. It seems like this number should concern me but maybe I just don't quite understand what I'm seeing.