Bitcoin Forum
June 21, 2024, 02:56:25 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) on: October 27, 2019, 02:58:02 PM
Today i waked up to my nvidia rig fo 1050ti 4gb telleing me CUDA error 11 can allocate buffer.
Same problem. woke up, 2 farms with 1050ti 4gb are down.

claymore 15.0
win10 32gb virtual memory (was 16) but increase not helped


Also me. I have four 1050 Ti cards in my farm and as of this morning the stopped working (after the #294 DAG apparently) with following errors:

"CUDA error - cannot allocate big buffer for DAG. check readme.txt for possible solutions."
"GPU X failed"
"GPU X, CUDA error 11 - cannot write buffer for DAG"

Reinstalling the drive did not helped.
Win10 64bit. 4GB RAM. 32GB Virtual Ram. Claymore v15.0
Please advice, Thank you.
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.0 (Windows/Linux) on: February 19, 2018, 07:58:49 PM
Hi,
Can anyone help me please and give me some info on this error:

NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.
NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.
NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.
NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.

There are 4 1050 cards, and 2 1060 cards on the miner. Latest NVIDIA driver which for both cards is the same. MB: ASUS Z170-A ( I know a piece of crap!). PSU: 1050W Green. Win10 X64. MSI Afterburner for OC. 80 power limit, CC:+100. MC: +700. Runs at about 50 degree.

I've got lots of miners running stable. But this one works for about 3 days, then the 1060 cards fail, miner restarts, and the 2 1060 cards are gone. When it happens, the 1060 cards look fine physically, and both are fine in Device Manager, but in Afterburner, both cards are frozen without being able to do anything on them. And they are no giving any Hash either obviously. System need to be restarted for them to get fixed.

I'm hosting the system for a third party, the hardware is theirs, but I clean installed the OS, and did everything by the book. Only software issue that I can think of is, that after installing the OS and trying to run it for the first time, Claymore wouldn't start at all which was related to the OpenCL.dll file which for some reason was missing from sys32. I copied the .dll file from an identical system and put it in the miner's sys32 file.

The whole Claymore's log from when the issue seems to start:

18:41:37:870   cc4   ETH - Total Speed: 99.571 Mh/s, Total Shares: 1173, Rejected: 0, Time: 34:22
18:41:37:870   cc4   ETH: GPU0 13.016 Mh/s, GPU1 12.974 Mh/s, GPU2 13.037 Mh/s, GPU3 13.019 Mh/s, GPU4 23.765 Mh/s, GPU5 23.760 Mh/s
18:41:38:355   1738   srv_thr cnt: 1, IP: 192.168.XX.XX


WTF?  Angry
I know, right? How could people copy that huge wall of text?

A) Devil is in the details. I'm running over 25 miners with 6-8 GPUs each almost all alone by myself. Build from scratch. many different models. RX. R9. GTX, ... And I had no exp in these stuff 9 months ago. I managed to do all of this, get a perfectly stable system with little to none problems, only by paying a great deal of attention to details. So I do the courtesy to others who may want to help me, by giving them "the option" to see and read the details.

B) If you get off your high horse, you'll see that I put the important parts short and sweet in the beginning. Giving the line of error which I think is the main thing. System spec. And few lines on what's up. THEN. Only then, I wrote "the whole log file from which the problem starts". So the post is not in anyway or from defined by the log file. You can simply ignore it. You don't need to quote it. And it will take 2 sec to scroll past it.

So if you don't have anything to say, stop talking. It's not Facebook or twitter, or text messages with your bff. It's a  forum. You can expect time to time a lengthy post. And as long as it's not messy, it's perfectly fine.
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.0 (Windows/Linux) on: February 19, 2018, 08:12:52 AM
Hi,
Can anyone help me please and give me some info on this error:


18:42:06:498   12d8   GPU 4, GpuMiner kx failed 1
18:42:06:514   12d8   Set global fail flag, failed GPU4
18:42:06:404   11c8   Set global fail flag, failed GPU0
18:42:06:404   177c   Set global fail flag, failed GPU1
18:42:06:404   f0c   Set global fail flag, failed GPU2
18:42:06:654   f0c   GPU 2 failed
18:42:06:733   11c8   GPU 0 failed
18:42:06:811   12d8   GPU 4 failed
18:42:06:858   17fc   GPU 5, GpuMiner kx failed 1
18:42:06:858   17fc   Set global fail flag, failed GPU5
18:42:06:905   177c   GPU 1 failed
18:42:06:951   1390   GPU 3 failed
18:42:06:983   17fc   GPU 5 failed
18:42:08:655   498   srv_thr cnt: 1, 192.168.XX.XX
18:42:08:670   498   recv: 51
18:42:08:670   498   srv pck: 50
18:42:08:670   498   NVML: cannot get current temperature, error 15
18:42:08:670   498   NVML: cannot get fan speed, error 15
18:42:08:670   498   NVML: cannot get current temperature, error 15
18:42:08:670   498   NVML: cannot get fan speed, error 15
18:42:08:670   498   srv bs: 0
18:42:08:670   498   sent: 196
18:42:09:514   1070   NVML: cannot get current temperature, error 15
18:42:09:514   1070   NVML: cannot get fan speed, error 15
18:42:09:514   1070   NVML: cannot get current temperature, error 15
18:42:09:514   1070   NVML: cannot get fan speed, error 15
18:42:12:530   1070   NVML: cannot get current temperature, error 15
18:42:12:530   1070   NVML: cannot get fan speed, error 15
18:42:12:530   1070   NVML: cannot get current temperature, error 15
18:42:12:530   1070   NVML: cannot get fan speed, error 15
18:42:13:718   1094   srv_thr cnt: 1, 192.168.XX.XX
18:42:13:718   1094   recv: 51
18:42:13:718   1094   srv pck: 50
18:42:13:718   1094   NVML: cannot get current temperature, error 15
18:42:13:718   1094   NVML: cannot get fan speed, error 15
18:42:13:718   1094   NVML: cannot get current temperature, error 15
18:42:13:718   1094   NVML: cannot get fan speed, error 15
18:42:13:718   1094   srv bs: 0
18:42:13:718   1094   sent: 196


I had the same issue and did the following things

a) shutdown everything and make sure no loss riser, means GPU are fully fitted into the riser and not loss and all the cables are fully in.

b) if you are overclocking GPUs, reduce OC by a bit, may be 10 each (core and memory) and see if the things improve.




I did lowered the OC but it's the same and even worse. First time it ran for 3 days and failed. Then 1 day and fail again. And now 6 hours of the third fail which made me to ask here, it has failed again. I did checked the risers. But it's looks good. And what are the chances that 2 risers be loose like that?
Right now I'm clean Uninstalling the NVIDIA driver and reinstalling it to see if the problem goes away. My next step is PSU. Since both cards are getting power from same 700W PSU and nothing else is connected to that PSU. (P.S. I said PSU is 1050W. I made a mistake that's another miner. On this rig, there are two 700W PSUs. 1 for MB and 4 1050 cards. And 1 for two 1060 cards which are failing)
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.0 (Windows/Linux) on: February 19, 2018, 03:59:21 AM
Hi,
Can anyone help me please and give me some info on this error:

NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.
NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.
NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.
NVML API: failed to get device handle 4, error 15.
NVML API: failed to get device handle 5, error 15.

There are 4 1050 cards, and 2 1060 cards on the miner. Latest NVIDIA driver which for both cards is the same. MB: ASUS Z170-A ( I know a piece of crap!). PSU: Two 700W PSUs. One fore MB and 4x 1050 cards. One for 2x 1060 cards (P.S. Oroginally I wrote that there is a 1050W PSU. I mixed it up with another miner. My apologies) . OS: Win10 X64. MSI Afterburner for OC. 80 power limit, CC:+100. MC: +700. Runs at about 50 degree.

I've got lots of miners running stable. But this one works for about 3 days, then the 1060 cards fail, miner restarts, and the 2 1060 cards are gone. When it happens, the 1060 cards look fine physically, and both are fine in Device Manager, but in Afterburner, both cards are frozen without being able to do anything on them. And they are no giving any Hash either obviously. System need to be restarted for them to get fixed.

I'm hosting the system for a third party, the hardware is theirs, but I clean installed the OS, and did everything by the book. Only software issue that I can think of is, that after installing the OS and trying to run it for the first time, Claymore wouldn't start at all which was related to the OpenCL.dll file which for some reason was missing from sys32. I copied the .dll file from an identical system and put it in the miner's sys32 file.

The whole Claymore's log from when the issue seems to start:

18:41:37:870   cc4   ETH - Total Speed: 99.571 Mh/s, Total Shares: 1173, Rejected: 0, Time: 34:22
18:41:37:870   cc4   ETH: GPU0 13.016 Mh/s, GPU1 12.974 Mh/s, GPU2 13.037 Mh/s, GPU3 13.019 Mh/s, GPU4 23.765 Mh/s, GPU5 23.760 Mh/s
18:41:38:355   1738   srv_thr cnt: 1, IP: 192.168.XX.XX
18:41:38:355   1738   recv: 51
18:41:38:355   1738   srv pck: 50
18:41:38:386   1738   srv bs: 0
18:41:38:386   1738   sent: 228
18:41:43:418   b18   srv_thr cnt: 1, IP: 192.168.XX.XX
18:41:43:418   b18   recv: 51
18:41:43:418   b18   srv pck: 50
18:41:43:418   b18   srv bs: 0
18:41:43:418   b18   sent: 228
18:41:43:715   cc4   ETH: checking pool connection...
18:41:43:715   cc4   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:41:43:871   cc4   got 243 bytes
18:41:43:871   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0x281924bac5eb3db7dc8ae3ec8e5d53a2b427e4d1a97082e1d721e2eb47535c16","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:41:43:871   cc4   parse packet: 242
18:41:43:871   cc4   ETH: job is the same
18:41:43:871   cc4   new buf size: 0
18:41:48:465   1338   srv_thr cnt: 1, 192.168.XX.XX
18:41:48:465   1338   recv: 51
18:41:48:465   1338   srv pck: 50
18:41:48:465   1338   srv bs: 0
18:41:48:465   1338   sent: 228
18:41:53:512   260   srv_thr cnt: 1, IP: 192.168.XX.XX
18:41:53:512   260   recv: 51
18:41:53:512   260   srv pck: 50
18:41:53:512   260   srv bs: 0
18:41:53:512   260   sent: 228
18:41:53:731   cc4   ETH: checking pool connection...
18:41:53:731   cc4   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:41:53:888   cc4   got 243 bytes
18:41:53:888   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0x281924bac5eb3db7dc8ae3ec8e5d53a2b427e4d1a97082e1d721e2eb47535c16","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:41:53:888   cc4   parse packet: 242
18:41:53:888   cc4   ETH: job is the same
18:41:53:888   cc4   new buf size: 0
18:41:55:216   cc4   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x5f0ad9b", "0x000000000000000000000000000000000000000000000000000000003835314d"]}

18:41:57:044   1070   GPU0 t=52C fan=46%, GPU1 t=52C fan=46%, GPU2 t=50C fan=45%, GPU3 t=52C fan=50%, GPU4 t=41C fan=22%, GPU5 t=48C fan=38%
18:41:58:560   b44   srv_thr cnt: 1, 192.168.XX.XX
18:41:58:560   b44   recv: 51
18:41:58:560   b44   srv pck: 50
18:41:58:560   b44   srv bs: 0
18:41:58:560   b44   sent: 228
18:41:58:904   18f4   em hbt: 15, fm hbt: 109,
18:41:58:904   18f4   watchdog - thread 0 (gpu0), hb time 140
18:41:58:904   18f4   watchdog - thread 1 (gpu0), hb time 15
18:41:58:904   18f4   watchdog - thread 2 (gpu1), hb time 15
18:41:58:904   18f4   watchdog - thread 3 (gpu1), hb time 140
18:41:58:904   18f4   watchdog - thread 4 (gpu2), hb time 47
18:41:58:904   18f4   watchdog - thread 5 (gpu2), hb time 156
18:41:58:904   18f4   watchdog - thread 6 (gpu3), hb time 93
18:41:58:904   18f4   watchdog - thread 7 (gpu3), hb time 203
18:41:58:904   18f4   watchdog - thread 8 (gpu4), hb time 156
18:41:58:904   18f4   watchdog - thread 9 (gpu4), hb time 31
18:41:58:904   18f4   watchdog - thread 10 (gpu5), hb time 31
18:41:58:904   18f4   watchdog - thread 11 (gpu5), hb time 140
18:42:00:591   cc4   got 243 bytes
18:42:00:591   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0xa23a079378889763907051a78499d9f150a6a0a12fd8d935b1620f7db6792159","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:00:591   cc4   parse packet: 242
18:42:00:591   cc4   ETH: job changed
18:42:00:591   cc4   new buf size: 0
18:42:00:591   cc4   ETH: 02/18/18-18:42:00 - New job from eth-eu1.nanopool.org:9999
18:42:00:591   cc4   target: 0x000000006df37f67 (diff: 10000MH), epoch 170(2.33GB)
18:42:00:591   cc4   ETH - Total Speed: 99.597 Mh/s, Total Shares: 1173, Rejected: 0, Time: 34:22
18:42:00:591   cc4   ETH: GPU0 12.936 Mh/s, GPU1 13.038 Mh/s, GPU2 13.033 Mh/s, GPU3 13.032 Mh/s, GPU4 23.778 Mh/s, GPU5 23.780 Mh/s
18:42:05:514   cc4   ETH: checking pool connection...
18:42:05:514   cc4   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:42:05:529   cac   srv_thr cnt: 1, 192.168.XXX.XXX
18:42:05:529   cac   recv: 51
18:42:05:529   cac   srv pck: 50
18:42:05:701   cac   NVML: cannot get current temperature, error 15
18:42:05:686   cc4   got 243 bytes
18:42:05:748   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0xa23a079378889763907051a78499d9f150a6a0a12fd8d935b1620f7db6792159","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:05:748   cc4   parse packet: 242
18:42:05:748   cc4   ETH: job is the same
18:42:05:748   cc4   new buf size: 0
18:42:05:764   f34   GPU 2, GpuMiner cu_k1 failed 30, unknown error
18:42:05:779   188   GPU 5, GpuMiner cu_k1 failed 30, unknown error
18:42:05:779   127c   GPU 3, GpuMiner cu_k1 failed 30, unknown error
18:42:05:779   134   GPU 0, GpuMiner cu_k1 failed 30, unknown error
18:42:05:779   e5c   GPU 1, GpuMiner cu_k1 failed 30, unknown error
18:42:05:779   f34   GPU 2, GpuMiner kx failed 1
18:42:05:779   188   GPU 5, GpuMiner kx failed 1
18:42:05:779   127c   GPU 3, GpuMiner kx failed 1
18:42:05:779   134   GPU 0, GpuMiner kx failed 1
18:42:06:123   e5c   GPU 1, GpuMiner kx failed 1
18:42:06:123   e5c   Set global fail flag, failed GPU1
18:42:06:123   e5c   GPU 1 failed
18:42:06:123   cac   NVML: cannot get fan speed, error 15
18:42:05:779   127c   Set global fail flag, failed GPU3
18:42:06:123   127c   GPU 3 failed
18:42:05:779   f34   Set global fail flag, failed GPU2
18:42:06:123   f34   GPU 2 failed
18:42:06:123   e40   GPU 4, GpuMiner cu_k1 failed 30, unknown error
18:42:06:123   e40   GPU 4, GpuMiner kx failed 1
18:42:06:139   cac   NVML: cannot get current temperature, error 15
18:42:05:779   188   Set global fail flag, failed GPU5
18:42:06:170   1390   GPU 3, GpuMiner cu_k1 failed 30, unknown error
18:42:06:123   134   Set global fail flag, failed GPU0
18:42:06:186   134   GPU 0 failed
18:42:06:201   188   GPU 5 failed
18:42:06:217   1390   GPU 3, GpuMiner kx failed 1
18:42:06:248   f0c   GPU 2, GpuMiner cu_k1 failed 30, unknown error
18:42:06:358   177c   GPU 1, GpuMiner cu_k1 failed 30, unknown error
18:42:06:139   e40   Set global fail flag, failed GPU4
18:42:06:404   11c8   GPU 0, GpuMiner cu_k1 failed 30, unknown error
18:42:06:404   11c8   GPU 0, GpuMiner kx failed 1
18:42:06:404   177c   GPU 1, GpuMiner kx failed 1
18:42:06:404   f0c   GPU 2, GpuMiner kx failed 1
18:42:06:248   1390   Set global fail flag, failed GPU3
18:42:06:404   17fc   GPU 5, GpuMiner cu_k1 failed 30, unknown error
18:42:06:404   cac   NVML: cannot get fan speed, error 15
18:42:06:451   12d8   GPU 4, GpuMiner cu_k1 failed 30, unknown error
18:42:06:451   e40   GPU 4 failed
18:42:06:451   cac   srv bs: 0
18:42:06:467   cac   sent: 220
18:42:06:483   1070   NVML: cannot get current temperature, error 15
18:42:06:483   1070   NVML: cannot get fan speed, error 15
18:42:06:498   1070   NVML: cannot get current temperature, error 15
18:42:06:498   1070   NVML: cannot get fan speed, error 15
18:42:06:498   12d8   GPU 4, GpuMiner kx failed 1
18:42:06:514   12d8   Set global fail flag, failed GPU4
18:42:06:404   11c8   Set global fail flag, failed GPU0
18:42:06:404   177c   Set global fail flag, failed GPU1
18:42:06:404   f0c   Set global fail flag, failed GPU2
18:42:06:654   f0c   GPU 2 failed
18:42:06:733   11c8   GPU 0 failed
18:42:06:811   12d8   GPU 4 failed
18:42:06:858   17fc   GPU 5, GpuMiner kx failed 1
18:42:06:858   17fc   Set global fail flag, failed GPU5
18:42:06:905   177c   GPU 1 failed
18:42:06:951   1390   GPU 3 failed
18:42:06:983   17fc   GPU 5 failed
18:42:08:655   498   srv_thr cnt: 1, 192.168.XX.XX
18:42:08:670   498   recv: 51
18:42:08:670   498   srv pck: 50
18:42:08:670   498   NVML: cannot get current temperature, error 15
18:42:08:670   498   NVML: cannot get fan speed, error 15
18:42:08:670   498   NVML: cannot get current temperature, error 15
18:42:08:670   498   NVML: cannot get fan speed, error 15
18:42:08:670   498   srv bs: 0
18:42:08:670   498   sent: 196
18:42:09:514   1070   NVML: cannot get current temperature, error 15
18:42:09:514   1070   NVML: cannot get fan speed, error 15
18:42:09:514   1070   NVML: cannot get current temperature, error 15
18:42:09:514   1070   NVML: cannot get fan speed, error 15
18:42:12:530   1070   NVML: cannot get current temperature, error 15
18:42:12:530   1070   NVML: cannot get fan speed, error 15
18:42:12:530   1070   NVML: cannot get current temperature, error 15
18:42:12:530   1070   NVML: cannot get fan speed, error 15
18:42:13:718   1094   srv_thr cnt: 1, 192.168.XX.XX
18:42:13:718   1094   recv: 51
18:42:13:718   1094   srv pck: 50
18:42:13:718   1094   NVML: cannot get current temperature, error 15
18:42:13:718   1094   NVML: cannot get fan speed, error 15
18:42:13:718   1094   NVML: cannot get current temperature, error 15
18:42:13:718   1094   NVML: cannot get fan speed, error 15
18:42:13:718   1094   srv bs: 0
18:42:13:718   1094   sent: 196
18:42:15:077   cc4   got 243 bytes
18:42:15:077   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0x630ddc19229b1c3ff095b3c657a3b8d4ceae04cabbf2548f6d9611dfad8a5209","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:15:077   cc4   parse packet: 242
18:42:15:077   cc4   ETH: job changed
18:42:15:077   cc4   new buf size: 0
18:42:15:077   cc4   ETH: 02/18/18-18:42:15 - New job from eth-eu1.nanopool.org:9999
18:42:15:077   cc4   target: 0x000000006df37f67 (diff: 10000MH), epoch 170(2.33GB)
18:42:15:077   cc4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 1173, Rejected: 0, Time: 34:22
18:42:15:077   cc4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
18:42:15:234   cc4   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000003835314d"]}

18:42:15:530   cc4   ETH: checking pool connection...
18:42:15:530   cc4   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:42:15:546   1070   NVML: cannot get current temperature, error 15
18:42:15:546   1070   NVML: cannot get fan speed, error 15
18:42:15:546   1070   NVML: cannot get current temperature, error 15
18:42:15:546   1070   NVML: cannot get fan speed, error 15
18:42:15:702   cc4   got 243 bytes
18:42:15:702   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0x630ddc19229b1c3ff095b3c657a3b8d4ceae04cabbf2548f6d9611dfad8a5209","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:15:702   cc4   parse packet: 242
18:42:15:702   cc4   ETH: job is the same
18:42:15:702   cc4   new buf size: 0
18:42:18:562   1070   NVML: cannot get current temperature, error 15
18:42:18:562   1070   NVML: cannot get fan speed, error 15
18:42:18:562   1070   NVML: cannot get current temperature, error 15
18:42:18:562   1070   NVML: cannot get fan speed, error 15
18:42:18:765   f58   srv_thr cnt: 1, 192.168.XX.XX
18:42:18:765   f58   recv: 51
18:42:18:765   f58   srv pck: 50
18:42:18:765   f58   NVML: cannot get current temperature, error 15
18:42:18:765   f58   NVML: cannot get fan speed, error 15
18:42:18:765   f58   NVML: cannot get current temperature, error 15
18:42:18:765   f58   NVML: cannot get fan speed, error 15
18:42:18:765   f58   srv bs: 0
18:42:18:765   f58   sent: 196
18:42:21:578   1070   NVML: cannot get current temperature, error 15
18:42:21:578   1070   NVML: cannot get fan speed, error 15
18:42:21:578   1070   NVML: cannot get current temperature, error 15
18:42:21:578   1070   NVML: cannot get fan speed, error 15
18:42:23:141   cc4   got 243 bytes
18:42:23:141   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0x64ee3f3e4661af1c08a9d78d8d4c3f4af860ef089324ff294a9e2b836f087f9b","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:23:141   cc4   parse packet: 242
18:42:23:141   cc4   ETH: job changed
18:42:23:141   cc4   new buf size: 0
18:42:23:141   cc4   ETH: 02/18/18-18:42:23 - New job from eth-eu1.nanopool.org:9999
18:42:23:141   cc4   target: 0x000000006df37f67 (diff: 10000MH), epoch 170(2.33GB)
18:42:23:141   cc4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 1173, Rejected: 0, Time: 34:22
18:42:23:141   cc4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
18:42:23:813   1974   srv_thr cnt: 1, IP: 192.168.XX.XX
18:42:23:813   1974   recv: 51
18:42:23:813   1974   srv pck: 50
18:42:23:813   1974   NVML: cannot get current temperature, error 15
18:42:23:813   1974   NVML: cannot get fan speed, error 15
18:42:23:813   1974   NVML: cannot get current temperature, error 15
18:42:23:813   1974   NVML: cannot get fan speed, error 15
18:42:23:813   1974   srv bs: 0
18:42:23:813   1974   sent: 196
18:42:24:594   1070   NVML: cannot get current temperature, error 15
18:42:24:594   1070   NVML: cannot get fan speed, error 15
18:42:24:594   1070   NVML: cannot get current temperature, error 15
18:42:24:594   1070   NVML: cannot get fan speed, error 15
18:42:25:547   cc4   ETH: checking pool connection...
18:42:25:547   cc4   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:42:25:703   cc4   got 243 bytes
18:42:25:703   cc4   buf: {"jsonrpc":"2.0","id":0,"result":["0x64ee3f3e4661af1c08a9d78d8d4c3f4af860ef089324ff294a9e2b836f087f9b","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:25:703   cc4   parse packet: 242
18:42:25:703   cc4   ETH: job is the same
18:42:25:703   cc4   new buf size: 0
18:42:27:610   1070   NVML: cannot get current temperature, error 15
18:42:27:610   1070   NVML: cannot get fan speed, error 15
18:42:27:610   1070   NVML: cannot get current temperature, error 15
18:42:27:610   1070   NVML: cannot get fan speed, error 15
18:42:27:610   1070   NVML: cannot get current temperature, error 15
18:42:27:610   1070   NVML: cannot get fan speed, error 15
18:42:27:610   1070   NVML: cannot get current temperature, error 15
18:42:27:610   1070   NVML: cannot get fan speed, error 15
18:42:27:610   1070   GPU0 t=36C fan=45%, GPU1 t=35C fan=45%, GPU2 t=34C fan=45%, GPU3 t=35C fan=45%, GPU4 t=0C fan=0%, GPU5 t=0C fan=0%
18:42:28:860   478   srv_thr cnt: 1, 192.168.XX.XX
18:42:28:860   478   recv: 51
18:42:28:860   478   srv pck: 50
18:42:28:860   478   NVML: cannot get current temperature, error 15
18:42:28:860   478   NVML: cannot get fan speed, error 15
18:42:28:860   478   NVML: cannot get current temperature, error 15
18:42:28:860   478   NVML: cannot get fan speed, error 15
18:42:28:860   478   srv bs: 0
18:42:28:860   478   sent: 196
18:42:30:626   1070   NVML: cannot get current temperature, error 15
18:42:30:626   1070   NVML: cannot get fan speed, error 15
18:42:30:626   1070   NVML: cannot get current temperature, error 15
18:42:30:626   1070   NVML: cannot get fan speed, error 15
18:42:33:642   1070   NVML: cannot get current temperature, error 15
18:42:33:642   1070   NVML: cannot get fan speed, error 15
18:42:33:642   1070   NVML: cannot get current temperature, error 15
18:42:33:642   1070   NVML: cannot get fan speed, error 15
18:42:33:845   18f4   em hbt: 16, fm hbt: 47,
18:42:33:845   18f4   watchdog - thread 0 (gpu0), hb time 28203
18:42:33:845   18f4   watchdog - thread 1 (gpu0), hb time 29438
18:42:33:845   18f4   watchdog - thread 2 (gpu1), hb time 28188
18:42:33:845   18f4   watchdog - thread 3 (gpu1), hb time 28313
18:42:33:845   18f4   watchdog - thread 4 (gpu2), hb time 28219
18:42:33:845   18f4   watchdog - thread 5 (gpu2), hb time 28344
18:42:33:845   18f4   watchdog - thread 6 (gpu3), hb time 28328
18:42:33:845   18f4   watchdog - thread 7 (gpu3), hb time 28203
18:42:33:845   18f4   watchdog - thread 8 (gpu4), hb time 30672
18:42:33:845   18f4   watchdog - thread 9 (gpu4), hb time 30781
18:42:33:845   18f4   watchdog - thread 10 (gpu5), hb time 30766
18:42:33:845   18f4   watchdog - thread 11 (gpu5), hb time 30656
18:42:33:845   18f4   WATCHDOG: GPU error, you need to restart miner Sad
18:42:33:845   18f4   NVML: cannot get current temperature, error 15
18:42:33:845   18f4   NVML: cannot get fan speed, error 15
18:42:33:845   18f4   NVML: cannot get current temperature, error 15
18:42:33:845   18f4   NVML: cannot get fan speed, error 15
18:42:35:079   18f4   Restarting OK, exit...



8:42:37:650   600   Check and remove old log files...
18:42:37:650   600   args: -epool eth-eu1.nanopool.org:9999 -ewal
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -mode 1 -ftime 10
18:42:37:650   600   
18:42:37:650   600   ΙΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝ»
18:42:37:650   600   Ί                Claymore's Dual GPU Miner - v11.0               Ί
18:42:37:650   600   Ί              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             Ί
18:42:37:650   600   ΘΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΝΌ
18:42:37:650   600   
18:42:37:665   600   b501
18:42:37:884   600   ETH: 6 pools are specified
18:42:37:884   600   Main Ethereum pool is eth-eu1.nanopool.org:9999
18:42:38:353   600   OpenCL platform: NVIDIA CUDA
18:42:38:353   600   AMD OpenCL platform not found
18:42:38:822   600   CUDA initializing...

18:42:38:822   600   NVIDIA Cards available: 4
18:42:38:822   600   CUDA Driver Version/Runtime Version: 9.1/8.0
18:42:38:837   600   GPU #0: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1  (pci bus 1:0:0)

18:42:38:837   600   GPU #1: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1  (pci bus 2:0:0)

18:42:38:837   600   GPU #2: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1  (pci bus 3:0:0)

18:42:38:837   600   GPU #3: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1  (pci bus 7:0:0)

18:42:38:837   600   Total cards: 4
18:42:42:916   600   No AMD cards in the list, ADL library will not be used.
18:42:42:916   600   NVML version: 9.390.77
18:42:42:978   600   NVML API: failed to get device handle 4, error 15.
18:42:42:978   600   NVML API: failed to get device handle 5, error 15.
18:42:42:978   600   NVML API: failed to get device handle 4, error 15.
18:42:42:978   600   NVML API: failed to get device handle 5, error 15.
18:42:42:978   600   NVML API: failed to get device handle 4, error 15.
18:42:42:978   600   NVML API: failed to get device handle 5, error 15.
18:42:42:978   600   NVML API: failed to get device handle 4, error 15.
18:42:42:978   600   NVML API: failed to get device handle 5, error 15.
18:42:43:474   1064   ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <213.32.29.168> port 9999
18:42:43:583   600   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

18:42:43:583   600   ETH: eth-proxy stratum mode
18:42:43:583   600   Watchdog enabled
18:42:43:583   600   Remote management (READ-ONLY MODE) is enabled on port 3333
18:42:43:583   600   

18:42:43:630   1064   send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"], "id": 2, "method": "eth_submitLogin"}

18:42:43:630   1064   ETH: Stratum - Connected (eth-eu1.nanopool.org:9999)
18:42:43:818   1064   got 282 bytes
18:42:43:818   1064   buf: {"jsonrpc":"2.0","id":2,"result":true}
{"jsonrpc":"2.0","id":0,"result":["0x2923145ddbff2d14d72a0f314075ddde33289e1c7acbb8cfc9acd22741d7a17e","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:43:818   1064   parse packet: 38
18:42:43:818   1064   ETH: Authorized
18:42:43:818   1064   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:42:43:818   1064   remove first packet 243
18:42:43:818   1064   new buf size: 243
18:42:43:818   1064   parse packet: 242
18:42:43:818   1064   ETH: job changed
18:42:43:818   1064   new buf size: 0
18:42:43:849   1a50   Setting DAG epoch #170...
18:42:43:990   1064   got 243 bytes
18:42:43:990   1064   buf: {"jsonrpc":"2.0","id":0,"result":["0x2923145ddbff2d14d72a0f314075ddde33289e1c7acbb8cfc9acd22741d7a17e","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:43:990   1064   parse packet: 242
18:42:43:990   1064   ETH: job is the same
18:42:43:990   1064   new buf size: 0
18:42:46:037   50c   Setting DAG epoch #170 for GPU1
18:42:46:037   1a50   Setting DAG epoch #170 for GPU3
18:42:46:037   1a50   Create GPU buffer for GPU3
18:42:46:037   a14   Setting DAG epoch #170 for GPU2
18:42:46:037   58c   Setting DAG epoch #170 for GPU0
18:42:46:037   a14   Create GPU buffer for GPU2
18:42:46:037   50c   Create GPU buffer for GPU1
18:42:46:037   58c   Create GPU buffer for GPU0
18:42:47:928   384   srv_thr cnt: 1, IP: 192.168.XXX.XXX
18:42:47:943   384   recv: 51
18:42:47:943   384   srv pck: 50
18:42:47:943   384   srv bs: 0
18:42:47:943   384   sent: 170
18:42:48:990   10e0   srv_thr cnt: 1, IP: 192.168.XXX.XXX
18:42:48:990   10e0   recv: 51
18:42:48:990   10e0   srv pck: 50
18:42:48:990   10e0   srv bs: 0
18:42:49:006   10e0   sent: 170
18:42:53:835   1064   ETH: checking pool connection...
18:42:53:835   1064   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:42:53:991   1064   got 243 bytes
18:42:53:991   1064   buf: {"jsonrpc":"2.0","id":0,"result":["0x2923145ddbff2d14d72a0f314075ddde33289e1c7acbb8cfc9acd22741d7a17e","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:42:53:991   1064   parse packet: 242
18:42:53:991   1064   ETH: job is the same
18:42:53:991   1064   new buf size: 0
18:42:54:038   13f8   srv_thr cnt: 1, IP: 192.168.XXX.XXX
18:42:54:038   13f8   recv: 51
18:42:54:038   13f8   srv pck: 50
18:42:54:038   13f8   srv bs: 0
18:42:54:038   13f8   sent: 170
18:42:59:069   7d4   srv_thr cnt: 1, IP: 192.168.XXX.XXX
18:42:59:069   7d4   recv: 51
18:42:59:069   7d4   srv pck: 50
18:42:59:069   7d4   srv bs: 0
18:42:59:069   7d4   sent: 170
18:43:00:195   50c   GPU1 DAG creation time - 13928 ms
18:43:00:195   50c   Setting DAG epoch #170 for GPU1 done
18:43:00:398   58c   GPU0 DAG creation time - 14032 ms
18:43:00:398   58c   Setting DAG epoch #170 for GPU0 done
18:43:00:445   1a50   GPU3 DAG creation time - 14003 ms
18:43:00:445   1a50   Setting DAG epoch #170 for GPU3 done
18:43:00:445   a14   GPU2 DAG creation time - 14037 ms
18:43:00:445   a14   Setting DAG epoch #170 for GPU2 done
18:43:03:632   1064   got 243 bytes
18:43:03:632   1064   buf: {"jsonrpc":"2.0","id":0,"result":["0xc998a3e3ccf78c4d8558bdc2848fbb02f6e884711540eb791981ef2d8e0a2a6f","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:43:03:632   1064   parse packet: 242
18:43:03:632   1064   ETH: job changed
18:43:03:632   1064   new buf size: 0
18:43:03:632   1064   ETH: 02/18/18-18:43:03 - New job from eth-eu1.nanopool.org:9999
18:43:03:632   1064   target: 0x000000006df37f67 (diff: 10000MH), epoch 170(2.33GB)
18:43:03:632   1064   ETH - Total Speed: 51.898 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
18:43:03:632   1064   ETH: GPU0 12.932 Mh/s, GPU1 12.991 Mh/s, GPU2 12.986 Mh/s, GPU3 12.989 Mh/s
18:43:03:836   1064   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x31884f1", "0x000000000000000000000000000000000000000000000000000000004cddc83f"]}

18:43:03:851   1064   ETH: checking pool connection...
18:43:03:851   1064   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

18:43:04:101   8fc   srv_thr cnt: 1, IP: 192.168.XXX.XXX
18:43:04:101   8fc   recv: 51
18:43:04:101   8fc   srv pck: 50
18:43:04:101   8fc   srv bs: 0
18:43:04:101   8fc   sent: 190
18:43:04:195   1064   got 243 bytes
18:43:04:195   1064   buf: {"jsonrpc":"2.0","id":0,"result":["0xc998a3e3ccf78c4d8558bdc2848fbb02f6e884711540eb791981ef2d8e0a2a6f","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:43:04:195   1064   parse packet: 242
18:43:04:195   1064   ETH: job is the same
18:43:04:195   1064   new buf size: 0
18:43:08:039   bf4   GPU0 t=45C fan=45%, GPU1 t=44C fan=45%, GPU2 t=43C fan=45%, GPU3 t=45C fan=45%
18:43:09:164   136c   srv_thr cnt: 1, IP: 192.168.XXX.XXX
18:43:09:164   136c   recv: 51
18:43:09:164   136c   srv pck: 50
18:43:09:164   136c   srv bs: 0
18:43:09:164   136c   sent: 190
18:43:09:758   1064   got 243 bytes
18:43:09:758   1064   buf: {"jsonrpc":"2.0","id":0,"result":["0xc772cea755b1dd6a9037337e7c38f4c29a47e9ae52e6c509c347cfc2617ca9a0","0x4e99a30e99712c8c6e292fe7ba6b27a37c7ced12e2ec7862f31fb676724cb404","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

18:43:09:758   1064   parse packet: 242
18:43:09:758   1064   ETH: job changed
18:43:09:758   1064   new buf size: 0
18:43:09:758   1064   ETH: 02/18/18-18:43:09 - New job from eth-eu1.nanopool.org:9999
18:43:09:758   1064   target: 0x000000006df37f67 (diff: 10000MH), epoch 170(2.33GB)
18:43:09:758   1064   ETH - Total Speed: 51.955 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
18:43:09:758   1064   ETH: GPU0 12.985 Mh/s, GPU1 12.994 Mh/s, GPU2 12.990 Mh/s, GPU3 12.986 Mh/s

5  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.0 (Windows/Linux) on: September 14, 2017, 08:22:56 AM
Due to the changes AMD made starting with the 17.7.2 drivers, you need to use the latest Afterburner beta build, not the one listed on the main download page. Afterburner 4.4.0 Beta 16 works fine in Windows 10 with the AMD blokchain drivers.

https://forums.guru3d.com/threads/rtss-6-7-0-beta-1.412822/page-32#post-5459908

The next Afterburner build that is released will have a lot of changes.

https://forums.guru3d.com/threads/rtss-6-7-0-beta-1.412822/page-35#post-5471671


THANKS!
I owe you one, mate.
Problem fixed.
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.0 (Windows/Linux) on: September 14, 2017, 06:23:18 AM
Hello people,
I've RX470 cards.
I'm trying to use the AMD blockchain driver to deal with DAG file issue that we are having.
But MSI afterburner does not respond to it and I can't overclock the cards. I've used the afterburner beta and applied the fixes, but still no respond.
Here my steps:
Fully updated win10. I removed the old driver with AMD clean uninstaller > Reboot > Installed the blockchain driver. > Since the I've edited the card's BIOS, I used the driver patcher BEFORE rebooting the system, All options are found, patch done. > Reboot. > And after system comes up, Card is good, but Afterburner Beta still can't overclock it.

I tried to overclock with the Claymore itself, which may I add, is pretty easy and effective, but the problem I get is, that I can only overclock the GPU 0. 6 next cards (I have 7 cards on the rig) won't get the settings. I used the code like this:
" -cclock 1100 -mclock 2050"
or
"-cclock 1100,1100,1100,1100,1100,1100,1100 -mclock 2050,2050,2050,2050,2050,2050,2050" (Or different values)
And no results. I only can overclock GPU0.

I could use some help. I really need to overclock these cards.
With current price and difficulty, I'm starting to get hurt.

I have never gotten Afterburner to work with any of my AMD cards and I spent a LOT of time on the problem. 

It took me a while too. Had so many problems at first.But at last I got the hang of it.
About my current problem, I finally after hours upon hours, I got to open core and memory clock unlocked on the afterburner, but It does NOT work at all. Not only it doesn't apply the changes now, it's even has the cards memory and core at 30Mhz! It even doesn't go up to the default 1250 160 anymore...!
7  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.0 (Windows/Linux) on: September 13, 2017, 07:49:52 PM
Hello people,
I've RX470 cards.
I'm trying to use the AMD blockchain driver to deal with DAG file issue that we are having.
But MSI afterburner does not respond to it and I can't overclock the cards. I've used the afterburner beta and applied the fixes, but still no respond.
Here my steps:
Fully updated win10. I removed the old driver with AMD clean uninstaller > Reboot > Installed the blockchain driver. > Since the I've edited the card's BIOS, I used the driver patcher BEFORE rebooting the system, All options are found, patch done. > Reboot. > And after system comes up, Card is good, but Afterburner Beta still can't overclock it.

I tried to overclock with the Claymore itself, which may I add, is pretty easy and effective, but the problem I get is, that I can only overclock the GPU 0. 6 next cards (I have 7 cards on the rig) won't get the settings. I used the code like this:
" -cclock 1100 -mclock 2050"
or
"-cclock 1100,1100,1100,1100,1100,1100,1100 -mclock 2050,2050,2050,2050,2050,2050,2050" (Or different values)
And no results. I only can overclock GPU0.

I could use some help. I really need to overclock these cards.
With current price and difficulty, I'm starting to get hurt.
8  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.5 (Windows/Linux) on: June 18, 2017, 11:03:50 PM
Hi all,

I started mining with Claymore a few days ago and I am seeing an upsetting thing.
My GPU is an EVGA GTX 1080 FTW, watercooled, MSI Afterburner reports a RAM frequency of 5000 MHz, which is fine... but when mining with Claymore, the RAM frequency automatically drops to 4500 MHz. If I stop mining and start a game, the frequency goes back to 5000 - the 4500 MHz behavior only appears when mining using Claymore.

I suspect the driver somehow knows I am using Claymore and taxes me for that.
If I boost RAM frequency by +1000, it goes up from 4500 to 5500 MHz and the hash speed goes from 20.5 MH to over 25 MH - 25% boost - but this solution is clumsy, because whenever I stop mining I have to dial back the frequency boost, otherwise as soon as the GPU encounters any regular load, it tries to boost from 5000 to 6000 MHz and the memory can't handle it.

What should I do to keep mining with Claymore, but at correct RAM frequencies?

Anyone?
Is the driver detecting Claymore and forcefully reducing memory speed?
Is there a workaround?

I Got a similar problem with 1 of my RX470 rigs.
Try this and it might work:
Default the GPU via afterburner.
and then restart. Default it again. Remover after burner and any trace of it from your system. Restart. remove the driver via display driver remover in safe mode( run it, and it will recommend and offer reboot to safe mode itself). Install the latest driver. Install Afterburner. And see if the problem goes away.
I did something along these lines and my problem was fixed. I had 6 GPU locking on some ridiculous settings while the 7th being Okay, resulting in system crash minutes in under the Claymore.

The settings go in drivers and even registry some times...
9  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.5 (Windows/Linux) on: June 18, 2017, 10:53:05 PM
Hey,
Right now I'm running 12 rigs under Claymore miner, and expanding.
8 rigs with 7x RX 470 GPUs.
2 rigs with 6x RX 470.
1 rig with 6x GForce GTX 1070.
1 rig with 4x 1070 and 1 1080 Ti.

I have some Qs.

2 for now:

1) My rigs with 470s just show fan and temp for GPU0. In remote manager it's the same.

2) the GPU hangs in OpenCL call error. For what reasons that may be? So I fix it. I got it a lot under Eth+Dcr. Now on only Eth it's far far better, but I still get it time to time.
@claymore

Thanks
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!