I have try 5.5b on RaveOS (miner loaded from repo) and wattage consumption is still higher than TRM and stii the same as 5.4c...
How to check driver version on a RaveOS? Maybe that ***king me?
Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 140. (Read 784965 times)
January 15, 2021, 12:12:06 AM
January 14, 2021, 06:21:32 PM
Is anybody trying to mine with 6x 3080s and having issues with GPU#1 on 5.4c? After a duration of time GPU#1 just starts going crazy with the hashrate jumping around. When I look in GPU-z it shows vrel and vop being hit by the GPU. Upon closing and opening the software it doesn't seem to fix the issue. Now if I physically remove GPU#1 from the system (shut down and re-boot), and then I fire it up the next GPU that was #2 and has now become #1 now has the same issues. These things were perfectly stable in other rigs with only 1 or 2 3080s in them... Any ideas what the problem may be? These are EVGA 3080s (FTW3 and XC3 Ultras). I have tried different Nvidia drivers 460.89 and 461, but no luck. I just downloaded 5.5b and am trying that now. It has been stable for the first half an hour but we'll see if it just fails like the other one after a few hours.
what are the over clock settings?
try older driver 457 I think
Overclock settings aren't a factor here since the cards are perfectly stable at their overclocks if they aren't in the #1 position. No matter how low I turn the overclocks it is still unstable. So far with 5.5b I have been stable for 10 hours now. I am also considering that maybe the 5.4c was just corrupted when I downloaded it and I just needed a fresh install possibly. Currently stable with 460.89 drivers and 5.5b
January 14, 2021, 04:53:49 PM
can anyone share good settings for 5700xt?
Thanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
for example use AMD.Memory.Tweak.XL.exeThanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
core ~ 1300MHz at 912MHz memory frequency and ~ 1320MHz at 930MHz memory frequency on optimized timings, etc.
mem 912MHz or higher (at 912MHz memory frequency, SOK operates at 950MHz. With memory frequency higher than 912MHz, SOK operates at 1085MHz, so more voltage is required
SOK ~ 812mV at a memory frequency of up to 912MHz and about 840 at a memory frequency of 930MHz. change step 6
cvddci ~ 724mv change step 6
mvdd ~ 1302mV at a memory frequency of up to 912MHz and ~ 1326 and higher at a memory frequency of 930MHz. change step 6
but in general, each card needs its own settings, you need to adjust, then you can select the minimum necessary settings
I have a link to the site on the left under the name in russian with a description of my example
Where do I get AMD.Memory.Tweak.XL.exe?
Well you could search but let me get you the link.....
https://bitcointalksearch.org/topic/amd-mem-tweak-xl-readmodify-timingsppstraps-on-the-fly-5123724
Thanks
I tried 1.3, 1.4 & 1.5 Beta. All just give me a white window. Any ideas?
January 14, 2021, 04:40:54 PM
can anyone share good settings for 5700xt?
Thanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
for example use AMD.Memory.Tweak.XL.exeThanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
core ~ 1300MHz at 912MHz memory frequency and ~ 1320MHz at 930MHz memory frequency on optimized timings, etc.
mem 912MHz or higher (at 912MHz memory frequency, SOK operates at 950MHz. With memory frequency higher than 912MHz, SOK operates at 1085MHz, so more voltage is required
SOK ~ 812mV at a memory frequency of up to 912MHz and about 840 at a memory frequency of 930MHz. change step 6
cvddci ~ 724mv change step 6
mvdd ~ 1302mV at a memory frequency of up to 912MHz and ~ 1326 and higher at a memory frequency of 930MHz. change step 6
but in general, each card needs its own settings, you need to adjust, then you can select the minimum necessary settings
I have a link to the site on the left under the name in russian with a description of my example
Where do I get AMD.Memory.Tweak.XL.exe?
Well you could search but let me get you the link.....
https://bitcointalksearch.org/topic/amd-mem-tweak-xl-readmodify-timingsppstraps-on-the-fly-5123724
January 14, 2021, 04:19:54 PM
can anyone share good settings for 5700xt?
Thanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
for example use AMD.Memory.Tweak.XL.exeThanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
core ~ 1300MHz at 912MHz memory frequency and ~ 1320MHz at 930MHz memory frequency on optimized timings, etc.
mem 912MHz or higher (at 912MHz memory frequency, SOK operates at 950MHz. With memory frequency higher than 912MHz, SOK operates at 1085MHz, so more voltage is required
SOK ~ 812mV at a memory frequency of up to 912MHz and about 840 at a memory frequency of 930MHz. change step 6
cvddci ~ 724mv change step 6
mvdd ~ 1302mV at a memory frequency of up to 912MHz and ~ 1326 and higher at a memory frequency of 930MHz. change step 6
but in general, each card needs its own settings, you need to adjust, then you can select the minimum necessary settings
I have a link to the site on the left under the name in russian with a description of my example
Where do I get AMD.Memory.Tweak.XL.exe?
January 14, 2021, 02:59:55 PM
can anyone share good settings for 5700xt?
Thanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
for example use AMD.Memory.Tweak.XL.exeThanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
core ~ 1300MHz at 912MHz memory frequency and ~ 1320MHz at 930MHz memory frequency on optimized timings, etc.
mem 912MHz or higher (at 912MHz memory frequency, SOK operates at 950MHz. With memory frequency higher than 912MHz, SOK operates at 1085MHz, so more voltage is required
SOK ~ 812mV at a memory frequency of up to 912MHz and about 840 at a memory frequency of 930MHz. change step 6
cvddci ~ 724mv change step 6
mvdd ~ 1302mV at a memory frequency of up to 912MHz and ~ 1326 and higher at a memory frequency of 930MHz. change step 6
but in general, each card needs its own settings, you need to adjust, then you can select the minimum necessary settings
I have a link to the site on the left under the name in russian with a description of my example
January 14, 2021, 02:01:31 PM
my gigabyte 5700 xt goes down to 750 mv and stable 1860 mem clock with bios mod 57 mhs, 1900 causes it to crash every few days but it goes to 59 mhs, also core 1400 or 1300
January 14, 2021, 01:23:51 PM
can anyone share good settings for 5700xt?
Thanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
Thanks. First time touching these ... I just can't get how to set all different voltages /core/mem cvdd cvddci mvdd ...
January 14, 2021, 01:04:51 PM
Is anybody trying to mine with 6x 3080s and having issues with GPU#1 on 5.4c? After a duration of time GPU#1 just starts going crazy with the hashrate jumping around. When I look in GPU-z it shows vrel and vop being hit by the GPU. Upon closing and opening the software it doesn't seem to fix the issue. Now if I physically remove GPU#1 from the system (shut down and re-boot), and then I fire it up the next GPU that was #2 and has now become #1 now has the same issues. These things were perfectly stable in other rigs with only 1 or 2 3080s in them... Any ideas what the problem may be? These are EVGA 3080s (FTW3 and XC3 Ultras). I have tried different Nvidia drivers 460.89 and 461, but no luck. I just downloaded 5.5b and am trying that now. It has been stable for the first half an hour but we'll see if it just fails like the other one after a few hours.
what are the over clock settings?
try older driver 457 I think
January 14, 2021, 12:59:47 PM
Is anyone else having trouble controlling fan speed in batch file? I have -fcm 2 and have -fanmin 50, 60, 70, ect... but some of the cards just randomly run the fan based off temp. I have various rx5700. The ones that seem to not want to play along with batch file command are MSI Gaming, Sapphire Pulse and Powercolor red dragon. This all started when I started running 5.5b and installed newer drivers like 20.5.1 and 20.11.2. When running 5.3 and 5.4 with 19.x.x drivers the fan controls were excellent.
January 14, 2021, 10:59:24 AM
Dev i have a question about dual mining.. i was trying to mine verge coin but i couldn't so i added nicehash as was written in the readme file, but it hashes 0
January 14, 2021, 09:33:01 AM
Windows auto upgrade amd driver to 20.10.35.02,
GPU0: clSetKernelArg (-48)
GPU0: clSetKernelArg (-48)
January 14, 2021, 08:16:38 AM
Is anybody trying to mine with 6x 3080s and having issues with GPU#1 on 5.4c? After a duration of time GPU#1 just starts going crazy with the hashrate jumping around. When I look in GPU-z it shows vrel and vop being hit by the GPU. Upon closing and opening the software it doesn't seem to fix the issue. Now if I physically remove GPU#1 from the system (shut down and re-boot), and then I fire it up the next GPU that was #2 and has now become #1 now has the same issues. These things were perfectly stable in other rigs with only 1 or 2 3080s in them... Any ideas what the problem may be? These are EVGA 3080s (FTW3 and XC3 Ultras). I have tried different Nvidia drivers 460.89 and 461, but no luck. I just downloaded 5.5b and am trying that now. It has been stable for the first half an hour but we'll see if it just fails like the other one after a few hours.
January 14, 2021, 07:01:35 AM
i was mining a sia coin in the past, with dual mining, and now what coin do you advise me?
January 14, 2021, 05:42:17 AM
What issue are you referring to? If you are talking about the slow down over the years, there is nothing miner software can do to fix that. It's an problem with hardware/firmware design and NVIDIA won't fix it.
No, it’s only win7 and win8 issue, and ethash performance under win10 is OK, and some else miners devs fix it. January 13, 2021, 07:26:08 PM
Still no DAG fix for 3000 series 
Nope, doesn’t seem to be a lot of urgency behind PhoenixMiner for some reason. Thinking about switching...
January 13, 2021, 06:15:22 PM
Still no DAG fix for 3000 series
January 13, 2021, 02:12:55 PM
The new beta version is ready. You can download PhoenixMiner 5.5b from here:
https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ (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):
The new features in this release are:
If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C.
Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ (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.5b_Windows.zip
===================================
SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957
File: PhoenixMiner_5.5b_Linux.tar.gz
====================================
SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are:
- Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
- The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
- Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
- Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating
If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C.
Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
5.5b seems to run pretty well on 6800 XT. So far seems to have fixed a stale share issue I was getting before that.
Any idea why it reports 6800 XT as 36 CUs? As far as I understand 6800 XT has 72 CUs?
Is there a known reason for this?
See: https://i.imgur.com/AQDUr5E.png
Thanks
January 13, 2021, 02:01:31 PM
The new beta version is ready. You can download PhoenixMiner 5.5b from here:
https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ (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):
The new features in this release are:
If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C.
Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ (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.5b_Windows.zip
===================================
SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957
File: PhoenixMiner_5.5b_Linux.tar.gz
====================================
SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are:
- Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
- The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
- Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
- Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating
If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C.
Please let us know if you have any problems or questions related to PhoenixMiner 5.5b.
GOOOOD WORK
WITH 5.4c
x7 RX-580 8Gb
Speed = 227.5 MH/s
GPUs Power = 628/630 Watts
WITH 5.5b
x7 RX-580 8Gb
Speed = 227.5 MH/s
GPUs Power = 600/602 Watts
PhoenixMiner team.
veeeery thanks
January 13, 2021, 01:59:13 PM
Something is not right with 5.5b, after running like 20-30minutes miner turns off. same setting used in 5.4c. it was working many days without any issue.
Jump to: