I'd like to think some other variable is at play here. I've run every single version of cgminer from 3.3.1 to 3.5.1 and have never had a single problem. I ran it on a Windows 7 machine 24/7 with two 7970 video cards and six block erupters. The only down time I've had is from halting for software updates and the maybe an average of one restart a month for system updates. After 3.5.1 I moved the block erupters to a raspberry pi and it has almost literally 100% up time. The only times it has stopped mining are when I halted the process to start the latest version of cgminer. It's run every version between 3.5.1 all the way up to 3.6.6 without issue.
There almost has to be some key variable...os, wiring, electrical, hardware defect, environment...
Chad
I have two win7x64 machines. One is AMD based, somewhat older technology (was a sempton single core, is now an athlon II dual core @ 3.4GHz with 4 gb memory), doesn't have any USB 3.0 ports. 3.6.4 works fine with my 36 erupters. No problems aside from the possible winsock error, but recently I've been restarting it for other reasons before it runs more than a few days, so I don't know if the winsock error is still around or not.
I move the same 36 erupters and same hubs to the other machine, Intel based, core i7, 12 gb of memory, with USB 3.0 ports. I almost immediately get zombies and IO errors. Neither of which I get on the older machine. Oh, and the erupters aren't detected at all on the USB 3.0 ports. I have to plug them into the 2.0 ports to see them.
I think it's hardware based. Chipset maybe? Something beyond your control?
M