The new version v16.0.3 seems to have a problem. Bminer crashes on all my rigs, mining Cuckaroo29m


The prior version v16.0.2 runs perfect, with the same configuration.

crash on C31
is it way to turn off api?

Confirmed broken c31 support.

Same ... broken c31.

It seems that dev is not interested in C31 algo. To bad.

We're pleased to release Bminer 16.0.6.

* Improve the performance of Cuckaroo29m miner.
* Fix the regression that the Cuckatoo Cuckoo miners failed to start.
* Fix the performance regression of Cuckaroo29m under Windows.
* Fix the compatibility issues on Windows system.

Please see https://www.bminer.me/releases/ for more details.

Happy mining.

On latest version:

> [INFO] [2020-02-18T19:48:45+05:30] Bminer: When Crypto-mining Made Fast (v16.0.6-137dbe6)
> [INFO] [2020-02-18T19:48:45+05:30] Watchdog has started.                       
> [INFO] [2020-02-18T19:48:45+05:30] Detected CUDA platform                       
> [FATA] [2020-02-18T19:48:45+05:30] Failed to initialize the CUDA platform: CudaError: Could not initialize the NVML library

OS: Microsoft Windows 10 Pro 64-bit
nVidia driver version: 442.19

Well, then you need to look for another bminer that will support C31 algo

Same here, never been able to run it for the past few months

To whoever it may concern(bminer devs):
Did extensive 48hr test comparing your miner(may it be called Miner1) with another popular grin miner(may it be called Miner2).
Hardware used: 10 NVIDIA GTX 1070 8Gb 125 core offset, 900 memory offset, 112W powerlimit - OS linux based.
Pool used: Grinmint
Miner1 reported 9.25g/s, average accepted hashrate was ~8g/s
Miner2 reported 8.74g/s, average accepted hashrate was ~8.3g/s

Stale shares were in ordinary rate of <2%, same latency to pool.
Even with slightly higher devfee and slightly lower hashrate, Miner2 performed better poolside.
There is definitely something not working correctly in Miner1 solver. Bminer developers can feel free contact me via PM to perform tests or share results.