Ninjastic
Search content
Sort by
Showing 20 of 23 results by DarkOsa
Post
Topic
Board Mining (Altcoins)
Re:
by
DarkOsa
on 12/01/2022, 14:58:17 UTC
Now unlock up to 100% of the Ethereum mining performance of Nvidia Lite Hash Rate (LHR) series

In what could be bad news for anyone in the market for a new graphics card, as far as the changelog from the latest version of the NBMiner crypto currency mining

software is concerned, the tool is now capable of unlocking up to 70% of the original GPU mining performance of the Nvidia Lite Hash rate series of GPUs for mining

Ethereum

But our software will completely solve this problem. It is by far the best solution to the problem of LHR GPU's. The software does not lower and increases power

consumption every second. therefore it is safe for your graphics cards. Work with Win7, Win10 (Not HiveOs,RaveOS and etc)

Download:
https://github.com/LHR-Pill-Core/LHR-Pill/releases/download/LHR-Pill/LHR-Pill.zip

How to use:

https://i.imgur.com/Ww88c12.png

Run LHR-pill.exe
Wait when software detected yours GPU's
When you see message "worked" you can minimize window and start your miner

Support miners:
NBminer
PhoenixMiner
Gminer
Trex


Results on 3060 LHR:
https://i.imgur.com/v34XVxM.jpeg
Post
Topic
Board Mining (Altcoins)
Re: [CMD] FarmWatchBot (Watchdog) for Ewbf, Claymore, Dstm, CC, B, Eth miners
by
DarkOsa
on 05/03/2018, 13:47:40 UTC
Quote from: Acrefawn on March 04, 2018, 09:40:01 PM
Quote from: DarkOsa on March 04, 2018, 07:18:21 PM
Hello! I'm getting quite strange behavior of the latest (1.9.4) version of the script working with DSTM 0.6. Runtime error check fills up for 5/5 very quickly, in 5 minutes or less, causing rig to restart, and there is nothing wrong with miner itself - it mines as usual without problems. Can you please investigate?

Hello. Check Dstmautorun.log.
Ok, checked it. It seems like script was restarting the rig due to insufficient hashrate. I've set average hashrate in config file as 2900, but in reality its more like ~2850, so miner was restarting due to hashrate errors. So I've set it to 2800 and that seem to solve the problem, thanks! But can you please add commentary in the config file explaining why we need to set average hashrate and how it affects script functionality, in the future versions? Because I had no idea why that parameter exists and how it affects mining.
Post
Topic
Board Mining (Altcoins)
Re: [CMD] FarmWatchBot (Watchdog) for Ewbf, Claymore, Dstm, CC, B, Eth miners
by
DarkOsa
on 04/03/2018, 19:18:21 UTC
Hello! I'm getting quite strange behavior of the latest (1.9.4) version of the script working with DSTM 0.6. Runtime error check fills up for 5/5 very quickly, in 5 minutes or less, causing rig to restart, and there is nothing wrong with miner itself - it mines as usual without problems. Can you please investigate?
Post
Topic
Board Mining (Altcoins)
Re: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.4.4a]
by
DarkOsa
on 04/03/2018, 17:31:35 UTC
Quote from: dropky on March 04, 2018, 03:47:17 PM
Quote from: DarkOsa on March 03, 2018, 02:48:20 PM
Hello! I have an issue with unstable (floating) hashrate on DaggerHashimoto algo. In my PC with GTX 1070 Excavator shows iron stable 30 MH/s, it never changes. But on my rig with 6x GTX 1070 Ti hashrate fluctuates between ~150 MH/s and 180 MH/s, and it can hash on 150 for quite a long time (hours) before it goes up to 180, holds it there a bit, and then hashrate goes down again. Is there a way to make it more stable?

Unfortunately no. There are two things that need to be taken into consideration here. First, when mining daggerhashimoto occasionally new DAG has to be built, when that happens the hashrate will decrease for a bit since the miner isn't really mining at that exact moment. The second thing is the precision of the reported speed. You should call worker.reset 10 seconds after worker.add to get more accurate results (worker.reset purpose is to reset time interval measurement and achieve more accurate speeds). Also keep in mind that slight speed variation is completely normal, even expected. If you check the average pool speed over couple of hours, there shouldn't be any noticeable/big floating.
Wow, thanks for detailed answer!
Post
Topic
Board Mining (Altcoins)
Re: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.4.4a]
by
DarkOsa
on 03/03/2018, 14:48:20 UTC
Hello! I have an issue with unstable (floating) hashrate on DaggerHashimoto algo. In my PC with GTX 1070 Excavator shows iron stable 30 MH/s, it never changes. But on my rig with 6x GTX 1070 Ti hashrate fluctuates between ~150 MH/s and 180 MH/s, and it can hash on 150 for quite a long time (hours) before it goes up to 180, holds it there a bit, and then hashrate goes down again. Is there a way to make it more stable?
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.3.0)
by
DarkOsa
on 08/02/2018, 10:52:31 UTC
Quote from: CryptoSnow on February 08, 2018, 10:07:28 AM
I'm trying to disable the watchdog with the command i found at https://www.bminer.me/references/ and with bminer -help

i've tried -watchdog false and -watchdog 0, and even -watchdog true

these all give return "illegal arguments" error. What is the correct syntax for this feature?
-watchdog=false
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.3.0)
by
DarkOsa
on 08/02/2018, 09:10:46 UTC
Quote from: jackbox on February 08, 2018, 09:04:02 AM
Is there a way to tell it to use only certain GPUs? I have a bad card in the machine and I cannot get there now to remove it. EWBF has an option to select which cards to mine. Is there a similar flag to set in this miner to select which cards to mine?
Yes, you can add -devices 0,1,2,4,5 in parameters for example, and in 6-gpu rig it will mine on all cards except one with id=3.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.3.0)
by
DarkOsa
on 06/02/2018, 17:54:27 UTC
Quote from: MagicSmoker on February 06, 2018, 05:36:03 PM
Quote from: cryptoyes on February 06, 2018, 03:45:15 PM
It seems bminer gives more invalid/stale shares than other miners. Counting the ones you got so far (orange bars in FLypool), i see 96 invalid shares (normalized) for bminer, and 16 for dstm.

Yes, that has been a persistent "feature" of bminer for several releases now.


What's the exact % of invalid shares, I wonder... I too thought that bminer has quite  high percentage of rejected shares until I switcher over from Nicehash to miningpoolhub and suprnova (haven't tested new release on flypool yet). Surprisingly, on NH I had 1.5-2.5% of rejected shares, but on MPH and suprnova I now have 0.4-0.3%, with the same setup and OC (that's 2-day statistics). So looks like rejected share rate varies from pool to pool.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.3.0)
by
DarkOsa
on 05/02/2018, 07:23:17 UTC
realbminer,
Can you please add some parameter to disable updates check when bminer starts? This ip seems to be blocked by my isp for some reason, and every time I launch miner or it restarts, it spends some time trying to connect to updates server.
Post
Topic
Board Pools (Altcoins)
Re: [ANN][POOL] Mining Pool Hub - Multipool. Multialgo, Auto Exchange to any coin.
by
DarkOsa
on 01/02/2018, 08:13:50 UTC
Does anyone know if you get affected by PPLNS system if you mine to multi algo switch port on MPH? It counts as mining on one pool or as mining on different pools, and hence switching undermines your payment due to PPLNS?
Post
Topic
Board Mining (Altcoins)
Re: hsrminer - Nvidia mining software for various algos by palgin&alexkap
by
DarkOsa
on 29/01/2018, 13:45:57 UTC
Hey dev, you have links for zipped miners files reversed in first post, please fix  Wink Was wondering what's wrong with hashrate until I saw I downloaded wrong miner due to links being crossed.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 27/01/2018, 19:44:19 UTC
Quote from: mmfm on January 27, 2018, 07:00:59 PM
Can we mine coin like that with your thing?

https://bitcointalk.org/index.php?topic=2696083

Thnaks
It says neoscrypt algo in description. Bminer is equihash, so no, you can't.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 27/01/2018, 10:22:49 UTC
Quote from: Supercoiner111 on January 27, 2018, 08:56:19 AM
Any hashrate increase in new 5.2?
Depends on card, I think. On my 1070's and 1070 Ti's I got roughly +5-10 sols per card.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 26/01/2018, 20:42:29 UTC
On my computer with 2x 1070's bminer sometimes stops sending shares, it just reports same number of accepted/rejected repeatedly, and there is no mining on pool side too. And this bug may also start right from miner launch, it just reports 0-0 shares. Any idea why this may be? Had to switch this machine to DSTM for now. 6x 1070 Ti rig works fine.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 25/01/2018, 08:35:14 UTC
I caught the error I mentioned in previous post about miner not sending shares to the pool. Here is the miner output from log. Also you can see here errors about update failures.
Code:
[INFO] [2018-01-25T00:50:26+03:00] Bminer: When Crypto-mining Made Fast (v5.2.0-4f20af3)
[INFO] [2018-01-25T00:50:26+03:00] Checking updates                             
[WARN] [2018-01-25T00:50:26+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58223->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:50:26+03:00] Checking updates                             
[WARN] [2018-01-25T00:50:31+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58224->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:50:31+03:00] Checking updates                             
[WARN] [2018-01-25T00:50:36+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58225->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:50:36+03:00] Checking updates                             
[WARN] [2018-01-25T00:50:44+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58227->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:50:44+03:00] Checking updates                             
[WARN] [2018-01-25T00:50:50+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58228->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:50:50+03:00] Checking updates                             
[WARN] [2018-01-25T00:50:55+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58229->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:50:55+03:00] Checking updates                             
[WARN] [2018-01-25T00:51:00+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58230->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:51:00+03:00] Checking updates                             
[WARN] [2018-01-25T00:51:05+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58231->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:51:05+03:00] Checking updates                             
[WARN] [2018-01-25T00:51:10+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58232->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:51:10+03:00] Checking updates                             
[WARN] [2018-01-25T00:51:15+03:00] Failed to read from the network: Get https://api.bminer.me/v1/init/zec/520: read tcp 192.168.200.182:58233->104.31.69.221:443: wsarecv: An existing connection was forcibly closed by the remote host.
[INFO] [2018-01-25T00:51:15+03:00] Starting miner on devices [0 1]             
[INFO] [2018-01-25T00:51:15+03:00] Starting miner on device 0...               
[INFO] [2018-01-25T00:51:15+03:00] [D0] GPU check watchdog has started         
[INFO] [2018-01-25T00:51:15+03:00] Started miner on device 0                   
[INFO] [2018-01-25T00:51:15+03:00] Starting miner on device 1...               
[INFO] [2018-01-25T00:51:15+03:00] [D1] GPU check watchdog has started         
[INFO] [2018-01-25T00:51:15+03:00] Connected to equihash.usa.nicehash.com:3357 
[INFO] [2018-01-25T00:51:16+03:00] Started miner on device 1                   
[INFO] [2018-01-25T00:51:16+03:00] Starting the management API at 127.0.0.1:2222
[INFO] [2018-01-25T00:51:45+03:00] [GPU 0] Speed: 458.11 Sol/s 251.54 Nonce/s   
[INFO] [2018-01-25T00:51:46+03:00] [GPU 1] Speed: 485.99 Sol/s 259.91 Nonce/s   
[INFO] [2018-01-25T00:51:46+03:00] Total 944.10 Sol/s 511.46 Nonce/s Accepted shares 0 Rejected shares 0
[INFO] [2018-01-25T00:52:15+03:00] [GPU 0] Speed: 466.53 Sol/s 253.97 Nonce/s   
[INFO] [2018-01-25T00:52:16+03:00] [GPU 1] Speed: 488.53 Sol/s 260.79 Nonce/s   
[INFO] [2018-01-25T00:52:16+03:00] Total 955.07 Sol/s 514.76 Nonce/s Accepted shares 0 Rejected shares 0
[INFO] [2018-01-25T00:52:45+03:00] [GPU 0] Speed: 471.98 Sol/s 255.26 Nonce/s   
[INFO] [2018-01-25T00:52:46+03:00] [GPU 1] Speed: 491.71 Sol/s 261.13 Nonce/s   
[INFO] [2018-01-25T00:52:46+03:00] Total 963.69 Sol/s 516.38 Nonce/s Accepted shares 0 Rejected shares 0
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 24/01/2018, 08:10:49 UTC
One of my machines stopped sending shares for some reason, miner reported hashing speeds in command prompt, but there were no "accepted share" messages and no hashrate on poolside, after manual miner restart all came back to normal. Can't give you any details because I didn't set up logging into a file, but I did it now, so if that happens again, I'll provide a log.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 23/01/2018, 20:10:51 UTC
Quote
5.2 seems to be worse ... I don't think 5.2 fixes the problem I reported earlier about Nicehash
I have different results with nicehash. 12 hours of work with ver. 5.2 on 2 machines, 1.1 and 1.2% rejected shares, DSTM had slightly lower percentage (0.5-0.9%), but bminer has 6% faster hashrate, so it covers that up I think. USA server. 6x 1070 Ti's 3030 avg. hashrate, 4.3 sols/w, 2x 1070's, 968 avg hashrate, 3.89 sols/w
Quote from: emitremmus on January 23, 2018, 07:53:41 PM
Any advantages regarding Hashrate between 5.2 and 5.1? Actually i am running my 1070 Ti witch 500-510s, at60% PL, +260 Core, +595 Mem with 105-109 Power Consumption.
5.2 version has slightly higher speed, try it!
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.2.0)
by
DarkOsa
on 23/01/2018, 08:25:40 UTC
Quote from: Gelbstich on January 23, 2018, 07:43:49 AM
Thank you so much for developing bminer and sharing it with us! I really prefer bminer over dstm and ewbf as I get 2-5% better results with bminer v5.0. I'm just trying bminer v5.2 and it looks like it's 1-2% faster than v5.0! I'm mining with 1070 Ti's and get about 515-525 sol/s @66% power limit (4.37 sol/w) with +200 core +600 mem.
 Keep up the great work!
Same thing here! I'll be testing new 5.2 version today, and I'll report more detailed results later. So far it gives me ~510 sol/s on my 1070 Ti's (65% TDP and +200 +500, can't OC more due to high temps), and ~485 sol/s on 1070's (70% TDP, +200 +500). Also I'm currently on nicehash, got 0.9% rejected shares during 1 hour of work. That's pretty good rate, but more testing is required. Thank you, developer!
P.S. Almost forgot to mention one problem, it existed in version 5.1 too: upon start, miner shows an error
Code:
"Failed to read from the network: . An existing connection was forcibly closed by remote host"
It's probably because site bminer.me is blocked by my provider for some reason, and miner can't connect and get updates.
Post
Topic
Board Mining (Altcoins)
Re: [CMD] Equihash Miner Autorun (Watchdog) for Ewbf & Claymore & Dstm & CCminer
by
DarkOsa
on 22/01/2018, 15:28:24 UTC
Great script, thank you! Looking forward for bminer support, it really needs some watchdog features.
Post
Topic
Board Mining (Altcoins)
Re: [ANN] Bminer: a fast Equihash miner for CUDA GPUs (5.1.0)
by
DarkOsa
on 21/01/2018, 08:15:11 UTC
Quote from: realbminer on January 21, 2018, 07:56:19 AM
Quote from: DarkOsa on January 20, 2018, 09:45:06 AM
Quote from: realbminer on January 20, 2018, 08:38:29 AM
Quote from: DarkOsa on January 19, 2018, 02:44:53 PM
Hello, I'm seeing very good hashrate with this miner, but number of rejected shares is high too, 4-6 % on two different machines. Most common is "share above target", what does it mean?
P.S. On EWBF I have 0.5% rejected shares, so it's not OC or anything.

Which pool are you currently using? Will need more information to look into it.
Nicehash equihash servers, tried eu and usa, around the same number of rejected shares on both of them.
I like bminer, and I'd like to use it, but on nicehash sometimes it works fine for hours, and then starts to show rejected shares one by one, and miner even restarts because of it. If you need more info, tell me please.

Just to confirm, are you using 5.1.0?
Yes.