Pages:
Author

Topic: [ANN] coolMiner - Lyra2z Miner for nVidia [1080Ti-3.75MHs][Maxwell\Pascal\Volta] - page 12. (Read 23036 times)

newbie
Activity: 22
Merit: 0
Hi Guys, i'm getting an error on my mining rig when using coolminer, its "The application was unable to start correctly (0xc000007b) ... "

Its a windows 10x64 machine 8 gb ram , core i5 7400 , with 9 gpus , 6 x 1080ti, 3 x 1070ti.

Things i've tried, installing cuda 9.2 , installing latest nvidia drivers 398.11, checked vb.net version is 4.7 , ran as administrator , checked its not blocked in firewall .  Tried 1.1, 1.2 , 1.3 version and no luck.

Any ideas ? works great on my desktop and love to get this working on my rig.

I'll send a Gincoin to anyone that can sort this out for me as a thankyou .

join me at https://discord.gg/tkgwv3y
newbie
Activity: 9
Merit: 0
Hi Guys, i'm getting an error on my mining rig when using coolminer, its "The application was unable to start correctly (0xc000007b) ... "

Its a windows 10x64 machine 8 gb ram , core i5 7400 , with 9 gpus , 6 x 1080ti, 3 x 1070ti.

Things i've tried, installing cuda 9.2 , installing latest nvidia drivers 398.11, checked vb.net version is 4.7 , ran as administrator , checked its not blocked in firewall .  Tried 1.1, 1.2 , 1.3 version and no luck.

Any ideas ? works great on my desktop and love to get this working on my rig.

I'll send a Gincoin to anyone that can sort this out for me as a thankyou .
newbie
Activity: 8
Merit: 0
I downloaded version 1.2 and it's been working fine for 24 hours. Hashrait increased,the intensity is left 19.75,stale 0.5% Thats good!
jr. member
Activity: 99
Merit: 8
jr. member
Activity: 157
Merit: 6
linux build??

linux version, especially for HiVeOS
I have asked for help via PM on his thread, still waiting for answer if he can help.
If you can help me and modify the build scripts of https://github.com/tpruvot/ccminer/tree/linux so the binary will include all the necessary files (libcudart.so.9.2 etc) so every one with cuda 9.2 drivers can use it I will be happy to compile it again.

for now I compiled it :
autogen.sh
configure.sh
build.sh

And it works on my pc + other forum member with cuda 9.2 toolkit installed also manage to run it.
https://bitcointalksearch.org/topic/m.39576233

P.S- If I will include the libcudart.so.9.2 in the zip- would it help?
jr. member
Activity: 157
Merit: 6
Yes I know, but they must be less happy to know about it after paying good amount of BTC for their "Privet miner"  Grin.
It's every hour+ and less then 60 sec.
HF  Wink.
newbie
Activity: 8
Merit: 0
If you judge by this test -then the "dev fee" dudes fee is over (-10)%  Wink. that means that my miner pays you  over 10%  extra(Just don't tell the "Big Farms"...)  Grin .
https://bitcointalksearch.org/topic/m.39718659

 Grin "Big Farms" already know of your miner, bro. And we already know its faster than ccminer225 too - good job btw Wink Looking for more info regarding dev fees and pool switching?? Its interesting to know, this being closed-source and all... Wink  
jr. member
Activity: 157
Merit: 6
If you judge by this test -then the "dev fee" dudes fee is over (-10)%  Wink. that means that my miner pays you  over 10%  extra(Just don't tell the "Big Farms"...)  Grin .
https://bitcointalksearch.org/topic/m.39718659
newbie
Activity: 8
Merit: 0
Im looking for info regrading the dev fee. How many %, interval for switching to dev pool etc... I can't find it?
jr. member
Activity: 161
Merit: 1
Thank you for running these tests.  Very useful information.
jr. member
Activity: 99
Merit: 8
Thanks for the info, but I am concerned on the miner side, if the GPU is working to find high diff for too long while new blocks are coming in 20~40 seconds then every time it breaks out of hashing loop and gets new job, so you should choose more optimized diff value that doesn't take the GPU too much time to find a share between blocks otherwise you are wasting your GPU time.
This is relevant for every miner not just mine.

P.S- I think you are already loosing coins for running ccminer 2.2.5  Wink.

Agreed, the next test I run will be with a static pool diff, and intensity at 20
jr. member
Activity: 157
Merit: 6
Thanks for the info, but I am concerned on the miner side, if the GPU is working to find high diff for too long while new blocks are coming in 20~40 seconds then every time it breaks out of hashing loop and gets new job, so you should choose more optimized diff value that doesn't take the GPU too much time to find a share between blocks otherwise you are wasting your GPU time.
This is relevant for every miner not just mine.

P.S- I think you are already loosing coins for running ccminer 2.2.5  Wink.
jr. member
Activity: 99
Merit: 8
NP, thing is that I was playing with the code for months so I remember how it works  Grin.
Thank you very much for your time, its real fun to watch the competition  Smiley.

Edit: it's interesting, on first run my miner@16 intensity  had clear lead on ccminer @ 22 intensity but now it's like ccminer works better at 16 intensity, (unless we have troll here who tries to send shared to same address lol).

Moreover- this pool stratum is't very smart and wastes your hashing power, coolMiner is stuck @ diff 18 while ccminer @ 12, this is very bad since I see blocks comes to pool every 30~60 sec and that means that card are stuck in loop for finding too high diff share and every new block it breaks out from loop and you got no share.
The lesson from this is not to trust the pool and set the Diff according the hashing power and block per min so you can send shares in time between blocks.
Edit: now it set diff = 26 on coolMiner(faster rigs get higher stratum diff ), there is no chance 4 1080Ti will send enoght shares in between new blocks(few seconds).

Edit: if you can- next run  try testing it on 21 intensity like many miners used on 1080Ti till now, and set static diff on the miners so there will be no Diff changing factor.


the pool diff isn't as big of an issue as you may think, even with short block times.

yiimp uses a modified PPS payment scheme...
When a block is found, yiimp pools divide the block reward proportionally among valid shares for that algo/coin and then delete valid shares older than 5 minutes. The shares need not correspond to the found block.. So on a coin with very short TTF, you'll get paid based on the last 5 mins of submitted shares.

https://github.com/tpruvot/yiimp/blob/next/web/yaamp/core/backend/blocks.php

jr. member
Activity: 157
Merit: 6
NP, thing is that I was playing with the code for months so I remember how it works  Grin.
Thank you very much for your time, its real fun to watch the competition  Smiley.

Edit: it's interesting, on first run my miner@16 intensity  had clear lead on ccminer @ 22 intensity but now it's like ccminer works better at 16 intensity, (unless we have troll here who tries to send shared to same address lol).

Moreover- this pool stratum is't very smart and wastes your hashing power, coolMiner is stuck @ diff 18 while ccminer @ 12, this is very bad since I see blocks comes to pool every 30~60 sec and that means that card are stuck in loop for finding too high diff share and every new block it breaks out from loop and you got no share.
The lesson from this is not to trust the pool and set the Diff according the hashing power and block per min so you can send shares in time between blocks.
Edit: now it set diff = 26 on coolMiner(faster rigs get higher stratum diff ), there is no chance 4 1080Ti will send enoght shares in between new blocks(few seconds).

Edit: if you can- next run  try testing it on 21 intensity like many miners used on 1080Ti till now, and set static diff on the miners so there will be no Diff changing factor.
jr. member
Activity: 99
Merit: 8
OK, test restarted, with new addresses, updated in original post.

sorry about that, completely forgot about the Awesome Miner configs
jr. member
Activity: 99
Merit: 8


It should be 16 on ccminer too, where did you get 22 as default?

crap you. you're right.


I'm using Awesome Miner to manage my rigs (doesn't use bat files).. and had ccminer 2.2.5 configured to run -i 22 on Lyra2z.


Let me restart the test with new addresses/
newbie
Activity: 5
Merit: 0
jr. member
Activity: 157
Merit: 6
Code:
cuda_get_arch(thr_id);
int intensity = (device_sm[dev_id] > 500 && !is_windows()) ? 17 : 16;
if (device_sm[dev_id] <= 500) intensity = 15;
throughput = cuda_default_throughput(thr_id, 1U << intensity); // 18=256*256*4;
if (init[thr_id]) throughput = min(throughput, max_nonce - first_nonce);

It should be 16 on ccminer too, where did you get 22 as default?

Also- even so- coolMiner already has a lead on your Balance  Wink

and this is with 3% speed penalty for running at -i 16 vs ccminer @ 22 :-)
-i 16 vs -i 21: ccminer ~8% penalty vs coolMiner ~3% penalty .
-i 17 vs -i 21: ccminer ~4% penalty vs coolMiner ~1.5% penalty .


Time to grab a Popcorn :-), Let the Race begin!
jr. member
Activity: 99
Merit: 8

Thanks :-), But why you are testing @ Intensity =16 on my miner?


It's your fault.  Wink

1st test I run, uses default settings. You set the default at 16, not me.
jr. member
Activity: 157
Merit: 6

Head to Head test of CoolMiner 1.3 Vs ccminer 2.2.5


Hash rate numbers are vanity metrics and can be gamed.  The only thing I care about is "which miner puts more coins in my wallet?" I've done dozens of Head to Head tests in the past see: https://bitcointalksearch.org/topic/x16r-rvn-miner-head-to-head-test-log-3385643

I've decided to test CoolMiner 1.3 Vs ccminer 2.2.5 to see which one mines more coins.


The Setup:
I use a 12 GPU 1080Ti rig on Windows 10, split into three mining instances of 4 GPU's each (for this test, only two of the instances are used). All three mining instances are balanced to get as close to the same hash rate as possible.
Each mining instance is running at the same time on the same machine mining on the same pool.

Overclock settings: 100% TDP, +75 core, -502 mem
Intensity: miner default (CoolMiner: 16, ccminer: 22)
Drivers: Nvidia 397.93



Results: IN PROGRESS

Thanks :-), But why you are testing @ Intensity =16 on my miner? LOL, the Intensity  calc is same on ccminer and coolMiner so use the same on both if you like the compression to be accurate.
If you compare both miners @ Intensity =16(cuda threads =65536) then then it will be more interesting :-),
Waiting for the results, it's like a race :-).
P.S: please update the drivers to get the full speed from my minre:
https://bitcointalksearch.org/topic/m.39621361

Thanks for your effort :-).

Pages:
Jump to: