Bitcoin Forum
June 17, 2024, 09:44:44 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 12, 2018, 08:04:53 PM
Does EWBF need a large virtual memory swap like Claymore does or can I reduce the Virtual Memory size to reclaim some badly needed disk space?

My understanding is that claymore's large virtual memory requirement is associated with DAG, so no,you don't need a large swap file for EWBF as there is no DAG. I might be wrong though.

For more then 3 GPU - large virtual memory is required - 16 000 MB minimum.

I hope you know what you are talking about. Care to explain why?

I read that somewhere - If you are using multiple GPUs, recomended settings for stability is 16 000 MB or more.

Also when I try to connect to my PC more then 3 GPUs, miner was unstable all the time (OS Windows aswell).

Yes, you have to use at least 16 000 000 MB. If windows goes unstable, you might have overclock your cards too much. And yes, go and disable the windows updates.. .This thing f*cked up all my rigs yesterday...

Just because you both repeat something you've heard or read somewhere without understanding of what that means - it doesn't make it true. Without referencing the source (so that we can evaluate the info ourselves) you are just spreading rumours.
I like this explanation https://github.com/nicehash/NiceHashMinerLegacy/issues/6, that suggests that swap file for Claymore is taken by mirroring DAG from GPU to virtual memory. There is no DAG on GPU for equihash, and therefore my understanding is that virtual memory is not needed for EWBF. I'm not a big expert and may be absolutely wrong. Happy to hear from a specialist; not that this issue bothers me much, but since the question was raised - let's find the answer.

Me and my friend (from same town) just had same experience. Unstable windows during mining Zcash with EWBF. After virtual memory was rise to 16 000 MB or more - no more problems with stability. End of story for me.
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 10, 2018, 01:46:14 PM
Does EWBF need a large virtual memory swap like Claymore does or can I reduce the Virtual Memory size to reclaim some badly needed disk space?

My understanding is that claymore's large virtual memory requirement is associated with DAG, so no,you don't need a large swap file for EWBF as there is no DAG. I might be wrong though.

For more then 3 GPU - large virtual memory is required - 16 000 MB minimum.

I hope you know what you are talking about. Care to explain why?

I read that somewhere - If you are using multiple GPUs, recomended settings for stability is 16 000 MB or more.

Also when I try to connect to my PC more then 3 GPUs, miner was unstable all the time (OS Windows aswell).
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 09, 2018, 07:44:03 PM
Need some advice guys.

I notice that 26% all of my shares which I can see at monitor is Devfee. Is it possible? (you know - the green line with text)

+-------------------------------------------------+
|         EWBF's Zcash CUDA miner. 0.3.4b         |
+-------------------------------------------------+

I mean this is share for me:
INFO 02:27:48: GPU4 Accepted share 31ms [A:19, R:0]
INFO 02:27:57: GPU7 Accepted share 32ms [A:24, R:0]

I mean this is share for Devfee:
INFO 02:28:04: GPU6 DevFee Accepted share
INFO 02:28:06: GPU6 DevFee Accepted share

And when I count all of my shares which I can see at monitor, 26% goes to to Devfee.

For example 4197 (of my shares) vs 1114 (Devfee) or 3181 (of my shares) vs 839 (Devfee) and so on.

I try to change URL mining pool but no positive results. Thank you.
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 09, 2018, 07:21:46 PM
Hello, how can I add a second backup server to .bat file?

tnx for helping me :/

Use parameter --config

For example:

miner --server --config zec-eu1.nanopool.org --user WALLET/WORKER/E-MAIL --pass z --port 6666 --templimit 80 --eexit 3

--config will use miner.cfg file which you can modify. For more information open Help.txt file in root directory.
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 09, 2018, 07:11:30 PM
Huh WHO knows why this miner sets lower speed for GPU 0 Huh
And every time I'm closing and opening the miner it shows different speed for GPU 0!!! EWBF 0.3.4b WHY???
I have 3 ferms and the same problem! For example 7x1070 GPU 0 speed varies from 272-390 others are ~440  But the temperature and power usage of all GPU's the same! Is there any hidden mining on GPU 0 dear dev Huh And please lower fee to 1%.

1. Try to exchange hole PCI-E Riser for GPU 0
2. Switch PCI-E slot at motherboard for GPU 0
2. If you are using MSI Afterburner, rise up "Temp. Limit"
3. Check "Core Clock" and "Memory Clock" settings, change values for GPU 0 only
4. Check your Power Supply Unit, maybe is it overloaded or damaged. Switch PSU cables between GPUs.
5. Check dust in ventitalion (cooler) of GPU 0
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 09, 2018, 06:51:06 PM
Does EWBF need a large virtual memory swap like Claymore does or can I reduce the Virtual Memory size to reclaim some badly needed disk space?

My understanding is that claymore's large virtual memory requirement is associated with DAG, so no,you don't need a large swap file for EWBF as there is no DAG. I might be wrong though.

For more then 3 GPU - large virtual memory is required - 16 000 MB minimum.
7  Alternate cryptocurrencies / Mining (Altcoins) / Re: EWBF's CUDA Zcash miner on: March 02, 2018, 08:21:52 PM
Need some advice guys - I am desperate from poor mining results...

Is possible that from all of my shares which I can see at monitor is 26% Devfee HuhHuh


+-------------------------------------------------+
|         EWBF's Zcash CUDA miner. 0.3.4b         |
+-------------------------------------------------+
INFO: Current pool: zec-eu1.nanopool.org:6666
INFO: Selected pools: 1
INFO: Solver: Auto.
INFO: Devices: All.
INFO: Temperature limit: 80
INFO: Api: Disabled
---------------------------------------------------
INFO: Target: 00028f5c00000000...
INFO: Detected new work: 1519952111
CUDA: Device: 0 GeForce GTX 1080 Ti, 11264 MB i:64
CUDA: Device: 1 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 2 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 3 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 4 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 5 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 6 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 7 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 8 GeForce GTX 1080, 8192 MB i:64
CUDA: Device: 0 Selected solver: 0
CUDA: Device: 1 Selected solver: 0
CUDA: Device: 4 Selected solver: 0
CUDA: Device: 2 Selected solver: 0
CUDA: Device: 3 Selected solver: 0
CUDA: Device: 5 Selected solver: 0
CUDA: Device: 8 Selected solver: 0
CUDA: Device: 6 Selected solver: 0
CUDA: Device: 7 Selected solver: 0
INFO: Detected new work: 1519966076
INFO 16:38:26: GPU1 Accepted share 31ms [A:542, R:0]
INFO 16:38:27: GPU5 Accepted share 94ms [A:595, R:0]
Temp: GPU0: 72C GPU1: 66C GPU2: 60C GPU3: 63C GPU4: 64C GPU5: 66C GPU6: 68C GPU7: 64C GPU8: 63C
GPU0: 592 Sol/s GPU1: 481 Sol/s GPU2: 516 Sol/s GPU3: 518 Sol/s GPU4: 527 Sol/s GPU5: 469 Sol/s GPU6: 469 Sol/s GPU7: 510 Sol/s GPU8: 521 Sol/s
Total speed: 4603 Sol/s
INFO 16:38:28: GPU2 Accepted share 125ms [A:635, R:2]
INFO 16:38:42: GPU6 DevFee Accepted share
Temp: GPU0: 71C GPU1: 66C GPU2: 60C GPU3: 63C GPU4: 64C GPU5: 66C GPU6: 68C GPU7: 64C GPU8: 63C
GPU0: 602 Sol/s GPU1: 472 Sol/s GPU2: 519 Sol/s GPU3: 519 Sol/s GPU4: 522 Sol/s GPU5: 470 Sol/s GPU6: 468 Sol/s GPU7: 509 Sol/s GPU8: 520 Sol/s
Total speed: 4601 Sol/s
INFO 16:39:05: GPU4 Accepted share 32ms [A:640, R:2]
INFO 16:39:07: GPU2 Accepted share 32ms [A:636, R:2]
INFO 16:39:08: GPU6 Accepted share 15ms [A:541, R:1]
INFO 16:39:08: GPU4 Accepted share 31ms [A:641, R:2]
INFO 16:39:12: GPU5 DevFee Accepted share
INFO 16:39:13: GPU5 DevFee Accepted share
INFO 16:39:14: GPU5 DevFee Accepted share
INFO 16:39:14: GPU2 Accepted share 47ms [A:637, R:2]
INFO: Detected new work: 1519966077
INFO 16:39:24: GPU8 Accepted share 31ms [A:616, R:0]
Temp: GPU0: 71C GPU1: 66C GPU2: 60C GPU3: 62C GPU4: 65C GPU5: 66C GPU6: 68C GPU7: 65C GPU8: 63C
GPU0: 598 Sol/s GPU1: 476 Sol/s GPU2: 518 Sol/s GPU3: 512 Sol/s GPU4: 520 Sol/s GPU5: 473 Sol/s GPU6: 471 Sol/s GPU7: 513 Sol/s GPU8: 524 Sol/s
Total speed: 4605 Sol/s
INFO 16:39:36: GPU8 Accepted share 31ms [A:617, R:0]
INFO 16:39:53: GPU4 DevFee Accepted share
INFO 16:39:55: GPU4 DevFee Accepted share
INFO 16:39:55: GPU4 DevFee Accepted share
INFO 16:39:57: GPU2 Accepted share 32ms [A:638, R:2]
...
8  Alternate cryptocurrencies / Altcoin Discussion / Re: What is the address 0x0000000000000000000000000000000000000000 on: February 20, 2018, 07:56:00 PM
I had same feelings about that address.

I just succesfully trade some ICO tokens (NCT) of Polyswarm. I notice that address show up in Etherscan.io when I checking authenticity of ICO project.

After trade was done, I manualy add token contract address to my wallet and tokens show up. No problem in my case.

I will stay in touch with news if token is valuable or worthless.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!