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

[dollos]

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.

[DJMorgan]

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

[Ursul0]

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.

[DJMorgan]

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.

[Ursul0]

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

[staman]

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

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!

[Kukus]

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.

[greatauror28]

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.

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.

[perazdera]

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

[OXUS]

Hello

i have problem with my rig running claymore .... i get low hashrate on eth for some reason ...

windows 10 ... claymore v10.0

[Victorio]

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).

[Ursul0]

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.

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:

[OXUS]

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

[DJMorgan]

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

[twicx]

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

[OXUS]

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

[ccminer.net]

Where I can get a good tutorial on how to flesh bios to undervolt with linux?

[AzzAz]

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

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.

Good idea. More, it is possible that miner to check how long it is ON on every switch to DEVFEE and than to readjust to longer period. I.E. after 2 hours miner goes 4 min to DEVFEE and 4 hours of mining, than after 4 hours it does 8 min for DEV and 8 hours for owner...   Or simple command that make choice for periods.

[blackhwk77]

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.

[scryptr]

Okay, after 3 months of mining during the last couple weeks rig has been freezing and the last line of the log file indicates:

GPU got incorrect temperature 511 ignore

Thoughts?

I got this error when one of the fans on an RX580 failed. I don't know how long it was running with one failed fan but when I noticed the failed fan the card was very very hot !

In that case, the temperature was so high that the card itself couldn't measure it and that's why you got GPU got incorrect temperature 511.
That's my guess.

No, the card didn't respond - so it returned an code meaning invalid, which is what you see.

Hey Wolf0 do you think this is a failing riser issue? I kinda ruled that out already because it takes days before this happen. I believe if it's a failing riser it would kinda happen right away?

I hate to think this is a GPU issue as they're barely 4 months old.

Make sure Windows didn't update the drivers automatically. On Windows 10 Pro you can set Windows Update to not include drivers. Type 'gpedit' in the search box and in the Group Policy Editor navigate to Administrative Templates ==> Windows Components ==> Windows Update and set 'Do not include drivers with Windows Update' to enabled.

Good man, thanks for sharing this! Appreciated.

IT DEFINITELY COULD BE A RISER--

Risers do not always fail immediately.  The riser can overheat, or short within a connection, and fail to work properly.  Have you tried the card in a motherboard without a riser? By itself?  If you then get the same result, your card is bad.  However, it could have failed because of a bad riser, a riser with a short, or with a component that failed due to heat.

Have you swapped a fresh riser into the system?  Have you swapped risers in the system to see if the riser produces the same result on another card?

The "511" readout is not good news, but it does not automatically mean the card is dead.  And, failing risers can damage a card.  Other things to look for is cable friction against a fan, spacing between cards, or placing the card in a hot point within the system (not good).       --scryptr