Hi EWBF!
I have a question. Does anyone know if the current version of EWBF runs on the mining specific cards specifically the P106-090 3GB? This is the older version of the typical P106-100 which is 6GB. I am looking to mine BTG 144,5.
From the reading I have done I sounds like the most current version of EWBF 0.5 runs fine on win 10 with the GTX 1060 3GB. So it should run fine of the mining specific cards?
Any replies would be greatly appreciated!!
I do not have these cards, but I think they will work fine, also these cards look slower than 1060 3 GB.
I have 12 evga 1070 SCs on Win10 Pro using nvidia inspector to OC to 100/450 85% power. each card using around 123 watts. and my SOL/s is about 470 in EWBF 0.5
I previously had this machine running on Win10 Home, same hardware, using EWBF 0.4 I'd get about 470 sol/s then i upgraded to 0.5 and was getting 505-515 sol/s. but formatted ssd and did a clean install of win10 pro and now EWBF 0.5 is maxing at 475 sol/s and not over 500 as previously achieved with same OC settings. I'm at a loss.
I also updated B250 mining expert from bios 1010 to bios 1026, or whatever the latest BIOS is. Could this contribute?
Which version of nvidia driver are you currently using?
This is Equihash 200,9, you need to use an old miner.
Hello, i am having problem with 0.5 and 0.4 ( i havent tried the older one). When i start mining after 10 15 min all cards crash. There is a message that says GPU 0 , 1 ,2 are unavaible or busy and trying to restart. I am usisng 1060 6 g , 1070 TI and 1080 TI. My OC setttings are Power 90 % 0 clock on memory and the other one is 0 only my fan speed is changed and they crash with 0 OC i am usising windows 7. Can someone help ?
Run one copy of the miner for each card, this will help you figure out which card causes the problem, check the power supply (is it able to handle the load?), cables, risers, etc.
every second time restart miner API not start, please fix it
ubuntu 16
ERROR: Api bind error
Ok, I'll check it out.
EWBF is still not flushing stdout - is this by purpose?
It makes it almost impossible for monitoring apps to handle miner output
btw.: claymore has the same: not flushing stdout.
Just add --boff argument.