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

[Call_Me_Bambi]

Try uninstalling all of the AMD bloat especially Wattman.

I like to have the BIOS flashed with good fam and temp settings.  Then that becomes the default.

How to uninstall wattman only? If I look at add\remove programs, AMD software is listed there not the watt. Do you have steps?

I think you will have to uninstall the complete AMD Crimson package and reinstall it but only select "AMD Display Drivers". Use DDU to clean out all the AMD drivers http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

[1714106343]

1714106343

[1714106343]

1714106343

[peterboy1]

i give up with the new versions.

new kernels keep giving me incorrect shares no matter how i downclock, it comes the point that its giving me lower hashrate already than the old kernels/old versions.

however, using oldkernels 1 with 11.5 also fluctuates my hashrate so much by 30-40mh/s less.

so my last option is use old versions.

for more info, im dual mining keccak with dcri 6.

This is exactly what I have found with my bios modded rx580s. I am glad I am not the only one. What version did you downgrade to 11.0?  Keep in mind what we are talking about is the fluctuation is in the miner or reported hashrate NOT effective hashrate which normally fluctuates due to luck.

So my options:
- try stock bios with new kernels
- wait for a fix
- use 11.0
- accept the fluctuation

reported of course.
i noticed 2mins after launch, all my hashrate gets less 3mh/s each, so leaving me almost 30+mh/s decrease. but there are times it will come back to original hashrate but little less and it wont stabilize there.

your options for me are:
- its frustrating reverting back to stock bios, since it is the most essential mod for amd cards
- waiting for a fix might not arrive, remember, claymore is always using stock cards for his testing
- while downgrading versions is the most suitable option, it would be frustrating we wont benefit latest features such as less stales and the like
- no, cant accept that. it would be annoying to see your graph wobbling in the pool. and its hard to troubleshoot that way

im on my way testing for 1 last time with the latest version and latest kernel, but i wont be using asm 2.

[big al]

it's possible with the new kernels that modified ram timings aren't needed. Will report back in a few days on that.

[peterboy1]

it's possible with the new kernels that modified ram timings aren't needed. Will report back in a few days on that.

please update us. but i highly doubt you'll gain comparable hashrate to modded one.

[Tuca]

Is anyone else getting the DAG error on 3gb nVidia 1060 cards (or any other 3072MB cards?)

Any fix for not enough vRAM for the DAG or am I better off switching to equihash coins now?

It was fine until I rebooted and I assume a new epoch was reached while I did that.

add the command line -eres 0

[ViWe]

Any chance of getting x16r as secondary coin algorithm?

[Poweriser]

Dear Claymore, do you plan to add new algorithms to the next version of the program? Smart coin, it seems that died, on other coins the difficulty is high. What about Keccakc?

[big al]

Dear Claymore, do you plan to add new algorithms to the next version of the program? Smart coin, it seems that died, on other coins the difficulty is high. What about Keccakc?

I bet nicehash upgraded from v10.6

[nitrobg]

Any chance of getting x16r as secondary coin algorithm?

Sure. Let's add 16 different algos into a single miner as a secondary algo, regardless of whether any of the algorithms actively uses memory or not. Perfect idea, 10/10.

[cryptoillusion1]

Dear Claymore, do you plan to add new algorithms to the next version of the program? Smart coin, it seems that died, on other coins the difficulty is high. What about Keccakc?

The miner is

Claymore's Dual Ethereum + Decred/Siacoin/Lbry/Pascal/Blake2s/Keccak AMD+NVIDIA GPU Miner.

[awdmesh]

Claymore -

Just wanted to give some feedback. I've been switching back and forth between 10.6 and your 11 series on a 7 card Windows 10 rig. The rig consists of
RX470
RX480
4 570s
1 1060 Nvidia 3GB.

The AMD cards have timing bios mods and have slight overclocks/underclocks within afterburner.

With the 10 series Claymore I used to run the system for weeks with no crashing. Once I switched to the 11 series and used the new kernel options I'd get a random crash and I couldn't figure out what was happening because I had it set to reboot upon crash. Yet I'd walk up to the machine, see that Windows 10 was running but the command prompt was gone.

I recently switched back to 10.6 but noticed it wasn't generating as many shares, but was stable. Then a few days ago I saw your new 11.5 with the old kernels option set. I thought I'd give that a try and for two days it ran with no dying until last night. I checked the machine this morning and sure enough, windows 10 was running but there was no command prompt open. I was able to open the log and noticed that a card died and it appeared your software caught this and was going/tried to reboot but a line or two later I saw the server error 10004 (which is mentioned on page 153 of this thread). It appears this is a windows issue and you replied on page 153.

My question is why can Claymore miner in the command prompt just die and or can it think its starting a reboot and windows not actually reboot?

My linux machine with 2 RX570 is happy with 11.4 new ASM mode and has not stopped running at all/no crashes.

[big al]

Keccakc is different than keccak

[big al]

My question is why can Claymore miner in the command prompt just die and or can it think its starting a reboot and windows not actually reboot?

Try disabling QuickEdit Mode for the console

[acv111]

For some reason upon crashing, 11.5 freezes windows or crashes the miner (program). Never happens on 11.2. Anyone had this happen ? Really eager to move on to 11.5 because it halved my stale shares and amd cards mine a bit better.

[RYXES]

Latest version is v11.5:

- added "-oldkernels" option (AMD GPUs only), you can try "-oldkernels 1" to use old-style GPU kernels from v10, they can be more stable for hard OC and custom BIOSes.

Waheey my constructive advice worked!

Will try tomorrow against my v10 rigs.

[awdmesh]

My question is why can Claymore miner in the command prompt just die and or can it think its starting a reboot and windows not actually reboot?

Try disabling QuickEdit Mode for the console

Thank you. I disabled it in both defaults and in the current window. I should've mentioned that my claymore bat file is set to start on boot which pulls settings from my config. That works perfectly so I'm at a lose as to why I woke up, went upstairs tp find windows 10 at the desktop with no cmd prompt up.

I looked over the log file again and it would appear that last night the rig did reboot after a failed attempt to generate the new DAG 176. It generated a new log file which I looked over and I could see that after windows rebooted it still failed to generate the dag or a card filed (can't remember) at which point it was saying that the miner needed to restart/reboot. One of the last few lines said something about error 10004 and like I mentioned the desktop was up with no command prompt.

Almost as if claymore thought it was going to reboot, closed out the command prompt, but windows did not actually reboot. I'll keep a closer eye on it and check things to see how long windows has been running to correlate stuff with my logs. Other than this issue everything works perfect. I get a solid 195-196MHS with the 7 card rig and I have not spent a lot of time tweaking it.

[Call_Me_Bambi]

My question is why can Claymore miner in the command prompt just die and or can it think its starting a reboot and windows not actually reboot?

Try disabling QuickEdit Mode for the console

Thank you. I disabled it in both defaults and in the current window. I should've mentioned that my claymore bat file is set to start on boot which pulls settings from my config. That works perfectly so I'm at a lose as to why I woke up, went upstairs tp find windows 10 at the desktop with no cmd prompt up.

I looked over the log file again and it would appear that last night the rig did reboot after a failed attempt to generate the new DAG 176. It generated a new log file which I looked over and I could see that after windows rebooted it still failed to generate the dag or a card filed (can't remember) at which point it was saying that the miner needed to restart/reboot. One of the last few lines said something about error 10004 and like I mentioned the desktop was up with no command prompt.

Almost as if claymore thought it was going to reboot, closed out the command prompt, but windows did not actually reboot. I'll keep a closer eye on it and check things to see how long windows has been running to correlate stuff with my logs. Other than this issue everything works perfect. I get a solid 195-196MHS with the 7 card rig and I have not spent a lot of time tweaking it.

If Claymore crashes the reboot option should work, but if Windows had crashed and rebooted then Claymore will not (AFAIK) restart. You need to add Claymore to the Windows start menu. Do this by pressing the "Windows Key + R" type "shell:startup" in the dialog box and add Claymore, as a shortcut, to the folder that pops up.
Just Google "shell:startup" for more info.

[jdubya]

Can someone share their config string for dual mining? 

Specifically for etherium and a blake2s coin (Verge). 

Any help would be appreciated.


Thanks

[whoismoses]

I use a config file.

-epool ssl://us1.ethermine.org:5555
-ewal <your ETH wallet>.<your rig name>
-epsw x
-etha 0
-mode 0
-ftime 10
-gser 1
-dcri 35,35,35,35,35
-platform 1
-logsmaxsize 64
-dpool stratum+tcp://pool.unimining.net:5770
-dwal <your xvg wallet>
-dcoin blake2s
-dpsw c=XVG

[cryptoillusion1]

For some reason upon crashing, 11.5 freezes windows or crashes the miner (program). Never happens on 11.2. Anyone had this happen ? Really eager to move on to 11.5 because it halved my stale shares and amd cards mine a bit better.

Same issue here  windows freezes