So I have 8 block erupters on one powered USB Orico hub on port 1 of my computer and 1 Antminer and 3 red furies on another Orico powered hub. Everything works fine but one red fury starts to slow down Ghash and the eventually starts running at 0.00 mhash. Does this just happen with this hardware that they need to be rebooted every 2-5 days? I have a fan on them cooling them and I haven't pencil moded or done anything like that. It appears to rotate between my red furies. I'm running the bfgminer that is compatible with Antminers and running Windows Home Server 2011 64bit on this particular machine which is a build off Windows Server 2008 R2. Although these are USB 3.0 hubs, my home server has 2.0 ports. Thanks!
Have you swapped the hubs over? That may eliminate a dodgy hub/power supply.
I'll try switching them. Maybe I should invest in an Anker but I bought these when they cost as much as one just because I wanted all black ones.
I'm running the Blue Furies through Orico ten port hubs and it's not the hubs, let me assure you of that (there's comment somewhere on this forum that the Orico's are made by Anker anyway), it's the Furies, they are so fickle. I've got some Antminer U1's arriving in the mail so cannot comment on those yet but I run both Block Erupter usbs and the Blue Furies in the Orico hubs. The trick that has been working is to use two instances of bfg miner, one to recognise the Block Erupters (I use 3.2.1) and once they are hashing away, open up bfg 3.5.1 for the Blue Furies. If at first the Furies aren't being recognised, close your bfg 3.5.1 window, then leaving the Erupters hashing, manually remove each Fury, wait a few seconds, then plug it back into the hub, do that with all of them then open up 3.5.1 again, it should recognise them this time.
There's more about this on my post on page 14 of this thread with other posts subsequent also being very helpful. It might be that you need one window of bfg for the Ants and one for the Furies. I'm half expecting to be using a third window when my Antminers arrive, so maybe I'll have something to post in about a week or so about this.
The other thing that some people have suggested is if you are determined to use only the one instance of bfg and make it recognise your different type of miners, then you can identify each miner in each COM port in your target string in bfg which is fine if you have a handful of usbs but impractical if you're running a lot of them.
There's other solutions that have been found and people have documented their conclusions on this, admittedly, rather long thread but the Furies are not the easiest usbs to use and there always seems to be one that stops working every day or two, so 3.5.1 has to be closed briefly, the offending Fury pulled out of the hub, give it a few seconds, then push the Fury back in, start 3.5.1 and it should recognise them all again.
The other thing to point out is that different versions of bfg appear to work better with different system setups, so look for posts which outline solutions suitable to the OS you're using. I'm using Win7x32 but I did find that 3.2.1 for Erupters and 3.5.1 for the Furies also worked when I tried it on Win7x64, although it gave me hassles on Win8 and 8.1 so went back to 7x32 but you'll find that with hair-pulling and tweaking, most folks have finally got the Furies to work on whatever setup they use but it sure as hell is not 'one size fits all' like some other usb miners out there.
Good luck with it all.