Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[WhackOBill]

Does anyone know which is the last good Polaris driver version before they destroyed performance when re-writing for the 5700XT?

[UnclWish]

Strap 1 on hynix should be the most stable, check your frequency on the memory setting. rather than using gpuz i run strap on 1 to find out the memory cause its faster not sure why you'd be having problems crashing unless you're pushing it too hard. If its the memory on the cards giving you an issue, remember Strap 4 is the higher intensity for Strap 1. It might? run better with that for some reason?

Make sure to watch your voltages. and DO NOT run Afterburner or wattman after setting the strap. Set the speed in the command line. Changing the speeds while Claymore is running you will enduce crashing as its not designed to work with on the fly like that. Its designed for you to change the straps and frequencies without rebooting, not without shuttind down the miner. I've seen many MANY people thinking on the fly means while the miner is running not within windows w/out rebooting.

Keep me posted. I am interested in your status on this.

I'm long time use my own straps. They work stable and fast for me. But we talking about Claymore miner straps.
I returned original vbios to check Claymore straps. And didn't used OC or UV, to check them. And my notices:
1. 1st strap is almost stable, but low speed.
2. 2nd less stable, speed is still low.
3. 3-4 straps are fast enough, but BSODs can happen in any time even after several seconds after launch.

Closing miner can hang sustem 50/50% even with strap 1. I think it's cause of miner returns old straps to card when closing.
I even tried to use my strap via string in command - all works fine, but closing miner can hang system too.
I repeat - all test maded with original cards bioses without any OC or voltage changing.
So I just flashed my straps and all goes normal.

It's all with hynix 8Gb MJR memory. It's very capricious.

[NefariousFool]

Does anyone know which is the last good Polaris driver version before they destroyed performance when re-writing for the 5700XT?

Destroyed performance? I'm running 19.8.1 on all my rigs and my performance is uneffected, if anything they're more stable across 15 Polaris model cards, 580's, 570's, 8GB and 4GB....

Not sure where you're getting the hit.

As for the hanging on closing the miner mentioned above... I've seen that when under volting the cards, or trying to push the clock to high, however I do not experience hanging of the miner that often.

I have 4 of my own rigs, and have provided support on well over 25 others... and that ranges on memory through all memory types.

Very interesting you're experiencing it consistently.

[UnclWish]

As for the hanging on closing the miner mentioned above... I've seen that when under volting the cards, or trying to push the clock to high, however I do not experience hanging of the miner that often.

I have 4 of my own rigs, and have provided support on well over 25 others... and that ranges on memory through all memory types.

Very interesting you're experiencing it consistently.

I writes original vbioses and didn't touched clocks and voltages to test. And if I set straps via miner taken from miner or my own via string, after closing miner system can hang. About 50% chance of this. And when system hangs often a visual glitches stays on screen.
Myabe it because one of my cards have monitor connected. Maybe something else. I sure that it causes by returning straps back when miner closes.
Hynix MJR 8Gb memory - is a pain...

[WhackOBill]

Does anyone know which is the last good Polaris driver version before they destroyed performance when re-writing for the 5700XT?

Destroyed performance? I'm running 19.8.1 on all my rigs and my performance is uneffected, if anything they're more stable across 15 Polaris model cards, 580's, 570's, 8GB and 4GB....

Not sure where you're getting the hit.

As for the hanging on closing the miner mentioned above... I've seen that when under volting the cards, or trying to push the clock to high, however I do not experience hanging of the miner that often.

I have 4 of my own rigs, and have provided support on well over 25 others... and that ranges on memory through all memory types.

Very interesting you're experiencing it consistently.

19.4.3 runs fine for me but 19.8.1 runs about 8% lower hash.  I know there was a 19.5.2 in there somewhere, not sure if it gets the same degradation.  There was talk of lower gaming performance on Polaris with the newer Radeon drivers when Navi support was introduced.  It was assumed that it would get worked out.  I see the same on my rig using Claymore 14.7 in Win10 1903.  Are you running under Windows?  Also on mine, the strap and rxboost commands don't work.  They say they work, but the values are unchanged and so is the hash rate.  So I still have to run a modded BIOS with the straps burned in.

[mu_enrico]

I want to tell you about my experience today, well it might be helpful for those who experienced the same issue. My Windows 10 OS has been updated into the newest patch, thus made the AMD hashrate drop significantly. The workaround is straightforward. Press "y"-key at the initialization process to switch all cards to compute mode, reboot, and you are done!

[NefariousFool]

Does anyone know which is the last good Polaris driver version before they destroyed performance when re-writing for the 5700XT?

Destroyed performance? I'm running 19.8.1 on all my rigs and my performance is uneffected, if anything they're more stable across 15 Polaris model cards, 580's, 570's, 8GB and 4GB....

Not sure where you're getting the hit.

As for the hanging on closing the miner mentioned above... I've seen that when under volting the cards, or trying to push the clock to high, however I do not experience hanging of the miner that often.

I have 4 of my own rigs, and have provided support on well over 25 others... and that ranges on memory through all memory types.

Very interesting you're experiencing it consistently.

19.4.3 runs fine for me but 19.8.1 runs about 8% lower hash.  I know there was a 19.5.2 in there somewhere, not sure if it gets the same degradation.  There was talk of lower gaming performance on Polaris with the newer Radeon drivers when Navi support was introduced.  It was assumed that it would get worked out.  I see the same on my rig using Claymore 14.7 in Win10 1903.  Are you running under Windows?  Also on mine, the strap and rxboost commands don't work.  They say they work, but the values are unchanged and so is the hash rate.  So I still have to run a modded BIOS with the straps burned in.

I heard about issues with the Linux drives from AMD, heard they were complete garbage after 19.4.3.

yes i run windows 10 x64 with all the latest updates and patches. I try to purposefully break things in windows with the patches and windows security crap. To ensure i have answers for our discord members when it comes to Claymore. However i am not a Linux guy. lol sorry.

[Wcryan]

Hi I’ve been browsing these threads for a little before I posted but it is a lot to sift through. Having trouble with 14.7. Using AMD 19.4.3 all in compute mode.  Whenever I put -strap 1 in start bat I get “driver is in use, try -driver uninstall”.  I added driver uninstall but need to do it in administrator.  I start in administrator but ethminer start.bat opens for like a split second and then closes.  I’ve tried different drivers, added folder pathway to start.bat.  I’m at a loss right now.  If anyone knows PM me or post.  I will pay PayPal also to the person who helps me solve this

[RAKOT]

Hi I’ve been browsing these threads for a little before I posted but it is a lot to sift through. Having trouble with 14.7. Using AMD 19.4.3 all in compute mode.  Whenever I put -strap 1 in start bat I get “driver is in use, try -driver uninstall”.  I added driver uninstall but need to do it in administrator.  I start in administrator but ethminer start.bat opens for like a split second and then closes.  I’ve tried different drivers, added folder pathway to start.bat.  I’m at a loss right now.  If anyone knows PM me or post.  I will pay PayPal also to the person who helps me solve this

Hi!

You should run command prompt( Administrator) - its if you are in W10. Then navigate to folder there miner is. run EthDcrMiner64.exe -driver uninstall. Then reboot
Next - also run command promt  (Administrator) - navigate to miner folder and run start bat wih straps option. Thats it.

Next time you can run start.bat not with admin rights, cause drivers allready been installed.

[Wcryan]

Hi I’ve been browsing these threads for a little before I posted but it is a lot to sift through. Having trouble with 14.7. Using AMD 19.4.3 all in compute mode.  Whenever I put -strap 1 in start bat I get “driver is in use, try -driver uninstall”.  I added driver uninstall but need to do it in administrator.  I start in administrator but ethminer start.bat opens for like a split second and then closes.  I’ve tried different drivers, added folder pathway to start.bat.  I’m at a loss right now.  If anyone knows PM me or post.  I will pay PayPal also to the person who helps me solve this

Hi!

You should run command prompt( Administrator) - its if you are in W10. Then navigate to folder there miner is. run EthDcrMiner64.exe -driver uninstall. Then reboot
Next - also run command promt  (Administrator) - navigate to miner folder and run start bat wih straps option. Thats it.

Next time you can run start.bat not with admin rights, cause drivers allready been installed.

Does it matter if my cards have already been bios modded?   Looking to override those with claymore

[big_daddy]

I want to tell you about my experience today, well it might be helpful for those who experienced the same issue. My Windows 10 OS has been updated into the newest patch, thus made the AMD hashrate drop significantly. The workaround is straightforward. Press "y"-key at the initialization process to switch all cards to compute mode, reboot, and you are done!

can you please tell us what is the Windows version (build) you are writing about?

(run-> winver -> )

[RAKOT]

Hi I’ve been browsing these threads for a little before I posted but it is a lot to sift through. Having trouble with 14.7. Using AMD 19.4.3 all in compute mode.  Whenever I put -strap 1 in start bat I get “driver is in use, try -driver uninstall”.  I added driver uninstall but need to do it in administrator.  I start in administrator but ethminer start.bat opens for like a split second and then closes.  I’ve tried different drivers, added folder pathway to start.bat.  I’m at a loss right now.  If anyone knows PM me or post.  I will pay PayPal also to the person who helps me solve this

Hi!

You should run command prompt( Administrator) - its if you are in W10. Then navigate to folder there miner is. run EthDcrMiner64.exe -driver uninstall. Then reboot
Next - also run command promt  (Administrator) - navigate to miner folder and run start bat wih straps option. Thats it.

Next time you can run start.bat not with admin rights, cause drivers allready been installed.

Does it matter if my cards have already been bios modded?   Looking to override those with claymore

If your bioses are modified , you wont get big bedefit of using strap option , cause it does same thing as your moded bios did. rxboost can speedup a liitle.

[mu_enrico]

can you please tell us what is the Windows version (build) you are writing about?

Version 1903 (OS Build 18362.295)

[cirlama]

I want to tell you about my experience today, well it might be helpful for those who experienced the same issue. My Windows 10 OS has been updated into the newest patch, thus made the AMD hashrate drop significantly. The workaround is straightforward. Press "y"-key at the initialization process to switch all cards to compute mode, reboot, and you are done!

Hi, "y" key at the initialization process of what?

[mu_enrico]

Hi, "y" key at the initialization process of what?

For Claymore 14.7:

-y   enables Compute Mode and disables CrossFire for AMD cards. "-y 1" works as pressing "y" key when miner starts. This option works in Windows only.

If you are running older version before "y option" implemented , you can change it manually one by one in "Radeon Settings" or use "amd-compute-mode-switcher-script" available somewhere on the internet.

Just use newest Claymore 

[cirlama]

Hi, "y" key at the initialization process of what?

For Claymore 14.7:

-y   enables Compute Mode and disables CrossFire for AMD cards. "-y 1" works as pressing "y" key when miner starts. This option works in Windows only.

If you are running older version before "y option" implemented , you can change it manually one by one in "Radeon Settings" or use "amd-compute-mode-switcher-script" available somewhere on the internet.

Just use newest Claymore 

thanks, will try with the latest Claymore, with the W10 1903 build update, my couple of RX480-580 switched to non compute mode and the Radeon settings doesn't opened anymore (it just appears in tasks but the window doesn't open)... I need to sort that out (I tried briefly to re-install the AMD driver, but then only one card was there in graphic cards instead of 2, reverted to latest restore point)

[big_daddy]

Hi, "y" key at the initialization process of what?

For Claymore 14.7:

-y   enables Compute Mode and disables CrossFire for AMD cards. "-y 1" works as pressing "y" key when miner starts. This option works in Windows only.

If you are running older version before "y option" implemented , you can change it manually one by one in "Radeon Settings" or use "amd-compute-mode-switcher-script" available somewhere on the internet.

Just use newest Claymore 

thanks, will try with the latest Claymore, with the W10 1903 build update, my couple of RX480-580 switched to non compute mode and the Radeon settings doesn't opened anymore (it just appears in tasks but the window doesn't open)... I need to sort that out (I tried briefly to re-install the AMD driver, but then only one card was there in graphic cards instead of 2, reverted to latest restore point)

When you install the AMD driver, install it without the “Settings”
Than use the compute-switcher parcher to turn them in compute mode

[karim_hassan777]

Does any one know AMD team will resolve the Dag file problem for RX 5700 XT or not ?

[Binary100100]

Does any one know AMD team will resolve the Dag file problem for RX 5700 XT or not ?

+1
I've been logging on daily to see if there has been some update to this. Radeon VII cards are becoming scarce and I just started a 4800w 12 GPU mining rig that needs some cards! But what to use?

[NefariousFool]

Does any one know AMD team will resolve the Dag file problem for RX 5700 XT or not ?

+1
I've been logging on daily to see if there has been some update to this. Radeon VII cards are becoming scarce and I just started a 4800w 12 GPU mining rig that needs some cards! But what to use?

Not yet. Sadly.

As for what to use.... Keep getting those Radeon Vii's as long as you can!!!

after that its a huge cliff to the Rx 500 series and AMD has been unable to resolve the Dag issue with the 5700.

The pressure is mounting though, now that the AIB cards are now in the wild, they need to fix that driver ASAP.