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

Hello, enter the Device Manager: Network Adapters and if you have this (WAN Miniport) then disable them all and restart your computer. Then verify that they are really disabled.
You must also verify with HWiNFO64 that you do not have memory errors in the GPUS, if you have them, just lower the memory clock until you eliminate them. I had that glitch and managed to fix it with these 2 options.
Excuse my bad english  

that is not a solution..
that is exactly what we are all saying.

you never know the epoch change time  and don't want to be by the miner to check it for that.
Perhaps a new parameter to temporarily change the mem clock before the epoch change  in phonexminer would fix this.

The greater the dag, the more ips it will use it, actually a gtx 1070 can do 35mhs on etc right now if you know how to.

Hi All,

I'm using latest build of HiveOS (kernel version 5.0.21-201105-hiveos; os version 0.6-184@201221; drivers OpenCL 20.30) and PhoenixMiner 5.4c. My rig has a mix of 5xRX5700 XT 8GB cards, 1xRX590 8 GB and 1xRX580 8 GB.
I'm receiving "Disabling DAG pre-allocation (not enough VRAM)" for RX580 and RX590 cards.

2020.12.21:20:54:27.883: GPU4 GPU4: Free VRAM: 7.922 GB; used: 0.062 GB                                                                                                                                                                                                                   
2020.12.21:20:54:27.884: GPU4 GPU4: Allocating DAG (4.15) GB; good for epoch up to #403                                                                                                                                                                                                   
2020.12.21:20:54:27.885: GPU4 GPU4: Generating DAG for epoch #383                                                                                                                                                                                                                         
2020.12.21:20:54:28.255: GPU5 GPU5: Free VRAM: 7.922 GB; used: 0.062 GB                                                                                                                                                                                                                   
2020.12.21:20:54:28.255: GPU5 GPU5: Allocating DAG (4.15) GB; good for epoch up to #403                                                                                                                                                                                                   
2020.12.21:20:54:28.256: GPU5 GPU5: Generating DAG for epoch #383                                                                                                                                                                                                                         
2020.12.21:20:54:28.269: GPU1 GPU1: DAG  13%                                                                                                                                                                                                                                             
2020.12.21:20:54:28.679: GPU6 GPU6: Free VRAM: 7.968 GB; used: 0.019 GB                                                                                                                                                                                                                   
2020.12.21:20:54:28.680: GPU6 GPU6: Disabling DAG pre-allocation (not enough VRAM)                                                                                                                                                                                                       
2020.12.21:20:54:28.680: GPU6 GPU6: Allocating DAG for epoch #383 (3.99) GB                                                                                                                                                                                                               
2020.12.21:20:54:28.689: GPU6 GPU6: Generating DAG for epoch #383                                                                                                                                                                                                                         
2020.12.21:20:54:28.770: GPU2 GPU2: DAG  13%                                                                                                                                                                                                                                             
2020.12.21:20:54:28.807: GPU7 GPU7: Free VRAM: 7.968 GB; used: 0.019 GB                                                                                                                                                                                                                   
2020.12.21:20:54:28.807: GPU7 GPU7: Disabling DAG pre-allocation (not enough VRAM)                                                                                                                                                                                                        
2020.12.21:20:54:28.807: GPU7 GPU7: Allocating DAG for epoch #383 (3.99) GB                                                                                                                                                                                                               
2020.12.21:20:54:28.814: GPU7 GPU7: Generating DAG for epoch #383                                                                                                                                                                                                                         
2020.12.21:20:54:29.258: GPU3 GPU3: DAG  15%

I'm concerned that when the ETH DAG hits 4 GB I will be unable to mine with these two cards. Is this error message expected and I should not worry or there is really something wrong and I should somehow fix it?

Thanks,
Dinko

Does anyone know how to relate the Pheonixminer GPU number to the physical card under Ubuntu?

Thanks

No all card temp is around 61c. I search every and there are many miners experience the same issue but some people are not affected?
There might be something about straps changes?

to make it a little easier, What frequencies are you using?

It normally reaches 60 mhs:
powerlimit: 56
core: -502
memory: +1000

I achieved these results with a Galax 3060 TI EX (36ISL6MD1WGG)

What happen to gtx 1070 now with ETC mining  I get around 32.280mh/s now 90watt,with the Eth mining it is around 24 mh/s  and use 122Watt even increase mmclock and core ican only get around 24. What happen.i use win64 lite with latest nvidia driver recent and latest version of Poenixminer,what is the problem please pm developer help with a good update and straps option dont work with nvidia P106-100 mining cards trex miner work with this cards

i have EVGA P106-100 now run with 441.66 stock bios
PM 5.3b, 5.4b and 5.4c get the same 21,2 Mhs on Ethas
i dont adjust anything, lets you try
maybe you can get luck with your experience

There's been a wave of spambots posting the same malware. Just avoid them for now.

Here's what I did,
reset every oc settings to stock
start the miner
wait it to load the dag file and everything
let it run for 2-3 minutes
crank the memory oc +1500 in one go

never got invalid shares until it loads the new dag then the issue comes back
hope this help

Interesting.. thanks for reporting this.. did you try any other miner see if the same issue persists?
so it is not a driver issue, it is a general rtx 3000 series issue

If I start on +1200 mem clock I can survive  but I still get bunch of invalid shares ,  if i start under +1000mem clock and go up I get no invalid shares even up to 1500+for now I start them at +900 and go up to +1200 since you never know when the Epoch change happens and the whole thing goes down if you have it set above +1250 or so memory clock




I have an MSI and a Zotac  3060 ti ,   Zotac runs hotter and faster , but more prone to invalid shares, same story as above applies to both

I get 59-60 MH on the 900+ mem
and can get close to 64 MH if I go up to +1500 and give it some  power like 66% to 68%

I had this issue.  I think it was 20.1.3 that worked   I used afterburner after that.  None other drivers worked

I have a 9 x 5500xt rig. 4 of the cards generate the DAG just fine. The other 5 generate like 1% per minute, meaning it takes a REALLY long time for it to complete. This doesn't happen when I use other miners. Any ideas what might be going on? I prefer Phoenix, but obviously can't use it if that is happening.

Just to give more information, this is running in SMOS. I have tried multiple versions of phoenix back to 5.2e, and I get the same issue.

got a strange prob on my personal computer and one of my rigs. after a day or two teamviewer goes offline (but miner still works for half a day) and in the end this error message appear An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. Windows 10 latest build drivers: 18.12 and 18.6 . systems have sufficient vram . any suggestions?

Afterburner 4.6.2 works just fine with saphhire 5700xt pulse and driver 20.8.1

Hello,
I have 8 5700XT
My Red Devil & Sapphire 5700XT does not respond to fan commands in phoenixminer nor afterburner with the latest AMD drivers. is there a solution or workaround for this? Can’t use Radeon software as it resets fancurve if the computer crashes and I’ve tried going back to January drivers (20.5.1) where Phoenix fan commands work but NiceHash crashes the computer upon startup and there are other problems with using Phoenix directly.

I’ve read about the core temp limiter to downclock to avoid overheating but the problem is memory temps that reach beyond 96C due to the low fan curves without option to adjust them.

Is there a solution or fix in coming versions for this?

What is your hashrate for 3060 TI?
 I have a Zotac with difficulty gives 57 Mh.
 Card marriage or normal?

happens to me as well (RTX3070), I thought it was a bug on the driver or the bios, I was updating/flashing for 2 hours before figured what you just said lol

thats to low, using PM 5.4c

i got 26,8 minimum, with : PL 80 CC +100 MC +400 (after burner)
using "Ehereum-nanopool.bat" - only change the wallet and worker name

maybe ur cards over heat ...