Can this coin be mined with Nvidia?
sure. title says "cuda gpus", which is nvidia. 
Topic: [ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9 - page 108. (Read 148347 times)
April 04, 2018, 12:56:53 PM
April 04, 2018, 11:55:49 AM
I have used bminer for some time now and have had no issues with it. My impression is that it is faster than competitors, and with 6.0 far fewer rejected shares. Several people on this thread and elsewhere have done systematic tests.
April 04, 2018, 07:31:49 AM
Can this coin be mined with Nvidia?
April 04, 2018, 02:35:56 AM
bminer doesn't work with 13 GPU ? ( Error initializing the CUDA context. )
April 04, 2018, 02:06:04 AM
This miner is much more stable than the DSTM. I have 6*1080Ti 4800sol. Thanks to the developer
April 03, 2018, 09:14:06 AM
Firmware.bin stores the license information of bminer, including for example where bminer should mine its devfee.
April 02, 2018, 04:21:07 AM
Hi guys. How can i choose single device for mining? In ewbf that was --dev #number, in bminer i dont found. Thank you.
Its there:
https://www.bminer.me/references/
April 02, 2018, 04:16:00 AM
Hi guys. How can i choose single device for mining? In ewbf that was --dev #number, in bminer i dont found. Thank you.
April 02, 2018, 03:54:23 AM
It contains data that can be updated from devs web site, for example if he decide to change the dev address and pool he can do it remotely without forcing the users to update the miner to a newer version. Its like auto updater for some parts of his miner.
April 01, 2018, 10:49:04 PM
in response to anyone using bminer just because its more stable than dstm or vice versa. theres another option which i feel is way better than expecting the mining program's watchdog to work 100% bug free.
https://bitcointalksearch.org/topic/cmd-farmwatchbot-ewbf-claymore-bminer-dstm-cc-eth-castxmr-phoenix-2071108
arcefawn made a nice open source FREE watchdog script that works for several miners. its a simple script that you edit how you want to work (he has simple instructions in the cfg file.) very straight forward and works with dstm, bminer, ewbf, claymore, ccminer, ethminer, phoenix, cast xmr, and hes adding more all the time.
his script monitors the mining console and resets the miner if it crashes. it monitors your hashrate so if its reporting lower like some gpu's are reporting too low of a hashrate, it can restart the miner. it can reload your overclocking profiles if you set it to. you can set a schedule on how often to restart the miner or the pc. you also has pool fallover support to 5 pools set in your cfg file so if you lose connection you're not mining for nothing.
its really a great script and the guy is nice enough to give it away for free. totally worth sending him a donation and then not having to worry about your miner(s) going down
https://bitcointalksearch.org/topic/cmd-farmwatchbot-ewbf-claymore-bminer-dstm-cc-eth-castxmr-phoenix-2071108
arcefawn made a nice open source FREE watchdog script that works for several miners. its a simple script that you edit how you want to work (he has simple instructions in the cfg file.) very straight forward and works with dstm, bminer, ewbf, claymore, ccminer, ethminer, phoenix, cast xmr, and hes adding more all the time.
his script monitors the mining console and resets the miner if it crashes. it monitors your hashrate so if its reporting lower like some gpu's are reporting too low of a hashrate, it can restart the miner. it can reload your overclocking profiles if you set it to. you can set a schedule on how often to restart the miner or the pc. you also has pool fallover support to 5 pools set in your cfg file so if you lose connection you're not mining for nothing.
its really a great script and the guy is nice enough to give it away for free. totally worth sending him a donation and then not having to worry about your miner(s) going down
Thanks for sharing!
April 01, 2018, 09:54:58 PM
4. It might be a good idea or not, but I think it will be a bit more transparent if next to the accepted shares, rejected shares you included a new count named Dev Shares then we could keep track and see if it really is a 2% what you are taking away.
4. Yes, I am open to this idea. But simply counting the number of shares will just confuse people due to potentially different difficulties of shares. Once I figured out a right way to implement this, I will do it.
For a more accurate number, that accounts for the difference in difficulties, a few calculations can be introduced.
1) "avgDevD", the average difficulty of the developers shares.
2) "avgMnrD", the average difficulty of the miners shares.
3) "%diffD", the percent difference in difficulty or more precisely, the % increase or decrease in the average difficulty of the miners shares compared to the average difficulty of the developers shares. It looks like this: %diffD = (avgDevD / avgMnrD) / avgMnrD * 100
The "avgDevD" and "avgMnrD" values can just go into the bminer.log to lessen console clutter but with the "%diffD" value added to the console, the following equations can be used for verification and should increase confidence in the code.
Dev Shares = 0.02 * Accepted Shares * (1 + %diffD / 100)
Miner Shares = Accepted Shares - Dev Shares
Maybe there's an easier method but this one is not terribly complicated.
Thank you for your suggestions. We are currently working on a major release of Bminer which will add in a new hash algorithm. We will improve Bminer based on your suggestions after that release is out.
April 01, 2018, 09:44:18 PM
April 01, 2018, 09:43:33 PM
Hi
I have been using bminer on 2x 12 1070ti rigs with no issue.
I have setup another rig with 9x 1080tis. The miner constantly restarts every 30mins or so. The last line in the console is "killed".
Previously when I had a riser fail while running bminer, it stated exactly which gpu/riser it could not get temperature from.
The restarts do not happen with other softwares.
I am using simple mining and mining on nicehash.
I have been using bminer on 2x 12 1070ti rigs with no issue.
I have setup another rig with 9x 1080tis. The miner constantly restarts every 30mins or so. The last line in the console is "killed".
Previously when I had a riser fail while running bminer, it stated exactly which gpu/riser it could not get temperature from.
The restarts do not happen with other softwares.
I am using simple mining and mining on nicehash.
Can anybody assist with the above
Can't assist you on how to solve the problem, but can report I am having the same problem or similar problem to yours also on a nine card rig. I am also using smos.
Mine is a 9x 1070ti rig. It took me a while to realise I had a problem. I was not paying attention to the console.
Whats happening with mine is that the rig loads up as normal on smos with the slow start from Bminer, then when all GPUs are running at full speed, GPU 8 starts dropping off slowly, the sol rate eventually drops down to zero, the rig keeps running for a while and but then I start getting the restarts about every 30 minutes or so. When I revert back to Bminer v5.5.0 the problem goes away, the rig runs normally. I tried dialing back the overclock on GPU 8 to see if this was the problem but that didn't work either. So for now just working v5.5.0. on this rig.
Funny thing is I have another 9 card rig with identical setup to the first, same mobo same power supply etc. Except this is a mixed card rig, 6x 1070 and 3x 1070t1 but this rig runs normally on Bminer v6.0.0.
I have a third 6x 1070ti card rig and this runs problem free as well with v6.0.0.
Just go back to v5.5.0 is my fix for the moment anyhow.
Thanks for feedback. Are you mining nicehash by any chance?
The restarts have somehow reduced to 1 per day.
I have now noticed that my rig shows offline on the pool as well as on simplemining monitor console but strangely the system is still drawing +750watts off power during this state, as per my energy meter. Full draw on this rig is - +2150watts. This would mean that my system is in some kind on halt state? Is some watchdog initiating?
@minebomb @Roby1
Thank you for the feedback. How many memory the rig has? This information will help me diagnose the problem and fix it in the next release.
@realbminer
Thanks for response.
I am using 4gb Ram and a celeron cpu on simplemining.
Thanks await your feedback
We improved the miner stability in the version 6.1. Hope it will resolve your issue. If the issue still persists, you may want to check your raiser cables in your rigs.
April 01, 2018, 09:23:07 PM
what is firmware.bin?
April 01, 2018, 09:20:40 AM
Anyone see positive results from 6.1.0?
Yes - this build with Fuerboos trojan.
Really? This version has that virus in it??
This version and all previous versions of bminer are clean. Like other miners, Bminer uses DRM techniques to prevent itself to be tempered. Anti-virus software sometimes misclassifies it.
Please see https://www.bminer.me/faq/#why-does-windows-defender-report-bminer-as-virus-malicious-software
But prev.version (0.55) was not detected like Fuerboos.
March 31, 2018, 11:50:56 PM
Anyone see positive results from 6.1.0?
Slightly higher sol/s on my rigs (~0.5%, 1080Ti + 1070) comparing to 6.0.
I now use bminer to mine ZEC again not because ZEC price recovered, but because ETH price fell...
When will the stupid market recover? Could these miners lower their devfee to give us some breathing room in this difficult time?
March 31, 2018, 11:38:27 PM
Anyone see positive results from 6.1.0?
Yes - this build with Fuerboos trojan.
Really? This version has that virus in it??
This version and all previous versions of bminer are clean. Like other miners, Bminer uses DRM techniques to prevent itself to be tempered. Anti-virus software sometimes misclassifies it.
Please see https://www.bminer.me/faq/#why-does-windows-defender-report-bminer-as-virus-malicious-software
March 31, 2018, 10:08:28 AM
Anyone see positive results from 6.1.0?
Yes - this build with Fuerboos trojan.
Really? This version has that virus in it??
March 31, 2018, 09:37:16 AM
Anyone see positive results from 6.1.0?
Yes - this build with Fuerboos trojan.
March 31, 2018, 08:27:19 AM
Anyone see positive results from 6.1.0?
Jump to: