Doubled the page file, errors persist, so no thank you I guess.

There's no problem, that's what the network difficulty is.   Per your screen shot you are hashing to difficulty 32, pool difficulty, every hash you hash that results in a solution with difficulty greater than 32 should be accepted.  You're using a way out dated version of cgminer.  4.9.1 is current, try a new version maybe?

I found it though google, searching for stuff and always being directed here.  So much information, basically everything you want to know about BTC.

I will trade you a bridge for one.

Fan Boys.  Absolutely terrible.  I didn't laugh, hell, I didn't even smile once. Terrible plot, terrible story, terrible everything.  Total shitbox, worst movie I ever watched.

I had my U3 plugged into a powered USB 3.0 hub plugged into a 2.0 port on my computer, it didn't like this, lots of LIBUSB errors.  Now running in a powered 2.0 hub, seems to be happy for ~24 hours (knock on wood).  Using a new power cable, too.  This one is a molex 4-pin to barrel plug and has thicker wires than the pci-e to barrel plug I was using (2.5mm vs ~2.1mm).

I've had to reinstall bitcoin core, still re-syncing the block chain, hopefully it will be done when I get home and my payment will be there waiting for me.

How long have you been running stable with such a high voltage?

I will give that a shot.  Seems odd to me that Bitcoin Core would need more VM than any other program I have ever run, never needed to up the pagefile size for anything.

If it were as easy as the scenario you outline to make a huge fortune people would be doing it/would already have done it.  The fact that it hasn't happened and won't happen answers your question: no one does this because that's not how the system works.

That is a very simplistic way of looking at a market, and not at all how it works in real life.  If it were that simple it would be done; the fact that it doesn't happen should answer your question before you even ask it.

Here are a couple graphics that help drive home the number of potential btc addresses.

I get MinGW Runtime Assertion errors while d/ling the block chain, please see this thread: https://bitcointalk.org/index.php?topic=972389.0

You can install 0.10 over the old version, just make sure it's not running.

Lucky you!  I pay about $0.20/kWh on average, residential rates in southern California are very high.  Good thing I mine as a hobby, not for profit.

Price has been steadily rising past couple weeks, it may continue.  Of course, it may not, that's why we call it speculation.

source: http://www.c n b c.com/id/102456187 (why is cnbc a suspicious site?)

It's an interesting graph, not totally convinced it's corollary or causational.  Is this relationship a result of people selling off btc for fiat as soon as they're done with a transaction, or are there other factors?

This is a fresh install with a fresh wallet, and I am re-dl the whole blockchain, that is where this issue happens as I said in the first post.  It happens while syncing (i.e. downloading the blockchain).

I had it stable for a week stock voltage/freq with the factory power supply, then got a new 850watt psu to use with the S1 and hooked the U3 to it as well.  Messed around with overclocking, went as high as 800v/250freq, it ran stable for several hours, then ZOMBIE.  Full reset it and everything else, re-zadig, and running stock volt/freq again, was stable overnight.  Seems to only be stable at stock settings unfortunately.  I see about 42-50gh out of it, was getting 60gh oc'd.


I used Bitcoin Wallet on my android phone, had it send the address directly to my email account, and I copy/pasted it from there.  Not sure where I lost a digit in that process, but I'll assume it must be user error because I've used that walled to generate keys several times and not had an issue before.

I have and prefer this method, looks much cleaner!