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

Cyhnzy

newbie

Activity: 4

Merit: 0

Hello friends asrock rx 5700 xt 54.2 mhs works on average for 7-8 hours and stops giving errors ,do you have commands to detect and start automatically? how is it done, if any ? waiting for your help...Thanks
if it stops when I'm not near the Computer, How do I set it to work again ? - wdtimeout does this command Work, How Should I do the bat file.

this is my bat file :

PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal 0x86a77ab5dee66b948c4afa124e55d7c7cd5ef3bd -worker ceyo -epsw x -mode 1 -log 0 -mport 0 -hstats 2 -etha 0 -ftime 55 -retrydelay 1 -tt 79 -tstop 89 -coin eth -mclock 1886 -mvddc 900 -cvddc 785 -cclock 1420 -gt 43 -clKernel 1 -clNew 1 -clf 1 -minRigSpeed 52 -eres 2 -daglim 6000 -lidag 3 -rvram 384 -wdog 1 -wdtimeout 45 -rmode 1 -fanmin -1 -fanmax -1 -fcm 0 -tmax 0 -powlim 50
pause

gpu : asrock rx 5700 xt phantom gaming oc

melpheos

jr. member

Activity: 557

Merit: 5

Quote from: Cyhnzy on January 08, 2021, 01:34:01 PM

merhaba arkadaşlar asrock rx 5700 xt 54.2mhs ortalama 7-8 saat çalışıp hata verip duruyor, otomatik olarak durdugunu algılayıp başlatabilme komutları varmı ? var ise nasıl yapılır ? yardımlarınızı bekliyorum...Teşekkürler

And in english ?

Cyhnzy

newbie

Activity: 4

Merit: 0

merhaba arkadaşlar asrock rx 5700 xt 54.2mhs ortalama 7-8 saat çalışıp hata verip duruyor, otomatik olarak durdugunu algılayıp başlatabilme komutları varmı ? var ise nasıl yapılır ? yardımlarınızı bekliyorum...Teşekkürler

AzzAz

legendary

Activity: 1030

Merit: 1006

Quote from: reep74 on January 08, 2021, 11:26:12 AM

Quote from: bit-sokol on January 08, 2021, 11:23:02 AM

Quote from: reep74 on January 08, 2021, 11:16:13 AM

Quote from: ?? on ??

Quote from: bit-sokol on January 08, 2021, 10:33:45 AM

Quote from: reep74 on January 08, 2021, 10:31:21 AM

Quote from: ?? on ??

Quote from: reep74 on January 08, 2021, 10:13:21 AM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG 22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG 65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

Same problem, delete all and paste what you write and same vram problem, today was working fine, i did not update nothing and stop mining

go back and read few post, I had same problem post #7311 ( https://bitcointalksearch.org/topic/m.56049534 )
Also, windows 20.4 with PM 5.4c and AMD 20.11.2 working nice

+merit if solved

reep74

newbie

Activity: 14

Merit: 0

Quote from: Xform on January 08, 2021, 12:11:50 PM

Quote from: reep74 on January 08, 2021, 11:16:13 AM

Same but i saw this:

Try -eres 0 -rvram -1

ya lo intente, estoy instalando los drivers de nuevo a ver

Xform

newbie

Activity: 5

Merit: 0

Quote from: reep74 on January 08, 2021, 11:16:13 AM

Same but i saw this:

Try -eres 0 -rvram -1

FEKIH

newbie

Activity: 6

Merit: 0

2021.01.08:17:09:48.320: GPU2 GPU2: DAG generated in 9.9 s (414.7 MB/s)
2021.01.08:17:09:48.321: GPU2 GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
2021.01.08:17:09:48.321: GPU2 GPU2: no -gt value specified, switching to auto-tune
2021.01.08:17:09:48.321: GPU2 GPU2: starting auto-tune process
2021.01.08:17:09:48.321: GPU2 GPU2: clSetKernelArg (-48)
2021.01.08:17:09:48.321: wdog Fatal error detected. Restarting.

reep74

newbie

Activity: 14

Merit: 0

Quote from: bit-sokol on January 08, 2021, 11:23:02 AM

Quote from: reep74 on January 08, 2021, 11:16:13 AM

Quote from: ?? on ??

Quote from: bit-sokol on January 08, 2021, 10:33:45 AM

Quote from: reep74 on January 08, 2021, 10:31:21 AM

Quote from: ?? on ??

Quote from: reep74 on January 08, 2021, 10:13:21 AM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG 22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG 65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

Same problem, delete all and paste what you write and same vram problem, today was working fine, i did not update nothing and stop mining

bit-sokol

newbie

Activity: 48

Merit: 0

Quote from: reep74 on January 08, 2021, 11:16:13 AM

Quote from: ?? on ??

Quote from: bit-sokol on January 08, 2021, 10:33:45 AM

Quote from: reep74 on January 08, 2021, 10:31:21 AM

Quote from: ?? on ??

Quote from: reep74 on January 08, 2021, 10:13:21 AM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG 22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG 65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

reep74

newbie

Activity: 14

Merit: 0

Quote from: ?? on ??

Quote from: bit-sokol on January 08, 2021, 10:33:45 AM

Quote from: reep74 on January 08, 2021, 10:31:21 AM

Quote from: ?? on ??

Quote from: reep74 on January 08, 2021, 10:13:21 AM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG 22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG 65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

bit-sokol

newbie

Activity: 48

Merit: 0

Quote from: reep74 on January 08, 2021, 10:31:21 AM

Quote from: ?? on ??

Quote from: reep74 on January 08, 2021, 10:13:21 AM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

reep74

newbie

Activity: 14

Merit: 0

Quote from: ?? on ??

Quote from: reep74 on January 08, 2021, 10:13:21 AM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

reep74

newbie

Activity: 14

Merit: 0

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

batsonxl

member

Activity: 1201

Merit: 26

@Mr.Phoenix please fix issue with miner. it is consuming more power than used to be. it happened like 10 days ago. Since then my rigs are consuming more power and getting hotter. Same settings nothing changed but wattmeter shows more now. thanks

Baldezh2016

newbie

Activity: 22

Merit: 0

Quote from: 18-Terahash on January 08, 2021, 09:36:36 AM

Quote from: Baldezh2016 on January 08, 2021, 09:33:19 AM

anyone tried to compare hashrate on GTX 1080 vs claymore?

yes, it's pretty much the same.

On AMD there's a noticeable difference (cca 1MH/s higher). Besides that I can see a much more consistent submitted share count compared to Claymore. The graph is not so choppy but almost a nice straight line. This goes for nVidia gpus as well.

thank you, seems not worth to try another miner

PepsiCoin88

newbie

Activity: 13

Merit: 0

Quote from: ?? on ??

Quote from: PepsiCoin88 on January 08, 2021, 09:25:48 AM

Hi! Only now I noticed that my AMD RX 570 (8 Gb) began to give out not 31 MH/s, but 29 MH/s (all cards). What could be the reason? Overheating (cards suffer a little from it - all at least 74 degrees Celsius)? Or is it normal?
Thank you, sorry for my English Grin

Which driver?
Turn on calculation mode.

Most recent

18-Terahash

newbie

Activity: 29

Merit: 0

Quote from: Baldezh2016 on January 08, 2021, 09:33:19 AM

anyone tried to compare hashrate on GTX 1080 vs claymore?

yes, it's pretty much the same.

On AMD there's a noticeable difference (cca 1MH/s higher). Besides that I can see a much more consistent submitted share count compared to Claymore. The graph is not so choppy but almost a nice straight line. This goes for nVidia gpus as well.

oklickmanworld

newbie

Activity: 17

Merit: 0

tell me what the problem may be
I run the miner (Phoenix) on ETH, it works stably: Ubuntu 18.04.05, h110-d3a, g4400 6 cards msi rx 588, drivers 18.20, RAM 8gb, swap file 60gb, the system is on ssd-120gb.
The problem is that the miner is constantly stopped due to a memory segmentation error (the memory stack is flushed to disk).

I tried different Ubuntu distributions, different driver versions, different versions of Phoenix miner (and other miners!!), different versions of the bios, the problem does not go away, it can work from 3 minutes to 3 days

on 1 video card, the system started, and worked stably, but after setting all 6 cards, this error was repeated, I tried to shoot some of the cards, the problem did not go away.
Tell me what to do?
Huh