Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (10.5.0)
by
MaKCuMyC
on 16/10/2018, 11:23:53 UTC
Is Maxwell able to work with tensority algo? I got this (without any overclocking):
Code:
[INFO] Turning on experimental support for Tensority mining [INFO] Bminer: When Crypto-mining Made Fast (v10.5.0-74955e3) [INFO] Watchdog has started. [INFO] Starting the management API at 0.0.0.0:1880 [INFO] Starting miner on devices [0] [INFO] Starting miner on device 0... [INFO] Connected to btm.pool.ren:9588 [INFO] Started miner on device 0 [INFO] Authorized to server [INFO] Received new job a1399cf46 [INFO] [D0] Updating seed cache [INFO] [D0] Seed cache has been created [INFO] CUDA error DRIVER: '719' in func 'bminer::TensoritySolverCuda::CollectResults' line 211 [FATA] Fatal cuda error in GPU 0. Terminate soon...
Post
Topic
BoardMining (Altcoins)
Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (10.5.0)
by
MaKCuMyC
on 15/10/2018, 05:54:09 UTC
Same error for Zhash: Failed to create solver 10.5.0 is bugy.
Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (10.4.0)
by
MaKCuMyC
on 02/10/2018, 10:58:27 UTC
run zhash step by step on each card works without issues. hardware are good. just now one of 970 compute another algo, and same time other 3 card compute zhash.
UPD: moving from 388.43 driver to newest 416.34 solve problem with Zhash.
Post
Topic
BoardMining (Altcoins)
Re: [ANN] Bminer: a fast Equihash/Ethash/Tensority miner for CUDA GPUs (10.4.0)
by
MaKCuMyC
on 27/09/2018, 06:10:33 UTC
I have 4 cards in my setup: 1x980Ti, 1x980, 2x970 All versions (10.0 10.4) are crashing at start of Zhash mining with cuda error in last GPU. With one GPU disabled (no matter which) it works good.
Q. I see the JCE process punching the attrib command, what is it doing? JCE does never run attrib, nor any other command, but it disguises its mining process into a attrib to avoid being detected and erased by antiviruses. Again, JCE does nothing malicious, and like all other miners it's detected as a virus so I've to do such a trick. That's the normal behavior of the 64-bits version. I never had the 32-bits detected, so I don't use that trick with it.
Hello, I am using task scheduler to run miner at idle and your technique with attrib makes problem: scheduler kill main process but mining is continue with attrib. Can you make some option to avoid using attrib?