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

[janhrmod]

Hi, do you use one of the GPU card to display your monitor?
If yes you should use internal video output on mainboard to your monitor.
Also do you use your computer only for mining?
Did you setup extra virtual memory? Eg you should have atleast 16GB virtual memory
If you have free mainboard slots you can try to move the GPU that mine at a low rate to another slot.
Maybe also upgrade you OS a new Win10 install may run better, it is best if you have another HD that you can swap with a new OS

[1714894380]

1714894380

[1714894380]

1714894380

[1714894380]

1714894380

[big_daddy]

now can't mining anymore?
I got error "CUDA error 11 - cannot allocate big buffer for dag" last night.

how many GB on your GPUs do you have? and check the virtual mem on your system

[big_daddy]

now can't mining anymore?
I got error "CUDA error 11 - cannot allocate big buffer for dag" last night.

how many GB on your GPUs do you have? and check the virtual mem on your system

My card is 1060 3G x6 , Virtual mem is 51200

OS : win7 Ram : 4GB

The ETH dag file is at 2,86 GB so there should be no problem by uploading it
Can you copy paste in the code the bat file config

[big_daddy]

now can't mining anymore?
I got error "CUDA error 11 - cannot allocate big buffer for dag" last night.

how many GB on your GPUs do you have? and check the virtual mem on your system

My card is 1060 3G x6 , Virtual mem is 51200

OS : win7 Ram : 4GB

The ETH dag file is at 2,86 GB so there should be no problem by uploading it
Can you copy paste in the code the bat file config

here is my bat file config
EthDcrMiner64.exe -epool asia.ethash-hub.miningpoolhub.com:20535 -ewal circruiz.Miner-02 -eworker circruiz.Miner-02 -esm 2 -epsw x -eres 0

claymore version 12

and here is my log file

12:27:02:406   d80   Check and remove old log files...
12:27:02:407   d80   args: -epool europe.ethash-hub.miningpoolhub.com:20535 -ewal circruiz.Miner-02 -eworker circruiz.Miner-02 -esm 2 -epsw x -dpool stratum+tcp://hub.miningpoolhub.com:20550 -dwal circruiz.Miner-02 -dpsw x -dcoin sc
12:27:02:407   d80   
12:27:02:407   d80   ษออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออป
12:27:02:408   d80   บ     Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v10.6      บ
12:27:02:408   d80   ศออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออออผ
12:27:02:408   d80   
12:27:02:408   d80   b471
12:27:02:608   d80   ETH: 3 pools are specified
12:27:02:608   d80   Main Ethereum pool is europe.ethash-hub.miningpoolhub.com:20535
12:27:02:609   d80   SC: 1 pool is specified
12:27:02:609   d80   Main Siacoin pool is hub.miningpoolhub.com:20550
12:27:02:980   d80   OpenCL platform: Intel(R) OpenCL
12:27:02:980   d80   OpenCL platform: NVIDIA CUDA
12:27:02:980   d80   AMD OpenCL platform not found
12:27:03:363   d80   CUDA initializing...

12:27:03:364   d80   NVIDIA Cards available: 6
12:27:03:364   d80   CUDA Driver Version/Runtime Version: 8.0/8.0
12:27:03:377   d80   GPU #0: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 1:0:0)

12:27:03:379   d80   GPU #1: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 3:0:0)

12:27:03:381   d80   GPU #2: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 5:0:0)

12:27:03:382   d80   GPU #3: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 6:0:0)

12:27:03:384   d80   GPU #4: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 7:0:0)

12:27:03:386   d80   GPU #5: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 8:0:0)

12:27:03:386   d80   Total cards: 6
12:27:07:386   d80   No AMD cards in the list, ADL library will not be used.
12:27:07:388   d80   NVML version: 8.372.54
12:27:08:321   a6c   ETH: Stratum - connecting to 'europe.ethash-hub.miningpoolhub.com' <18.197.166.72> port 20535
12:27:08:416   d80   DUAL MINING MODE ENABLED: ETHEREUM+SIACOIN

12:27:08:417   d80   ETH: miner-proxy stratum mode
12:27:08:418   cfc    SC: Stratum - connecting to 'hub.miningpoolhub.com' <18.215.83.151> port 20550
12:27:08:418   d80   Watchdog enabled
12:27:08:419   d80   Remote management (READ-ONLY MODE) is enabled on port 3333
12:27:08:419   d80   

12:27:08:516   a6c   send: {"id": 1, "method": "mining.subscribe", "params": []}

12:27:08:516   a6c   send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

12:27:08:517   a6c   send: {"id": 2, "method": "mining.authorize", "params": ["circruiz.Miner-02","x"]}

12:27:08:517   a6c   ETH: Stratum - Connected (europe.ethash-hub.miningpoolhub.com:20535)
12:27:08:693   cfc   send: {"id": 1, "method": "mining.subscribe", "params": []}

12:27:08:693   cfc   send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

12:27:08:693   cfc   send: {"id": 2, "method": "mining.authorize", "params": ["circruiz.Miner-02","x"]}

12:27:08:694   cfc    SC: Stratum - Connected (hub.miningpoolhub.com:20550)
12:27:08:718   a6c   got 162 bytes
12:27:08:718   a6c   buf: {"id":1,"result":[[["mining.set_difficulty","deadbeefcafebabe24b4010000000000"],["mining.notify","deadbeefcafebabe24b4010000000000"]],"3000f074",4],"error":null}

12:27:08:718   a6c   parse packet: 161
12:27:08:718   a6c   new buf size: 0
12:27:08:974   cfc   Socket was closed remotely (by pool)
12:27:08:975   cfc    SC: Job timeout, disconnect, retry in 20 sec...
12:27:09:108   a6c   got 302 bytes
12:27:09:108   a6c   buf: {"id":null,"method":"mining.notify","params":["1ed","0xcab4fb9764bf4f0781f9df5b63d8a9a073840f74fecba867f34b6e879945f86d","0xf60094216ea7e9fbb0131eed41f30bc1204bf17a451d9f5af9c36b78aa225806","0x000000007fd9a60121074ca47566bc6799d82cd4456f0ff830a7bf9e181e79d3",true]}
{"id":2,"result":true,"error":null}

12:27:09:108   a6c   parse packet: 265
12:27:09:108   a6c   ETH: job changed
12:27:09:108   a6c   remove first packet 36
12:27:09:108   a6c   new buf size: 36
12:27:09:108   a6c   parse packet: 35
12:27:09:109   a6c   ETH: Authorized
12:27:09:109   a6c   new buf size: 0
12:27:09:125   d34   Setting DAG epoch #238...
12:27:12:049   d34   Setting DAG epoch #238 for GPU2
12:27:12:051   cac   Setting DAG epoch #238 for GPU0
12:27:12:049   6b4   Setting DAG epoch #238 for GPU1
12:27:12:050   fe0   Setting DAG epoch #238 for GPU4
12:27:12:050   114   Setting DAG epoch #238 for GPU3
12:27:12:050   cd0   Setting DAG epoch #238 for GPU5
12:27:12:051   d34   Create GPU buffer for GPU2
12:27:12:051   cac   Create GPU buffer for GPU0
12:27:12:052   6b4   Create GPU buffer for GPU1
12:27:12:052   fe0   Create GPU buffer for GPU4
12:27:12:052   114   Create GPU buffer for GPU3
12:27:12:053   cd0   Create GPU buffer for GPU5
12:27:12:054   d34   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

12:27:12:054   cac   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

12:27:12:055   6b4   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

12:27:12:055   fe0   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

12:27:12:056   114   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

12:27:12:057   cd0   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

12:27:15:054   d34   Set global fail flag, failed GPU2
12:27:15:054   d34   GPU 2 failed
12:27:15:054   cac   Set global fail flag, failed GPU0
12:27:15:056   cac   GPU 0 failed
12:27:15:055   6b4   Set global fail flag, failed GPU1
12:27:15:056   6b4   GPU 1 failed
12:27:15:056   f30   Setting DAG epoch #238 for GPU2
12:27:15:056   114   Set global fail flag, failed GPU3
12:27:15:057   f30   GPU 2, CUDA error 11 - cannot write buffer for DAG

12:27:15:057   114   GPU 3 failed
12:27:15:055   fe0   Set global fail flag, failed GPU4
12:27:15:058   fe0   GPU 4 failed
12:27:15:058   6b0   Setting DAG epoch #238 for GPU3
12:27:15:057   f10   Setting DAG epoch #238 for GPU0
12:27:15:057   cd0   Set global fail flag, failed GPU5
12:27:15:057   c78   Setting DAG epoch #238 for GPU1
12:27:15:059   6b0   GPU 3, CUDA error 11 - cannot write buffer for DAG

12:27:15:059   f10   GPU 0, CUDA error 11 - cannot write buffer for DAG

12:27:15:058   f54   Setting DAG epoch #238 for GPU4
12:27:15:059   cd0   GPU 5 failed
12:27:15:060   c78   GPU 1, CUDA error 11 - cannot write buffer for DAG

12:27:15:060   f54   GPU 4, CUDA error 11 - cannot write buffer for DAG

12:27:15:060   c14   Setting DAG epoch #238 for GPU5
12:27:15:061   c14   GPU 5, CUDA error 11 - cannot write buffer for DAG

12:27:18:057   f30   Set global fail flag, failed GPU2
12:27:18:057   f30   GPU 2 failed
12:27:18:059   f10   Set global fail flag, failed GPU0
12:27:18:059   f10   GPU 0 failed
12:27:18:059   6b0   Set global fail flag, failed GPU3
12:27:18:060   6b0   GPU 3 failed
12:27:18:060   f54   Set global fail flag, failed GPU4
12:27:18:060   c78   Set global fail flag, failed GPU1
12:27:18:060   c78   GPU 1 failed
12:27:18:061   f54   GPU 4 failed
12:27:18:061   c14   Set global fail flag, failed GPU5
12:27:18:061   c14   GPU 5 failed
12:27:28:975   cfc    SC: Stratum - connecting to 'hub.miningpoolhub.com' <18.215.83.151> port 20550
12:27:29:112   a6c   send: {"id":6,"worker":"circruiz.Miner-02","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000f4cfa1c8"]}

12:27:29:237   cfc   send: {"id": 1, "method": "mining.subscribe", "params": []}

12:27:29:237   cfc   send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

12:27:29:237   cfc   send: {"id": 2, "method": "mining.authorize", "params": ["circruiz.Miner-02","x"]}

12:27:29:238   cfc    SC: Stratum - Connected (hub.miningpoolhub.com:20550)
12:27:29:305   a6c   got 36 bytes
12:27:29:305   a6c   buf: {"id":6,"result":true,"error":null}

12:27:29:305   a6c   parse packet: 35
12:27:29:305   a6c   new buf size: 0
12:27:29:508   cfc   Socket was closed remotely (by pool)
12:27:29:509   cfc    SC: Job timeout, disconnect, retry in 20 sec...
12:27:32:613   f50   em hbt: 0, dm hbt: 3635, fm hbt: 93,
12:27:32:613   f50   watchdog - thread 0 (gpu0), hb time 17550
12:27:32:613   f50   watchdog - thread 1 (gpu0), hb time 17550
12:27:32:613   f50   watchdog - thread 2 (gpu1), hb time 17550
12:27:32:613   f50   watchdog - thread 3 (gpu1), hb time 17550
12:27:32:613   f50   watchdog - thread 4 (gpu2), hb time 17550
12:27:32:613   f50   watchdog - thread 5 (gpu2), hb time 17550
12:27:32:613   f50   watchdog - thread 6 (gpu3), hb time 17550
12:27:32:613   f50   watchdog - thread 7 (gpu3), hb time 17550
12:27:32:613   f50   watchdog - thread 8 (gpu4), hb time 17550
12:27:32:613   f50   watchdog - thread 9 (gpu4), hb time 17550
12:27:32:613   f50   watchdog - thread 10 (gpu5), hb time 17550
12:27:32:613   f50   watchdog - thread 11 (gpu5), hb time 17550
12:27:32:614   f50   WATCHDOG: GPU error, you need to restart miner
12:27:32:656   2e4   GPU0 t=45C fan=0%%, GPU1 t=43C fan=0%%, GPU2 t=49C fan=0%%, GPU3 t=47C fan=0%%, GPU4 t=41C fan=28%%, GPU5 t=40C fan=28%%
12:27:33:819   f50   Restarting OK, exit...


Thank you so much

Try by adding this at the beginning of the bat file:

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

[Elange]

Christ, these environment variables are ONLY pertaining to AMD videocards. It's been told a million times...

1060 3Gb are through with Ethereum. R.I.P.

[astraleureka]

Nice cargo cult behavior right there

[astraleureka]

Because it doesn't do anything for nVidia drivers.

[big_daddy]

Because it doesn't do anything for nVidia drivers.

  yup, you are right, is for AMD only that setting, I am out of ideas here ... 

[scryptr]

HACKED VERSION OF CLAYMORE? --

The top of circuiz log file states he is running version 10.6.  He stated he is running v12.  I would suggest using a fresh copy of Claymore v12, downloaded from an official archive.

There is no longer a need for running a hacked version of Claymore for any 3GB GPU, nVidia or AMD.  Claymore v12 is free (0% fee) for these cards on both Linux and Windows.       --scryptr

[scryptr]

ETHEREUM ASICS ARE MORE EFFICIENT THAN GPUS--

I do not know how to solve your problem, but there are currently ASIC devices that will mine Ethereum with far less electricity usage.    Like many other algorithms (and coins), Ethereum is no longer for GPUs only.       --scryptr

[onuraslan07]

Hello,

file: C:\Users\WHITE-~1\AppData\Local\Temp\Rar$DRa0.098\Claymore's Dual Ethereum+Decred_Siacoin_Lbry_Pascal_Blake2s_Keccak AMD+NVIDIA GPU Miner v12.0\cuda6.5\EthDcrMiner64.exe

Trojan: Win64/CoinMiner
Uyarı düzeyi: Ciddi
Tarih: 30.01.2019
Katagori Adı: Trojen

last version v12 

[rabbi-t]

mine exp on dwarf
started to get dcs from yesterday

Socket was closed remotely (by pool)
ETH: Connection lost, retry in 20 sec...

what happened?

ethdcrminer64 -epool exp-eu.dwarfpool.com:8018 -ewal xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/$worker -mport -2222 -allcoins 1

[ala12uk]

Hi All

I am using Claymore 12.0 on Windows 10 Pro 64
I have few AMD (RX580) machines and I have few Nvidia (1080ti) machines
I have put a bat file to start Claymore's Miner automatically in:
~\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Some of the AMD and some of the Nvidia miners will not work and will throw the below error when the Claymore's Miner is started in the background (when the monitor is not connected):
A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available

If i connect the monitor to that machine and restart the machine, the bat file will execute, Claymore Miner will run and no error messages will be displayed on the screen, so the machine can run for several days with no interruption. However, once the machine is restarted for whatever reason (Temporary electricity outage, windows updates, some GPU crahses, among many other reasons) the miner will never work until i connect the monitor to that machine and restart it while the monitor is connected then it will work. I can disconnect the monitor after that and the machine will stay up and running for a week or so.

Has anyone faced such issues?
How did you solve them?
I tried DDU the existing drivers, and i tried installing the latest ones, it has never helped
Other machines with similar configuration have no issues, but what i notice is that every month one more machine starts to behave in this way, to me it seems something happens after windows updates. I can't uninstall those updates because windows will reinstall them again. Although i have the Pro version i can only postpone the updates up to one month not more, so that wont really help

Any good solution please? 

[sxemini]

You need a hdmi dummy that will simulate the monitor.

https://www.ebay.de/i/282908756304?chn=ps&var=582640777890

[yaros]

Who will prompt the password for the archive?

[ala12uk]

You need a hdmi dummy that will simulate the monitor.

https://www.ebay.de/i/282908756304?chn=ps&var=582640777890

Thank you very much for the advice, i will surely do that if there is no other solution
I have built an entire farm of more than 200 GPU from an absolute scratch, so i am very passionate about technology and always like to dig behind the issue. Those machines worked perfectly well without a monitor for more than a year. I can definitely use a workaround, but i would love to know what has caused this issue and solve it
I have tried all the below solutions but NOTHING helped:
1) https://support.gamehouse.com/hc/en-us/articles/215857618-A-problem-caused-the-program-to-stop-working-correctly-Windows-will-close-the-program-and-notify-you-if-a-solution-is-available
2)https://troubleshooter.xyz/wiki/fix-a-problem-caused-the-program-to-stop-working-correctly/
3)https://www.drivereasy.com/knowledge/a-problem-caused-the-program-to-stop-working-correctly-solved/#f


Do you have any other idea of how to fix it?
If there is no way to fix it then for sure i will try the workaround

[SnowLeopard]

Oh no!
Epoch 239 has arrived and my 3GB GTX 1060s stopped working: CUDA error - cannot allocate big buffer for DAG.

[Jonet]

Do you have any other idea of how to fix it?
If there is no way to fix it then for sure i will try the workaround

I've had an issue where I had to connect dummy or monitor to motherboard GPU. Solved it by installing latest Intel graphics driver (Z270 chipset)
Would be interesting to know the real reason behind this. I had identical rigs, the old ones updated to build 1709 was OK, build 1709 installed from scratch did not work.
I suppose the problem could have been fixed in the mining software if anyone knew what was causing it.

[big_daddy]

Oh no!
Epoch 239 has arrived and my 3GB GTX 1060s stopped working: CUDA error - cannot allocate big buffer for DAG.

move on and choose another coin to mine, ETH is not the only minable coin

[ala12uk]

Do you have any other idea of how to fix it?
If there is no way to fix it then for sure i will try the workaround

I've had an issue where I had to connect dummy or monitor to motherboard GPU. Solved it by installing latest Intel graphics driver (Z270 chipset)
Would be interesting to know the real reason behind this. I had identical rigs, the old ones updated to build 1709 was OK, build 1709 installed from scratch did not work.
I suppose the problem could have been fixed in the mining software if anyone knew what was causing it.

I have not tried to update the chipset driver, i thought this is also done as part of the overall windows updates, i hope this will solve my problem. The strange thing is that 6 machines worked for almost a whole year with absolutely no issues. I have not changed even a single wire on them. So the only changes were windows updates. I tried to DDU and reinstall fresh updated AMD or Nvidia drivers but that did not really help at all, and i tried just about many other things, it never worked. I have already ordered the dummies, but i am always curious to learn new things about technology. Why one machine would work for a whole year and then one day (supposedly after a windows update) it will stop to work and virtual no software workaround would solve that. Moreover, i still have other machines with the SAME EXACT hardware & software configuration, and yes with the same windows updates, but they work just absolutely fine, they never needed any dummies. However, it seems that during the last few months, one machine gets this issue every month or few weeks, so this phenomena is getting spread almost on all machines. What makes me wonder, is that if it was windows updates, then why not all machines which has the same windows updates switched on, dont suffer from the same issue?