 Show Posts
|
|
Pages: [1]
|
I used 109 last night and it did the first dev fee at 1% but the second one it did 22.0877%.
[NOTICE ] 18/05/13 07:16:59 Shares: 1129 (A:99.65%, R:0.35%), Diff:0.612, 62.99MH/s, 124ms - OK
[NOTICE ] 18/05/13 07:17:08 Shares: 1130 (A:99.65%, R:0.35%), Diff:0.557, 62.99MH/s, 124ms - OK
[DEV ] 18/05/13 09:58:34 Mining some dev fee 1.00501%
[DEV ] 18/05/13 12:29:03 Done mining dev fee.
[DEV ] 18/05/13 12:29:03 Ratio: 22.0877%
[INFO ] 18/05/13 12:29:06 zealot/enemy-1.09a miner
[INFO ] 18/05/13 12:29:06 NVIDIA CUDA 9.1
[INFO ] 18/05/13 12:29:06 Dev fee is 1.0%
[NOTICE ] 18/05/13 12:29:06 MAIN POOL----------------------------------------------
It wasn't mining on my pool for 5+ hours. Seems like it just paused from 7:17 until 9:58. Then mined dev fee for 2 and a half hours. I'd post screen grabs but I think I'm too new to post pics.
In the last 24 hours now it has maintained a 1% dev fee. It did crash once in that time, but the dev fee it is reporting is 1%. My pool side hashrate looks right on the mining pool page. Are you solo mining ? No I'm mining btx on yiimp. Please do not overclock your GPU too much ! The program stuck and did not perform work with GPU from 07:17:08 , there are no blocks inside a dev fee too and after no block/accepted shares. We will add software watchdog in future releases, but again - please use recommended settings and OC only after miner work stable and LONG time. About defender... Miner is packed and Microsoft can't unpack the file and thinks, a virus there. Nothing new. There was no overclocking and power level was set to 80%. GPUs never went above 64 degrees. |
|
|
|
I used 109 last night and it did the first dev fee at 1% but the second one it did 22.0877%.
[NOTICE ] 18/05/13 07:16:59 Shares: 1129 (A:99.65%, R:0.35%), Diff:0.612, 62.99MH/s, 124ms - OK
[NOTICE ] 18/05/13 07:17:08 Shares: 1130 (A:99.65%, R:0.35%), Diff:0.557, 62.99MH/s, 124ms - OK
[DEV ] 18/05/13 09:58:34 Mining some dev fee 1.00501%
[DEV ] 18/05/13 12:29:03 Done mining dev fee.
[DEV ] 18/05/13 12:29:03 Ratio: 22.0877%
[INFO ] 18/05/13 12:29:06 zealot/enemy-1.09a miner
[INFO ] 18/05/13 12:29:06 NVIDIA CUDA 9.1
[INFO ] 18/05/13 12:29:06 Dev fee is 1.0%
[NOTICE ] 18/05/13 12:29:06 MAIN POOL----------------------------------------------
It wasn't mining on my pool for 5+ hours. Seems like it just paused from 7:17 until 9:58. Then mined dev fee for 2 and a half hours. I'd post screen grabs but I think I'm too new to post pics.
In the last 24 hours now it has maintained a 1% dev fee. It did crash once in that time, but the dev fee it is reporting is 1%. My pool side hashrate looks right on the mining pool page. Are you solo mining ? No I'm mining btx on yiimp. |
|
|
|
I used 109 last night and it did the first dev fee at 1% but the second one it did 22.0877%.
[NOTICE ] 18/05/13 07:16:59 Shares: 1129 (A:99.65%, R:0.35%), Diff:0.612, 62.99MH/s, 124ms - OK
[NOTICE ] 18/05/13 07:17:08 Shares: 1130 (A:99.65%, R:0.35%), Diff:0.557, 62.99MH/s, 124ms - OK
[DEV ] 18/05/13 09:58:34 Mining some dev fee 1.00501%
[DEV ] 18/05/13 12:29:03 Done mining dev fee.
[DEV ] 18/05/13 12:29:03 Ratio: 22.0877%
[INFO ] 18/05/13 12:29:06 zealot/enemy-1.09a miner
[INFO ] 18/05/13 12:29:06 NVIDIA CUDA 9.1
[INFO ] 18/05/13 12:29:06 Dev fee is 1.0%
[NOTICE ] 18/05/13 12:29:06 MAIN POOL----------------------------------------------
It wasn't mining on my pool for 5+ hours. Seems like it just paused from 7:17 until 9:58. Then mined dev fee for 2 and a half hours. I'd post screen grabs but I think I'm too new to post pics.
In the last 24 hours now it has maintained a 1% dev fee. It did crash once in that time, but the dev fee it is reporting is 1%. My pool side hashrate looks right on the mining pool page. |
|
|
|
Hello guys!
I'm having the following issues with my rig:
[INFO] 18/05/14 09:11:01 NVIDIA CUDA 9.1
[ERROR] 18/05/14 09:11:01 Unable to query number of CUDA devices! Is an nVidia driver installed?
Its an endless loop. In my case it is caused by power off/on(delay between 2 PSU's; GPU PSU turns on with small delay, so my system cannot see GPU's), to solve this i must simply restart the system.
My "monitoring device" will do it automatically IF process or network dies, so in this case i have to do it manually every time (because miner process wont exit with this error).
I need to write an argument that will exit my miner on this error.
will something like "--eexit 1" do the work or should it be something else?
Can you help me with code, so my miner will automatically exit on this error?
Thank you very much in advance!
Did you try adding a -d 0,1,2,3 for however many GPUs you have? I had to add that with 109. |
|
|
|
|
I used 109 last night and it did the first dev fee at 1% but the second one it did 22.0877%.
[NOTICE ] 18/05/13 07:16:59 Shares: 1129 (A:99.65%, R:0.35%), Diff:0.612, 62.99MH/s, 124ms - OK
[NOTICE ] 18/05/13 07:17:08 Shares: 1130 (A:99.65%, R:0.35%), Diff:0.557, 62.99MH/s, 124ms - OK
[DEV ] 18/05/13 09:58:34 Mining some dev fee 1.00501%
[DEV ] 18/05/13 12:29:03 Done mining dev fee.
[DEV ] 18/05/13 12:29:03 Ratio: 22.0877%
[INFO ] 18/05/13 12:29:06 zealot/enemy-1.09a miner
[INFO ] 18/05/13 12:29:06 NVIDIA CUDA 9.1
[INFO ] 18/05/13 12:29:06 Dev fee is 1.0%
[NOTICE ] 18/05/13 12:29:06 MAIN POOL----------------------------------------------
It wasn't mining on my pool for 5+ hours. Seems like it just paused from 7:17 until 9:58. Then mined dev fee for 2 and a half hours. I'd post screen grabs but I think I'm too new to post pics.
|
|
|
|
Enemy - Today at 2:00 PM on Discord Z-ENEMY VER 1.09a ( PUBLIC ) For Windows (Cuda 9.1)zealot/enemy-1.09a (z-enemy) From: Dk & Enemy - Kernels speed improvements 1.08 vs 1.09a, for all 9x0 and 10x0 GTX: x16r +5-8%, x16s +5-10%, bitcore +5-8%, xevan +5-20% ( vs basic public), phi + 2-3%, x17 (basic), vit (new algo). - Support new algos : Xevan (-a xevan) and Vitality (-a vit), recommended intensity for Xevan 19-20, for Vitality 19-21 - "Search mode" is enabled on 1.09a! This means that if you use a low diff you may see extra shares come through on your miner. You may see something like "2 shares" or "3 shares", up to 10+. This is a BONUS!.If you can find more than one share on your scan range you’ll find them all.If you have a bigger farm and use a higher diff you may also see the double or triple shares ,but it will be more rare. I still advise larger farms to continue to use higher diff. - Revised dev-fee mechanism. Now the miner does not break off connection with a pool and does not drop work of video cards. Everything works without switch-offs. - Now supporting failover pool! It is now possible to add additional pools incase your main pool loses stratum connection. Here is an example for your .bat file: z-enemy -a x16r -o stratum+tcp://ravenminer.com:6666 -u RFQXKVKpHMwyJ86YqQUJSZK1S8m8oRbC5h -p d=16 -o stratum+tcp://krawww-miner.eu:3636 -u RFQXKVKpHMwyJ86YqQUJSZK1S8m8oRbC5h -p d=3 - Duplicate output into log file (-l, --log=logfile.txt ) - Better error reporting. Now you see device number with its name if you encounter any cuda errors. - Pool latency. When submitting shares now you see pool's response time in milliseconds. https://mega.nz/#!RaBEELza!p4mtA2Ullr4V4Ocd-siNAaxZYHXmDhGQvC0ztYgTuQELinux ( Hive OS, Ubuntu ) Z-ENEMY VER 1.09a ( PUBLIC )Cuda 8.0 https://mega.nz/#!VDBEhYAI!j-WB0FzmyO3sBG_NXlmSI7apD89zmUHpgGdZpoAkRNQCuda 9.0 https://mega.nz/#!cDhgGBZS!DKsdS6HdgBr8-O2qvYkKnOya_RiY-N5-xTCwSqcY8_wCuda 9.1 https://mega.nz/#!VSY3QAQT!xnJ1e2lMgBKYPY_ytipNtEjpCTkWkj-UmJRcUJzWPBE[NOTICE ] 18/05/13 07:16:59 Shares: 1129 (A:99.65%, R:0.35%), Diff:0.612, 62.99MH/s, 124ms - OK [NOTICE ] 18/05/13 07:17:08 Shares: 1130 (A:99.65%, R:0.35%), Diff:0.557, 62.99MH/s, 124ms - OK [DEV ] 18/05/13 09:58:34 Mining some dev fee 1.00501% [DEV ] 18/05/13 12:29:03 Done mining dev fee. [DEV ] 18/05/13 12:29:03 Ratio: 22.0877% [INFO ] 18/05/13 12:29:06 zealot/enemy-1.09a miner [INFO ] 18/05/13 12:29:06 NVIDIA CUDA 9.1 [INFO ] 18/05/13 12:29:06 Dev fee is 1.0% [NOTICE ] 18/05/13 12:29:06 MAIN POOL---------------------------------------------- Something must be wrong with the dev fee... 22.0877% I'd post a screen shot but I think I'm too new. It wasn't mining on my pool for 5+ hours. |
|
|
|
Moderator please delete the topic. It hurts to watch.
I don't understand - why now? The blockchain is ready, wallet is ready, MasterNodes working. They can go to the exchanger and to sell PreMain quietly. Not understand!
not so fast buddy these ANN posts are needed to be alive years from now who knows these guys cant keep doing this they will get caught eventually greed is a desease The last scam I saw was Dual2s and the even deleted the ANN. Wonder why this is still up. |
|
|
|
Anyone have hash result for 1080ti?
and which exact brand, version card(s) you using, etc...
I have EVGA SC2 Gaming cards and they get about 24mh with ccminer 2.2.4 and 30mh with bitcore-spmod. They are running at 80% power which hovers around 200watts. Many mining pool pages will have a benchmark page where you can see some of this info. http://www.zpool.ca/bench?algo=bitcore&chip=549OK Thank for reply about what I expected I have EVGA 1080ti Blacks arrive tomorrow Q: You have set at 80%? I stopped SPMod2 cos over several equal elapsed time I was not getting any more BTX in real compared to CCMiner 2.2.4/ and Kaspersky told there were infected..I talked to Kaspersky main and they insisted. I am hearing most or all downloads out there carry file larger than original SPMod2 In afterburner I turn the power draw down to 80% or so for bitcore algo. It is not required but you will get better efficency hash per watt. You can add --plimit=200W into the miner .bat file but I just use afterburner. There is no doubt malware on some of the SPmod files floating around the internet. You could watch it with wireshark or something to see if it is legit. See who it is talking to. |
|
|
|
Anyone have hash result for 1080ti?
and which exact brand, version card(s) you using, etc...
I have EVGA SC2 Gaming cards and they get about 24mh with ccminer 2.2.4 and 30mh with bitcore-spmod. They are running at 80% power which hovers around 200watts. Many mining pool pages will have a benchmark page where you can see some of this info. http://www.zpool.ca/bench?algo=bitcore&chip=549 |
|
|
|
|
