Topic: EWBF's Cuda Equihash Miner 0.6 - page 28. (Read 85776 times)

The irony that crypto is all about security and that people clamor for Winduhs_this and Winduhs_that so that they can crypto with less security is just staggering. 

You say "*  Solver for equihash 200,9 has been deleted." and "I'll probably return 200,9 variant later"

Can you confirm that you are working on a Windows miner for 200,9?

A couple people above complained about this issue. I myself had these errors a few times. And indeed a soft restart  (closing and opening EWBF) fixes it.
I just increased virtual memory from 30 to 50 GB and never had that problem again (4-5 days running stable).

Who can solve this problem ? I close tool and run again,  it's normal
But many rigs are faulty
1060 3G , 1060 6G
https://cdn.discordapp.com/attachments/365065627200651265/467545954845851648/unknown.png

21:36:45 INFO: GPU4 are restarted.
21:36:45 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:36:45 WARNING: Looks like GPU5 are stopped. Restarting...
21:36:45 INFO: GPU5 are restarted.
21:36:45 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:36:45 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:36:45 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:36:46 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:36:46 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:36:46 WARNING: Looks like GPU0 are stopped. Restarting...
21:37:16 INFO: GPU0 are restarted.
21:37:01 Temp: GPU0: 36C GPU1: 31C GPU2: 36C GPU3: 36C GPU4: 33C GPU5: 33C
21:37:16 GPU0: 0 Sol/s GPU1: 0 Sol/s GPU2: 0 Sol/s GPU3: 0 Sol/s GPU4: 0 Sol/s GPU5: 0 Sol/s
21:37:16 Total speed: 0 Sol/s
21:37:16 WARNING: Looks like GPU1 are stopped. Restarting...
21:37:16 INFO: GPU1 are restarted.
21:37:17 WARNING: Looks like GPU2 are stopped. Restarting...
21:37:17 INFO: GPU2 are restarted.
21:37:17 WARNING: Looks like GPU3 are stopped. Restarting...
21:37:17 INFO: GPU3 are restarted.
21:37:17 WARNING: Looks like GPU4 are stopped. Restarting...
21:37:17 INFO: GPU4 are restarted.
21:37:17 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:37:17 WARNING: Looks like GPU5 are stopped. Restarting...
21:37:17 INFO: GPU5 are restarted.
21:37:17 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:37:18 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
21:37:18 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"

The formula is not correct. It should be 8/11*Vram+3/4*RAM +1/36*(Core Frequency)-36/87*(Ram Frequency)+3/14*(your grandmother's age)

Increase Virtual Memory (Page file), safe size is amouth of total VRAM + RAM + RAM/2
Recommended 40GBs by some tutorials is not enough for every mining algo.

So If you have 4GB of RAM, thats:
3*11GB + 3*8GB + 4GB + 4GB/2 = 63GB should be enough.

So i have 3x1080ti and 3x 1080 and one of the 1080 wont start

"Looks like GPU5 are stopped. Restarting"
GPU 5 are restarted
Device: 5 Thead exited with message "out of memory"

And that on a loop

Miner is very stable on smos. 3.0 version using 8 1080tis

Not sure if I am paying a fee but I did not click no fee and don’t mind giving a fee to ewbf

Maybe he can tell us what the standard fee is on smos 3.0

Btw I am almost up to 1 Btg earned on miningpoolhub

Which will roll over to my trezor address.

I would like to mine this for a few months or 50 btg.

I think btg May go higher then it is at the moment.

What is your rejected shares rate? In some of my rigs it's as low as 0.25% while another rig has rejected 1.1%

What do you smoke, beef? Enlighten us: what license is EWBF on? subscription or perpetual one
And btw there is no better alternative to EWBF on the "market". DSTM does give slightly higher hash rate for some cards at the expense of stability, but again disabling fee in EWBF will results in the same revenue  as DSTM while being a more stable miner.
As of now DSTM failed to introduce new equihash algos. So I'm guessing you are just trolling here while silently using EWBF (no other options).

fee option is really a wise decision and it gives a choice to everyone - to thanks devs and share or develop their greed.
my respect, EWBF

Long ago, I predicted your point of view, so I decided to add the "fee" option, which allows you to disable fee. Therefore, if you want it, you can turn it off or use another miner. I see no reason for anger.
So, relax and be happy!

i gather you don't understand the concept of perpetual vs. subscription software licenses and the development implications thereof?  fortunately there were better alternatives brought to market in the time since ol' ewbf ghosted and counted his terraman cheese for a solid year.  so you go ahead and fuck with ewbf again if that's what floats your boat...just don't expect to see anything beyond a (possible) r2 of current gen equihash miner. 

Is this miner stable at mix rig (gtx 1060 + 1070 + 1080 ti)?

I am use 96_5 algo. I have 8 Ks - 1050ti, 13 Ks - 1060, 19Ks - 1070, 24 kS - 1080 and 28 kS on 1080ti (Ewbf 3.0. Windows 10, last gpu drivers). Why the 1080ti is so slow?

Doesn't matter, but with the old algo without adjusting the intensity i could use my computer for different stuff. Don't use farcebook or any other book that matter, but for programming work and so on. With the new algo's it's impossible to literally do anything on my system. Changing windows is a pain in the ass!. On my part just a suggestion, especially since this new code is based on old code that had this functionality baked in. If it's an easy fix, me and several others i guess will start mining and paying "fee" to devs. Win win in my book, no?

everyone or just hobby miners that need to slow mining down so they can Farcebook better? 

I support the proposal, EWBF_ everyone is looking for intensity fix .

Is the intensity functionality brought back yet? Did not see it in the changelog, but remember i was not the only one asking about it. Is it something that is planned for the next version?

Yes : 51 sol/s @ 170 W max setting in the driver (135 W in real).
OC : 175 core / 350 mem : stable during weelks.