Hey Guys... First time poster here, new-ish to mining...
I wanted to see if I can help some other people with the issues they are experiencing with mining ZCash using Genoil's miner. I have a few different machines I'm using for mining but my main rig is 6x 390Xs running Windows 10 Pro. I've, up until recently, been mining Ethereum on it running reliably at more than 200MH/s using Claymore's miner.
Mining ZCash has meant a lot of baby sitting crashing software for the past few days, but I've been running Genoil's 0.6 now for about 6-7 hours without issue. So far no decrease in hash rates and cards are all restarting upon a crash. Here is my configuration:
Crimson 16.6 - Windows 10 Pro 64bit
6x R9 390X 8GB - Stock
Intel Celeron - 16GB RAM - Samsung SSD - 2x 1000w PSUs
Running Genoil 0.6 with the following batch file(s):
title Miner01
:start
genoil.exe -c us1-zcash.flypool.org:3333 -u YourZCashTAddress.Miner01 -p z -i 20 -w 64 -P 1 -f 2 -g 0 1
cls
timeout /T 10
goto start
I am running 2 cards per instance, which seems to be very stable, so 3 slightly different batch files. The first line titles the cmd window so you know which miner you are looking at more easily. The -f switch is set to 2 which will exit genoil.exe if the miner crashes, and the -g switch just says to run the first two cards. That -g switch and the window title/address are the only that differ between my batch files. Basically when Genoil crashes, for any reason, it will continue on in the batch file and just start Genoil.exe over continuously.
You may need to change the -P switch to a 0 if this doesn't work, different rigs are picky about this switch.There is only one other problem with this... The windows debug window will pop up and yell at you saying Genoil.exe has crashed. This will prohibit the batch file from continuing until you press 'Close Program'.
The easiest solution to this is to turn off this dialog via Group Policy:
GPEdit.exe > Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Error Reporting > "Prevent display of the user interface for critical errors" = EnabledThere should be a way to do this via the registry if you don't have access to GPEdit, but the information I've found is inconclusive and hasn't seemed to work.
Now when one of your threads/cards crashes, they will restart automatically without any user interaction.
This setup has been tested on two different 'Hawaii' based rigs and another 'Pitcairn' rig.
Yield is about 30S/s on 390X & 17S/s on 270X.Happy Mining - Let me know if you have any questions
Show Posts
