cryptoyes
Member

Offline
Activity: 297
Merit: 10
|
 |
July 15, 2019, 12:13:37 AM |
|
yes. we will support the GRIN mid-July hard fork. You should release a beta before the fork. There are pools running the new cuckarood29 so that we can test and deploy (otherwise there's bound to be a surge of issues for everyone involved)
|
|
|
|
pinoli
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 15, 2019, 10:18:47 PM |
|
hey, I am getting this error when trying to mine on Windows 10 with an ASUS Arez Strix Vega 56 8GB OpenCL Error '-11' in func 'bminer::cuckoo::CuckooStyleSolverCLBase::InitializeCLEnvironment' line 78 I am on bminer 15.5.3 latest version, that otherwise works flawlessly on another rig with only GTX 1070. I have seen other users reporting it here in this thread and on Reddit as well, but I found no solution. Can you please help me solve this realbminer? Thanks for the great work.
|
|
|
|
strideynet2
Newbie
Offline
Activity: 7
Merit: 0
|
 |
July 16, 2019, 09:14:55 AM |
|
Hi, Many thanks for a great miner. Will you release an update with Cuckarood29 support before the fork that is only 1470 blocks away  I need to know if to keep my miners on BMiner or switch to GMiner before the fork 
|
|
|
|
realbminer (OP)
|
 |
July 16, 2019, 04:38:31 PM |
|
Hi, Many thanks for a great miner. Will you release an update with Cuckarood29 support before the fork that is only 1470 blocks away  I need to know if to keep my miners on BMiner or switch to GMiner before the fork  yes, we will support it, we will release ASAP.
|
When Crypto-mining Made Fast. @realbminer on TWTR
|
|
|
realbminer (OP)
|
 |
July 16, 2019, 04:39:03 PM |
|
yes. we will support the GRIN mid-July hard fork. You should release a beta before the fork. There are pools running the new cuckarood29 so that we can test and deploy (otherwise there's bound to be a surge of issues for everyone involved) thanks for the suggestion.
|
When Crypto-mining Made Fast. @realbminer on TWTR
|
|
|
pinoli
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 17, 2019, 10:14:02 AM |
|
Hello, I have just upgraded bminer to 15.7.0 in order to mine Grin after the hard fork. Unfortunately, after updating bminer, I always get this error mesasage: CUDA error DRIVER: '500' in func 'bminer::cuckoo::Cuckaroo29dSolverCudaBase::InitializeCudaEnvironment' line 81 This miner (3x GTX 1070) has been working for months without a problem, so I really don't know whats going on. Does it happen to some of you as well? Thanks
|
|
|
|
realbminer (OP)
|
 |
July 17, 2019, 10:44:39 AM |
|
We're pleased to release Bminer 15.7.0. The release provides: *Support the cuckaroo29d algorithm. Please see https://www.bminer.me/releases/ for more details. Happy mining.
|
When Crypto-mining Made Fast. @realbminer on TWTR
|
|
|
JFoxOne
Member

Offline
Activity: 640
Merit: 56
minerstat
|
 |
July 17, 2019, 11:27:49 AM |
|
Which one is correct? - cuckaroo29://
- cuckaroo29d://
- cuckarood29://
|
|
|
|
max64rus
Newbie
Offline
Activity: 5
Merit: 0
|
 |
July 17, 2019, 01:41:01 PM |
|
Which one is correct? - cuckaroo29://
- cuckaroo29d://
- cuckarood29://
Correct this: cuckaroo29d:// But doesn't work!!! WTF?! Goldminer is slow but work with new grin 29d. Use this miner before bminer will fix error Use gminer, it gives the maximum hashrate
|
|
|
|
laik2
|
 |
July 17, 2019, 01:54:26 PM |
|
Which one is correct? - cuckaroo29://
- cuckaroo29d://
- cuckarood29://
Correct this: cuckaroo29d:// But doesn't work!!! WTF?! Goldminer is slow but work with new grin 29d. Use this miner before bminer will fix error Use gminer, it gives the maximum hashrate I compared all 4 miners currently available for cuckaroo29d using single 1080ti(while encoding at the same time). gfxoffset: +125, memoffset: + 1000(windows +500), pwr limit: 160W bminer: 5.44(avg)-5.78(peak) gminer: 5.25(avg)-5.39(peak) nbminer: 5.22(avg)-5.46(peak) lolminer(opencl only): 4.23(avg)-4.24(peak)
|
|
|
|
casper77
Legendary
Offline
Activity: 2898
Merit: 1036
|
 |
July 17, 2019, 02:18:15 PM |
|
Which one is correct? - cuckaroo29://
- cuckaroo29d://
- cuckarood29://
Correct this: cuckaroo29d:// But doesn't work!!! WTF?! Goldminer is slow but work with new grin 29d. Use this miner before bminer will fix error Use gminer, it gives the maximum hashrate I compared all 4 miners currently available for cuckaroo29d using single 1080ti(while encoding at the same time). gfxoffset: +125, memoffset: + 1000(windows +500), pwr limit: 160W bminer: 5.44(avg)-5.78(peak) gminer: 5.25(avg)-5.39(peak) nbminer: 5.22(avg)-5.46(peak) lolminer(opencl only): 4.23(avg)-4.24(peak) which freqs do you have in stock ? and why so low PL with default 280W ?
|
|
|
|
max64rus
Newbie
Offline
Activity: 5
Merit: 0
|
 |
July 17, 2019, 02:25:26 PM |
|
Which one is correct? - cuckaroo29://
- cuckaroo29d://
- cuckarood29://
Correct this: cuckaroo29d:// But doesn't work!!! WTF?! Goldminer is slow but work with new grin 29d. Use this miner before bminer will fix error Use gminer, it gives the maximum hashrate I compared all 4 miners currently available for cuckaroo29d using single 1080ti(while encoding at the same time). gfxoffset: +125, memoffset: + 1000(windows +500), pwr limit: 160W bminer: 5.44(avg)-5.78(peak) gminer: 5.25(avg)-5.39(peak) nbminer: 5.22(avg)-5.46(peak) lolminer(opencl only): 4.23(avg)-4.24(peak) downgrade 1080ti to 1070ti? nonsense
|
|
|
|
laik2
|
 |
July 17, 2019, 02:33:56 PM |
|
Its used for encoder, not for miner. Proves that bminer is more memory intensive than others. In most cases the Pill can boost it more than with others.
|
|
|
|
max64rus
Newbie
Offline
Activity: 5
Merit: 0
|
 |
July 17, 2019, 02:41:57 PM |
|
Its used for encoder, not for miner. Proves that bminer is more memory intensive than others. In most cases the Pill can boost it more than with others.
Your test is incompatible with reality, but in reality the bminer loses to the gminer and nbminer
|
|
|
|
realbminer (OP)
|
 |
July 17, 2019, 03:29:26 PM |
|
We're pleased to release Bminer 15.7.1. The release provides: * Improve the performance of the Cuckaroo29d algorithm. * Fix the issue that the Cuckaroo29d failed to start for Turing-based cards. Please see https://www.bminer.me/releases/ for more details. Happy mining.
|
When Crypto-mining Made Fast. @realbminer on TWTR
|
|
|
laik2
|
 |
July 17, 2019, 04:29:41 PM |
|
Its used for encoder, not for miner. Proves that bminer is more memory intensive than others. In most cases the Pill can boost it more than with others.
Your test is incompatible with reality, but in reality the bminer loses to the gminer and nbminer Here are some reality tests: MSI Armor GTX 1070 - core +100, mem +900(+450 windows), PL: 130W bminer: Hash - 5.52 G/s, Fidelity - 1.973 nbminer: Hash - 1: 5.23 g/s , Fidelity - 1: 2.356 gminer: Hash - GPU1 5.21 G/s , Fidelity - GPU1 1.773 I will repeat again, bminer is tolerant to memory optimizations while other miners seem more compute bound.
|
|
|
|
dalibord
Jr. Member
Offline
Activity: 53
Merit: 1
|
 |
July 17, 2019, 05:36:17 PM |
|
[INFO] [2019-07-17T19:34:14+02:00] Bminer: When Crypto-mining Made Fast (v15.7.1-1c421a5) [INFO] [2019-07-17T19:34:14+02:00] Detecting platform [INFO] [2019-07-17T19:34:22+02:00] Watchdog has started. [INFO] [2019-07-17T19:34:22+02:00] Starting miner on 1 devices [INFO] [2019-07-17T19:34:22+02:00] Starting the management API at 127.0.0.1:1880 [INFO] [2019-07-17T19:34:22+02:00] Free memory 6721.42 MB available on device (#0). Selecting normal solver. [INFO] [2019-07-17T19:34:22+02:00] Operating in the thread safe mode for GPU 0 [INFO] [2019-07-17T19:34:22+02:00] Starting miner on device 0... [INFO] [2019-07-17T19:34:23+02:00] Started miner on device 0 [INFO] [2019-07-17T19:34:23+02:00] CUDA error DRIVER: '1' in func 'bminer::cuckoo::Cuckaroo29dSolverCudaBase::CollectEdges' line 463 [FATA] [2019-07-17T19:34:23+02:00] Fatal cuda error in GPU 0. Terminate soon...
[WARN] [2019-07-17T19:34:23+02:00] Miner died! It will be restarted soon...
Gtx 1070, win 10, drivers 431.36.
|
|
|
|
dortortz
Newbie
Offline
Activity: 7
Merit: 0
|
 |
July 17, 2019, 08:07:42 PM |
|
I keep getting rejected shares and then it restarts and does the same. I don't know what I'm doing wrong. I have a gtx 1060 mining to f2pool. All was good till the update. Did the update but still getting rejected shares. F2pool says Bminer only works for c31 for now is that right?
|
|
|
|
pinoli
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 18, 2019, 12:31:55 AM |
|
[INFO] [2019-07-17T19:34:14+02:00] Bminer: When Crypto-mining Made Fast (v15.7.1-1c421a5) [INFO] [2019-07-17T19:34:14+02:00] Detecting platform [INFO] [2019-07-17T19:34:22+02:00] Watchdog has started. [INFO] [2019-07-17T19:34:22+02:00] Starting miner on 1 devices [INFO] [2019-07-17T19:34:22+02:00] Starting the management API at 127.0.0.1:1880 [INFO] [2019-07-17T19:34:22+02:00] Free memory 6721.42 MB available on device (#0). Selecting normal solver. [INFO] [2019-07-17T19:34:22+02:00] Operating in the thread safe mode for GPU 0 [INFO] [2019-07-17T19:34:22+02:00] Starting miner on device 0... [INFO] [2019-07-17T19:34:23+02:00] Started miner on device 0 [INFO] [2019-07-17T19:34:23+02:00] CUDA error DRIVER: '1' in func 'bminer::cuckoo::Cuckaroo29dSolverCudaBase::CollectEdges' line 463 [FATA] [2019-07-17T19:34:23+02:00] Fatal cuda error in GPU 0. Terminate soon...
[WARN] [2019-07-17T19:34:23+02:00] Miner died! It will be restarted soon...
Gtx 1070, win 10, drivers 431.36.
I too keep getting the same error as daliboard CUDA error DRIVER: '1' in func 'bminer::cuckoo::Cuckaroo29dSolverCudaBase::CollectEdges' line 463 miner is 3x ASUS Strix GTX 1070 8GB with CUDA 10.1 and Drivers 431.36 on Windows 10 bminer is 15.7.1 is there anything I can do to fix this? thanks @realbminer
|
|
|
|
JacksCoins
Newbie
Offline
Activity: 5
Merit: 0
|
 |
July 18, 2019, 01:16:15 AM |
|
[INFO] [2019-07-17T19:34:14+02:00] Bminer: When Crypto-mining Made Fast (v15.7.1-1c421a5) [INFO] [2019-07-17T19:34:14+02:00] Detecting platform [INFO] [2019-07-17T19:34:22+02:00] Watchdog has started. [INFO] [2019-07-17T19:34:22+02:00] Starting miner on 1 devices [INFO] [2019-07-17T19:34:22+02:00] Starting the management API at 127.0.0.1:1880 [INFO] [2019-07-17T19:34:22+02:00] Free memory 6721.42 MB available on device (#0). Selecting normal solver. [INFO] [2019-07-17T19:34:22+02:00] Operating in the thread safe mode for GPU 0 [INFO] [2019-07-17T19:34:22+02:00] Starting miner on device 0... [INFO] [2019-07-17T19:34:23+02:00] Started miner on device 0 [INFO] [2019-07-17T19:34:23+02:00] CUDA error DRIVER: '1' in func 'bminer::cuckoo::Cuckaroo29dSolverCudaBase::CollectEdges' line 463 [FATA] [2019-07-17T19:34:23+02:00] Fatal cuda error in GPU 0. Terminate soon...
[WARN] [2019-07-17T19:34:23+02:00] Miner died! It will be restarted soon...
Gtx 1070, win 10, drivers 431.36.
I too keep getting the same error as daliboard CUDA error DRIVER: '1' in func 'bminer::cuckoo::Cuckaroo29dSolverCudaBase::CollectEdges' line 463 miner is 3x ASUS Strix GTX 1070 8GB with CUDA 10.1 and Drivers 431.36 on Windows 10 bminer is 15.7.1 is there anything I can do to fix this? thanks @realbminer Having same issues as well. Been using Bminer for months already and did not have any issues. For the hardfork i downloaded the latest version which was 15.7.0 at that time. This version gives a slightly different error message: CUDA error DRIVER: '500' in func 'bminer::cuckaroo29dSolverCudaBase::InitializeCudaEnvironment' line 81. So i downloaded the one posted today which is 15.7.1 and it doesnt give any errormessages at all it just says: Miner Died! It will be restarted soon. Which keeps repeating. Running on windows 10 with CUDA9 and 1x GTX1080-FE. Some guidance would be appreciated. Thanks!
|
|
|
|
|