Quote from: h311m4n on August 08, 2017, 02:46:11 PM

Quote from: wOvAN on August 08, 2017, 02:16:06 PM

Is claymore cheating with displaying hashrate?

I have rx580 which claymore's reported hashrate is 28.2
the speed must mine about 0.008135 ETH/24h

On dwarfpool the actual income in 24h is about 0.00635242

I do ETH only mining with devfee on? the pool takes 1% fee
so 2% is total fee

28.2 * 2% = 0,564
and pure profit speed is 28.2 - 0,564 = 27,636 which should give us 0.007962

0.007962-0.00635242 = 0.001610

0.00635242 - the sum of ETH should be mines with speed 22 M/h

So where's another 5,6 M/h gone? (27,636-22=5,636)

Or it's just claymore cheating the real mining speed, 22 instead of 27,6!!!

Sad

http://i95.fastpic.ru/big/2017/0808/1c/d5d78bc48519c8fff599cf70140f241c.jpg
http://i95.fastpic.ru/big/2017/0808/cc/4d9c105718945ed75300318f7834bacc.jpg

He's not cheating...first off, dwarfpool doesn't have the best reputation for profitability. Second, your hashrate at the pool will vary, depending on the number of shares you submit, your response time to the pool, your luck and the "quality" of your overclocking and other things. This is what defines your actual hashrate by the pool. It should act in waves and sometimes go above or at least be equal the reported hashrate. If it doesn't, you have a problem.

Quote from: BLNT on August 08, 2017, 02:29:02 PM

Without scouring through every post (as this might have been asked already), I wanted to see if anyone might have insight with regard to an issue I'm having.

I've got a few computers at my office which have 1050 TI's in them (single cards) running Win10pro. Two of them seem to be rather finiky about running Claymore (it worked once/twice initially), so I'm not sure what's going on. When I go to start the miner, the cmd window will open up for perhaps a second and it will get through the first 4 lines and then just close (as soon as it hits the EthDcrMiner64.exe line).

They're all "identical" Dell workstations running on a domain. I've got Kaspersky running on all of them, and disabled it on the problem machines to see if that was the hold up, but to no avail.

Any suggestions?

THANKS

Here's one: mine on you own hardware?

ahem.... I own the entire office...