Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
by
androstan1234
on 22/05/2018, 15:30:06 UTC
@Claymore

Saw this today in my log file:

08:38:29:239   4304   checked ETH share on CPU, spent 4ms
08:38:48:975   43b8   checked ETH share on CPU, spent 3ms
08:39:09:055   43c0   checked ETH share on CPU, spent 3ms

Don`t think that is normal.

Nothing to worry about, this is totally normal.
Look back through your old logs, (use grep for example), and you'll see it's a regular event in the log.
Mr Claymore would be the only person who can explain why he's programmed this, but no doubt there is a logical reason.

Side note: Generally, (assuming the programmer is not a total moron), log entries will have some prefix, or suffix, "warning", "error", "OK", "good" etc etc, which makes life easier when searching logs for problem events, or notable events you might like to check on.

Conversely, if you don't see such annotations, and the log entry is not self explanatory, you can generally ignore such entries. (as in they are not things you need to worry about).

And No, it's not a virus either.

Thanks for your reply iSuX. I was just wondering why is there CPU share

Thanks iSuX.  I checked old logs and see that this event is in all of them.  I never noticed it before.  I was experiencing system instability yesterday, checked the log, saw this event, assumed it was a virus, ran virus scanner, removed viruses, and system went back to stable.  IDK how I got a virus, but thanks for pointing out that it's not related to the cpu share.

Like Snake, I would appreciate an explanation from Claymore for why the program is checking for eth shares on the CPU.  Maybe it's checking for a virus mining on the cpu?


@androstan1234
Bummer man, what virus was it you had?

It was called coin-bitminer or something like that.  First time this has happened to me in almost 10 months of mining.  IDK how it happened.  Maybe related to windows 1803 update since that's the only thing that's changed.  But I updated both of my rigs, and both use the same router (really a 4G LTE hotspot).  Only one caught the virus.

On the subject of Virus, sigh, if you take 2 milliseconds to think about that, and you can probably assume a virus is unlikely to have your best intentions to heart, ergo, it's going to do something you'd rather not have happen, well, it's hardly likely to have the moronic goal of hacking the claymore binary to make it mine with the CPU or advertise itself, by writing it's own log entries.
Hahahaha.

I mean, people make stupid viruses, and stupid, lazy, and/or inattentive people fall for them.  I figured, maybe someone found a way to force claymore software to mine on cpu and send shares to their wallet, thinking that a tiny amount of mining on a cpu would go unnoticed.  A side effect could be that the claymore software dutifully reports and logs whatever is going on.  If enough rigs get infected, all those tiny amounts could add up to a decent chunk of free money.