DrX
Member
Offline
Activity: 233
Merit: 20
|
|
December 25, 2018, 10:36:09 PM |
|
hey guys, got a weird one today.
We built a new mining rig with rx 470 4GB (MSI Gaming X, Samsung memory and yeah, we're lucky enough to have free electricity), we copied the 1500 memory straps from 1500 to 2000 (like we always do), but for some odd reason we can't OC our cards memory above 1850Mhz without having the good old GPU#X got incorrect share etc... which means our cards are stuck around 27.2Mh/s.
You guys got any idea what the problem might be ? We have downvolted anything yet so our cards are definitely not power starved, I'm just a bit confused.
First of all, you have free elec Even if those cards are doing 15Mh/s youll have good profit... But ok What is your config? Win ver., driver ver., etc Yeah, I'm definitely not complaining about our situation (the rig belongs to me and my brother), I just thought I could squeeze a lil bit more out of our cards since I saw a lot of people having around 30mh/s with the same cards. So we're using Windows 10 (with the latest update), the latest Claymore version as well and the latest stable AMD drivers (18.12.2). In terms of hardware we are using : ASrock H81 Pro BTC 2.0 4GB of DDR3 a 1000W Aerocool Gold+ PSU a Celeron G1840 CPU and of course 6* MSI Gaming X RX 470@4GB I managed to slightly increase the memory clock to 1860Mhz but I can't go beyond that. those cards are bios modded or you are using an afterburner to set the clocks? Hey and sorry for the late reply (Xmas and stuff!). We tried to things: 1. No bios mod, we simply increased the clocks and we ended up with ~25Mh/s with the clocks around 2050Mhz but with a shit ton of GPU#x got incorrect shares 2. We then bios mod the card ourselves (using Polaris Bios Editor), copying the 1500 strap values from 1500 to 2000. (we also tried with the 1750 values from 1750 to 2000 as well), and this is the situation where we are at at the moment, with 27.2Mh/s and a few GPU errors here and there on our GPU2. This is our rig stats btw: https://ethermine.org/miners/f6c10F2CB2A2161efb43e4e0eabee60629329d5a/dashboardAny advices would be much appreciated ! try the driver versions 18.xxxx and with the compute patcher turn all the gpus in one shot to the compute mode and share if you get better results We're already on the latest stable driver version, the 18.12.2 with everything on compute mode. We just tried the latest Clayrmore version (12.0), didn't make much difference, still stuck at 27.2mh/s on average with our memory clocks at 1850mhz Did you read the guide by Mattthev? https://bitcointalk.org/index.php?topic=1954245.0
|
|
|
|
Dark Oopa
Newbie
Offline
Activity: 83
Merit: 0
|
|
December 26, 2018, 10:45:30 AM |
|
with memory at only 1850Mhz, 27Mhs is not bad
|
|
|
|
deforester
Newbie
Offline
Activity: 20
Merit: 0
|
|
December 26, 2018, 02:18:50 PM |
|
Winter is upon us and I need to either turn on an extra heater or dual mine Got free electricity, so I'm still mining ETH with my 6 RX580. Is there anything worth to dual mine to just hodl?
|
|
|
|
user0071
Newbie
Offline
Activity: 11
Merit: 0
|
|
December 26, 2018, 07:30:21 PM |
|
My miner is randomly turning completely off. Kernal Power error 41
So here's the situation. 5 GPU (2 570, 3 580) with a 1000w corsair HX1000i
Machine has been running great for the past 5 months. Swapped out a 580 that a friend wanted with a 470. Hard drive crashed, so i got my backup files and reinstalled windows ect. Saved the config file for Overdriven so i have the same clocks and everything. Even when running WITHOUT the new gpu (so 4 cards pulling 600 from the wall), it will crash and give me the kernal power error. The only difference between software in the old install and the new install is I used radeon adrenaline 18.12 instead of 18.9. Could the new driver be the problem? When the computer does restart, i get the radeon warning that default settings have been applied to the GPUS. Even with the overclock, I am getting 0 memory errors in hwinfo. I'm HOPING the answer is to DDU and go back to 18.9, but are there any other reasons ya'll can think of? Is there a way to see which gpu is causing the crash?
|
|
|
|
Fluchtzwerg
Newbie
Offline
Activity: 3
Merit: 0
|
|
December 27, 2018, 01:16:28 PM |
|
Hi guys!
My Brave Browser is complaining about the 12.0 windows version being harmful. I've never had that warning on the older versions, is this the new Brave version being overprotective or has the file been compromised somehow?
|
|
|
|
big_daddy
|
|
December 27, 2018, 02:02:20 PM |
|
Hi guys!
My Brave Browser is complaining about the 12.0 windows version being harmful. I've never had that warning on the older versions, is this the new Brave version being overprotective or has the file been compromised somehow?
I have no problems downloading the "mega" file via Mozilla, usually Chrome gives headache when downloading miners so try Mozilla, or even Explorer should be good
|
If you don't believe it or don't get it, I don't have the time to try to convince you, sorry.
|
|
|
solamentezeus
Newbie
Offline
Activity: 14
Merit: 0
|
|
December 27, 2018, 06:31:05 PM |
|
try the driver versions 18.xxxx and with the compute patcher turn all the gpus in one shot to the compute mode and share if you get better results
What did you meant by "the compute patcher turn all the gpus in one shot" is there a patcher that can puts all GPU to compute mode in one shot? if so could you provide a link?
|
|
|
|
|
ctp9
Jr. Member
Offline
Activity: 52
Merit: 5
|
|
December 27, 2018, 11:01:42 PM |
|
Re: Claymore v12.0 THANK YOU for this latest version, Claymore! We missed you.
|
|
|
|
ZombieWorm
Jr. Member
Offline
Activity: 71
Merit: 1
|
|
December 27, 2018, 11:37:07 PM |
|
Any coin worth hitting on the dual mode then? Looks like the usual few are too difficult to get any recognised shares.
|
|
|
|
Metroid
Sr. Member
Offline
Activity: 2142
Merit: 353
Xtreme Monster
|
|
December 28, 2018, 05:03:07 AM |
|
@Claymore, I'm having problems with the ethman monitor when I close it, it says sometimes, "cannot save file, options_temp.ini make sure you have rights to create/write this file", I'm using windows 1709 and I have full access regarding write to a folder as administrator and this folder is on desktop, is not even in the c:/ drive root.
|
BTC Address: 1DH4ok85VdFAe47fSVXNVctxkFhUv4ujbR
|
|
|
Jonet
Jr. Member
Offline
Activity: 82
Merit: 3
|
|
December 28, 2018, 11:18:10 AM |
|
What did you meant by "the compute patcher turn all the gpus in one shot" is there a patcher that can puts all GPU to compute mode in one shot? if so could you provide a link?
There is one but you don't need it. Start claymore as administrator and press y. All cards will be in compute mode after reboot. AMD-Compute-Switcher can be found here: https://bitcointalk.org/index.php?topic=2815803.0
|
|
|
|
big_daddy
|
|
December 28, 2018, 11:32:50 AM |
|
What did you meant by "the compute patcher turn all the gpus in one shot" is there a patcher that can puts all GPU to compute mode in one shot? if so could you provide a link?
There is one but you don't need it. Start claymore as administrator and press y. All cards will be in compute mode after reboot. AMD-Compute-Switcher can be found here: https://bitcointalk.org/index.php?topic=2815803.0and if you have installed the AMD settings with the driver, do the DDU again and install the driver only, caust in the AMD settings you'll get the wattman that can cause headaches on compute mode with higher clocks regards
|
If you don't believe it or don't get it, I don't have the time to try to convince you, sorry.
|
|
|
pp55
Newbie
Offline
Activity: 41
Merit: 0
|
|
December 28, 2018, 01:09:54 PM |
|
Just tried 12.0 version on NV 1060 3gb running Windows 7. Mine ETH only with -eres 0. -eres 1 causes DAG errors. Anyway, thanks for your miner!
|
|
|
|
Jonet
Jr. Member
Offline
Activity: 82
Merit: 3
|
|
December 30, 2018, 03:49:34 PM |
|
Hi there! All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
|
|
|
|
raas
Newbie
Offline
Activity: 14
Merit: 0
|
|
December 30, 2018, 06:17:00 PM |
|
To those who have GPU 390 / 390X, have you seen that the hash is considerably low? but it only happens to me when I'm ETH or ETC (each gpu is giving a hash of 24 +/-) but in other dagger coins, it's around 30mhs +/- (only with 390/390X, i have 380 too, and the hash is well with any coin)
|
|
|
|
ctp9
Jr. Member
Offline
Activity: 52
Merit: 5
|
|
December 31, 2018, 03:11:08 AM |
|
Hi there! All my rigs are still on Windows 10 build 1709. Has there been any development regarding mining on Win10 build 1803 and later? Is it known what is/was causing the problem?
I've had no issues with Windows 10 builds 1803 and 1809.
|
|
|
|
Haidong Liang
Newbie
Offline
Activity: 65
Merit: 0
|
|
December 31, 2018, 04:26:57 AM |
|
To those who have GPU 390 / 390X, have you seen that the hash is considerably low? but it only happens to me when I'm ETH or ETC (each gpu is giving a hash of 24 +/-) but in other dagger coins, it's around 30mhs +/- (only with 390/390X, i have 380 too, and the hash is well with any coin) Same here. It happens to 290/290X as well.
|
|
|
|
mrkimrkonja
Newbie
Offline
Activity: 1
Merit: 0
|
|
December 31, 2018, 08:04:48 AM |
|
Same here My 6 R9 290 are doing 21-22Mhs Before they were doing 29mhs However, this is not connected to ver 12.0 It happened gradually for me for months now I thought it was connected with overheating because of the fans failing
Maybe it is connected with DAG file size getting larger?
Does anyone know what to do? Have you tried running -oldkernells?
|
|
|
|
adaseb
Legendary
Offline
Activity: 3878
Merit: 1733
|
|
December 31, 2018, 08:09:58 AM |
|
Same here My 6 R9 290 are doing 21-22Mhs Before they were doing 29mhs However, this is not connected to ver 12.0 It happened gradually for me for months now I thought it was connected with overheating because of the fans failing
Maybe it is connected with DAG file size getting larger?
Does anyone know what to do? Have you tried running -oldkernells?
Basically its the DAG Thrashing bug which affected GPUs like the R9 280X and the RX 470/570 before AMD issued a driver fix. When the DAG exceeds a certain size the GPU has a longer seek time due to some error, Nvidia GPUs never experienced this. When the R9 280X was on DAG #0, it hashed at 28MH/s and now it hashes at less than 10MH/s. So the GPU is pretty much useless due to this bug. Same issue happened with the RX series GPUs, however AMD issued a fix with the GPU compute drivers. The R9 280X never got that fix and most likely neither will the R9 290.
|
|
|
|
|