Ninjastic
Search content
Sort by
Showing 2 of 2 results by Lindstroem
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 5.4c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
Lindstroem
on 25/12/2020, 16:37:08 UTC
Quote from: oskoa on Today at 04:30:30 PM
I think this doesnt have solution for now, the hashrate down a lot with 4 GB cards (and i already put all commands to try to get better). The 8 GB Cards are as the first day.

Ive 1 (the main) with 8 GB, and it is minning right now in 24 Mhz. The others 4gb cards from the same rig, are in half or less (12 mhz) when in the past this cards can mining in 20/22.

The 8 gb in Main is Asus Strix RX 570 8GB. Ive also other Asrock in other rig as main and its a little better (26 Mhz).

But in the olds 4 gb cards, the drop is huge (Sapp, MSI, Giga, 4 GB), 12,12,11 Mhz.


Im with Crimson Beta driver (17.X i think) by manual install, and works equal or little better that 20.X from Adrenaline.

Windows 10, Core2Quad, 8 GB DDR2, 30 GB in Virtual memory

All 4gb cards will soon cease to function in Ethereum mining tasks due to the DAG files now starting to exceed 4gb.Zombie mode still enables the cards to mine sometime in January 2021 but at continually decreasing hash rates.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 5.4c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
by
Lindstroem
on 21/12/2020, 11:51:55 UTC
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?