Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1181. (Read 6590757 times)
August 10, 2016, 02:55:12 AM
I think I might have broke something. I just grabbed a RX 480 today and it's showing over 60 MH in CDM, but no temp/fan speed.
August 10, 2016, 01:47:02 AM
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?
anyone can give me setting to minng dual mode at eth dwarfpool and sia nanopool?
Hey,
You can clearly see in RED that your SIA pool isnt connecting.
Paste your bat file configuration and help you out.
Cheers!
August 10, 2016, 12:53:44 AM
Problem whis Parity/v1.3.0-unstable-baa0871-20160725 ubuntu 14.04 server in ETC solo mode:
log 4.3 and 5.3
and 4.3 close whis criticall err
0.9.41-genoil-1.1.6 work whis no error whis same config
http://fs153.www.ex.ua/get/561775416582/264036490/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA.PNG
log 4.3 and 5.3
Code:
08:32:59:605 574 commandline: EthDcrMiner64.exe -epool http://10.0.0.2:8545/ -mode 1 -tstop 89
08:32:59:605 574
08:32:59:605 574 ЙHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH»
08:32:59:605 574 є Claymore's Dual Ethereum + Decred AMD GPU Miner v4.3 Beta є
08:32:59:605 574 ИHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHj
08:32:59:605 574
08:32:59:808 574 ETH: 1 pool is specified
08:33:01:480 574 OpenCL platform: AMD Accelerated Parallel Processing
08:33:01:480 574
Cards available: 6
08:33:01:480 574 GPU #0: name: Hawaii, 8192 MB available, 44 compute units
08:33:01:480 574 GPU #1: name: Tahiti, 3072 MB available, 32 compute units
08:33:01:480 574 GPU #2: name: Tahiti, 3072 MB available, 32 compute units
08:33:01:480 574 GPU #3: name: Tahiti, 3072 MB available, 32 compute units
08:33:01:480 574 GPU #4: name: Tahiti, 3072 MB available, 32 compute units
08:33:01:480 574 GPU #5: name: Tahiti, 3072 MB available, 32 compute units
08:33:01:480 574 Total cards: 6
08:33:01:480 574 Initializing...
08:33:01:480 574 GPU #0 recognized as Radeon 390X
08:33:01:480 574 GPU #1 recognized as Radeon 280X/380X
08:33:01:480 574 GPU #2 recognized as Radeon 280X/380X
08:33:01:480 574 GPU #3 recognized as Radeon 280X/380X
08:33:01:480 574 GPU #4 recognized as Radeon 280X/380X
08:33:01:480 574 GPU #5 recognized as Radeon 280X/380X
08:33:01:480 574 POOL/SOLO version
08:33:01:480 574 b142
08:33:01:496 574 start building OpenCL program...
08:33:11:278 574 done
08:33:11:278 574 GPU #0: set -etha as 0 (ETH algo for fast cards)
08:33:11:278 574 GPU #1: set -etha as 0 (ETH algo for fast cards)
08:33:11:278 574 GPU #2: set -etha as 0 (ETH algo for fast cards)
08:33:11:278 574 GPU #3: set -etha as 0 (ETH algo for fast cards)
08:33:11:278 574 GPU #4: set -etha as 0 (ETH algo for fast cards)
08:33:11:278 574 GPU #5: set -etha as 0 (ETH algo for fast cards)
08:33:11:403 980 ETH - connecting to 10.0.0.2:8545
08:33:11:403 980 http send request: {"method": "eth_getWork", "params": [], "id":0}
08:33:11:465 980 http got answer: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:33:11:465 980 ETH: Connected (10.0.0.2:8545)
08:33:11:465 980 parse packet: 92
08:33:11:465 980 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:33:11:465 980 remove first packet -1
Code:
08:40:35:002 a38 args: -epool http://10.0.0.2:8545 -mode 1 -ethi 16 -esm 1 -tstop 89 -gser 1
08:40:35:002 a38
08:40:35:002 a38 ЙHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH»
08:40:35:002 a38 є Claymore's Dual ETH + DCR/SC AMD GPU Miner v5.3 Beta є
08:40:35:002 a38 ИHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHj
08:40:35:002 a38
08:40:35:205 a38 ETH: 1 pool is specified
08:40:35:205 a38 Main Ethereum pool is 10.0.0.2:8545
08:40:36:861 a38 OpenCL platform: AMD Accelerated Parallel Processing
08:40:36:861 a38
Cards available: 6
08:40:36:861 a38 GPU #0: name: Hawaii, 8192 MB available, 44 compute units
08:40:36:861 a38 GPU #1: name: Tahiti, 3072 MB available, 32 compute units
08:40:36:861 a38 GPU #2: name: Tahiti, 3072 MB available, 32 compute units
08:40:36:861 a38 GPU #3: name: Tahiti, 3072 MB available, 32 compute units
08:40:36:861 a38 GPU #4: name: Tahiti, 3072 MB available, 32 compute units
08:40:36:861 a38 GPU #5: name: Tahiti, 3072 MB available, 32 compute units
08:40:36:861 a38 Total cards: 6
08:40:36:861 a38 Initializing...
08:40:36:861 a38 GPU #0 recognized as Radeon 390X
08:40:36:861 a38 GPU #1 recognized as Radeon 280X/380X
08:40:36:861 a38 GPU #2 recognized as Radeon 280X/380X
08:40:36:861 a38 GPU #3 recognized as Radeon 280X/380X
08:40:36:861 a38 GPU #4 recognized as Radeon 280X/380X
08:40:36:861 a38 GPU #5 recognized as Radeon 280X/380X
08:40:36:861 a38 POOL/SOLO version
08:40:36:861 a38 b176
08:40:36:877 a38 start building OpenCL program for GPU 0...
08:40:37:174 a38 done
08:40:37:299 a38 start building OpenCL program for GPU 1...
08:40:41:455 a38 done
08:40:41:565 a38 start building OpenCL program for GPU 2...
08:40:45:721 a38 done
08:40:45:846 a38 start building OpenCL program for GPU 3...
08:40:49:972 a38 done
08:40:50:097 a38 start building OpenCL program for GPU 4...
08:40:54:237 a38 done
08:40:54:362 a38 start building OpenCL program for GPU 5...
08:40:58:550 a38 done
08:40:58:675 a38 GPU #0: set -etha as 0 (ETH algo for fast cards)
08:40:58:675 a38 GPU #1: set -etha as 0 (ETH algo for fast cards)
08:40:58:675 a38 GPU #2: set -etha as 0 (ETH algo for fast cards)
08:40:58:675 a38 GPU #3: set -etha as 0 (ETH algo for fast cards)
08:40:58:675 a38 GPU #4: set -etha as 0 (ETH algo for fast cards)
08:40:58:675 a38 GPU #5: set -etha as 0 (ETH algo for fast cards)
08:40:58:831 6e0 ETH - connecting to 10.0.0.2:8545
08:40:58:831 6e0 http send request: {"method": "eth_getWork", "params": [], "id":0}
08:40:58:894 6e0 http got answer: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:40:58:894 6e0 ETH: Connected (10.0.0.2:8545)
08:40:58:894 6e0 parse packet: 91
08:40:58:894 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:40:58:894 6e0 new buf size: 0
08:40:58:941 a38 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
08:40:58:941 a38 ETH: HTTP SOLO mode
08:40:58:941 a38 Ethereum HTTP requests time (-etht) is set to 200 ms
08:40:58:941 a38 Watchdog enabled
08:40:58:941 a38 Remote management is enabled on port 3333
08:40:58:941 a38
08:40:59:144 6e0 parse packet: 91
08:40:59:144 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:40:59:144 6e0 new buf size: 0
08:40:59:425 6e0 parse packet: 91
08:40:59:425 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:40:59:425 6e0 new buf size: 0
08:40:59:706 6e0 parse packet: 91
08:40:59:706 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:40:59:706 6e0 new buf size: 0
08:40:59:988 6e0 parse packet: 91
08:40:59:988 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:40:59:988 6e0 new buf size: 0
08:41:00:269 6e0 parse packet: 91
08:41:00:269 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:00:269 6e0 new buf size: 0
08:41:00:550 6e0 parse packet: 91
08:41:00:550 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:00:550 6e0 new buf size: 0
08:41:00:816 6e0 parse packet: 91
08:41:00:816 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:00:816 6e0 new buf size: 0
08:41:01:081 6e0 parse packet: 91
08:41:01:081 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:01:081 6e0 new buf size: 0
08:41:01:363 6e0 parse packet: 91
08:41:01:363 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:01:363 6e0 new buf size: 0
08:41:01:644 6e0 parse packet: 91
08:41:01:644 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:01:644 6e0 new buf size: 0
08:41:01:925 6e0 parse packet: 91
08:41:01:925 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:01:925 6e0 new buf size: 0
08:41:02:207 6e0 parse packet: 91
08:41:02:207 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:02:207 6e0 new buf size: 0
08:41:02:472 6e0 parse packet: 91
08:41:02:472 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:02:472 6e0 new buf size: 0
08:41:02:753 6e0 parse packet: 91
08:41:02:753 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:02:753 6e0 new buf size: 0
08:41:03:035 6e0 parse packet: 91
08:41:03:035 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:03:035 6e0 new buf size: 0
08:41:03:300 6e0 parse packet: 91
08:41:03:300 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:03:300 6e0 new buf size: 0
08:41:03:566 6e0 parse packet: 91
08:41:03:566 6e0 ETH: Received error: {"jsonrpc":"2.0","error":{"code":-32600,"message":"Invalid request","data":null},"id":null}
08:41:03:566 6e0 new buf size: 0
08:41:03:691 fc recv: 51
08:41:03:691 fc srv pck: 50
08:41:03:753 fc srv bs: 0
08:41:03:753 fc sent: 169
0.9.41-genoil-1.1.6 work whis no error whis same config
http://fs153.www.ex.ua/get/561775416582/264036490/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA.PNG
August 09, 2016, 10:41:54 PM
@Claymore
a little bug or feature?
I got 6 gpu farm, gpu0-gpu2 are old cards, gpu3-gpu5 are rx480 which don't tell fans and temps data. When I run two miners at once with -di 012 (miner1) and -di 345 (miner2), I see temps and fans of gpu0,1,2 in both miner1 and miner2 windows and miner manager. It's better to see nothing in miner2 window I think?
a little bug or feature?
I got 6 gpu farm, gpu0-gpu2 are old cards, gpu3-gpu5 are rx480 which don't tell fans and temps data. When I run two miners at once with -di 012 (miner1) and -di 345 (miner2), I see temps and fans of gpu0,1,2 in both miner1 and miner2 windows and miner manager. It's better to see nothing in miner2 window I think?
August 09, 2016, 08:37:18 PM
Great miner! I see in the 1st page description of the miner that if you dual mine ETH and Decred there's no loss of ETH hashing when mining. Is there however a loss of Decred hashing when dual mining?
August 09, 2016, 06:09:05 PM
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
i run ubuntu 15.10 desktop x64 with 15.12 driver. 1x390 1x380. very stable.
had one card in when i installed it, then added the other.
August 09, 2016, 05:58:49 PM
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 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 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
August 09, 2016, 04:25:21 PM
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 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 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
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
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
August 09, 2016, 04:08:11 PM
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 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 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
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
August 09, 2016, 03:55:02 PM
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 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 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
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
August 09, 2016, 03:45:58 PM
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 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 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
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
August 09, 2016, 03:27:49 PM
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
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 ))
August 09, 2016, 03:13:22 PM
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 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 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.
August 09, 2016, 03:07:13 PM
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 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 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
August 09, 2016, 03:04:00 PM
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 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 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?
August 09, 2016, 02:40:23 PM
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
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.
August 09, 2016, 02:03:17 PM
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
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
August 09, 2016, 01:29:18 PM
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 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 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?
August 09, 2016, 01:06:32 PM
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 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 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.
August 09, 2016, 10:46:07 AM
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!
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!
Jump to: