I'm not new to mining, I'd hope by now I know how to set up, tune and troubleshoot a stable mining rig. You still have not put forward a valid reason as to how you believe a rig that can pool mine a coin indefinitely suddenly develops these suspected hardware instabilities from solo-mining the exact same coin.
Anyway, after trawling way back in this thread here's another chap with what appears to be a very similar issue:
wow, I just solo mined a diff 350 block!
[2013-08-07 13:05:59] Accepted 000000c3 Diff 21.9M/309191 BLOCK! GPU 1
awesomesauce
Nice what's your hash rate that you are solo mining?
8Mh/s
--
Dr Kimoto, here's what I'm getting from one of my miners after a few hours mining against the qt client:
[2013-08-07 13:20:01] Found block for pool 0!
[2013-08-07 13:20:01] Accepted 00002c07 Diff 381K/309191 BLOCK! GPU 0
[2013-08-07 13:21:06] New block detected on network
[2013-08-07 13:25:22] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:26:27] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:27:32] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:28:37] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:29:42] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:30:47] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:31:52] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:32:57] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:34:02] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:34:07] New block detected on network
[2013-08-07 13:35:07] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:35:12] New block detected on network
[2013-08-07 13:36:12] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:37:17] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:38:22] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:39:27] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:40:32] Pool 0 http://192.168.1.10:22222 not responding!
[2013-08-07 13:40:37] Network diff set to 294K
[2013-08-07 13:40:37] New block detected on network
You can see it's intermittent. Restarting the miner has no effect. Only restarting the qt client. megacoind has the same issue iirc.
I'm running four cgminer instances plus one perl script polling stats every five minutes.
(note: when the four miners are connected, the qt-client refuses the perl connection for stats (times out))
I do not have this issue with other coin qt clients.
Please look into it if you can.
Thanks
I'm done losing uptime over it, I'll just stay in a pool, but instead of being told I'm wrong I thought someone might be interested enough to look into it.
I noticed that the change in the script algo from shifting from other coin mining or attempting to comine two incompatible coins on the GPU's - caused my drivers to crash and I had to reinstall drivers. Later I found that if you turn off all GPU mining for a few moments then relaunch mining with just one coin that sometimes reloaded the drivers and I got all my hashrate back.