Greetings.
I'm a recent entry into the world of ASIC mining.
I've got a small array of 31 ASICMiner Block Erupters that I'm trying to set up as a "fire-and-forget" setup that I can just run in a remote location (where I get free electricity). Eventually I plan to run this off a Raspberry Pi, but that's a story for another day.
Right now, I'm using a Windows 8 x64 PC as a host. I've consistently been getting crashes when running cgminer. Here's my setup:
6x D-Link DUB-H7 hubs
Hub #1 is the "master" hub. The other five connect to it. Hub 1 also holds a USB fan and a single block erupter.
Hubs 2-5 each contain six block erupters. Each is plugged into hub #1.
Hub #1 is connected to my host PC.
I ran the zadig tool and configured the drivers.
With cgminer 3.3.1, if I plug in the array first, then start cgminer, cgminer will instantly crash. If I start cgminer first, then plug in the array, it seems to work. At least, I didn't experience any crash issues. However, this is unsustainable as I plan to run this rig remotely, so I need to be able to reboot the machine periodically without having to unplug and replug the array.
With cgminer 3.4.0, I can start it with the array plugged in, and it hashes normally, at expected values. However, after about 1-12 hours (varies), it crashes as per the screenshot below:
In this screenshot, it crashed after only about an hour of running.
My config file only contains my pool info, no other options. I start cgminer with a shortcut in the startup folder in windows, which just runs the executable - no command line options. Alternately, when restarting cgminer after a crash, I double-click on the .exe.
Any thoughts on what I might be doing wrong?
I'm thinking of just using the looping-restart batch file someone posted earlier in the thread, but that's just a workaround, not a fix.
(Side note: My PC has an AMD APU, which cgminer picks up and runs for an extra 50MH/s. Bonus!
)