Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 464. (Read 784985 times)

Great thank you.

Is there a certain date for dual mining? thx

yes i use blockchain beta drivers. thanks i will try new driver.

Hi did anybody ever figure out the Fatal Error: debugger detected problem?

Over the last week I have installed 3 rigs, 2 went fine, third one was a problem. The only thing I can point out as different is that on the 3rd one I had to grab a new win10 ISO from MS as I lost my USB, otherwise it is the same https://www.scan.co.uk/products/asrock-z270-killer-sli-intel-z270-s-1151-ddr4-sata3-m2-(pcie-sata)-2-way-sli-crossfire-gbe-usb-30-ap?v=c same ram, same psu, and same cpu. Cards are a bit different but shouldn't be relevant.

At work so I can't check the bios but all 6 cards are present and correct, dagpatch done etc. Claymores is currently running fine so it's not as far as I can tell a hardware issue. Can remote in and try settings if anyone has suggestions.

Otherwise superb miner, can't wait for linux version (focus on Ubuntu as that seems most common!).

It was a Windows limitation. Windows was limited to 8GPUs of the same brand, but since Windows 10 1709 this limit is now 12GPU.
Bear in mind that nVidia currently still has a driver limitation of 8GPUs. Only AMD has patched their drivers to reflect the 12GPU limit. So in theory you can run 20GPUs on 1 Windows 10 rig (12x AMD + 8x Nvidia).
MSI Afterburner also has a limitation of 8GPUs which they are not willing to change (the devs hate miners, so...). Claymore doesn't have any limitations.

Hi, I'm building three 12 gpu rigs. All AMD580, 8gb. But now I hear and read that claymore is limited so you can only use 8 or 10 gpu's at once. Probably that is why people have one rig whith a AMD/Nvida combo.

Can I use my rig with all 12 AMD580 rigs to mine? Or does Phoenix miner has a similar limitation like claymore?

edit: or was this due to a windows limitation before? Windows should now support 12 of the same gpu's.

 Not exactly, but similar. -tmax is equivalent to the max GPU temperature you can set via AMD WattMan. The card will raise the fan speed until it reaches the max fan speed and if the temperature is still edging over -tmax, the GPU core clocks will start to throttle just enough in order to keep the temperature at or below -tmax.

 It is possible that this is the infamous Debugger detected error - it is shown only on console and not in the log file. If you are starting PhoenixMiner.exe directly (without .bat file), use a .bat file and put pause on the next line:
 when PhoenixMiner.exe exists, the console window will remain open and you will be able to see if this is the Debugger detected message.


  Works without problems here. If the username is not correct, you will get the following error:


  This is a DNS problem - your DNS server can't resolve the pool name (or is intentionally blocking it). If you are using the DNS of your ISP (which is the default in most cases), you can try switching to Google DNS or OpenDNS.

  Not yet, will be added later along with -tstart (not in 2.7 official apparently as it is already too long in the making).

 Will do but it's going to take some time. What Linux distro you are using and (if you are using AMD drivers), which drivers?

 Make sure that you don't specify -cvddc or -mvddc (or specify 0 for them) in config.txt of PhoenixMiner, and it will not try to change them from their default values.

 Not yet but SSL support will be added very soon.

   The fan speed is ultimately under the control of GPU BIOS and the driver. We "tell" it to not exceed X% but some cards overshoot anyway, it at least for some time. As for the rest of the problems - what drivers you are using? If you are using the blockchain beta drivers, you better use other tools to set the clocks/voltages. With 18.1.1 or 18.2.1, the PhoenixMiner's hardware control options should work fine.

after many hours, i have some problem with 2.7b :

- after many lost internet connection, it lose -powlim, -cclock, -cvddc, -mclock, -mvddc setting.
- fanmax 95 but it's going to 99 (ok temp is to hot, but i have fixed a limit)
- after many reboot for solve the first problem, it's always same. my setting isn't apply but app show at start it want apply my setting.
- after all of this, he make # before all line of this setting (-powlim, -cclock, -cvddc, -mclock, -mvddc, -fanmin, -fanmax),  but app try to apply always the previous setting.

come back to 2.6, and work perfectly.

Hi,

I want add SSL support with pool certificate verification, it significantly improves security, use "ssl://" prefix for pools that support SSL encryption. 

Thx.

no fix yet ??

I agree!  Would love to see a Linux version

Thanks!

Hi

You can use "-minRigSpeed to restart the rig if the 5 min average speed is below specified threshold

Thanks for your work!!!! Please can you add "-speedmin"?  When my miner crash and restart It comes with less mh/s, i need restart 1 more time for run normal

Any ideas?
Also does Phoenix support SSL pools?

Thanks

It could be your power supplies are not enough or too high overclock...

hellow,the pheonix miner is great,my rigs are more stable .
But i have a problem whit undervolt,im using afterburner.
when i start the rig,miner goes first,1500 w on the wall,7 x 570 8 g sapphire nitro plus,then afterburner goes after, 20-30 secs, then the memory clock is reseted in miner console whit exact same numbers ( im using config,disable afterburner for memory and others,im using it only for undervolt).After all of that,power goes to normal,1050 w.
But if i restart the miner,the power goes back to 1500. why? how can i fix that?

Please make Linux version. and do not forget to make support for at least 13 gpus.
Thanks in advance!

No, check Readme.txt.

does the 2.7b version support individual card -tstop feature and then starts mining with same card once the temps are back within desired range?

havent tried, i put my clock speeds and voltages in the BIOS.


Claymore to Phoenix, YES
Phoenix 2.6 to 2.7b, NO