So when you post your GPU pictures, just say you're still mining BTC and make up a MH/sec number   It really shouldn't matter what it's mining, it's all hardware porn - I guess some don't get chubs looking at GPU's anymore

I force BIOS to "always on" on power restore, then use the Power Supply switch to kill power and bring it back on that way.

Nice work Eric - I work in a datacenter, and having professional looking machines in our racks is very important.  Best of luck to you!

How many GH does a 5 tier metal shelf hash at?  Home Depot's got them for cheap 

Agreed!  You'll have to pry my Thinkpad T60p (1600x1200 15" IPS screen) out of my cold dead hands

If you don't mind answering, how did you manage .38 BC per erupter average?  I haven't seen them below ~.8, except for the .175 offer for the folks who bought early and wanted more.

Thanks for the update - I hadn't looked since mid July and was almost in for .89 or somesuch... Time flies when you're having fun!

either, or both.

He does.  It forces 64 bit pointers, and requires some variable settings and different dll's.  It ran slower on my cards out of the box than the published kernel.  It might be different on 280x/290/290x, and cards with horsepower to spare, but that's not what I run.

Yes, in-between two of your posts, in response to one of yours.  Thanks for using the "reading" skill (/sarcasm)

https://bitcointalk.org/index.php?topic=206577.msg11883061#msg11883061

You forgot to factor in a server-grade motherboard, and the price of the specialized intel compiler into that.  Lets say the device itself is your only cost.  Even then, you're getting 57 threads at 1.1 GHz with access to 8GB memory at $224 pulling 300 Watts.  Compare to a radeon r7 240 4GB, with 320 threads at 1.1 GHz with access to 4GB memory at $80 pulling 25 Watts.

Xeon Phi's have been available for at least a year, but were price prohibitive, even for the low-end products.  The likelihood that this product will be reasonably price for what it offers in mining is slim-to-none.  Now, if you get one anyway, let us know and we'll try to help you figure out how to mine on it.

I'm not sure why you would even think this a valid strategy.  Starting over on N IS making a new coin. 

We don't jump to NF=18 for a whole year, so don't start stocking your survival shelter yet.  By the time it arrives, YAC will have been on NF=17 for nearly 1/3 of its existence and it will just be "normal".  Is NF=17 hard on our GPU's? It is.  Is it any different from any NFactor change in the past?  No.  Every change in NFactor is met with confusion, frustration, and HW errors.  This difference is that we have years of understanding now instead of days, or weeks, or months. 

We've known for a while that CPU would become competitive to GPUs again at this NFactor, we just need to figure out how to keep the hashrate spread out so that there's no 51% network ownership.  We had this situation for a long, lone time with coinmine.pl having >51%, but everyone was okay with it because that's where most of the miners were.  During that period, solo mining was difficult because the pool would get most of the blocks and people not on the pool would see orphans.  Now, we have someone who has quite the mining capacity, but he's solo-mining, but only during specified hours, leaving the pools with orphans.  It's quite possible that this is not even malicious intent (other than likely using computers that aren't his or hers), but just that much hashpower that it dominates the network. 

The new AMD GPU's are coming with 8 GB of memory on the 390's.  The Fury's are only 4GB, but it's newer fabbed stuff called HBM (High bandwidth memory) and it has substantially more memory bandwidth of GDDR5 (I think it's double-ish).  Should see 8GB cards with the stuff in the future as AMD is really pushing 4K gaming, which necessitates more memory.  Don't despair about N - there's always the cpu miner

buffer size too high for system ram
not enough swap file
could be many things

And what command line did the config generator I recommended to you generate?

something like...

yacminer --scrypt-chacha --worksize 128 -g 1 --lookup-gap 8 --buffer-size 3532 -R 1664

Your R is still WAY too high, that's what causes HW errors

probably lookup gap too

Post the new command line you're using and what you've tried changing

If what I provided doesn't help, and you're using YACMiner 3.5.0, then you're beyond the help I'm willing to provide for free (which is pretty far)

Check my reply to your post in the other thread you posted this exact same problem on.

Also, make sure you're using YACMiner 3.5.0 and not 3.3.1 - they are vastly different!  You can find binaries and source at the github link in my signature