CPU and GPU mining days for bitcoin mining are long gone. With a CPU you use 1000 times more in electricity than you earn in bitcoin, with a GPU 100 times more than you earn. Each difficulty 1 share takes over 4 billion hashes to find on average, and your CPU is doing 1.4 million hashes per second. That GPU will do something like 700 million hashes per second which is still ridiculously low for the amount of electricity it uses. It is only worthwhile bitcoin mining with hardware that is designed purely with bitcoin mining in mind (i.e. ASICs) today. The days of off-the-shelf commodity hardware being able to meaningfully bitcoin mine ended a year ago.

You are probably getting confused by threads discussing altcoin mining with GPUs. That has nothing to do with bitcoin mining.

That is not charm, everything uses the WinUSB driver on windows on cgminer - you install one driver for everything and just associate it with your device if you ever get a different type of device. Saying a driver happens to work for a piece of software is not really something special...

And coincidentally, I happen to have all the devices you're describing.

And they all work fine on my rig.

Once the drivers are set up on cgminer, you can plug and unplug as many of those same devices as you like and cgminer will hotplug and unplug them without any further intervention.

I have a tracking number, so *something* is being sent to me, for what it's worth.

Guys, if you get a crash, debugging information will help everyone long term since that's how I'll actually get to fix the bugs. This is not a closed source proprietary piece of hidden software, it is a community project  despite the fact there are only a very small number of developers, and we need information from the users as much as they need our code. While I'm forever developing code for new features and drivers, I am seriously interested in stability over anything else. My rigs run for months without a crash and that's how I want it to be for the other users, but I don't have all hardware combinations on all operating systems (nor do I even want that). I've debugged a LOT of issues courtesy of debug traces, logins into other people's machines and bug reports and so on that would never have been fixed otherwise.

Unless the crashing is because the software is fighting over the device in which case it will go away.

Well I already gave you a link to the instructions on how to help... but by far the easiest thing for you to do is just mine with everything on cgminer as the NF1 devices as they're called by cgminer are fully supported, and you set them up exactly as you set up every other USB device you've used so far on cgminer so it's about 10 seconds' work.

Every single USB device on cgminer uses exactly the same USB driver. Crashes should never happen, and any debugging would be most appreciated as per:
http://ck.kolivas.org/apps/cgminer/debug/README-debug

If you're not interested in helping the developers debug issues with the software you're depending on for free, feel free to read how to use the --usb command (as Kano has suggested) from the readme, to choose only the devices you want it to work on.

Almost 50% of the population is below average intelligence.

At 1.4 million hashes per second it will take you on average about 51 minutes to find a share.

Yes that's right, you ARE doing it right, but you are also seriously wasting your time.

I'm not entirely sure why either. Historically when this pool was bigger, changes were always very hard to come by and it was very conservative in adopting them, which of course did actually add to its stability since everything worked - but they were the last to adopt change. Heck they didn't even have ntime-roll support for the longest time, relying on sheer brute force of generating unique work items for each miner based on the vast amount of server power they had thrown at it, which no one else could afford at the time. Once pools started to move to stratum, there was no sign this pool was going to join in, and then about 6 months after the first ASICs appeared and every serious remaining pool was using stratum, Tycho briefly asked a question about stratum implementation on the stratum thread which was the only sign he was interested, but it never eventuated. By that time this pool had become nigh on irrelevant and perhaps they assumed the stratum thing wouldn't be required, or that multi-TH machines wouldn't exist or whatever, but that proved wrong.  Perhaps by that time the mega amounts of BTC they'd accumulated made the prospect of having to refashion the pool and maintain a whole new infrastructure proved uninteresting as a "job" for lesser rewards than they'd already made.

You'll note they skilfully address any actual issues with the pool, responding eventually to support queries, but continuing avoiding responding to any of these discussions or desperate pleas for modernising the pool. The smug way they responded to people almost demanding they upgrade or charge lower fees slowly stopped new members from joining and existing members were forced to move on.  I originally watched that behaviour in amusement and never said anything, but it has been over a year since ASICs hit and the pattern has been steadfast. Perhaps more notable members of the community speaking up will make them respond... or not.

I might also add, a lot of the pool hashrate used to be coming from Russia and China and were probably "deals" which are irrelevant today.

People obsessed with the possibility that the preorder that's available might put them ahead of the diff curve and be first with the hardware to stay ahead, combined with lots of newcomers who don't understand diff rises and its effect on profits losses from mining. Usually cognitive bias is how people explain their losses away and they move on and possibly even do it again (wiki: post purchase rationalization). It's a market that seems to have no bottom to it, and we'll keep seeing it for some time to come.

Icedrill still don't have the controllers they require to run all the Sierras they're getting from hashfast. This means a LOT of devices are being attached to less controllers(PCs running cgminer), and to make matters worse, the hashfast devices don't actually ntime roll internally in their firmware the way the documentation claims, which means cgminer has to actually generate every single work item for these devices, which is usually ~2300 at a time. We found the i3 in one laptop could reliably run about 50TH of Sierras. Note that this is thousands of time more work than a pool receiving and processing 50TH of shares.

...gotta love the efficiency of well written c code.

Memory makes no difference. But then, mining bitcoin with GPUs makes no sense now, so I guess you're talking about mining altcoins.

It also allows discussion of these asics, which are clearly only aimed at the scrypt market, to sneak their way into the bitcoin forum hardware section because they still allegedly mine bitcoin, although no on uses them for that. I doubt this is intentional but it has been noted.

-0 stratum.bitcoin.cz3333

should be

-o stratum.bitcoin.cz:3333

and remove the -i 10

Also if you start cgminer from a command prompt window first before you create your first batch file, you will see what the problem is without the window disappearing.

Yep restart's pretty broken. It's another one of those features from the GPU days unfortunately and shutting down all these threads reliably is really hard. I mentioned it a few pages back that only quit and start works. If I had infinite hours to work on it I'd eventually fix it, but new device drivers/features keep taking priority sorry.

I changed the queue size to auto adjust every time it hits zero now since it shouldn't - and there are devices with massive hashrates that need a huge queue to keep busy. Unfortunately that seems to be fighting with you trying to set it to zero, but that shouldn't actually drop the hashrate unless you're running out of cpu. So yeah it's not ideal. Kinda hard writing code for 333MH and 50TH setups at the same time. Lemme think about it. This might need a new command line option.

Did you miss the part where i offered firmware?
http://ck.kolivas.org/apps/cgminer/avalon/20140228/

Admittedly it was blindly built, but one user tried it and it was fine.

It is always profitable for the cloud and almost never for the miner. Genius business model; dunno why people keep throwing their money at it but I guess they repeatedly count on people not understanding diff and mining - and it seems to work every time.

Don't