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

[sentenza63]

Hello everybody;

i have an issue with nanopool, i can't change the password and hence the payout limit

 here is my config :

C:\Users\troll\Documents\etherum\PhoenixMiner\PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal wallet.Myrig/Bobmarley87 -rvram -1 -eres 0

error message :

Incorrect password

anybody have an idea?

thx all

[1715386942]

1715386942

[1715386942]

1715386942

[1715386942]

1715386942

[1715386942]

1715386942

[Vann]

Try this syntax:

Code:

PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal wallet.Myrig/Bobmarley87.Myrig/Bobmarley87 -rvram -1 -eres 0

e.g.
PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal walletaddress.worker/password.worker/password -rvram -1 -eres 0

[sentenza63]

Hello Vann;

thank you for your answer but still the same issue; i double checked case and unneeded space without success

[Vann]

Haven't mined on Nanopool for  a while. That was the syntax I used for the Claymore miner. Try this:

PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -worker Myrig -wal wallet -pass Bobmarley87 -rvram -1 -eres 0

[sentenza63]

still doesnt works :/
i dont get why

here is the official FAQ

PhoenixMiner.exe PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -pool2 stratum+tcp://eth-eu1.nanopool.org:9999 -wal YOUR_WALLET.YOUR_WORKER/YOUR_EMAIL

very disappointed with nanopool

[parple]

Hello everybody;

i have an issue with nanopool, i can't change the password and hence the payout limit

 here is my config :

C:\Users\troll\Documents\etherum\PhoenixMiner\PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal wallet.Myrig/Bobmarley87 -rvram -1 -eres 0

error message :

Incorrect password

anybody have an idea?

thx all

Had this happen a few times if i'd stopped mining for a few days or changed the password.  I'd leave it run for a while then it would work.  I think my problem was something to do with the worker needing a higher rating of 10. I'm guessing it wanted 10 recent shares before it would allow me to change the payout amount even though the rating on the stats page was way over this.
Most likely a different issue for you but thought i'd mention it.

[Geniusvzla]

Hello everybody;

i have an issue with nanopool, i can't change the password and hence the payout limit

 here is my config :

C:\Users\troll\Documents\etherum\PhoenixMiner\PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal wallet.Myrig/Bobmarley87 -rvram -1 -eres 0

error message :

Incorrect password

anybody have an idea?

thx all

inside *.bat file
C:\Users\troll\Documents\etherum\PhoenixMiner\PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal wallet.Myrig/Bobmarley87@gmail.com -rvram -1 -eres 0

inside epools.txt file
POOL: ssl://eth-eu1.nanopool.org:9433, WAL: wallet.Myrig/Bobmarley87@gmail.com

then:
(wallet) your ETH address
(Myrig) is the name of your worker
(Bobmarley87@gmail.com) is your email
Do not enter a password

After executing the bat file, wait 5 minutes or more and you will be able to make the modifications in Nanopool

[Shlimann]

Hello everybody;

i have an issue with nanopool, i can't change the password and hence the payout limit

 here is my config :

C:\Users\troll\Documents\etherum\PhoenixMiner\PhoenixMiner.exe -pool ssl://eth-eu1.nanopool.org:9433 -wal wallet.Myrig/Bobmarley87 -rvram -1 -eres 0

error message :

Incorrect password

anybody have an idea?

thx all

You need to specify an email, not a worker.

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal YOUR_WALET.Phoenix/mail@example.com -epsw x -coin eth
pause

[sentenza63]

thx guys the last answer was the good one !

[nullius]

I have no dog in the fight between PhoenixMiner and NiceHash.  I am just dropping in to note the following:

• The unsigned list of hashes that you provide is worse than useless:  It is a total waste of time, and it is security theatre which causes a false sense of security.
  
  Sorry, but—I am not sorry.  After so many years of dealing with this nonsense, I must be blunt:  To provide an unsigned list of hashes for “verification” requires such a level of mental retardation as to make me wary of everyone who does it.  Oh yes, this world is just chock full of retarded monkeys...  Duh, use some logic:  A hacker who can replace the downloadable files with a malicious version can easily replace the unsigned list of hashes, too.  Why wouldn’t he?  🤔  
• To produce digital signatures, you do not need to reveal your “real” identity.  Use PGP.  That is what I do.  See my PGP key fingerprint in my forum signature.  I did not dox myself to get that!
  
  You only need to dox yourself if you want a code signing certificate from certain CAs—including, I think (?), all of the CAs that Microsoft Windows trusts for Authenticode code signing.  Easy solution:  Use PGP.  Use PGP.  Use PGP.
  
  If you are new to PGP, a fun way to get started is to check out use PGP to send OgNasty a private message in public.  Then, get busy using PGP for digital signatures!  It should go without saying:  Secure your private keys.
• As a privacy advocate, a Tor user, and a strongly pseudonymous party myself, I take offence at the suggestion that only criminals want to avoid being doxed.  What PhoenixMiner alleges NiceHash to have said would make me tend to distrust NiceHash, if that is an authentic quote:
  
  

  In the meantime, we received another message, with quite different tone:
  
  

  djeZo on March 8th, 2021, 07:58:33 AM
  
  Everything will be established back as it was. But I am really curious, why are you so anonymous? I got another hint from someone that you are collecting fees from botnets. Is that true? Because then this is really not good for our business - we cannot afford to be linked with a crime of such proportions. And we would have to make greater distance between.
  
  Also what I dont understand is, even if you are connected with a crime somehow and this is the reason to stay anonymous, why not create a second miner, as a legal business - a miner that you could sign and distribute without any worries for end users?

  
  To be absolutely clear:  I do not know the PhoenixMiner people.  I neither defend them, nor accuse them; and I certainly cannot vouch for them.  They may be honest or dishonest; I do not know, and I have no reason to investigate.  However, I do NOT hold their anonymity against them.
  
  Satoshi Nakamoto never revealed his “real” identity; and according to theymos, he “always used Tor”.  Would NiceHash ask Satoshi, “Why are you so anonymous?  Are you doing something criminal?”  That is just the stupid old “nothing to hide” chestnut.

Note:  I myself would not run closed-source binary blobs from anyone whom I did not deeply trust.  On that particular point, digital signatures are irrelevant.  “Official” identification is irrelevant; I have deeply trusted totally anonymous parties, although that is very rare.  What is relevant is the level of trust required.  I will not hereby launch into some open-source rant; I know that the world is full of scum you want to rip off others’ work, etc., etc.  I simply must note the level of trust involved.


An exemplary lesson on why digital signatures are important:

In November of 2019, an unidentified malicious hacker compromised the downloads of Monero binaries (onion link for Tor users).  Some people got coins stolen straight from their wallets because of this.  I am not so sympathetic to them, for they were foolish:  They didn’t verify the files against the PGP-signed list of hashes.

Anyone who checked the digital signature on the hash list (and then verified the hashes!) was absolutely safe against this attack.  And the hacker could not simply replace the hash list, because he could not fake the digital signature.

The lists of file hashes for Monero downloads are signed by someone named “binaryFate” with the PGP fingerprint 81AC 591F E9C4 B65C 5806  AFC3 F0AF 4D46 2A0B DF92—always check the PGP fingerprint!  I have no idea what binaryFate’s “real name” is, and I do not care; it is none of my business.  I always check the validity of binaryFate’s digital signature.

This raises the question of obtaining and authenticating the signing key.  binaryFate’s public key is in the Monero source code repository; anyone who uses git to track the Monero sources has a copy of the key which would be difficult for an imposter to replace without anyone noticing.  The key is signed by some other people, though that may not be useful if you have not already obtained and authenticated their keys.  And when you import the key, you should check the PGP fingerprint to see if it is what you expect it to be.

Practical tips:

• Use digital signatures.
• Safeguard the private key.
• Distribute the public key in ways that make it easy for others to obtain, and difficult for an imposter to replace with a fake key.
• Scrawl your PGP fingerprint all over the Internet.

[babytaz]

I have problem using phoenix with RX 570 8G

i attached only 1 RX 570 but phoenix detect 2 VGA

GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU2: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs

i try using 5.5c dan 5.4c and the result same. Anyone can help?

[nullius]

Where this much money is involved in this type of industry and software, it would be irresponsible for the developers
to identify themselves and put themselves and their family in uncertain danger.

I agree.  It is undesirable to risk winding up on this list:  https://github.com/jlopp/physical-bitcoin-attacks

The maintainer of that list is not anonymous; his name is Jameson Lopp.  However, he took extraordinary measures to “vanish” after he himself suffered a real-world physical attack.

You can't control stupidity. I also don't feel sorry for any person who is incapable of following plain and simple
security instructions.

Security instructions:  Use PGP for code signing.  Generating a PGP key does not require identifying oneself, just as with generating a Bitcoin key.

The only plausible reasons not to sign code this way are either ignorance, technical ineptitude, or a desire potentially to repudiate the code.  Just do it!

The only people who have had a problem with the PhoenixMiner are the idiots that downloaded a hacked version
from an unauthorized link on a forum page that the developers have said NEVER do.

If that is true, past performance is no guarantee of future results.  What if Github gets hacked?  What if a Github employee acts maliciously, or an Amazon employee with access to Github’s AWS download backend, or...?

Every serious crypto project uses PGP signatures to verify downloads.  Bitcoin Core does not rely on Github’s security, or the security of any download server; they have a highly sophisticated process for making sure you can verify that what you download is exactly what the developers are trying to give you, and it is all ultimately anchored in PGP signatures.  See what I said above about Monero—oh, and I think you can be sure that the Monero people love anonymity!  Examples abound...

Mining takes a certain amount of knowledge, faith, trust and risk.

By design, mining is supposed to be trustless.

If anyone has reservations about the honesty or the safety of the code they are running they should simply format their hard
drives and open a bank savings account. And that is also not 100% safe and secure.

LOL, bank account.  I do not trust that.  I trust my Bitcoin wallet (and my underlying OS) much more.  Of course, I have verified the origin of every bit of code on my system using digital signatures—no exceptions!  There is no excuse to do otherwise!  (I have also audited not-insignificant portions of the source code myself; but that is obviously no way to exclude all vectors for malicious code.)

[Targonis]

I have problem using phoenix with RX 570 8G

i attached only 1 RX 570 but phoenix detect 2 VGA

GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU2: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs

i try using 5.5c dan 5.4c and the result same. Anyone can help?

If you are running Windows, which driver version are you running?   Are you using a riser card?

[DanOG]

I'm on 20.12.1 and been mining for the last couple months just fine.

21.3.1 and 21.3.2 are NOT compatible and have problems with Phoenix at the moment.   The next version is going to fix it, but no information has been given on the version number or when it will be released.

To be honest, 21.1.x was the last really good version.   21.2.1 crashed a LOT when trying to mine and web browse at the same time with my Radeon 6800(non-XT), 21.2.2 and 21.2.3 helped, but still had the occasional driver not responding and recovery(I am using 21.2.3 but performance is down a touch compared to the 21.1 series).   

Thank you I will try some of those drivers and hopefully fix the crashing.

[Shlimann]

...What if Github gets hacked?  What if a Github employee acts maliciously, or an Amazon employee with access to Github’s AWS download backend, or...?

What if the earth is flat What if Masons rule everything?

Don't go mad. This is not a wallet, it is only a mining program. It is usually installed on a separate machine.

And even if, in theory, they get hacked (0.01% chance) because in the whole history, there hasn't been a single hack of a console mining program, what will be stolen from the mining rig? Nothing.

Just reinstall and that's it. People have kept their coins in hardware wallets for a long time.

Don't go mad. The GitHub repository is completely sufficient. No PGP - no need to worry.

99,9% of mining programs are hosted on GitHub (gminer, teamred, trex, nbminer, lolminer even nicehash, etc.)

[UnclWish]

It's strange... But Phoenix usual quick update miner for new drivers... AMD soon release 21.4.1 driver, PM dosn't support even 21.3.1.

[CoolTomik]

WIN10+Afterburner: I can confirm that delay applying OC helped. But few more times even after DAG  I try update drivers to latest v465.86 but after restrt same issue with 3070 carts - invalid shares. So i put 2min delay between miner start and After Burner apply and all works without invalidshares - seems like some issue with miner and new cards? Especially with 3070 ....

With new RTX 3070 i am getting lot of incorrect shares in miner but no incorrect share reported on pool.

PhonixMiner 5.5c - ethermine.org

I only find ot by seeing graph at pool - reported hash rate is same constand, but avg and current start droping down, also shared go down.

I try remove OC (put 0 / stock value), but still see incorrect shared on RTX3070 cards.

Any idea?

[flashpoint1985]

can someone help me too, I have a R9 290X and below is what is working and it is hashing with very low speed of 0.171 MH/s and I just wondered why because when I use different tools like for example kryptex it's around 29 MH/s.
any help would be appreciated.



No CUDA driver found
OpenCL driver version: 21.1.1
Available GPUs for mining:
GPU1: AMD Radeon R9 200 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 44 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 9 pools (1 from command-line)
Eth: primary pool: ssl://eu1.ethermine.org:5555
Starting GPU mining
GPU1: AMD driver 21.2.2
Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
GPU1: 41C 20%
Listening for CDM remote manager at port 3333 in read-only mode
Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (172.65.207.106)
Eth: New job #8c6a1716 from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #406
Eth: New job #d2d8f8df from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #eab5c12b from ssl://eu1.ethermine.org:5555; diff: 4000MH
Light cache generated in 3.7 s (18.1 MB/s)
GPU1: DAG size limited from 4271 MB to 4023 MB
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: Free VRAM: 3.951 GB; used: 0.049 GB
GPU1: DAG size limited from 4271 MB to 4023 MB
GPU1: Allocating DAG for epoch #406 (3.93) GB
GPU1: Generating DAG for epoch #406
Eth: New job #8d7d990a from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  17%
Eth: New job #a65e05cb from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  35%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG  52%
GPU1: DAG  68%
Eth: New job #b51aecb9 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #9e8aba0e from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  85%
GPU1: DAG generated in 9.8 s (412.6 MB/s)
GPU1: Using Ethash OCL kernels (Hawaii; -clkernel 1)
GPU1: no -gt value specified, switching to auto-tune
GPU1: starting auto-tune process
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #41994575 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #dd323eb4 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #8750254b from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.173 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #66d728c8 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.173 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e84a3853 from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: 63C 30%
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #768d23ff from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #15afc3ab from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #72846c50 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #c3056a68 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #d0af9ece from ssl://eu1.ethermine.org:5555; diff: 4000MH

*** 0:00 *** 4/6 14:17 **************************************
Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 0:00
1 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 0.174 MH/s

Eth: New job #cb6d8575 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #dbb42c07 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #eed2ad07 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #4bec6f38 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #c67f0f6a from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #2ceb841e from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: 68C 35%
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #62ed8b3a from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #a8c053e9 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.171 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #98bc8fe9 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.170 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #6fb09f4c from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #8f3d480e from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #0b2556cf from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.170 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #9148e2a2 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #0b3c3b96 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #819b0ca6 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.172 MH/s, shares: 0/0/0, time: 0:01

[Targonis]

The Etherium DAG is at 4.15GB right now, so any video card with 4GB will not do well when it comes to mining Etherium.   The card itself might be able to borrow from main system memory to work, but performance will be severely degraded.

Other types of mining can be done on 4GB, but Etherium will be problematic.

can someone help me too, I have a R9 290X and below is what is working and it is hashing with very low speed of 0.171 MH/s and I just wondered why because when I use different tools like for example kryptex it's around 29 MH/s.
any help would be appreciated.



No CUDA driver found
OpenCL driver version: 21.1.1
Available GPUs for mining:
GPU1: AMD Radeon R9 200 Series (pcie 1), OpenCL 2.0, 4 GB VRAM, 44 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 9 pools (1 from command-line)
Eth: primary pool: ssl://eu1.ethermine.org:5555
Starting GPU mining
GPU1: AMD driver 21.2.2
Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
GPU1: 41C 20%
Listening for CDM remote manager at port 3333 in read-only mode
Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (172.65.207.106)
Eth: New job #8c6a1716 from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #406
Eth: New job #d2d8f8df from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #eab5c12b from ssl://eu1.ethermine.org:5555; diff: 4000MH
Light cache generated in 3.7 s (18.1 MB/s)
GPU1: DAG size limited from 4271 MB to 4023 MB
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: Free VRAM: 3.951 GB; used: 0.049 GB
GPU1: DAG size limited from 4271 MB to 4023 MB
GPU1: Allocating DAG for epoch #406 (3.93) GB
GPU1: Generating DAG for epoch #406
Eth: New job #8d7d990a from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  17%
Eth: New job #a65e05cb from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  35%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG  52%
GPU1: DAG  68%
Eth: New job #b51aecb9 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #9e8aba0e from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: DAG  85%
GPU1: DAG generated in 9.8 s (412.6 MB/s)
GPU1: Using Ethash OCL kernels (Hawaii; -clkernel 1)
GPU1: no -gt value specified, switching to auto-tune
GPU1: starting auto-tune process
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #41994575 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #dd323eb4 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #8750254b from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.173 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #66d728c8 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.173 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e84a3853 from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: 63C 30%
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #768d23ff from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #15afc3ab from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #72846c50 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #c3056a68 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #d0af9ece from ssl://eu1.ethermine.org:5555; diff: 4000MH

*** 0:00 *** 4/6 14:17 **************************************
Eth: Mining ETH on ssl://eu1.ethermine.org:5555 for 0:00
1 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 0.174 MH/s

Eth: New job #cb6d8575 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #dbb42c07 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #eed2ad07 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #4bec6f38 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #c67f0f6a from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #2ceb841e from ssl://eu1.ethermine.org:5555; diff: 4000MH
GPU1: 68C 35%
Eth speed: 0.174 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #62ed8b3a from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #a8c053e9 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.171 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #98bc8fe9 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.170 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #6fb09f4c from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #8f3d480e from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #0b2556cf from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.170 MH/s, shares: 0/0/0, time: 0:01
Eth: New job #9148e2a2 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #0b3c3b96 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth: New job #819b0ca6 from ssl://eu1.ethermine.org:5555; diff: 4000MH
Eth speed: 0.172 MH/s, shares: 0/0/0, time: 0:01

[flashpoint1985]

The Etherium DAG is at 4.15GB right now, so any video card with 4GB will not do well when it comes to mining Etherium.   The card itself might be able to borrow from main system memory to work, but performance will be severely degraded.

Other types of mining can be done on 4GB, but Etherium will be problematic.

thanks for replay mate, so which one do u suggest for me? also im just a beginner and wanted to test with my current car and have plan to buy RTX 3070.
Also can u tell me how can I dedicate system memory to this mining proccess for better result?