Uhh no, I was referring to the high CPU usage and inconsistent hash rate. The svchost issue is some background task (virus scan?) doing something and using cpu which takes away cpu from the mining process. http://windows.microsoft.com/en-us/windows/what-is-svchost-exe#1TC=windows-7
Okay, but is it known why it creates that svchost.exe and supposedly mines in parallel (what and for whom)? It certainly doesn't mine for me when it does so since hashrate for that worker in the pool goes down (and in the cgminer window too), while card temperatures stay high so they obviously do hash at full power and not only at half power as the cgminer window suggests. When I think about this, I saw that already back in February when it was launched. And I had it running 24/7 since then. So it must do this only temporarily and then go back to normal, i.e. it kills the svchost.exe and gives full hashrate back to cgminer.exe after some time.
I have no antivir installed on any rigs. They are not used for anything else, no browsing, nothing. I think I read in the past about cgminer masking as svchost in mining malware, but it is excluded that any malware is on my rigs. In fact I set up a new rig yesterday and it shows the same erratic behavior.
I edited my post to add more info so I'm not if you saw that or if it's just unclear. 1) cgminer uses way more CPU than it shouid while mining (this is being worked on) 2) svchost has nothing to do with cgminer 3) svchost is some other program/background task takes cpu away from cgminer 4) when that other program/background task is running cgminer's hash rate will take a dip
Well it is some process or background task running doing something. I would think it would be rather easy to track down. Maybe someone who knows Windows better can help you. Like I said though, I would give ccminer or sgminer a try since the CPU usage is much better with those.
Okay, let's assume it is just another native and legit windows process and not the case I mentioned above (I added a link). Will try to figure out which and prevent it from executing. What made me suspicious was however that the temperatures stay high. They should drop if hashrate drops, as they do whenever pool is not providing work fast enough for instance. But temps stay high and fan speed stays high, so the cards do work at full. Question is: Where is the missing hashrate going? EDIT: I am aware that svchost is a legit windows process. There are a dozen running on each rig. It's just that malware is sometimes masking as svchost and in my case the appearing svchost has over 200MB and runs at 50% CPU. The other dozen svchosts have a couple of MB and require basically 0% CPU.
BTW, global hashrate broke through the 7TH/s and difficulty too now at an all-time high of 434k. Happy diminishing returns mining!
Hey folks, i'd just like to apologize for the downtimes especially yesterday and today, but I have very sophisticated DDoS attacks since two days. it seems someone is watching my online-status and starts to poke around as soon as i'm (seeming to be) offline. The attacks are done in several ways, each attack differs from the earlier attack so its not as easy as usual to come by. I've posted most other pools in the Header of the pool and I'd recommend adding those pools as backup-pools so your miner switches automatically as soon as the stratum/pool goes down. i'm doing my best keeping the pool up and running - thanks for your understanding.
Okay, looks like my Counter measures are working and the pool is finally healthy again. Thanks for your understanding and patience
What ever was going on my miners that were running only on your pools just started crashing and trojans were discovered, .dll files went missing, now I can't start mining anything without gpus crashing (hottest they've ever been ~40c). Time for a drive format. Hopefully, it wasn't due to countermeasures...
Hmm really weird, by purely mining you cannot get a virus / trojan or something similar, because its only a tcp connection without any "interaction" - so the viruses must come from somewhere else, however the "countermeasures" are just some ip filters on my side which trigger a ban to a specific IP when a specific threshold of "bad work" has been submitted, so it cannot have anything to do with that.
figured out that the issue was that i burnt through my cords, i guess getting 3.2 hash per card is a little like icarus flying too close to the sun.
I have added a second server for stratum enabled mining @ suprnova, you can use stratum+tcp://dcr.suprnova.cc:2254 as well as stratum+tcp://dcr.suprnova.cc:2252 for current ccminer (old-style stratum) and stratum+tcp://dcr.suprnova.cc:2255 for nicehash rentals and nicehash's sgminer. Pool @ https://dcr.suprnova.cc Let me know if you have any problems.
Could somebody please explain to me, I'm mining to an address shown to me by a wallet like a month ago and my balance is still zero while pool showing balance on this address.
When you mine as a member of the pool, your funds are stored on your pool account. The address you added to your pool account just specifies where your funds will go. You probably haven't setup an automatic payout threshold yet, meaning - when your account hits X amount in DCR, send it all to 'the address you specified'. You can also do a manual payout to send everything in your account to the address you specified. Go to My Account -> Edit Account and there is a box at the bottom called Cash Out. Use this to perform a manual payout and withdraw your DCR from Suprnova.
Hi Ocminer, i reall would appreciate your help. I tried some versions of cgminer and also sgminer on suprnova......iam mining with the Claymore-Software in the Moment. But pure Decredmining will not work. I really tried everything. Most of the Time, the cgminer does nothing.....somtimes it crashes. I am on an Windos 8.1 Rig with 3x 390x GPUs. My Username at suprnova is QiaSol. Thank you for helping.
Try with this: cgminer.exe --blake256 -o http://dcr.suprnova.cc:9111 -u qiasol.worker-name -p worker-pass --no-adl --cert \\\"%LOCALAPPDATA%\\\\Dcrd\\\\rpc.cert\\\" --no-submit-stale --scan-time 2 --queue 0 Change the worker-name with the name you've chosen inside your suprnova dashboard. Do the same with worker-pass. hope this works for you.
Actually 9111 is the pushpool port, he probably wants to use stratum+tcp://dcr.suprnova.cc:2254 As the URL