Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 551. (Read 6590757 times)
October 30, 2017, 01:06:04 PM
Does anyone else get hosed when trying to update the AMD drivers on machines with multiple bios flashed 570? The driver update doesn't finish, screen just keeps flashing every 5 seconds. I end up having to disconnect all 570s(I leave 580s) before I do the update then add them back in one at a time between reboots after using the driver patch. It does this regardless or whether I DDU or not.
October 30, 2017, 12:58:57 PM
I would like to be honest, if i can escape your dev fee i will do it ...
It seems you made a lot of money and dont keep this one good has he can be with all found you get.
I expect some release with new algo top hashrate, more dual options, more detailed "s" report, like hashrate for 6hours, 12hours, 24hours.
The last update you made about DAG creation is ON YOUR is nice ...
Cause without this is more like 3,5% - 4% we loose ...
So thanks for this and do more good work please!
I would add where is checksum ? You earn some million dollars ... You have time to make a checksum ... Or pay someone for oO
It seems you made a lot of money and dont keep this one good has he can be with all found you get.
I expect some release with new algo top hashrate, more dual options, more detailed "s" report, like hashrate for 6hours, 12hours, 24hours.
The last update you made about DAG creation is ON YOUR is nice ...
Cause without this is more like 3,5% - 4% we loose ...
So thanks for this and do more good work please!
I would add where is checksum ? You earn some million dollars ... You have time to make a checksum ... Or pay someone for oO
Personally I think there should be a timer set for DEV mining. Where there is 2 hours of DEV mining then it stops or reduces to once every 12\24 hours. Counter is reset each time the miner restarts. Each miner then contributes 2 hours of hashing time towards the development of Claymore and then once or twice more daily. I really dont like the idea of ongoing DEV fee especially if my miner has an uptime of weeks\months.
October 30, 2017, 11:31:40 AM
Where I can get a good tutorial on how to flesh bios to undervolt with linux?
October 30, 2017, 10:59:22 AM
i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...
Post your miner configuration (the content of your .bat file).EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x
im mining ubiq which have smaller dagger file .....also the normal eth speed is low too
Try uninstalling the driver utility ddu and then install using the installer of wood in the system - for example after unpacking the driver 7zip can test after installing the driver Radeon Software Crimson ReLive Edition Beta for bc
its a nvidia 1060s cards ..... i did a fresh windows installations then put installed the driver now i even updated to the latest one 388.13 ....
strangly all another miners are okay doing the hashrate they should im getting normal hashes on all algos on nicehash miner ...everything is okay but eth
October 30, 2017, 10:51:23 AM
I'm having some minor difficulties with setting cclock, mclock, vddc and mvddc.
I have them set in both config and start.bat, but the timings don't take to the GPUs. However, I also have that thing going on where GPU temps and fan speeds are not shown in claymore, because I don't have a dummy plug and none of the GPUs are connected to a display. This info comes up in some software - it's displayed in CPUz and HWiNFO64, but not in Watttool for example.
I'm actually having a lot of difficulty with getting my undervoltage settings to stay put. I've tried watttool, OverdriveN, Afterburner and WattMan, but they won't stick. Ideally, I'd like to just use claymore to do it, it seems a lot easier and neater tbh. The GPU voltages are working when set with the bios, but not the memory one for some reason.
So, here's what i'm wondering. 1, is there a way to get claymore to show things like gpu fan/temp info without a dummy plug? 2. is that why i can't set the clock and mem voltages with claymore?
Also, it sounds like the latest drivers as mentioned by Ursul0 might help.
Thanks all,
N
I have them set in both config and start.bat, but the timings don't take to the GPUs. However, I also have that thing going on where GPU temps and fan speeds are not shown in claymore, because I don't have a dummy plug and none of the GPUs are connected to a display. This info comes up in some software - it's displayed in CPUz and HWiNFO64, but not in Watttool for example.
I'm actually having a lot of difficulty with getting my undervoltage settings to stay put. I've tried watttool, OverdriveN, Afterburner and WattMan, but they won't stick. Ideally, I'd like to just use claymore to do it, it seems a lot easier and neater tbh. The GPU voltages are working when set with the bios, but not the memory one for some reason.
So, here's what i'm wondering. 1, is there a way to get claymore to show things like gpu fan/temp info without a dummy plug? 2. is that why i can't set the clock and mem voltages with claymore?
Also, it sounds like the latest drivers as mentioned by Ursul0 might help.
Thanks all,
N
October 30, 2017, 10:45:54 AM
i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...
Post your miner configuration (the content of your .bat file).EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x
im mining ubiq which have smaller dagger file .....also the normal eth speed is low too
Try uninstalling the driver utility ddu and then install using the installer of wood in the system - for example after unpacking the driver 7zip can test after installing the driver Radeon Software Crimson ReLive Edition Beta for bc
October 30, 2017, 10:38:08 AM
i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...
Post your miner configuration (the content of your .bat file).EthDcrMiner64.exe -epool stratum+tcp://us.ubiqpool.io:8008 -ewal 0xc86bb711033e00abd01b197a57be42421678a987 -epsw x -eworker rig1 -allcoins 1 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal neverrazor.1 -dpsw x
im mining ubiq which have smaller dagger file .....also the normal eth speed is low too
October 30, 2017, 10:37:35 AM
ok gyus some good news:
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours
1) how can you even say that out loud? that driver is not even 7 days old
2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !
Please stay away from such a comments, you are fooling others!
really? this is where you want to be right? wow. fuck idiots... I guess
see at the bottom: 2*10*570
also on 2) see this:
October 30, 2017, 10:16:30 AM
i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...
Post your miner configuration (the content of your .bat file). October 30, 2017, 09:32:39 AM
Hello
i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...
windows 10 ... claymore v10.0
i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...
windows 10 ... claymore v10.0
October 30, 2017, 09:15:26 AM
Quote
So i need to to set bios to factory so that it can pass signature check?
You need to patch the video drivers. Get the bios signature patcher here: https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher
Just to check if I understand it correctly. I need to install driver then patch the driver with signature patcher from that link. Does that patcher work for every driver? Mainly I want to get AMD Blockchain Workloads driver to work.
Works with AMD Blockchain driver as well as with new one.
Procedure:
1) clean you system with DDU and reboot
2) install new driver and don't reboot
3) run utility Thread-AMD-ATI-Pixel-Clock-Patcher
4) and then restart the system
Thank you. I will try this today when I get home. One more question. Because i did not modded cards myself, I bought them like that from some guy, is there some way that I can find out what is factory settings for my cards?
You can find the memory type by reading from the BIOS. Save the bios using atiflash and read it off from Polaris Bios Editor. That would indicate the memory you have on the GPU. You can google for the original BIOS for that brand, particular model and memory.
Thank you guys allot, you are the best Smiley Smiley I hope I will menage to try every suggestion today, if not I will definitely try it over the weekend and get back to you for the results.
I tried it out over the weekend and it worked. Problem is solved. Thank you guys, I really appreciate for the help
October 30, 2017, 08:13:59 AM
ok gyus some good news:
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours
1) how can you even say that out loud? that driver is not even 7 days old
2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !
Please stay away from such a comments, you are fooling others!
Actually what Ursul0 cited is pretty factual, as I've experienced it myself.
This driver, together with the Win10 FCU fixed my OpenCL issues - and i've tried everything under the sun to fix it. I used to use aug 23 blockchain driver and a recently-installed win10 pro without any updates.
I only run 8 cards but here's some proof that's it's stable.
Previously with the setup above, miner doesn't get past 3 hours without openCL issues.
It has the dag fix just like the blockchain drivers - and this version is fully-supported by AMD and not in Beta status.
Note that you have to enable *compute* settings in each card in the Radeon Settings for this to work.
October 30, 2017, 08:12:33 AM
I did a try to install new AMD drivers. The clue is that I am unable to change "GPU workload" setting for one card in a rig. It remains at "Graphics" when I trying change it to "Compute". All other cards (similar ones) switched with no problems.
October 30, 2017, 08:08:15 AM
ok gyus some good news:
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
https://s1.postimg.org/1jpgnkmudb/10x570.png
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
https://s1.postimg.org/1jpgnkmudb/10x570.png
Well, i strongly disagree. My personal experience (and plenty of others) is completely opposite to yours
1) how can you even say that out loud? that driver is not even 7 days old
2) OverdriveNTool has been working just fine with blockchain drv (23aug)
3) yes, it let you post it in device manager and yes, it let you mine with it.. but do try enable compute workload and see that mess if you are running 12 cards! And loosing 4mh's per card with NO-dag-driver * 12 cards.. hell no !
Please stay away from such a comments, you are fooling others!
October 30, 2017, 07:32:20 AM
Will there be support for 14-16 cards in Windows? the output of drivers will be under Linux? Right now I use on 14 GPU ethOS.
I guess it's there as long as you have free pcie lanes. AMD apparently fixed... whatever was their issue with windows
October 30, 2017, 07:26:20 AM
Will there be support for 14-16 cards in Windows? the output of drivers will be under Linux? Right now I use on 14 GPU ethOS.
October 30, 2017, 06:58:09 AM
ok gyus some good news:
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
crimson-relive-17.10.2-oct23 driver is
1) more stable than the blockchain drv (has the DAG fix that can be enabled with "compute" workload)
2) has proper API (no issues for setting up the volts with overdriven tool)
3) supports more then 8 AMD gpus on the same platform
all good news indeed.
October 30, 2017, 06:47:19 AM
I recommend the developer - to improve the code for performance, in comparison with version 9.8 it became worse - not important is the hash the number of the shares is important - there is really performance.
Also work on stability, a lot of failures per day. with ping is not associated with loss of packets.
PS: RX 580
Also work on stability, a lot of failures per day. with ping is not associated with loss of packets.
PS: RX 580
October 30, 2017, 03:43:26 AM
All the idiots that are trying to cheat Claymores system please know that you are stealing. the man puts his effort and time into giving us something that is making us money.
he is entitled to make that money. if you dont like that then dont use it fair and simple.
Yes he is a dick most of the time with his attitude of knowing it all but still that does not allow or give us the right to steal from him.
Anyone who is stealing in this form know that you are feeding your families with stolen Money!!!
Wrong is always wrong and if you support wrong in whatever way you need to look deep down in your heart and check where it has all gone wrong.
This is a good and clean community so lets keep it that way.
he is entitled to make that money. if you dont like that then dont use it fair and simple.
Yes he is a dick most of the time with his attitude of knowing it all but still that does not allow or give us the right to steal from him.
Anyone who is stealing in this form know that you are feeding your families with stolen Money!!!
Wrong is always wrong and if you support wrong in whatever way you need to look deep down in your heart and check where it has all gone wrong.
This is a good and clean community so lets keep it that way.
October 30, 2017, 03:40:48 AM
Hello, Guys. I'm asking for help as I got stuck with a problem. I read through the topic and tried many things. but didn't work out.
I have two farms mining ETH+DCR for 6 and 4 cards. The problem with a second farm.
I have 4 RX570 cards, motherboard ASrock z97. It used to give me 100 mh/s stable. However, then miner started to crash with the message:
"NO AMD OPENCL or NVIDIA CUDA GPUs found, exit".
ok... uninstall drivers, update cards with Crimson ReLive beta Blockchain Driver, patch drivers, restart and launch miner again.
The problem arises exactly in 120 minutes again... not 119 or 121, it is exactly two hours before it crashes again. The monitor blinks a couple of time. speed goes to 0, and the end.
I tried to repatch cards via bios (atiflash), played with graphic cards, nothing works. The only thing I noticed that if I launch 3 cards from 4... they work fine for a relatively long time without crashes. Notable, that I tried each of the card, and they seem to be normal.
However, when i start all 4... it works only 120 minute and "NO AMD OPENCL...".
Please, let me know if there are any ideas, I can provide you with more info, whatever you ask.
I have two farms mining ETH+DCR for 6 and 4 cards. The problem with a second farm.
I have 4 RX570 cards, motherboard ASrock z97. It used to give me 100 mh/s stable. However, then miner started to crash with the message:
"NO AMD OPENCL or NVIDIA CUDA GPUs found, exit".
ok... uninstall drivers, update cards with Crimson ReLive beta Blockchain Driver, patch drivers, restart and launch miner again.
The problem arises exactly in 120 minutes again... not 119 or 121, it is exactly two hours before it crashes again. The monitor blinks a couple of time. speed goes to 0, and the end.
I tried to repatch cards via bios (atiflash), played with graphic cards, nothing works. The only thing I noticed that if I launch 3 cards from 4... they work fine for a relatively long time without crashes. Notable, that I tried each of the card, and they seem to be normal.
However, when i start all 4... it works only 120 minute and "NO AMD OPENCL...".
Please, let me know if there are any ideas, I can provide you with more info, whatever you ask.
I don't have a solution, but if it's really exactly 120 minutes, one workaround is to set the rig to auto-reboot after 119 minutes.
I've used that as a workaround on rigs running Win 10 Ent trial, which is good for 90 days... after 90 days, it expires, and will shut down after 60 minutes. So I set the machine up to reboot in 59 minutes. With a rig on SSD, it actually mines 98% as much as usual despite doing the reboots, so it's a good workaround until you have time to fix it properly.
Try to change the riser of the fourth gpu, if still persist, check the psu power rating, been on that, my psu is not enough powering up 4th card when dag is getting bigger along the way.
Jump to: