PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 483.

gsrcrxsi314

member

Activity: 367

Merit: 34

61hr tests on each claymore and Phoenix. on nanopool mining ETH

Claymore v10.0
4744 shares accepted
0 rejected

Phoenix 2.5d
4815 shares accepted
0 rejected
1.2% stales

this shows that over these two 61hr periods, Phoenix submitted 1.5% more shares. but phoenix also had 1.2% stales. I'm not sure how to compare this with claymore since claymore's program doesnt report stales.

Yellow_donkey

newbie

Activity: 31

Merit: 0

Quote from: Yellow_donkey on February 02, 2018, 11:52:43 PM

So sad, almost want to cry...

So 2.5 came and went, 2.6 is here but no solo geth|parity mining.../frowny face & upset tummy.

I think I am the only person asking for it, so not surprised. But will I be surprised with 2.7b?!?

Quote

The good news is that there are other requests for solo mining

No promises but there might be an experimental support for it in 2.7.

I will take experimental any day of the week!

PhoenixMiner

full member

Activity: 357

Merit: 101

Quote from: alkoholik24 on February 02, 2018, 01:05:33 PM

Quote

Please use a batch file to start the miner with the following contents (the important part are the setx statements to set the environment variables):

Code:

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 -clKernel 1 -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x36fd6ca7b320c46189bb9e78f5390573cace4745.Rig003 -proto 3
pause

Still the same problem. Occurs on different GPU, sometimes on 2 simultaneously.

Check the size of your Windows page file, it should be at least 16 GB. If not, raise the minimum size to 16 GB.

Quote from: Miner59 on February 02, 2018, 01:13:50 PM

Quote from: PhoenixMiner on February 02, 2018, 12:26:34 PM

Please try using the command line option -mi with different values (for example 8, or 9 instead of the default value of 10). You can change it only for the RX560s by using it like this:

Code:

-mi 8,8,10,10,10

In the above example the first two cards will run with mining intensity 8, and the other three - with mining intensity 10. This assumes that the RX560s are the first and the second card and you have five cards in the rig. The order of the cards must be the same that is listed by PhoenixMiner when starting up.

Didn't change much, still dropping hashrate.

We'll check it further, but we have only one RX560 and it doesn't behave this way. Could you tell us what version of Windows you are using and which drivers?

Quote from: shanepottermi on February 02, 2018, 03:34:38 PM

It probably isn't worth pushing back the linux version for dual mining capability. The Chinese released ASIC for Lbry, Pascal, Sia, and Decred so there isn't any point in dual mining anymore. If someone develops algos that play well with ethash in the future you'd probably need to start building from scratch anyways. The other tweaks are pretty sweet but once you get that linux version up an running talk to the ethOS guys an get them to incorporate your miner in their OS. I got 2 rigs on ethOS linux with 10 cards an 12 cards cuz windows don't play well with a lot of gpus on a single rig.. given the new mining boards coming out that can house 12+ gpus i think windows mining is going to be getting phased out by people running larger farms which i'm guessing is more your bread an butter target market. I'm running your miner on my desktop with 4 gpus an already wish the linux version was available for my other rigs. Faster hash rate, less fees, no dag switches. I get what you're saying about the dag switches I haven't watched enough to see the dev mining fee to see if my cards still have to spin up an i'm only running this on my small system anyways so even if i could see it it wouldn't be nearly as obvious as my other systems with 3x-4x as many cards. I skimmed the commands an i don't recall seeing a feature similar to -powlim from claymore. That would be a good feature to have so you can tweak power consumption. I'm not a pro or anything but I noticed that my cards will run at say 30mh/s with powerlimit 20.. but if I lower powerlimit it will drop total power consumption without decreasing hashrate or stability so the cards will just use whatever power they can for the most part. It would be nice to have the feature incorporated in the miner so we don't have to go around reflashing cards to find the sweet spot using powerlimit % / tdp in bios.

We'll try to release the dual mining as fast as we can because we are already invested a lot of time in it. The Linux support definitely is very important but given that there isn't one "true" Linux and a multitude of (AMD) drivers, it would take even more resources than the dual mining. The (probably flawed) rationale is that the dual mining window is closing fast, so if we don't release it soon, it becomes pointless. The Linux support will be useful a lot longer.
We are going to implement all (or at least most) of the hardware control features that are present in Claymore dual miner. They will gradually start to appear from version 2.7. Right now we are chasing a few elusive bugs that some of the miners are experiencing.

Quote from: Yellow_donkey on February 02, 2018, 11:52:43 PM

So sad, almost want to cry...

So 2.5 came and went, 2.6 is here but no solo geth|parity mining.../frowny face & upset tummy.

I think I am the only person asking for it, so not surprised. But will I be surprised with 2.7b?!?

The good news is that there are other requests for solo mining

No promises but there might be an experimental support for it in 2.7.

Quote from: murgorx on February 03, 2018, 01:13:58 AM

A question to the DEV - How may I undervolt with this miner? It's drawing 200W more than the Claymore's? I am scared to use undervolting from TRIXX, because my rig freezes if I touch something there Sad

I am using it only to set my fans speed. Are you planning on implementing the -cclock -mclock -cvddc etc etc?
Really happy with the miner so far!

There is no support for hardware control (fan speed, clocks, voltages) in the current version. We are going to add them gradually over the next few versions. For now use whatever over-clocking tool you feel most comfortable with - MSI Afterburner, OverdriveNTool, Wattman, etc.

Yellow_donkey

newbie

Activity: 31

Merit: 0

Quote from: KJCrypto on February 03, 2018, 08:28:08 AM

The dev is working those feature into the program but for now use overdriveNtool by the guy on guru3d

Works great for all over clocking, undervolting and fan control. I mod all my bios with polaris 1.6 but if I need to tweak anything after I use overdriveNtool

I don't think we are talking about the same thing. I am running a geth node and want to mine local/LAN to my own node of any given coin. Not mine to a pool. It was confirmed to not be in 2.4, and has not worked with 2.5 or 2.6.

A command line like this, with geth running on a local machine:

Code:

EthDcrMiner64.exe -epool http://192.168.1.74:8645 -allpools 1 -eworker R1 -ethi 4

You see, I have to use Claymore for this...

Quote from: murgorx on February 03, 2018, 08:33:46 AM

Quote from: KJCrypto on February 03, 2018, 08:28:08 AM

The dev is working those feature into the program but for now, use overdriveNtool by the guy on guru3d

Works great for all overclocking, undervolting and fan control. I mod all my bios with Polaris 1.6 but if I need to tweak anything after I use overdriveNtool

Could you please share a simple guide on how to undervolt with this tool mate? I don't want to mess up my cards Cheesy

I don't know if I should even do it, since for the first two weeks my rig is finally stable *fingers crossed* and I don't know if that would cause any instability, that's why I'm asking. It just much simple with those commands to do it and not go in-depth, that's why I asked, I don't mind waiting tho. Electricity is 0.06usd, so 100-150w won't cause me to lose much of the profit. It just bugs me, that the cards are getting hot and the fans, therefore, are working at 60%, producing a lot of noise.

It is super easy, so open the program, you can goggle -command lines to find all the strings you can use. You should know you frequencies you want to use and I have this in both my windows startup folder and at the start of each coin.bat:

Code:

cd\Users\Rig\Desktop
OverdriveNTool.exe -r1 -r2 -r3 -r4 -r5 -r6 -p1"570" -p2"570" -p3"570" -p4"570" -p5"570" -p6"580"
cd\rig\clay
EthDcrMiner64.exe -epool http://192.168.1.74:8645 -allcoins exp -eworker R0 -dcri 1 -r 1 -minspeed 175
pause

So I cd\ to the ODNT exe and then run -r on each card (be mindful of where you Intel GPU is at and don't call on it), that -r is a reset to default command so it takes each card in this one rig back to factory default, milliseconds lattr is runs the -p1, p2 commands which is load profile (p) on card number (1) "570" profile named 570. You can see I have a separate profile for the single 580 at the 6th slot.

The best part about this is that it resets all cards and then OCs them in half a second. All of them. And it does it when windows loads and when reboot.bat kicks in as well as whenever I load a coin to mine, as I start all .bat files with it. Global reset and OC works great to clear failed GPUs, in literally a second.

The Program itself its pretty simple, load the GUI, enter your settings onto one card, click to save that as a profile, that will create a config file right in the same folder, you can go in there and make other profiles with copy and paste and edit them faster then in the GUI, but either way woek, edit config file or GUI. That's how you make any number of profiles you want to call with the -pX function. You can have a profile for each card in your rig if you want.

These are my two profiles in this one rig, the voltages need a little touchup, kind of high:

Code:

[Profile_0]
Name=570
GPU_P0=300;750
GPU_P1=588;765
GPU_P2=976;956
GPU_P3=1065;950
GPU_P4=1130;950
GPU_P5=1192;950
GPU_P6=1233;950
GPU_P7=1268;950
Mem_P0=300;750
Mem_P1=1000;800
Mem_P2=2200;900
Fan_Min=750
Fan_Max=3000
Fan_Target=70
Fan_Acoustic=910
Power_Temp=90
Power_Target=0

[Profile_1]
Name=580
GPU_P0=300;750
GPU_P1=600;769
GPU_P2=918;893
GPU_P3=1167;1050
GPU_P4=1239;1050
GPU_P5=1282;1050
GPU_P6=1326;1050
GPU_P7=1366;1050
Mem_P0=300;750
Mem_P1=1000;800
Mem_P2=2250;900
Fan_Min=1125
Fan_Max=3500
Fan_Target=75
Fan_Acoustic=918
Power_Temp=90
Power_Target=0

And I have found that these 'hold' better then using watt man, afterburner, claymore command line, sapphire, any of them. Really rock solid.

If I could use Phoenix Miner with geth I would be getting 32 and 34.5 MHS on the 570s and 580s respectively but nope, I am suffering with Claymore still. haha.

murgorx

member

Activity: 443

Merit: 13

Quote from: KJCrypto on February 03, 2018, 08:28:08 AM

The dev is working those feature into the program but for now, use overdriveNtool by the guy on guru3d

Works great for all overclocking, undervolting and fan control. I mod all my bios with Polaris 1.6 but if I need to tweak anything after I use overdriveNtool

Could you please share a simple guide on how to undervolt with this tool mate? I don't want to mess up my cards Cheesy

I don't know if I should even do it, since for the first two weeks my rig is finally stable *fingers crossed* and I don't know if that would cause any instability, that's why I'm asking. It just much simple with those commands to do it and not go in-depth, that's why I asked, I don't mind waiting tho. Electricity is 0.06usd, so 100-150w won't cause me to lose much of the profit. It just bugs me, that the cards are getting hot and the fans, therefore, are working at 60%, producing a lot of noise.

KJCrypto

newbie

Activity: 14

Merit: 0

The dev is working those feature into the program but for now use overdriveNtool by the guy on guru3d

Works great for all over clocking, undervolting and fan control. I mod all my bios with polaris 1.6 but if I need to tweak anything after I use overdriveNtool

murgorx

member

Activity: 443

Merit: 13

Quote from: Yellow_donkey on February 02, 2018, 11:52:43 PM

So sad, almost want to cry...

So 2.5 came and went, 2.6 is here but no solo geth|parity mining.../frowny face & upset tummy.

I think I am the only person asking for it, so not surprised. But will I be surprised with 2.7b?!?

I was having the same issue yesterday for a couple of hours. Just restart the PC and start the file 3-4 times. It should fix it.
ALSO, been mining for 12+ hours straight with the miner, stales are pretty low (7 max, around 5-6%). I am using 2.5b
I have seen a hashrate drop when I connect with TeamViewer btw. One of the cards gets down to 3-4Mh/s from 30.

A question to the DEV - How may I undervolt with this miner? It's drawing 200W more than the Claymore's? I am scared to use undervolting from TRIXX, because my rig freezes if I touch something there Sad

I am using it only to set my fans speed. Are you planning on implementing the -cclock -mclock -cvddc etc etc?
Really happy with the miner so far!

Yellow_donkey

newbie

Activity: 31

Merit: 0

So sad, almost want to cry...

So 2.5 came and went, 2.6 is here but no solo geth|parity mining.../frowny face & upset tummy.

I think I am the only person asking for it, so not surprised. But will I be surprised with 2.7b?!?

https://ibb.co/n5zvM6

KJCrypto

newbie

Activity: 14

Merit: 0

Anyone else getting DEVFEE hang up? Starts to mine on DEVFEE- gets 3-4 ETH shares then INCORRECT SHARES start and it continues until I catch it. Lost 45 minutes as it's contagious and miner kept trying to get DEVFEE and producing incorrect shares one after another. Miner was stable for 10.5 hrs prior. Happened this morning too.

It appears based on logs that GPU 2 drops to 0 hash when devfee starts. But it is different GPU that starts the incorrect share on DEVFEE issue then one after another incorrect share over and over and over on devfee.

shanepottermi

newbie

Activity: 55

Merit: 0

RX 570 an RX 580 dual mined well at 1250 core / 2000-2100 mem but with the ASICs coming out for sia lbry pascal an decred.. sia and lbry are negative roi.. decred an pascal aren't profitable enough now unless ur power is free. Pascal lite is probably profitable for a little bit but both pascal and pascal lite are changing algos to push ASIC off their coins. Right now it might be good to mine pascal lite an wait for the algo switch (which will probably be to cryptonote or cryptonight) but you can't sell pascal lite cuz they're only listed on Cryptopia and their wallet has been down for weeks.. so no where to sell them at the moment.

puch0021

newbie

Activity: 35

Merit: 0

With dual mining you need an adequate amount of core overclock or higher power limits to support it vs mining ethereum solo.

When I was testing with mining ethereum solo, I could pull off 50% power limit without significant hash rate differences. With my calculations including power consumption, the lower the power limit the better. If I attempted to dual mine with that low of a power limit, the ethereum hash rate took a nose dive and I couldn't use a 50% power limit anymore.

The increased power consumption is something to consider when considering the profitability. It wasn't worth the headache of fine tuning for ~10-15 cents more a day.

minahan24

newbie

Activity: 23

Merit: 0

Requesting for Pascal Lite support in dual mining.

shanepottermi

newbie

Activity: 55

Merit: 0

It probably isn't worth pushing back the linux version for dual mining capability. The Chinese released ASIC for Lbry, Pascal, Sia, and Decred so there isn't any point in dual mining anymore. If someone develops algos that play well with ethash in the future you'd probably need to start building from scratch anyways. The other tweaks are pretty sweet but once you get that linux version up an running talk to the ethOS guys an get them to incorporate your miner in their OS. I got 2 rigs on ethOS linux with 10 cards an 12 cards cuz windows don't play well with a lot of gpus on a single rig.. given the new mining boards coming out that can house 12+ gpus i think windows mining is going to be getting phased out by people running larger farms which i'm guessing is more your bread an butter target market. I'm running your miner on my desktop with 4 gpus an already wish the linux version was available for my other rigs. Faster hash rate, less fees, no dag switches. I get what you're saying about the dag switches I haven't watched enough to see the dev mining fee to see if my cards still have to spin up an i'm only running this on my small system anyways so even if i could see it it wouldn't be nearly as obvious as my other systems with 3x-4x as many cards. I skimmed the commands an i don't recall seeing a feature similar to -powlim from claymore. That would be a good feature to have so you can tweak power consumption. I'm not a pro or anything but I noticed that my cards will run at say 30mh/s with powerlimit 20.. but if I lower powerlimit it will drop total power consumption without decreasing hashrate or stability so the cards will just use whatever power they can for the most part. It would be nice to have the feature incorporated in the miner so we don't have to go around reflashing cards to find the sweet spot using powerlimit % / tdp in bios.

evlo

jr. member

Activity: 155

Merit: 4

So I started 26b on all nvidia rigs (24 on AMD seems stable so far - claymore is still benchmark for me, i could get 20 days, or as long as power would not go out

), let's see in few days

I Still wonder how stale shares work, as even ethminer 13 got it to the half of what 12 produced. And I thought I'm having network issues.

Miner59

newbie

Activity: 5

Merit: 0

Quote from: PhoenixMiner on February 02, 2018, 12:26:34 PM

Quote from: Miner59 on February 01, 2018, 01:02:15 PM

Been using this miner for like 6 hours now and it's amazing. 4-5 MH/s more than Claymore, which is great!

But I'm having this weird problem right now, I have 2x RX560's which are getting 14.7 MH/s each, but every ~10 seconds they both drop to ~12 MH/s for 2 seconds and then it goes back to 14.7 MH/s. My RX580's are not doing this and are keeping strong on the 30.5 MH/s mark. With Claymore I do not have this issue, I also tested this with Ethminer and the RX560's do not drop in hashrate at all.

Would be great if you could get that fixed somehow, other than that, this miner simply amazes me, keep up the good work!

Please try using the command line option -mi with different values (for example 8, or 9 instead of the default value of 10). You can change it only for the RX560s by using it like this:

Code:

-mi 8,8,10,10,10

In the above example the first two cards will run with mining intensity 8, and the other three - with mining intensity 10. This assumes that the RX560s are the first and the second card and you have five cards in the rig. The order of the cards must be the same that is listed by PhoenixMiner when starting up.

Didn't change much, still dropping hashrate.

alkoholik24

newbie

Activity: 2

Merit: 0

Quote

Please use a batch file to start the miner with the following contents (the important part are the setx statements to set the environment variables):

Code:

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 -clKernel 1 -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x36fd6ca7b320c46189bb9e78f5390573cace4745.Rig003 -proto 3
pause

Still the same problem. Occurs on different GPU, sometimes on 2 simultaneously.

P00P135

full member

Activity: 1125

Merit: 136

Quote from: zeii on February 02, 2018, 03:36:05 AM

Quote from: P00P135 on February 01, 2018, 05:57:38 PM

Trojan.Win64.Wdfload is back in this version.

https://www.virustotal.com/#/file/57b3f97da3918232205201daf548a522a1dba920c1fccd94a483bad30420ed59/detection

this from claymore
https://www.virustotal.com/#/file/eec33b077ffa3ed4226ba97b7b6d996177cd1b01b6825abc3d8a6aa5b877cb32/detection

There is a big difference being flagged for riskware coin miners and a specific trojan. Also a few previous releases didn't have any flags.

PhoenixMiner

full member

Activity: 357

Merit: 101

Quote from: Miner59 on February 01, 2018, 01:02:15 PM

Been using this miner for like 6 hours now and it's amazing. 4-5 MH/s more than Claymore, which is great!

But I'm having this weird problem right now, I have 2x RX560's which are getting 14.7 MH/s each, but every ~10 seconds they both drop to ~12 MH/s for 2 seconds and then it goes back to 14.7 MH/s. My RX580's are not doing this and are keeping strong on the 30.5 MH/s mark. With Claymore I do not have this issue, I also tested this with Ethminer and the RX560's do not drop in hashrate at all.

Would be great if you could get that fixed somehow, other than that, this miner simply amazes me, keep up the good work!

Please try using the command line option -mi with different values (for example 8, or 9 instead of the default value of 10). You can change it only for the RX560s by using it like this:

Code:

-mi 8,8,10,10,10

In the above example the first two cards will run with mining intensity 8, and the other three - with mining intensity 10. This assumes that the RX560s are the first and the second card and you have five cards in the rig. The order of the cards must be the same that is listed by PhoenixMiner when starting up.

Quote from: Dhino on February 01, 2018, 05:29:37 PM

Any plan for Linux version?

Yes, but it was pushed back in order to implement hardware control (fan speed, clocks, voltages) and dual mining for decred first. Also, it would require more testing because there are a lot of Linux distributions that are used for mining. We are planning to release it in about two months now.

Quote from: shanepottermi on February 01, 2018, 08:42:01 PM

If you really want to make your fee lower than claymore and increase the fees you receive i'd suggest running your dev fee less often but for longer. Claymore runs his every hour.. it takes a minute for a system with a lot of gpus to spin them all up making that 30-70 seconds less effective because 10+ seconds its spinning the cards up.. then when it cuts off i have to wait for my cards to spin up to start mining again. It makes his 1% fee a lot larger than 1% an produces less for him. If you ran your fee like once every 4-6 hours instead of every 90 minutes but you ran it for an equivalent time relative to the 90 min dev fee.. we'd all make more long term. You might end up with some of the gamer miners trying to cut the fee but the people running a lot of cards 24/7 won't. Since you're not spinning up all the large farms over n over again for a short burst an instead mined for a 1-2 minutes you'd probably pull more in fees and we'd pay less due to downtime switching to dev pools. Win win for everyone.

The devfee period by itself is not the problem but the switching of DAG epochs. If you are mining any of directly supported coins (Ethereum, Ethereum Classic, Expanse, Musicoin, UBIQ, Pirl, Ellaism, Metaverse ETP, or Pegascoin), the miner will try to detect it and use the same coin for devfee, thus eliminating the DAG switch. If you mine any of these coins and PhoenixMiner fails to detect the coin correctly, use the -coin command-line option as described in the Reamde.txt file (or the first post in this thread) to force the usage of this coin for devfee and eliminate the DAG switches for devfee completely.
Also, if you are mining other ethash-based coins, we will be adding support for new coins soon.

Quote from: alkoholik24 on February 02, 2018, 06:21:57 AM

Hello,

Code:

17564:12:26:44.968: main Phoneix Miner 2.5d Windows/msvc - Release
17564:12:26:44.968: main Cmd line: -pool eu1.ethermine.org:4444 -wal 0x36fd6ca7b320c46189bb9e78f5390573cace4745.Rig003 -proto 3
17564:12:26:47.093: main Available GPUs for mining:
17564:12:26:47.170: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17564:12:26:47.170: main GPU2: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17564:12:26:47.170: main GPU3: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17564:12:26:47.210: main NVML library initialized
17564:12:26:51.887: main Listening for CDM remote manager at port 3333 in read-only mode
17564:12:26:51.887: main Eth: the pool list contains 3 pools
17564:12:26:51.887: main Eth: primary pool: eu1.ethermine.org:4444
17564:12:26:51.888: main Eth: Connecting to ethash pool eu1.ethermine.org:4444
17564:12:26:52.171: eths Eth: Connected to ethash pool eu1.ethermine.org:4444
17564:12:26:52.171: eths Eth: Starting GPU mining
17564:12:26:52.238: wdog Starting watchdog thread
17564:12:26:52.239: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["0x36fd6ca7b320c4g07cab9e78f5390573cace4745.Rig003"]}

17564:12:26:52.294: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17564:12:26:52.295: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

17564:12:26:52.355: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xf4b2522add423224a6cb7b8f6388076fcc9d2b37ef4576e8ee8ed4f2f1bf4242","0xb683d2a97f567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4c8da2"]}
17564:12:26:52.355: eths Eth: New job #f4b2522a from eu1.ethermine.org:4444; diff: 4000MH
17564:12:26:52.360: GPU1 GPU1: Starting up...
17564:12:26:52.360: GPU1 Eth: Generating light cache for epoch #167
17564:12:26:52.381: GPU2 GPU2: Starting up...
17564:12:26:54.430: GPU3 GPU3: Starting up...
17564:12:26:55.306: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x29db229bbcc8f6acc243be972de280ed12e2a302b18c1a00eeeda7bc7b2f9fbb","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4c8da3"]}
17564:12:26:55.306: eths Eth: New job #29db229b from eu1.ethermine.org:4444; diff: 4000MH
17564:12:26:56.977: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17564:12:26:56.977: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
17564:12:26:59.874: GPU2 GPU2: Allocating DAG (2.32) GB; good for epoch up to #169
17564:12:26:59.984: GPU2 CUDA error in CudaProgram.cu:282 : out of memory (2)
17564:12:26:59.987: GPU1 GPU1: Allocating DAG (2.32) GB; good for epoch up to #169
17564:12:27:00.004: GPU2 GPU2 initMiner error: out of memory
17564:12:27:00.191: GPU3 GPU3: Allocating DAG (2.32) GB; good for epoch up to #169
17564:12:27:00.318: GPU3 CUDA error in CudaProgram.cu:282 : out of memory (2)
17564:12:27:00.318: GPU3 GPU3 initMiner error: out of memory
17564:12:27:00.400: GPU1 GPU1: Allocating light cache buffer (37.1) MB; good for epoch up to #169
17564:12:27:00.521: GPU1 GPU1: Generating DAG for epoch #167
17564:12:27:00.572: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2e8a792c718867a8bdf1df222574c99b608f9a441e2b75bbc50af387f5842ad4","0xb683d2a971567602a1931b76b9fb447dd5563f0e4ab5dd69250556e7c1c94783","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4c8da4"]}
17564:12:27:00.572: eths Eth: New job #2e8a792c from eu1.ethermine.org:4444; diff: 4000MH
17564:12:27:00.590: GPU2 GPU2: Starting up...
17564:12:27:00.603: GPU3 GPU3: Starting up...
17564:12:27:00.848: wdog GPU thread(s) not responding. Restarting.
17564:12:27:02.073: GPU1 GPU1: DAG 13%
17564:12:27:02.084: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17564:12:27:02.084: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
17564:12:27:03.755: GPU1 GPU1: DAG 25%

the same in PhoenixMiner2.4
GPU default setting

Why is that?

Please use a batch file to start the miner with the following contents (the important part are the setx statements to set the environment variables):

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 -clKernel 1 -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x36fd6ca7b320c46189bb9e78f5390573cace4745.Rig003 -proto 3
pause

Quote from: Aurren on February 02, 2018, 11:33:30 AM

Tried the 2.5d and got a lot of stale (but when I switched back to claymore I noticed a lot of stale shares too (15%+)). When the stale shares went back to normal with claymore 2-4%, I got 2.6b and tried again. Getting normal amount of stales again, so far so good.

I've noticed that the log file stays at 1 KB until I stop the miner. Is the log file in memory until I stop it? I'm worried about running out of memory.

No, the file is not kept in memory, but Windows Explorer doesn't show the size of the file properly. Press F5 while Windows Explorer is open in the PhoenixMiner folder and you will see the real size of the log file.

Finally, a reminder that the release candidate of 2.6b is out with a possible fix for those that see more stales with 2.5d (and other improvements). For more information see this post: https://bitcointalksearch.org/topic/m.29359128.

Aurren

newbie

Activity: 8

Merit: 0

Tried the 2.5d and got a lot of stale (but when I switched back to claymore I noticed a lot of stale shares too (15%+)). When the stale shares went back to normal with claymore 2-4%, I got 2.6b and tried again. Getting normal amount of stales again, so far so good.

I've noticed that the log file stays at 1 KB until I stop the miner. Is the log file in memory until I stop it? I'm worried about running out of memory.

Hobosnax

newbie

Activity: 2

Merit: 0

Quote from: santan on February 02, 2018, 04:13:13 AM

Quote from: PcChip on February 01, 2018, 05:32:41 PM

I'm getting "Debugger detected" on my gaming rig, which I do have Visual studio installed as I'm a hobbyist visual c++ programmer - could that be why ?

Use the switch ..... -nvidia
if you are on NVIDIA GPU.... I was in the same situation.... solved by it.

Thanks, this fixed the "Debugger detected" error on my 1060 rig.

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