Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)
would these controls be also working for NVidias?
Not at this time. We had our hands full with AMD's semi-documented library and the Nvidia doesn't provide any documentation for the overclocking features of NVAPI. But we will definitely try to make it work in the future, but no promises as to when it will be ready.Developers please make option like Claymores -altnum, but in oposite. I want my GPUs be numbered from ZERO as all other miners and gpu settings software do. First GPU should be GPU0. Thanks. Your numbering starting from 1 makes me more diffucult to identify while tuning cards.
Well, as C programmers we can certainly see the appeal of indexes starting from 0 
We'll include in the TODO list of nice-to-have options, but no ETA.whenever i try to mine
ELLA or PIRL
i get
am i doing anything wrong in the batch file?
This pool seems to require the worker to be specified separately like this (-wal must contain only the wallet address):ELLA or PIRL
i get
Quote
connection closed by Pool
erroram i doing anything wrong in the batch file?
Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
PhoenixMiner.exe -pool pool.ellaism.org:8008 -wal Wallet.Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
PhoenixMiner.exe -pool pool.ellaism.org:8008 -wal Wallet.Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2
Code:
PhoenixMiner.exe -pool pool.ellaism.org:8008 -wal Wallet -worker Worker -cdm 0 -amd -wdog 0 -log 0 -rmode 2
Hi All,
I recently updated to 2.7a. Prior to this update i had quite the stable rig, that required very little attention. Now it seems its quite the opposite. The latest mystery. I have a 5 x RX 580 rig / win 10 / Corsair HX750i & 1200W server PSU / 4gb / 16 Vram.
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
PhoenixMiner.exe -pool asia1.ethermine.org:4444 -pool2 asia1.ethermine.org:14444 -ewal xxx.xxx -pass x -minspeed 147 -rmode 2 -mi 11 -coin eth -ptimeout 20
It had been hashing for 24 hours, when one of the GPU's for a minute went from 30 to 23. This then triggered the minspeed alert and reboot.
For the next 4 hours (while i was asleep) the computer kept rebooting as the DAG file couldn't be allocated/generated. Here is the first time stamp/log file.
....
All of a sudden at 8.10 after about 20+ reboots (same as above) it suddenly starts allocating/generating DAG file.
Any ideas why this might be the case, or is the 7a release a bit buggy compared to earlier versions ?
Many thanks.
There seems to be a problem with light cache generation, which normally shoudn't take more than 5-15 seconds and is done entirely on the CPU. Probably something else loads the CPU to 100% with high priority task and the light cache just can't be generated in time so the watchdog is kicking in. Check the CPU load in Task Manager if this behavior repeats and note which program "eats" the CPU time (PhoenixMiner.exe should only load one core to 100% during light cache generation and then keep it at nearly idle during normal operation).I recently updated to 2.7a. Prior to this update i had quite the stable rig, that required very little attention. Now it seems its quite the opposite. The latest mystery. I have a 5 x RX 580 rig / win 10 / Corsair HX750i & 1200W server PSU / 4gb / 16 Vram.
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
PhoenixMiner.exe -pool asia1.ethermine.org:4444 -pool2 asia1.ethermine.org:14444 -ewal xxx.xxx -pass x -minspeed 147 -rmode 2 -mi 11 -coin eth -ptimeout 20
It had been hashing for 24 hours, when one of the GPU's for a minute went from 30 to 23. This then triggered the minspeed alert and reboot.
For the next 4 hours (while i was asleep) the computer kept rebooting as the DAG file couldn't be allocated/generated. Here is the first time stamp/log file.
....
All of a sudden at 8.10 after about 20+ reboots (same as above) it suddenly starts allocating/generating DAG file.
Any ideas why this might be the case, or is the 7a release a bit buggy compared to earlier versions ?
Many thanks.
My rig keeps restarting when I use PhoenixMiner 2.6. I've no problem running Claymore, it's very stable but I'd like to try Phoenix as a lot of people have a good opinion about it. Here is the log of Phoenixminer ( https://imgur.com/uiFEcPm ). From what I can see, it hungs one of my gpus and then restars the system, no error so to say. Am I missing some parameteres? My settings are the same as in Claymore, i just ported the start.bat. Any ideas appreciated.
If it is always the same card probably it is either overclocked with Clyamore's dual miner and PhoenixMiner just ignores these options and runs the cards with their stock settings, or the cards is "on the edge" clock/voltage wise and the small increase of mining speed from PhoenixMiner pushes it over the edge. Lower the clock speed or up the voltage just a little bit on GPU2 and see if this fixes the problem (you can also try the new PhoenixMiner 2.7b which has support for the hardware control options).r7 370 2g can be mining eth with this program?
You can mine Pirl, Ellaism, Ubq, Expanse, etc. The profitability is usually about 80-90% of ETH, so 2 GB cards are still quite usable for mining.