Quote from: wartywarlock2 on February 28, 2018, 10:12:56 AM

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's definitely not a hardware problem - this is the anti-debug code activating without good reason apparently. We are trying to make these checks smarter and lighter but obviously we aren't there yet. Still, we are hesitant to relax the checks too much for obvious reasons - apparently there is no lack of highly esteemed developers trying to reverse our miner Wink

Quote from: xS-RaGnaR on February 28, 2018, 12:16:00 PM

Is there a certain date for dual mining? thx

Not yet, unfortunately, it is proving to be harder that we expected, so we better not throw around optimistic schedules without delivering.

Quote from: pickaxe123 on February 28, 2018, 05:28:53 PM

I've been mining since 2.4, now on 2.7b, on a single Vega 56, W10, latest drivers, and it's been mostly fine. I've only experienced one recurring problem where mining stops (driver crash AFAIK) then restart and hangs at detecting cards for 60-80 minutes before resuming mining. Before 2.7b, my wattman overclock settings were reset to default, now with 2.7b I get to keep my settings which is much better already.

Thank you for the logs. Unfortunately we can't determine much from there just that the GPU thread is freezing after the crash. You've got quite a bit of memory overclock though maybe try dialing it back a little. We also had problems with Vega because of the card high power consumption - even 600W quality PSU led to sporadic crashes when powering a single Vega56 even with big underclock. It seems like Vega has high peak currents that lead to crashes if the PSU is not ridiculously overpowered. We have some work to do with hardware controls support for Vega though, as it appears to use some new (and undocumented) ADL functions and structures.

Quote from: Branko on February 28, 2018, 07:24:42 PM

Any reason to NOT use -mi 12, but lower number?

Stale shares. The high mining intensity increases the time window within which a stale share can occur. Therefore the default is 10 even though 12 gives a slightly higher hashrate. Still, the stale shares are sometimes dominated by the pool latency so you may see a better results with -mi 12 but keep an eye on stale shares to avoid losing more via stale shares than you have gained from the higher hashrate.

Quote from: Bigdrago on February 28, 2018, 08:22:24 PM

Do this program support OC, undervolt and set a work temp for gpu?

Yes, but only the latest beta version which can be found here: https://bitcointalk.org/index.php?topic=2647654.msg31091660#msg31091660 The last official release (2.6) doesn't support these options yet.

Quote from: Bigdrago on February 28, 2018, 08:22:24 PM

Too bad if this is a ripoff of Claymore.

It isn't

Quote from: ZombieWorm on February 28, 2018, 09:21:21 PM

Can anyone help, Phoenix connects and mines away but it seems to get both my cards to mine under one miner. I have two cards that independantly mine using a profit switcher. How do I get Pheonix to mine an instance on one card and if the other card auto-switches opens another window should it need to?

I have nvidia and AMD card in case anyone is wondering.

Yes, you can. Start a two copies of PhoenixMIner and add the -amd command-line option on the first, and -nvidia on the second. The first will mine only with the AMD card and the second - with the Nvidia card.

Quote from: murgorx on February 28, 2018, 10:32:41 PM

Guys, I have seen that the miner finds shares 4950MH and goes up to 928.2GH, have seen also results that go to 1TH+.
What is the meaning of this and how to regulate it, if I have to?
Could anyone give me an advice, please?

Well, actually you don't profit at all from the higher difficulty shares - it only matters that the share is above the difficulty specified by the pool. There is nothing sinister there though - this is the reason the pool exists: to equalize the luck of the individual miners according to their actual hashrates so it doesn't matter who actually finds the block.