commonorx
Newbie
Offline
Activity: 99
Merit: 0
|
|
January 16, 2018, 04:36:13 PM Last edit: January 16, 2018, 04:52:05 PM by commonorx |
|
i wrote that dual claymore isnt as profitable as other cryptonight coins but in 1 month it will be for sure so i want to start adjusting my rig for Claymore dual thats why i asked if there is some1 who is currently running 6vegas + or more on Dual Claymore You are way in the wrong thread. Please leave. Enjoy making less money. Bye! as of now claymore is more profitable than nicehash cryptonight im enjoyin it There is no way in the world that you can make more with a Vega when you are using a miner (claymore) that is first off slower than CAST XMR at mining cryptonight, and then also mining another coin that is on average worth $10 less a day with 6 Vegas, and uses more power from the wall. Your math does not add up. Enjoy making less money with your Vegas!
|
|
|
|
|
|
The trust scores you see are subjective; they will change depending on who you have in your trust list.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
woodaxe
Member
Offline
Activity: 129
Merit: 10
|
|
January 16, 2018, 05:02:14 PM |
|
cannot run more than 2 rx 470 8gig cards without crashing i get error cl_mem_object_allocation_failure calling c1enqueueNDRangeKernel for kernel 0
works fine with 2 cards as soon as i add more i get the above.
windows 10 with august 23 blockchain drivers xmr cast 0.81 using -G 0,1 etc to enable cards
any ideas or help would be welcome
|
|
|
|
commonorx
Newbie
Offline
Activity: 99
Merit: 0
|
|
January 16, 2018, 07:04:31 PM |
|
cannot run more than 2 rx 470 8gig cards without crashing i get error cl_mem_object_allocation_failure calling c1enqueueNDRangeKernel for kernel 0
works fine with 2 cards as soon as i add more i get the above.
windows 10 with august 23 blockchain drivers xmr cast 0.81 using -G 0,1 etc to enable cards
any ideas or help would be welcome
Oh wow. A problem no one has ever seen before in this thread. ANSWER: http://bfy.tw/G4tl
|
|
|
|
chimdikweks
Newbie
Offline
Activity: 22
Merit: 0
|
|
January 16, 2018, 07:57:31 PM |
|
Sounds limited with the crashes.
|
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 06:12:12 AM Last edit: January 17, 2018, 06:22:49 AM by eduncan911 |
|
Hello all. I must be missing something simple as I am not getting the expected 1800-2000 H/s per Vega out of my setup using Cast XMR. AMD Blockchain drivers Aug 23rd, 17.30.1029 as the Installer says. However, the digging into the Software stuff shows "17.30.1091.1011-170922a-318486C" ^- note that this is dated Aug 23rd, where others are saying "17.30.1029". Also Cast XMR says that the Blockchain driver isn't detected!?!? I only get the following: Vega 64: ~1250 H/s @ 1630c/900mV, 1095m/1050mV (stock settings is ~930 H/s) Vega 56: ~1150 H/s @ 1630c/900mV, 1095m/1050mV (stock settings is ~870 H/s) I started off following this guide to the letter: https://steemit.com/mining/@briggsy/briggsy-s-exhaustive-vega-56-64-monero-mining-guide-part-1-flashing-vega-56-with-vega-64-biosI've since moved onto about a dozen different guides and recommendations. Been browsing this post for hours and trying all sorts of combinations. Nada. One thing I have noticed is that Cast XMR does not report the proper temp or fan speed for the given CPU. At least, I see a vast difference between Afterburner and what Cast XMR says (not the different GPU numbers, but actual values). 1x Vega 64 1x Vega 56 (flashed to Vega 64) 2x Vega 56 MSI Air Boost OC (can' flash to Vega 64) 1x Vega 56 Sapphire Nitro paperweight Windows 10 Creative Update fresh install. I have disabled everything with the "Windows 10 Registry tweaks for mining.bat" batch file (saved me the trouble). I'm trying to stick only to OverdriveNTool for tweaking the settings. I've over-volted and under-volted. I've +50% Power Target and -30% Power Target. I've overclocked core and mem (oops, crash). I've tried various combinations of all of the above, and left some alone, and can never see more than 1250 on the Vega64. I've tried one GPU at a time, all GPUs, various combinations, etc. I have not done any registry edits, as it seems the more recent guides don't have those settings. I have tried 5 different pools and 2 different coins - all with the same effect. Any help would greatly be appreciated.
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
Michael20
Member
Offline
Activity: 118
Merit: 10
|
|
January 17, 2018, 06:25:37 AM |
|
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better? If not go this how to http://vega.miningguides.com/Don't thought 900mhz gpu is enough for 1900+h/s
|
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 06:39:24 AM |
|
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better? If not go this how to http://vega.miningguides.com/Don't thought 900mhz gpu is enough for 1900+h/s I saw that disable/reenable in a few guides. But the newer ones don't have that step. I'll try it now though; however, I do reboot often and power-cycle without any differences. Back... Nope, made no difference at all. Even powered off, booted, disable/enabled in device manager. Oh and not 900mhz core - 900 millivolt. It greatly lowers power consumption. Even at the full stock millivolts, it makes no difference in mining. What bugs me is that it continues to say: "[22:35:41] Blockchain Compute Driver NOT detected." The AMD installer explicitly says 17.30.1029. However, once installed it shows 17.30.1091. Yes, I ran DDU as well to clean. Still only 1091 gets installed? EDIT: If it matters, I do have IGPU enabled in bios and am using the onboard video.
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
StellarX88
Newbie
Offline
Activity: 39
Merit: 0
|
|
January 17, 2018, 07:31:43 AM |
|
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better? If not go this how to http://vega.miningguides.com/Don't thought 900mhz gpu is enough for 1900+h/s I saw that disable/reenable in a few guides. But the newer ones don't have that step. I'll try it now though; however, I do reboot often and power-cycle without any differences. Back... Nope, made no difference at all. Even powered off, booted, disable/enabled in device manager. Oh and not 900mhz core - 900 millivolt. It greatly lowers power consumption. Even at the full stock millivolts, it makes no difference in mining. What bugs me is that it continues to say: "[22:35:41] [Suspicious link removed]pute Driver NOT detected." The AMD installer explicitly says 17.30.1029. However, once installed it shows 17.30.1091. Yes, I ran DDU as well to clean. Still only 1091 gets installed? EDIT: If it matters, I do have IGPU enabled in bios and am using the onboard video. http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-[Suspicious link removed]pute-Release-Notes.aspx Ensure crossfire is off just in case. If you installed the correct driver, Cast-XMR won't throw the warning.
|
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 07:43:33 AM |
|
Have you disable and enabled gpu in device manager before you start the miner. After reboot also if miner crash. Yet better? If not go this how to http://vega.miningguides.com/Don't thought 900mhz gpu is enough for 1900+h/s I saw that disable/reenable in a few guides. But the newer ones don't have that step. I'll try it now though; however, I do reboot often and power-cycle without any differences. Back... Nope, made no difference at all. Even powered off, booted, disable/enabled in device manager. Oh and not 900mhz core - 900 millivolt. It greatly lowers power consumption. Even at the full stock millivolts, it makes no difference in mining. What bugs me is that it continues to say: "[22:35:41] [Suspicious link removed]pute Driver NOT detected." The AMD installer explicitly says 17.30.1029. However, once installed it shows 17.30.1091. Yes, I ran DDU as well to clean. Still only 1091 gets installed? EDIT: If it matters, I do have IGPU enabled in bios and am using the onboard video. http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-[Suspicious link removed]pute-Release-Notes.aspx Ensure crossfire is off just in case. If you installed the correct driver, Cast-XMR won't throw the warning. Yep, that's the exact driver I installed. The installer shows 17.30.1029 however the info page shows 17.30.1091. At this point, I've just paved the entire PC and I am installing again.
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 08:10:07 AM |
|
Well, the good news is after a full pave and reinstall of the drivers - I no longer get that warning message of not using the blockchain drivers.
I am also now able to use the same tweaked settings in the guides, and getting around 1300 H/s. So yes, that's a little better.
But still a far cry from 1900 or 2000 H/s as advertised.
Guess I'll sleep on it. Let me know if y'all have another ideas.
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
StellarX88
Newbie
Offline
Activity: 39
Merit: 0
|
|
January 17, 2018, 08:34:12 AM |
|
Well, the good news is after a full pave and reinstall of the drivers - I no longer get that warning message of not using the blockchain drivers.
I am also now able to use the same tweaked settings in the guides, and getting around 1300 H/s. So yes, that's a little better.
But still a far cry from 1900 or 2000 H/s as advertised.
Guess I'll sleep on it. Let me know if y'all have another ideas.
Crossfire disabled? Ensure that you do a vega driver reset after reboot once at least, it should push your vega to the expected range at 1050 to 1100 mem for vega64 BIOS.
|
|
|
|
Michael20
Member
Offline
Activity: 118
Merit: 10
|
|
January 17, 2018, 11:02:44 AM |
|
Maybe Windows has updated your driver, first time i also had this problem If hbm2 is not to hot, i think deactivate/activate should help you. No automated scripts, made this automatically. Also dont open any tools like gpuz etc.
|
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 04:18:10 PM |
|
Crossfire disabled? Ensure that you do a vega driver reset after reboot once at least, it should push your vega to the expected range at 1050 to 1100 mem for vega64 BIOS.
I don't have any options to enable/disable crossfire. That area is blank in my Radeon settings. I didn't before, but now I am Disabling/Enabling each card after a reboot just in case. It has not helped. I also have tried the trick of enabling/disabling HBCC memory segment - and it doesn't have any effect either on hashrates. Only tweaking the memory to 1050 or 1100 increases it to 1200 or 1300 depending on the card. And lowering the GPU voltage to 900mV greatly reduces power consumption without affecting the the hashrate at all. If I leave the GPU vcore at stock voltage, the hashrates are the same. Maybe Windows has updated your driver, first time i also had this problem If hbm2 is not to hot, i think deactivate/activate should help you. No automated scripts, made this automatically. Also dont open any tools like gpuz etc. I installed Windows without network connected, disabled Windows Update and that little known driver update portion as well - before I connected to the internet. Remember, I am using the IGPU from the Intel CPU connected to my display, so I didn't need any drivers to use the machine upon setup. Then I connected the internet and went online to download the blockchain drivers. But yeah, I guess somehow Windows snuck in a driver even with everything disabled. I used to open MSI Afterburner just to keep tabs on the cards as I am most fimilar with that app over the last 10 years with its logging and INI settings. However, I no longer load it - and just try to start mining. Again, it doesn't make a difference. I'm missing something there... I'm sure it's something easy.
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 04:24:21 PM |
|
Let's examine everything I am doing... Let's take a look at the mining settings. cast_xmr-vega -G 1 --fastjobswitch -S pool.supportxmr.com:7777 -p <snip> -u <snip> Testing it on the true Vega64 first to dial it in, before I start tackling the Vega56s. I've tried this pool, and a few other coins. I've tried with and without --fastjobswitch. That port, 7777, is for "highend hardware" starting at 25,000 difficulty. I have tried lower difficulty, of 5,000. I have tried setting the difficulty flat in 50,000 increments from 50,000 to 350,000 to no effect.
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
StellarX88
Newbie
Offline
Activity: 39
Merit: 0
|
|
January 17, 2018, 04:28:29 PM |
|
Let's examine everything I am doing... Let's take a look at the mining settings. cast_xmr-vega -G 1 --fastjobswitch -S pool.supportxmr.com:7777 -p <snip> -u <snip> Testing it on the true Vega64 first to dial it in, before I start tackling the Vega56s. I've tried this pool, and a few other coins. I've tried with and without --fastjobswitch. That port, 7777, is for "highend hardware" starting at 25,000 difficulty. I have tried lower difficulty, of 5,000. I have tried setting the difficulty flat in 50,000 increments from 50,000 to 350,000 to no effect. Pool difficulties is not going to impact your card performance, shoot me a message on skype @ mo.jin.ee, I will try to trouble shoot this with you.
|
|
|
|
eduncan911
Member
Offline
Activity: 101
Merit: 10
Miner / Engineer
|
|
January 17, 2018, 04:46:30 PM |
|
Pool difficulties is not going to impact your card performance, shoot me a message on skype @ <snip>, I will try to trouble shoot this with you.
Will do later in the day. Need to get some work done. So something happened between the multiple reboots and power offs this morning. Seriously, only setting that changed was me enabling/disabling HBCC (all GPUs are Enabled at the moment). Now I get has rates at 1900/2000+ with the correct memory! ...Except, 1 GPU. When I "Disable/Enable" it in Device Manager, it no longer comes back and always errors with a Code 43. I've tried moving it to another slot, swapping out cables, pcie risers, etc. Doesn't matter, same GPU always fails to be "re-enabled." But the other four are happy now. Close...
|
BTC: 131Zt92zoA7XUfkLhm1p2FwSP3tAxE43vf
|
|
|
borderline
|
|
January 18, 2018, 08:53:52 AM |
|
if i want set a list of server? so when a servers will be down the miner change to other server?
|
|
|
|
Michael20
Member
Offline
Activity: 118
Merit: 10
|
|
January 18, 2018, 09:19:34 AM |
|
As in the link i posted, don't open radeon settings. btw only install driver and nothing other from the install package. Deactivate crossfire, and ulps via regedit as in the how to i posted.
|
|
|
|
CyberTrader
Newbie
Offline
Activity: 43
Merit: 0
|
|
January 18, 2018, 05:40:50 PM |
|
I wonder what I am doing wrong. Optimized version of stak-amd is getting around 5670 hashes (3 vega 64s @ around 215 watts per card). CAST_XMR ist at around 5680 hashes [Hash Rate Avg: 5685.2 H/s]. That makes a difference of about 10 hashes on avg.
Any settings you can recommend so I can get more out of my vega 64s?
Did you read through this thread? Also - standard response - I encourage you to read through the following threads/guides: Vega thread https://bitcointalk.org/index.php?topic=2002025.0Cast thread https://bitcointalk.org/index.php?topic=2256917.0vega.miningguides.com Sure...because everybody has the time to read all these posts again! Thanks for nothing anyway.
|
|
|
|
Morgon
Member
Offline
Activity: 75
Merit: 10
|
|
January 18, 2018, 07:06:40 PM |
|
Sure...because everybody has the time to read all these posts again! Thanks for nothing anyway. Yes, you absolutely should be reading the thread to find if other people have had your issue before making a separate, redundant comment. That goes for all forums on all topics. Shnikes even gave you other resources you could use, so I don't know why you would say 'thanks for nothing'.
|
|
|
|
|