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

[scryptr]

Hi Claymore,

i get with R9 280x 15.5Mh only not 20Mh
How can i improve it  ?

Its normal for 280x.

DEPENDING HOW HOT YOUR ROOM IS--

280X cards run hot and eat power.  If your cards are overheating, you may need to downclock, and earn 15-16MH/s per card.   If you set "-dcri 15" in your config, you will reduce the intensty of your secondary coin by 1/2  and give your 280X cards more room to breathe; they will run faster  and at lower temperature.  If you set "-cclock 1100", you will overclock your card, increase the hash rate, and increase the temperature of the card.  A core clock of 1100 may not be stable for your card/rig, you have to check postings by other miners regarding overclocking.  If you set "-tt 87", your card will self regulate, attempting to keep the temperature at or below 87 deg F.  If you are in a hot room, your hash may be 15-16MH/s because of temperature throttling.  My 280X cards made 22MH/s last winter, when the room was cooler, and the difficulty lower, and the DAG smaller.

All of this and more is in the README!!!.txt file, you should study it.       --scryptr

scryptr - will the Stilt BIOS help maximize 280/280x for ETH mining? Thanks

THE LEGENDARY STILT BIOS MODS--

Stilt BIOS mods are from the days of LiteCoin (LTC) and its meteoric rise prior to the Mt. Gox hack  There is a thread for those still interested.:  https://forum.ethereum.org/discussion/5937/gpu-optimized-stilt-bios-anyone-have-them] .  Some users of the modded BIOS are able to point to the  location of these legendary files, other users are downloading the entire archive to preserve the treasured data.

I have never flashed my recently ROI'd 280X cards.  It can affect the resale value of your cards if detected.  From what I read in the above Stilt BIOS thread, there is no guaranteed hashrate improvement, even if you flash your card.  The thread is still short, and a good read.  It points to the old, archived, 100+ page Stilt BIOS thread where I may find myself reading about the Black VooDoo of BIOS modding.

Bottom line, a BIOS mod is not a sure thing, and you need to save a copy of your original manufacturer's BIOS in order to set things back to default.       --scryptr

[Dev_Sempak_coin]

hello i have tried use dual mining but my dcr stat's is zere hash
anyone can give me setting to minng dual mode at eth dwarfpool and sia nanopool?

[melloyellow]

Hi Claymore,

i get with R9 280x 15.5Mh only not 20Mh
How can i improve it  ?

Its normal for 280x.

DEPENDING HOW HOT YOUR ROOM IS--

280X cards run hot and eat power.  If your cards are overheating, you may need to downclock, and earn 15-16MH/s per card.   If you set "-dcri 15" in your config, you will reduce the intensty of your secondary coin by 1/2  and give your 280X cards more room to breathe; they will run faster  and at lower temperature.  If you set "-cclock 1100", you will overclock your card, increase the hash rate, and increase the temperature of the card.  A core clock of 1100 may not be stable for your card/rig, you have to check postings by other miners regarding overclocking.  If you set "-tt 87", your card will self regulate, attempting to keep the temperature at or below 87 deg F.  If you are in a hot room, your hash may be 15-16MH/s because of temperature throttling.  My 280X cards made 22MH/s last winter, when the room was cooler, and the difficulty lower, and the DAG smaller.

All of this and more is in the README!!!.txt file, you should study it.       --scryptr

scryptr - will the Stilt BIOS help maximize 280/280x for ETH mining? Thanks

THE LEGENDARY STILT BIOS MODS--

Stilt BIOS mods are from the days of LiteCoin (LTC) and its meteoric rise prior to the Mt. Gox hack  There is a thread for those still interested.:  https://forum.ethereum.org/discussion/5937/gpu-optimized-stilt-bios-anyone-have-them] .  Some users of the modded BIOS are able to point to the  location of these legendary files, other users are downloading the entire archive to preserve the treasured data.

I have never flashed my recently ROI'd 280X cards.  It can affect the resale value of your cards if detected.  From what I read in the above Stilt BIOS thread, there is no guaranteed hashrate improvement, even if you flash your card.  The thread is still short, and a good read.  It points to the old, archived, 100+ page Stilt BIOS thread where I may find myself reading about the Black VooDoo of BIOS modding.

Bottom line, a BIOS mod is not a sure thing, and you need to save a copy of your original manufacturer's BIOS in order to set things back to default.       --scryptr

Most cards have a dual bios switch.  If you screw up one, just flip the switch to the other.  You can fix the bad one (if you have dual bios).  People flash vbios all the time, even card manufacturers provide updated vbios so it shouldn't affect your resale value (just make sure you have a switch).  In my experience with stilt and eth mining, I didn't see a significant hashrate improvement but I did see lower temperatures, not dramatic but still there, especially with Hynix memory.  

[melloyellow]

Claymore, when I edit my configs through remote manager, some digits are added to the end.  Since I have dcri at the bottom it looks something like this

-dcri 404
0
9

and the miner starts with 404.  I'm on 5.1 beta 2.

[Claymore]

Claymore, when I edit my configs through remote manager, some digits are added to the end.  Since I have dcri at the bottom it looks something like this

-dcri 404
0
9

and the miner starts with 404.  I'm on 5.1 beta 2.

Fixed in 5.3, check OP:

.....
Latest version v5.3:

- added experimental "-di detect" option value to detect correct GPU order for temperatures management.
- improved Nicehash pool support (mining.extranonce.subscribe).
- fixed issue with sending config.txt to EthMan.
- fixed issue in EthMan (possible garbage during remote editing config.txt).

[vapourminer]

[
Most cards have a dual bios switch.  If you screw up one, just flip the switch to the other.  You can fix the bad one (if you have dual bios).  

even for cards without the dual bios you can usually recover from a bad flash via using onboard video or use a second card like an old pci card to see what you are doing.

usually.

[tmigz]

Hey folks,

This has been bugging me for a few days.  Keep getting the following error, but only after adding my newest rx480 GPU.

Tried with both 5.1 and 5.3

01:40:06:662 ccc GPU 2, OpenCL error -36 - cannot write buffer for DAG

I have all of the environmental variables set at the beginning of my batch file as shown below.
GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

I have 4GB physical memory
I have 16GB virtual memory set with 24GB max.  Windows 7 x64.

Hard drive is an older 7200rpm 250GB drive I had laying around.  Seems to work fine, no errors found when running disk check.

GPUS
290x - 4GB
380x - 4GB
390x - 8GB
rx480 - 8GB

GPU2 is the rx480.  I have no problems running the miner with the rx480 disabled.  I have tried both the newest 16.7.3 drivers as well as a clean install with the 16.7.2 drivers.  All 4 GPU's show up in device manager with no warnings.

Minor Detects GPU's as below.  (I notice the rx480 does not have a name next to it, not sure if this is of significance.)
01:39:31:892 ffc GPU #0: name: Hawaii, 4096 MB available, 44 compute units
01:39:31:912 ffc GPU #1: name: Hawaii, 8192 MB available, 44 compute units
01:39:31:917 ffc GPU #2: name: , 8192 MB available, 36 compute units
01:39:31:917 ffc GPU #3: name: Tonga, 4096 MB available, 32 compute units
 
Thanks in advance for any assistance!

[TheKoolaider]

Hey everyone 

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website. 

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard. 

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

[citronick]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

I run 5 x MSI 390s with USB3 PCI risers without any issues, at -100mV, 1040 core and 1125 mem, pushing 30MHs per card. EVGA 1600 G2, ASrock H81 mobo, Celeron 1840, 8GB RAM, 120SSD, W8.1, CDM 4.7 & 5.3 -ethi 16, ETH mining only

Did you use Crimson 15.12 and 16GB minimum virtual memory?

[Arsenay]

pool nicehash
OS Linux Debian 8.5 amd64
fglrx-driver 15.12
Claymore Miner v5.3

GPU0 -> HD 7850 cclock =1000 mclock = 1250 ethi= 32   
CPU1 -> HD 7950 cclock = 1000 mclock =1250 ethi = 48






 

[Claymore]

pool nicehash
OS Linux Debian 8.5 amd64
fglrx-driver 15.12
Claymore Miner v5.3
GPU0 -> HD 7850 cclock =1000 mclock = 1250 ethi= 32  
CPU1 -> HD 7950 cclock = 1000 mclock =1250 ethi = 48

See "Setting DAG" message between your selections.
Nicehash switched to ETH (epoch #68) from some other coin (may be EXP?) with less epoch number (afaik about #10-15 for EXP). Bigger epoch number - less speed.

[TheKoolaider]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

I run 5 x MSI 390s with USB3 PCI risers without any issues, at -100mV, 1040 core and 1125 mem, pushing 30MHs per card. EVGA 1600 G2, ASrock H81 mobo, Celeron 1840, 8GB RAM, 120SSD, W8.1, CDM 4.7 & 5.3 -ethi 16, ETH mining only

Did you use Crimson 15.12 and 16GB minimum virtual memory?

I did now.  I remember initially doing it, but I guess it didn't take.  It has been changed, and I'm testing it now. Thank you for that.

May I ask you to post your start.bat file as a reference for myself?  I'm still trying to figure out why the other commands that are given after "-eworker x"  do not work.  Any idea for this other problem I'm having?

[aleixoto]

Hey everyone 

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website. 

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

https://s10.postimg.org/h0li0nfgp/All_Chart_Marked.jpg

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard. 

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

[TheKoolaider]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

Reading your post made my day.  I don't feel like I'm going mad anymore.

Edit 1: Ok this is weird, but Claymore just did the thing I talked about.  It looked like it wasn't processing shares, but the computer didn't freeze.  I clicked on the cmd window and clicked enter.  Then suddenly, the missing hashes that I thought weren't happening appeared.  

1. Click on cmd window until you see your cursor blinking on a line.
2. Press enter.
3.
4. All the shares that didn't show for 2 minutes, appeared suddenly.
5. Profit?

Edit 2: Claymore shows hashing and share submissions, but 0 hash on Nanopool. Weird.

[Arsenay]

pool nicehash
OS Linux Debian 8.5 amd64
fglrx-driver 15.12
Claymore Miner v5.3
GPU0 -> HD 7850 cclock =1000 mclock = 1250 ethi= 32  
CPU1 -> HD 7950 cclock = 1000 mclock =1250 ethi = 48

See "Setting DAG" message between your selections.
Nicehash switched to ETH (epoch #68) from some other coin (may be EXP?) with less epoch number (afaik about #10-15 for EXP). Bigger epoch number - less speed.

yes, may be ))

[zero1]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

https://s10.postimg.org/h0li0nfgp/All_Chart_Marked.jpg

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

i has some similar issues with my rig
first you must check is psu... i had 5 gpus and and when i make them 4  the crashes goes from 10 hours to    24+ random. i manage the rig for single mining so 2x 700 gold psu is not enough for dual
second i did i make the pc restart every 8 hours and run the miner on start up (im using ubuntu so you must google for that )
now rig works w/o any issue
i hope that helps

[aleixoto]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

https://s10.postimg.org/h0li0nfgp/All_Chart_Marked.jpg

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

i has some similar issues with my rig
first you must check is psu... i had 5 gpus and and when i make them 4  the crashes goes from 10 hours to    24+ random. i manage the rig for single mining so 2x 700 gold psu is not enough for dual
second i did i make the pc restart every 8 hours and run the miner on start up (im using ubuntu so you must google for that )
now rig works w/o any issue
i hope that helps

thanks,, im changing to ubuntu i dont like win claymore.

for install Oficcial catalyst 15.12 on ubuntu i cant with LTS versions...

how i cant get the best drivers for ubuntu.

and what version of ubuntu you use? 12x 14.04 15.10 or 16x? and server version or desktop?(xubuntu kubuntu etc..
thanks

[scryptr]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

i has some similar issues with my rig
first you must check is psu... i had 5 gpus and and when i make them 4  the crashes goes from 10 hours to    24+ random. i manage the rig for single mining so 2x 700 gold psu is not enough for dual
second i did i make the pc restart every 8 hours and run the miner on start up (im using ubuntu so you must google for that )
now rig works w/o any issue
i hope that helps

thanks,, im changing to ubuntu i dont like win claymore.

for install Oficcial catalyst 15.12 on ubuntu i cant with LTS versions...

how i cant get the best drivers for ubuntu.

and what version of ubuntu you use? 12x 14.04 15.10 or 16x? and server version or desktop?(xubuntu kubuntu etc..
thanks

YOU CAN INSTALL CATALYST 15.12 ON UBUNTU LTS--


Google "Install Catalyst 15.12 on Ubuntu 14.04" and you will find many how-tos.  Basically, on a fresh install of Ubuntu, download the installation file from AMD directly and run it.  On a fresh Ubuntu 14.04 install, there are no drivers to purge.

I am not writing a tutorial here, just google an Ubuntu official support page and you will be good.  I build my rigs on Lubuntu 14.04.5 (just now the latest), and it is no real trick, just follow the support page steps.       --scryptr

[zero1]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

https://s10.postimg.org/h0li0nfgp/All_Chart_Marked.jpg

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

i has some similar issues with my rig
first you must check is psu... i had 5 gpus and and when i make them 4  the crashes goes from 10 hours to    24+ random. i manage the rig for single mining so 2x 700 gold psu is not enough for dual
second i did i make the pc restart every 8 hours and run the miner on start up (im using ubuntu so you must google for that )
now rig works w/o any issue
i hope that helps

thanks,, im changing to ubuntu i dont like win claymore.

for install Oficcial catalyst 15.12 on ubuntu i cant with LTS versions...

how i cant get the best drivers for ubuntu.

and what version of ubuntu you use? 12x 14.04 15.10 or 16x? and server version or desktop?(xubuntu kubuntu etc..
thanks

ubuntu 14.04 lts desktop
i use this commands for drivers (all my gpus are amd)
sudo apt-get -y update  
 sudo apt-get -y upgrade -f  
 sudo apt-get install fglrx-updates  
 sudo amdconfig --adapter=all --initial  
my 280x gpus are running for 17-19 hash on default values

[d57heinz]

Hey everyone  

I would like to ask the community for help.

I've been having an issue with my 3x MSI R9 390 miner.  The problem I am having is it seems that Claymore hangs/crashes after ~7 hours of continuous running.  The computer is still fine, I'm able to use it, but Claymore doesn't update with info. I'm able to confirm this because the hash rate for the miner is 0 when I look on the pool website.  

This problem occurs with both stock clock settings of the cards and with overclock settings of Core Clock 1190 and Memory Clock of 1500 and with/without undervolting.  However, last night I tested undervolt settings of -19 on MSI AB, and the same problem occurred ~7 hours into mining.

The charts are able to show where I know/believe the software crashed/the rig froze.

The first circle: I don't remember what happened here. I was either moving the rig or playing with settings.

The second circle: This is where at 3:30 in the morning, the rig crashed.  I know the rig crashed because when I tried to access the rig with chrome remote desktop, it couldn't connect.  At this time the rig was at stock settings. I don't know why it crashed.  The crash has only occurred once. Freezing of Claymore happens more often.

The third circle: Here I stayed up late to play with overclock/undervolt settings.  Overclock settings initially were Core Clock 1190, Memory Clock 1500(stock) without undervolt.  I tested that for about an hour and a half and it seemed to work fine, so I moved on to undervolting.  I found that undervolting -19 on MSI AB seemed to run well enough. I ran that for about 2 hours and it seemed to work well, and I went off to bed.

The fourth circle: Rig ran overnight overclocked and undervolted(Core voltage 0, Core clock 1190, Memory clock 1500) for ~7 hours again. When I woke up and first checked Nanopool around 6:45, the hash rate was being seen by the server.  Then around 7:30, I checked the hash rate again, and it was 0.  Here I know Claymore froze. I was able to access it remotely from my phone, open programs, but Claymore was not updating, as well as go to it physically and use the mouse and keyboard.  

What I'm trying to have done, is tell Windows 10 to restart Claymore if it freezes or doesn't send/receive info.  I have a shortcut for my start.bat file in the startup folder to start Claymore when the computer restarts.  But I want this to happen with Claymore only, and if the rig happens to freeze itself, if it's possible to restart the rig itself, that would be great. But I'm not sure about that.

OP says that the watchdog command should help with this, but that command and a lot of other commands do not work.  Everything past the "-eworker x" command does not work for me no matter what I try.

EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal Wallet Address -epsw x -eworker x -etha -1,-1,-1 -eres 1 -erate 1 -gser 2 -wd 1 -r 1

I've read about a reboot.bat file, but I would like to have this process as automated as possible.  Without me having to keep checking the pool website and see if I still have a hash rate.

Sorry for the long post.  I would really appreciate the help.  Thank you everyone.

i have the same problem. at just 7h pools report hash 0 and 0 shares but client hashing and sharing and pc not crash...

sia nanopool + eth dwarfpool

Reading your post made my day.  I don't feel like I'm going mad anymore.

Edit 1: Ok this is weird, but Claymore just did the thing I talked about.  It looked like it wasn't processing shares, but the computer didn't freeze.  I clicked on the cmd window and clicked enter.  Then suddenly, the missing hashes that I thought weren't happening appeared.  

1. Click on cmd window until you see your cursor blinking on a line.
2. Press enter.
3.
4. All the shares that didn't show for 2 minutes, appeared suddenly.
5. Profit?

Edit 2: Claymore shows hashing and share submissions, but 0 hash on Nanopool. Weird.

this "bug" if you call it that relates to the new miner.  if i click on the window it pauses it.  When this happen to me before it was from having quick edit mode turned on (think it may have been on by default on the 5.3 version).  when you load the miner . right click the top left corner of window.  Then click properties then turn off quick edit mode.  if you click on your window and press the s key and it shows the s or pauses it you have this problem.  If it shows the stats then your good to go.

Hope that helps ya


edit.. little snippet from the rx470 with no oc.  Not a bad little card.. Going to run it a couple days then do some readings on power draw  22.1 mhs atm on ethereum so i can imagine it does well on expanse.. will do some more in the morning.  Been fighting trying to get a pcie splitter to work but i found out the hard way you cant seem to add pcie with a 1x - 3(1x) it recognizes the cards just wont install the driver properly.  havent given up on it just yet.  IF anyone knows any tricks be greatly appreciated.  So far i have tried to release some irq by killing the onboard sound and lpt1 and serial ports.. Kept getting thread exceptions and bsod.  Anyway thats for another thread.

One thing i might add is AMD did a fine job at this new wattman instead of radeon.. Be nice if they gave that functionality to the older cards.  Atm trixx will do but amd really stepped it up on the new OC tool

Code:

ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
17:36:39:771	290	º     Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.1      º
17:36:39:771	290	ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
17:36:39:771	290	
17:36:39:977	290	ETH: 1 pool is specified
17:36:39:977	290	DCR: 0 pool is specified
17:36:40:620	290	
Cards available: 4 
17:36:40:620	290	GPU #0: name: Hawaii, 4096 MB available, 40 units 
17:36:40:620	290	GPU #1: name: Ellesmere, 4096 MB available, 32 units 
17:36:40:635	290	GPU #2: name: Hawaii, 8192 MB available, 44 units 
17:36:40:636	290	GPU #3: name: Hawaii, 8192 MB available, 44 units 
17:36:40:637	290	Total cards: 4 
17:36:40:638	290	Initializing...

17:36:40:639	290	GPU #0 recognized as Radeon 290
17:36:40:639	290	GPU #2 recognized as Radeon 390X
17:36:40:640	290	GPU #3 recognized as Radeon 390X
17:36:40:640	290	POOL version
17:36:40:641	290	b126 
17:36:43:029	290	GPU #0: set -etha as 0 (ETH algo for fast cards)
17:36:43:029	290	GPU #1: set -etha as 0 (ETH algo for fast cards)
17:36:43:029	290	GPU #2: set -etha as 0 (ETH algo for fast cards)
17:36:43:029	290	GPU #3: set -etha as 0 (ETH algo for fast cards)
GPU 1 DAG creation time 4327 ms
17:36:50:498	2320	Setting DAG epoch #68 for GPU #1 done
17:36:50:499	2320	Job changed, drop current round
17:36:50:499	1308	Job changed, drop current round
17:36:51:111	3a0	GPU 2 DAG creation time 5002 ms
17:36:51:112	3a0	Setting DAG epoch #68 for GPU #2 done
17:36:51:112	3a0	Job changed, drop current round
17:36:51:112	16e0	Job changed, drop current round
17:36:51:129	a54	GPU 3 DAG creation time 5023 ms
17:36:51:130	a54	Setting DAG epoch #68 for GPU #3 done
17:36:51:130	a54	Job changed, drop current round
17:36:51:130	1394	Job changed, drop current round
17:36:51:789	1768	GPU 0 DAG creation time 5621 ms
17:36:51:791	1768	Setting DAG epoch #68 for GPU #0 done
17:36:51:791	1768	Job changed, drop current round
17:36:51:793	2238	Job changed, drop current round
ETH - Total Speed: 112.604 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
17:37:01:919	cb0	ETH: GPU0 29.345 Mh/s, GPU1 22.103 Mh/s, GPU2 30.389 Mh/s, GPU3 30.766 Mh/s

Best Regards
d57heinz