It's a DNS Problem, used to happen to me lots, add the following to your hosts file

How do you get this into BAMT?

290x/win7 x64/13.12cat
before(2%-version): -w 256 -tc 20481 -g 1 -I 21 -----> 3.85mhs
after(free-version): -w 256 -tc 20481 -g 2 -I 15   ----->2.75mhs
no way for -g 1/-w64/-w128-parameters - it`s always 2.6mhs or less

PS What are the optimal settings for 290x/290?
I still think that the lack off "-I" (crash of miner when "-I" is above 15) is the main issue in reaching more mhs.  

That needs to go in the development queue.  Rehires should only be valid for the original rental term?

I tryed a few drivers, but the fact is that it happened only with Darkcoin mining, so it should put the driver/bios/hardware aside if I'm correct.
I'm pretty sure that there is something in the miner that react baddly with the R9 290.

I just noticed one more thing:
When the loss happened: all my cards (even the non-290) had a huge drop.
After that drop, all the cards climb up again, the other model reach their max hasrate, and the 290 reach only 90% of max hasrate.

Since I'm not really fluent in English here is an example:

Coldreboot
290: 2.5  270: 1.3
10 minutes then a drop in the same second of all the cards in the rigg
290:1.5  270 0.9
Immediatly the hasrate started to recover and a few seconds later:
290: 2.3  270: 1.3  so a loss is visible only on the 290
If I restart the miner, I keep that last hasrate.
If I coldreboot: It starts over.

PS: it happend the same way without overclocking: 290 went from 2.0 to 1.8.

So the coin is, in essence, ''miner resistant'' no matter what device mines it. pfft, advertise asic resistant when asics won't be mainstream for another few months. This changes everything and once again, hidden and tweaked info. utc seeming more and more like a sophisticated pump and dump since all ''miner-attainable coins'' will have been mined in 1 month with millions of coin inaccessible, in the blockchain. Diff will drop dramatically when gpu's no longer able to mine, so its good for the cpu's until the next nfactor after this next nfactor in april. Then pointless to mine completely.

In the end it's not that CPU's hash way faster than GPU's at high N's; specifically, it's that CPU's cost less Watts per Kh/s to mine at higher N's.

 Some examples of hash rates and setups with CPU's and GPUs @ N = 14;  can be seen here - http://yacoinwiki.tk/index.php/Mining_Hardware_Comparison

You can see, as an example here @ N14

2x E5645 Procesors    2x 80W --   1.53Kh/s    

7950 GPU                  (250w)    1.3-1.5 Kh/s

R7 250 	2 GB 	32W 	2.47 kH/s

We need to know how n-factor affected cpu miners, if hashes halved. Is anyone even cpu mining?

Nfactor	  	N	  	Memory	  	UNIX Time	   	Date/Time in GMT	   	Hashrate for 2x Xeon E5450
13		16384		2MB		1380574112		Mon - 30 Sep 2013 - 20:48:32 GMT		2,276
14		32768		4MB		1384768416		Mon - 18 Nov 2013 - 09:53:36 GMT		606

PS. With regards to power consumption, does this scrypt-jane consume less power than scrypt itself?

Why just not lease yours on betarigs.com ?

Here, in this very thread: https://bitcointalk.org/index.php?topic=413978.msg4890528#msg4890528

Ermmm guys... Am I doing my math right here?
According to what I'm reading here and the following parameters:

6x R9 280x (alledgedly they should hash @ 550 ~135 Kh/s each?) = 3.3 ~0.81 Mh/s
Current difficulty: ~6.5
Block Reward: 50
UTC/BTC rate: ~ 0.00033
BTC/USD rate: ~ 640

...would make me over $100/day !?

I somehow doubt this is correct...

More than a warning with RED I cannot do.

underclocked your memory to 999 and it gave you better results?

am i getting the most out of my MSI r9 290?

i tried thread concurrencies (45000,56320,47930,42000), 45000 gave me same hash rate while the other 3 gave me either crash or no improvement. in doge and vert i had my optimum tc at 24550

a little help would be great if necessary.  


and ofcourse, would be glad if anyone could send some excess UTC here i just have 80 UTC atm and would appreciate help to be in this ride to the sky

UQNBCouqvxe3BCcUZ2n9f6Dsujieiwi2nB