Hello guys, i have a problem, the cards are 1050ti 4gb, updated to latest drivers and latest claymore, tried changing virtual memory, but there is still problem. What to do? Thanks in advance!
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:234 ab8 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:240 1f48 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:258 1f18 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:295 1b30 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:24:991 a58 Set global fail flag, failed GPU2
19:36:24:999 a58 GPU 2 failed
19:36:24:998 1fec Setting DAG epoch #189 for GPU2
19:36:25:010 1fec GPU 2, CUDA error 11 - cannot write buffer for DAG
19:36:25:241 ab8 Set global fail flag, failed GPU0
19:36:25:247 ab8 GPU 0 failed
19:36:25:254 af0 Setting DAG epoch #189 for GPU0
19:36:25:251 1f48 Set global fail flag, failed GPU4
19:36:25:266 1f48 GPU 4 failed
19:36:25:277 af0 GPU 0, CUDA error 11 - cannot write buffer for DAG
19:36:25:272 1f18 Set global fail flag, failed GPU5
19:36:25:289 1f2c Setting DAG epoch #189 for GPU4
19:36:25:305 1f2c GPU 4, CUDA error 11 - cannot write buffer for DAG
19:36:25:311 1e08 Setting DAG epoch #189 for GPU5
19:36:25:305 1b30 Set global fail flag, failed GPU3
19:36:25:326 1b30 GPU 3 failed
19:36:25:337 1e08 GPU 5, CUDA error 11 - cannot write buffer for DAG
19:36:25:343 1f18 GPU 5 failed
19:36:25:350 1ff0 Setting DAG epoch #189 for GPU3
19:36:25:360 1ff0 GPU 3, CUDA error 11 - cannot write buffer for DAG
19:36:25:394 1ff4 buf: {"id":0,"jsonrpc":"2.0","result":["0x8cc05aa8be75170e0cf74ab6ac892516828e014b33e2ece87efcf493ff753f1d","0x7bb6f14a940828054edc1aa9ec9f31e274e036a730709926e1f2900225e2f745","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x56c530"]}
19:36:25:403 1ff4 ETH: 05/27/18-19:36:25 - New job from eu1.ethermine.org:4444
19:36:25:407 1ff4 target: 0x0000000112e0be82 (diff: 4000MH), epoch 189(2.48GB)
19:36:25:414 1ff4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:36:25:423 1ff4 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
19:36:28:018 1fec Set global fail flag, failed GPU2
19:36:28:023 1fec GPU 2 failed
19:36:28:289 af0 Set global fail flag, failed GPU0
19:36:28:294 af0 GPU 0 failed
19:36:28:312 1f2c Set global fail flag, failed GPU4
19:36:28:322 1f2c GPU 4 failed
19:36:28:344 1e08 Set global fail flag, failed GPU5
19:36:28:351 1e08 GPU 5 failed
19:36:28:367 1ff0 Set global fail flag, failed GPU3
19:36:28:376 1ff0 GPU 3 failed
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:234 ab8 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:240 1f48 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:258 1f18 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:22:295 1b30 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
19:36:24:991 a58 Set global fail flag, failed GPU2
19:36:24:999 a58 GPU 2 failed
19:36:24:998 1fec Setting DAG epoch #189 for GPU2
19:36:25:010 1fec GPU 2, CUDA error 11 - cannot write buffer for DAG
19:36:25:241 ab8 Set global fail flag, failed GPU0
19:36:25:247 ab8 GPU 0 failed
19:36:25:254 af0 Setting DAG epoch #189 for GPU0
19:36:25:251 1f48 Set global fail flag, failed GPU4
19:36:25:266 1f48 GPU 4 failed
19:36:25:277 af0 GPU 0, CUDA error 11 - cannot write buffer for DAG
19:36:25:272 1f18 Set global fail flag, failed GPU5
19:36:25:289 1f2c Setting DAG epoch #189 for GPU4
19:36:25:305 1f2c GPU 4, CUDA error 11 - cannot write buffer for DAG
19:36:25:311 1e08 Setting DAG epoch #189 for GPU5
19:36:25:305 1b30 Set global fail flag, failed GPU3
19:36:25:326 1b30 GPU 3 failed
19:36:25:337 1e08 GPU 5, CUDA error 11 - cannot write buffer for DAG
19:36:25:343 1f18 GPU 5 failed
19:36:25:350 1ff0 Setting DAG epoch #189 for GPU3
19:36:25:360 1ff0 GPU 3, CUDA error 11 - cannot write buffer for DAG
19:36:25:394 1ff4 buf: {"id":0,"jsonrpc":"2.0","result":["0x8cc05aa8be75170e0cf74ab6ac892516828e014b33e2ece87efcf493ff753f1d","0x7bb6f14a940828054edc1aa9ec9f31e274e036a730709926e1f2900225e2f745","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x56c530"]}
19:36:25:403 1ff4 ETH: 05/27/18-19:36:25 - New job from eu1.ethermine.org:4444
19:36:25:407 1ff4 target: 0x0000000112e0be82 (diff: 4000MH), epoch 189(2.48GB)
19:36:25:414 1ff4 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:36:25:423 1ff4 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
19:36:28:018 1fec Set global fail flag, failed GPU2
19:36:28:023 1fec GPU 2 failed
19:36:28:289 af0 Set global fail flag, failed GPU0
19:36:28:294 af0 GPU 0 failed
19:36:28:312 1f2c Set global fail flag, failed GPU4
19:36:28:322 1f2c GPU 4 failed
19:36:28:344 1e08 Set global fail flag, failed GPU5
19:36:28:351 1e08 GPU 5 failed
19:36:28:367 1ff0 Set global fail flag, failed GPU3
19:36:28:376 1ff0 GPU 3 failed
Hey there, by any chance, are you dual mining?
BTW 3GB cards can't mine ETH any more, and probably, given time, 4GB will go the same way, but at least right now, 4GB cards are ok.
Things to check, Nvidia driver, (cuda) install ok, or DDU, and clean install Nvidia drivers.
Post your batchfile content, it's helpful to get a better understanding about your rig and expectations.
Also, how much VM are you running?
I am running 16000 MB VM, i am not dual mining, the cards are 4gb, i have another rig same exact configuration and it is working well. I did a clean installation on drivers and still no progress...
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal xxx.Mechanic -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg 0 -ethi 16
Today I had the same problem with 6 GPU Nvidia 1060 6GB, my solution it was increase the VM to 25 GB