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

[UnclWish]

hi friends, I have a rig with 5 - RX570 4gb, I was using the Clymore it has always worked well but lately the GPU0 does not start, mostly it is at 0.00mhs, in few opportunities to open and close the Clymore all 5 cards started, but I am getting tired, I read that with this miner (Phoenix) all 4GB cards work well, I am testing configurations but no! With this miner now GP0 does not start, it is always at 0.00, what can I do? is there any specific configuration?


tested configurarion:

Wind 10x64, Driver amd: Radeon Software Crimson ReLive Edition Beta for Blockchain Compute Driver Version 17.30.1029 (Windows Driver Store Version 22.19.659.0)

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 us1.ethermine.org:4444 -wal 0xa1780dMIWALLET.Myrig -mport -3000 -dagrestart 1 -rvram -1 -eres 0
pause

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 us1.ethermine.org:4444 -wal 0xa1780dMIWALLET -worker Myrig -epsw x -mode 1 -log 0 -mport -3000 -etha 0 -ftime 55 -retrydelay 1 -tt 79 -tstop 89  -coin eth
pause

Code:

GPUs: 1: 0.000 MH/s (0) 2: 28.592 MH/s (0) 3: 28.808 MH/s (0) 4: 28.803 MH/s (0) 5: 28.810 MH/s (0)
GPU1: 45C 85% 77W, GPU2: 56C 80% 147W, GPU3: 52C 85% 125W, GPU4: 52C 85% 120W, GPU5: 53C 85% 138W
GPUs power: 606.5 W

You need one of latest AMD drivers for use PM miner. Your driver is too old.
Here Phoenix Miner wrotes about 4Gb cards and driver versions: https://bitcointalk.org/index.php?topic=2647654.msg54541099#msg54541099

IMPORTANT!  ETC is already at DAG epoch 350, so you must use PhoenixMiner 5.0b or later if you have 4 GB AMD cards. Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0b:

• If your rig is using Intel CPU, use the integrated graphics as primary display adapter. To do this, go to motherboard's BIOS setup and change the "Primary display adapter" to iGPU (or integrated GPU). Also, if you are using actual monitor or HDMI plug, put it in the motherboard video output.
• If you can't use integrated GPU, replace the primary GPU with one with 6 or 8 GB VRAM.
• Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
• After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.

After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers:

• Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.4.2 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
• Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
• Drivers older than 18.1.1 were not tested for 4 GB DAG operation.

Under Linux all relatively recent drivers (i.e. last 24-36 months) allow mining until epoch 378-380 but there are much more driver bugs, so if you are happy with your current driver version, do not change it.

[UnclWish]

Hello, thanks for answering, which configuration and drivers do you recommend to install? I use Etherminer pool, I have the last PMiner, i installed the 20.4.2 drivers but it does not work well either, the first continuous in 0mhs, and by the way I am underperforming. at 11mhs

Code:

No CUDA driver found
OpenCL driver version: 20.4.1-2
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 32 CUs
GPU2: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 32 CUs
GPU3: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 32 CUs
GPU4: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 4 GB VRAM, 32 CUs
GPU5: Radeon RX 570 Series (pcie 8), OpenCL 2.0, 4 GB VRAM, 32 CUs

Eth speed: 46.361 MH/s, shares: 1/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 11.588 MH/s (0) 3: 11.599 MH/s (0) 4: 11.620 MH/s (0) 5: 11.554 MH/s (1)
GPU1: 33C 85% 5W, GPU2: 46C 85% 88W, GPU3: 45C 85% 90W, GPU4: 45C 85% 88W, GPU5: 44C 85% 89W
GPUs power: 359.4 W

Drivers 20.4.2 is normal. You can use them. Did you changed GPU's workflow to "compute" in Radeon Settings? You can press "Y" during PM mining to change GPU's workflow to "compute".
What command line you're using? What command line you used for CM? PM supports most of CM options. Press "Z" key after launching for autotune the -gt parameter. It use about 5-10 minutes.
Did you set enough pagefile size?
Monitor connected to your 1st GPU?

[BFL88]

can't get it to work, does anyone have any ideas....?

Thanks for any help!

If you see "Unknow opencl driver..." at the beginning of the log you need to install newer driver.

Thanks @bategojko74 ..!

Updated drivers - Phoenix worked a few seconds longer - but still quits.

However, claymore works again now, thanks for your help!

[UnclWish]

Monitor connected to GPU1?

[UnclWish]

Monitor connected to GPU1?

yes my friend, a monitor by HDMI cable, also connect the cable in the GPU2 and the same thing happens, the GP1 that is in the main pcixpress, I also try to boot without connecting any hdmi cable to the cards, and nothing, my motherboard has no integrated video

I think Windows uses more video memory on primary videocard. This causes your problem. And nothing will help there. You need integrated videocard or 1st GPU with 6G or 8G onboard...

[sxemini]

Monitor connected to GPU1?

yes my friend, a monitor by HDMI cable, also connect the cable in the GPU2 and the same thing happens, the GP1 that is in the main pcixpress, I also try to boot without connecting any hdmi cable to the cards, and nothing, my motherboard has no integrated video

I think Windows uses more video memory on primary videocard. This causes your problem. And nothing will help there. You need integrated videocard or 1st GPU with 6G or 8G onboard...

+1

Nothing more to say.

[shimmishim]

Nothing is pushing "P" and also the window would need to be selected for that to occur so it must be generating an error somehow or is it possible that antivirus could cause it to stop as well? I'm just frustrated trying to figure out what the heck would cause it to just stop like this. it's maddening. All my other mining rigs are fine but this one... just 1 card is causing me the biggest headache.  If I can't run it, it's not the end of the world but would still like to know why the heck this is happening.

Crazy stuff, my single RX580 get recognized as two RX580 GPUs. and mining at 12MH/s each,
while fan stays at 0 rpm, until it crashes due to overheating

Does anyone have latest AMD driver and latest 2004 windows 10 version, and its working well?

  Probably a driver issue with two OpenCL drivers each reporting the same GPU. We had somewhat similar issue with DDU not removing the drivers completely -  to be sure, please check if all Radeon GPUs are missing from the Device Manager after DDU finishes and restarts the PC (and before installing the new drivers) - you should see only the iGPU and generic "Microsoft Display Adapter" GPUs there. If there is a Radeon GPU still recognized, DDU must be started again to finish the job before installing the new drivers.

   On a related note, you will need PhoenixMiner 5.1b for the latest AMD drivers 20.7.1 to work properly.

I'm getting a strange occurrence. It took me a while to troubleshoot and I just can't seem to figure out what's wrong. After a random amount of time (anywhere between 5 minutes to almost 2 hours), the miner will "pause" and indicates to press any key to continue at which point it just shuts off. There's no error message. It just says "pause Press any key to continue..." Does anyone know what might cause this? Thanks!

   Check if something emulates pressing 'p' in the console window (it may be some process that "feeds" text data to the standard input of PhoenixMiner and if 'p' occurs there, the miner will be paused).

[Ursul0]

The new beta version is ready. You can download PhoenixMiner 5.1b from here:

https://mega.nz/folder/XYkTQZiI#HT_dcKdLtsU26nwbE8pMBQ  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.1b_Windows.zip
    ===================================
   SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
 SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
 SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd

    File: PhoenixMiner_5.1b_Linux.tar.gz
    ====================================
   SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
 SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
 SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The new features in this release are:

• Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
• Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
• Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
• Fixed long-standing problems with -gpow option, which now works properly
• Many other small improvements and fixes

Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:

• Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
• The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
• The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
• When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
• The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.

Please let us know if you have any problems or questions related to PhoenixMiner 5.1b.

@PhoenixMiner I think you may want to add a delay in applying the memory timings, so it will be applied AFTER the DAG generation. could be the same story with increasing the mem frequency

keep seeing stuff like this:

and inconsistent:


however applying edited config after the dag generation works ok:

[commandera]

it was run fine now all 7 GPU's 0.000
https://imgur.com/a/DlwNVCW

[Ursul0]

could be very useful not to run the pill separately, as it does work applied after the dag generalion:


@Phoenixminer - if you can make a section of config file for delayed execution that would be good enough.
good job on timings integration!
adding kawpow could be even better, as this miner is mostly very stable:)  

[claypaky]

do new features work under linux?

[echo00114]

I just woud like to register here my ethash rate on my 24x Asus (Arez) RX 580 8GB

30.1 Mh/s stable
https://i.ibb.co/0cVRbBT/hash-rate.png

Rigs
https://i.ibb.co/q7T8FNM/RX-580-8-GB.png
https://i.ibb.co/xJ2p6JQ/RX-580-8-GB-1.png


-tmax 69
-fanmin 70
-tstop 75
-tstart 40
-minRigSpeed 155
-hstats 2
-cdmpass ********
-mt 1
-cclock 1100
-cvddc 800
-mclock 2050
-mvddc 825
-rmode 2

I did some modifications on the timmings like:
--R2W 31 --RC 75 --RRD 5 --RCDRA 26 --RCDR 26 --RCDWA 14 --RCDW 14 --RFC 184 --RP_WRA 55 --RASMACTWR 33 --RASMACTRD 28 --ACTWR 9 --ACTRD 10 --RAS2RAS 101 --RP 24 --WRPLUSRP 30 --REF 45

PhoenixMiner 5.0e
AMD driver 20.4.2
Windows 10 19041.264

I still need to finish installing the other cards
Using 4x 220v 23w FAN at the back of each the rig (too loud)

hello
how set the timings ? read the readme and nothing found i try google some forums and nothing my best speed my rx 580 25 mhs please help
thank you

[guyom78]

Hello,

I have two 5700xt mining together.
I would like to put differents fan settings like that, but it's not working, only one card is working the first one (-gpus 1) :

Code:

PhoenixMiner.exe -pool pool -wal wallet -worker worker 
-gpus 1 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 75 -fanmax 100 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1 
-gpus 2 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 50 -fanmax 75 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1

Is there a way to make different settings for each cards?

Thanks for any advice.  

[Ursul0]

Hello,

I have two 5700xt mining together.
I would like to put differents fan settings like that, but it's not working, only one card is working the first one (-gpus 1) :

Code:

PhoenixMiner.exe -pool pool -wal wallet -worker worker 
-gpus 1 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 75 -fanmax 100 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1 
-gpus 2 -gt 55 -tt 67 -cvddc 750 -cclock 1300 -fanmin 50 -fanmax 75 -mclock 1850 -amd -mode 1 -clKernel 1 -clNew 1

Is there a way to make different settings for each cards?

Thanks for any advice.  

use overdriventool for volts and frequencies on amd.
just run scheduled task on login with something like: OverdriveNTool.exe  -p1"My_profile1" -p2"My_profile2"

[fiucsavar]

Could someone explain what does this new strap command do? Does it worth to start experiment with it? Should we see better hashrate with it?

[maxime506]

The new beta version is ready. You can download PhoenixMiner 5.1b from here:

https://mega.nz/folder/XYkTQZiI#HT_dcKdLtsU26nwbE8pMBQ  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_5.1b_Windows.zip
    ===================================
   SHA-1: b71a5b22bb9a6fbd26d4a85272f73defabad2b70
 SHA-256: 1592d04efa4ef427b6e42388d012ac6a68154f09848aaaa4f0418e3425e07155
 SHA-512: c543b8bc5d0c345e81fb2586b2807b842fc2b666bd033ceb78820d1732a61ef8529a228f9df8777029dfc9f7a8e90853fa65600c4d3b976787e1630f0ea03dfd

    File: PhoenixMiner_5.1b_Linux.tar.gz
    ====================================
   SHA-1: 9ba244a12698ca30015ef273c9f3cd9a9443c04f
 SHA-256: ade4a07bd0c738fb875b2a42b5153271fedd23c60ba4527655360a8f718be4de
 SHA-512: 860491408731c63bf42bb8288711de2f29534b4bac14313e376869d221a62a985ce4ea1a5a22cb39d875eb876016aa741275702665cc3ee1116c5cc3637ec21c

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The new features in this release are:

• Added support for VRAM timing adjustments for Nvidia cards of 10x0 series (see the new command-line parameters -straps, -vmt1, -vmt2, -vmt3, and -vmr for more information)
• Added -ttli option to automatically decrease the mining speed to avoid overheating the GPUs over the target temperature (useful when -tmax option is not supported by the drivers)
• Added support for latest AMD drivers 20.7.1 under Windows and 20.20-1089974 under Linux
• Fixed long-standing problems with -gpow option, which now works properly
• Many other small improvements and fixes

Here are some additional notes about the VRAM timing adjustments of Nvidia 10x0 cards:

• Most recent Nvidia drivers require running as administrator (or as root under Linux) to allow hardware control, so you need to run PhoenixMiner as administrator for the VRAM timing options to work.
• The four independently adjustable VRAM timings are controlled by four different parameters: -vmt1, -vmt2, -vmt3, and -vmr. The last one controls the memory refresh rate, and the first three are other timings. The possible values for each of them are from 0 to 100, where 0 are the default timings, and 100 is the most aggressive timing (most GPUs probably wont work with 100).
• The -straps option gives an easy way to set one of the predefined levels of VRAM timing adjustment. The possible values are 0 to 6. 0 is the default value and uses the default timings from the VBIOS. Each strap level corresponds to a predefined set of memory timings ("-vmt1", "-vmt2", "-vmt3", "-vmr"). Strap level 3 is the fastest predefined level and may not work on most cards, 1 is the slowest (but still faster than the default timings). Strap levels 4 to 6 are the same as 1 to 3 but with less aggressive refresh rates (i.e. lower "-vmr" values).
• When using the VRAM timing options, start with lower values and make sure that the cards are stable before trying higher and more aggressive settings. You can use -straps along with the other options. For example -straps 1 -vmt1 60 will use the timings from 1st strap level but -vmt1 will be set to 60 instead of whatever value is specified by the 1st strap level. In such case the -straps option must be specified first.
• The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.

Please let us know if you have any problems or questions related to PhoenixMiner 5.1b.

Can you add memory strap support to the P106 series GPUs as well (P106-100, P106-90). They're basically just GTX 1060 but the mining version.

Here's the log output:

2020.07.19:07:08:19.473: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 -bench 0 -straps 5
2020.07.19:07:08:19.673: main CUDA version: 11.0, CUDA runtime: 8.0
2020.07.19:07:08:19.740: main No OpenCL platforms found
2020.07.19:07:08:19.740: main Available GPUs for mining:
2020.07.19:07:08:19.740: main GPU1: P106-100 (pcie 2), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2020.07.19:07:08:19.740: main GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2020.07.19:07:08:19.740: main GPU3: P106-090 (pcie 6), CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.740: main GPU4: P106-090 (pcie 7), CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.740: main GPU5: P106-090 (pcie , CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.740: main GPU6: P106-090 (pcie 9), CUDA cap. 6.1, 2.9 GB VRAM, 5 CUs
2020.07.19:07:08:19.749: main NVML library initialized
2020.07.19:07:08:19.796: main Nvidia driver version: 445.87
2020.07.19:07:08:19.800: main NVAPI error in NvapiWrapper.c:301 : -6
2020.07.19:07:08:19.800: main Unable to load NvAPI: error 3
2020.07.19:07:08:20.841: main Benchmark mode. DAG epoch #0
2020.07.19:07:08:20.841: main GPU1: unable to init NvAPI with bus ID 131072
2020.07.19:07:08:20.841: main GPU2: unable to init NvAPI with bus ID 196608
2020.07.19:07:08:20.841: main GPU3: unable to init NvAPI with bus ID 393216
2020.07.19:07:08:20.841: main GPU4: unable to init NvAPI with bus ID 458752
2020.07.19:07:08:20.841: main GPU5: unable to init NvAPI with bus ID 524288
2020.07.19:07:08:20.842: main GPU6: unable to init NvAPI with bus ID 589824
2020.07.19:07:08:22.660: hwmc GPU5: unable to get fan speed - Unknown Error (999)
2020.07.19:07:08:23.847: GPU1 GPU1: Starting up... (0)
2020.07.19:07:08:23.847: GPU1 GPU1: Generating ethash light cache for epoch #0
2020.07.19:07:08:23.851: GPU2 GPU2: Starting up... (0)
2020.07.19:07:08:23.854: GPU3 GPU3: Starting up... (0)
2020.07.19:07:08:23.860: GPU4 GPU4: Starting up... (0)
2020.07.19:07:08:23.865: GPU5 GPU5: Starting up... (0)
2020.07.19:07:08:23.867: GPU6 GPU6: Starting up... (0)
2020.07.19:07:08:23.872: wdog Starting watchdog thread
2020.07.19:07:08:24.487: hwmc GPU1: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU2: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU3: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU4: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU5: unable to set straps - unsupported GPU
2020.07.19:07:08:24.487: hwmc GPU6: unable to set straps - unsupported GPU

[patthara74]

I plan to buy a new card but heard about problem with amd driver after DAG size over 4GB although on 8gb card. Did this still be a problem?

[bategojko74]

I plan to buy a new card but heard about problem with amd driver after DAG size over 4GB although on 8gb card. Did this still be a problem?

No

[BeefyBitcoinBoy]

Just reporting an issue I ran into on v5.1b with mixed-gen ETH mining on one XFX RX 5700 8GB + one XFX RX 480 8GB + one MSI RX 480 8GB on Ubuntu 20.04 (via both minerstatOS v1.5 and v1.6).  When I upgraded from PhoenixMiner v5.0e to v5.1b, I saw my RX 5700 hashrate drop to about 58% of normal, and the two RX 480s dropped to about 67% of normal hashrate.  Whether related to the miner or the OS, I cannot say, but I also saw the GPU memory clocks intermittently bouncing back to stock settings for 20 seconds at a time instead of locking in at my normal overclocks, and I would hear the fans adjust their throttles each time the clocks adjusted.

Rolling back to v5.0e followed by a reboot seems to have resolved these issues.  I have happily used a few versions of the PhoenixMiner for about four months on this mixed-gen rig without issue, so this was a bit of a surprise.  Unfortunately, my normal log file didn't have any suspicious messages or errors to report.

[patthara74]

please advice me. Now almost all vendor in my country cut off warranty if I flash bios so I have been use claymore with strap for a long time. after he look like stop update I start to try mining with pheonix miner but got a probelm.

I try -mt option. My asus 570 8gb (not flash bios) with mt 0 got 25MH, 4.0MH with -mt 1 and crash with -mt 2.

What am I done wrong? please advice me. I use latest amd driver.