CUDA error 11 - cannot write buffer for DAG #207
Comments
|
You need 4gb cards, 2gb is too small. The dag is about 2.3gb now. |
|
@jeremyisme sometimes has the same error on 1070. |
|
I don't think this is the issue. I have a 1060 with 3GB and I am also getting this error. This just started happening, I was able to mine without an issue a few days ago. |
|
I have exactly the same problem, it started suddenly on February 1. My cards are 1060 3gb just. |
|
same problem with DAG file for ETC |
|
Still not working.... Set page file to 16GB, still getting the error. Odd that this is suddenly occurring after months of perfect operation, and the DAG file size is < 3GB. |
|
same issue, after a mounts of perfect work rig just refuse to mine Other miners works same way with very low hashrate |
|
Same here with Zotac 1060 3GB card. Since last epoch change in ETC it refuses to work with "cannot allocate big buffer for DAG" error. I tried different pagefile sizes, no fix. |
|
I had the same issue going from Version 10 to 11. I change 2 or 3 options in the batch file and I think the LIDAG was the important one. It makes the DAG creation go slower....I think. I entered into the batch file: |
|
Thanks for the advice, rdavis852, but still no go for ETC with -lidag1 and 0. |
|
Also got the same issue, tried lidag and gser 2 & 5, dident have this issue before could write dag for 8 gpus same time, but after i´ve connected 3 more gpus it wont work, but it goes further with gser 5 but still not good enought, any solution? |
|
I did some looking around and it seems this issue is caused by Windows 10 not allocating all VRAM to CUDA apps. Many posts say it reserves about 20% memory even if the gpu is a secondary (not used for output). 3GB - 0.6 (20%) = 2.4GB. Which is about the size of the current ETC DAG 186 (2.45GB) while ETH is still at DAG 176 (2.37GB) If my analysis is right then ETH mining itself will give the same error when it's DAG size start using more than 2.4GB Unfortunately, the issue is Windows based and Microsoft knew about it for almost 3 years now and still there is no solution. I guess people should try Win 7 or 8.1 and see if the issue remains... |
|
-eres 0 1060 3gb works with this param |
|
already tried: |
|
Same Problem here also have 1060 3gb Cards. @albalirus your solution worked for me |
|
-eres 0 fixed mine, thank you. |
|
can also confirm that the '-eres 0'-setting fixed the issue for my 1060 3gb-cards |
|
Can someone post their bat file to show how -eres 0 worked? My 1060 3g rig just started doing the "CUDA error - cannot allocate big buffer for DAG" today and I've tried everything. -eres 0 - 16g vram and nadda |
|
-eres 0 worked up until today's DAG (178) If you want to continue mining ETH with 1060 3GB, you need to downgrade to Win 7/8.1 or Linux |
|
Set your driver back to V.388.71. It does resolve the problem today. See below for the Nvidia's link for 388.71 driver - http://www.nvidia.com/content/DriverDownload-March2009/confirmation.php?url=%2FWindows%2F388.71%2F388.71-desktop-win10-64bit-international-whql.exe&lang=tw&type=TITAN |
|
@Muaadib same here with zotac 1060 3GB @netkingtw will try drivers and report, i got 390.65 atm |
|
@stefanwendelmann yes same here |
|
worked for me |
|
thank you |
|
Zotac gtx 1060 3 gb. Same error guys -CUDA error 11-cannot write buffer for DAG gpu failed. I m using Windows 10. Somebody please help. |
|
I confirm that nvidia driver 388.71 resolves the issue. Thank you @netkingtw. However, out of eleven nvidia cards, only nine are detected with 388 driver. That's not an issue with 390.xx or 391.xx tho. |
|
I have tried all the things mentioned here until now, just installed the 388.71 drivers as well (and checked if it was applied to everything). Also eres 0, lidag combos, starting two instances of miner to force rebuild dag. Nothing works. Have 10 3gb 1060-s and one 6gb 1060 in the rig. Any help would be great |
|
@Aljook @remon-georgy Driver 388.71 works for most miners that had the same cuda error for 1060 3GB GPU yesterday but does not work for a very small part of miners. Taiwan mining pool forum released a solutions to their miners as below: Step 1, Add the following 5 line commands in your Claymore's miner's .bat file（ -eres 0 should still be added as it was before yesterday's problem occured)： setx GPU_FORCE_64BIT_PTR 0 Step 2， Step 3, If all above-mentioned steps still do not resolve your problem, use Claymore 10.6 and try to decrease both core and memory clock a bit until it works. If all steps fail, use Ethminer instead because Ethminer does not have this issue. |
|
Claymore quote "It seems 3GB cards won't be able to mine ETH/ETC in Windows10 soon because this OS reserves about 20% of GPU memory size and there is no way to fix it (at least easily). https://bitcointalk.org/index.php?topic=1433925.msg33471755#msg33471755 Seems my theory is correct |
|
I had the problem for over a day. took me ages but finally changed to windows 7 and it's up back and running. |
|
Thanks for the update! Windows 7 and Ethos is as expected. Did someone tried Windows 8.1? |
|
Hello, I can confirm that on 8.1 Enterprise OS 5xGTX 1060 3GB work fine. It was tested from yesterday. |
|
Thanks for the update @dzidass . I am going to give it a shot Win8.1 when I am back from work. Off topic but if someone doesn't have access to Win8.1 or don't wana install etc... just switch to UBIQ almost same hash rate and returns, not too bad IMO vs ETH. |
|
Time for a second hdd or bootmanager for Linux/Ubuntu any good guide how to set up linux for claymore eth ? |
|
Sorry, I don't have the instructions but I would go with ethos, pay a little fees but has alot better stability, monitoring, scalability. With ethos is peace of mind! GTX 1060 3 GB's are wokring in ethos as it was before. |
|
How you make 35 gb file and where to do that? |
|
Today i have the same problem after update win 10, i solve it setting up the virtual memory to 32gb My rig have 4 gtx1070 8gb and 3 gtx1060 6gb driver 397.64 |
|
I ran into the issue on an all 1070 8GB rig. Had to update to 11.7 and increase virtual to 20GB. Very strange |
|
I moved to HiveOS and haven't had a problem since. No hassles with drivers or virtual memory, plus I'm getting slightly higher hashrates. Windows is a piece of shit. Do yourself a favor and mine using a different OS. |
|
-lidag 1 on my gtx 1070 resolved. thank you |
|
gpu: ge force gtx 1050ti (4gb) oc dual fan edition -eres this setting is related to Ethereum mining stability. Every next Ethereum epoch requires a bit more GPU memory, miner can crash during reallocating GPU buffer for new DAG. check your read me file miner;Claymore.s.Dual.Ethereum.Decred_Siacoin_Lbry_Pascal.AMD.NVIDIA.GPU.Miner.v10.0** GPU_FORCE_64BIT_PTR 0 my miner was running fine till the about month ago, i read a post here to add this code to your miner -eres 0 after worker email of the eth miner not the pascal miner,i only added the bold -eres 0 to my miner it fixed it and i have a brand new 4gb card, so make your conclusion. this issue started after bad thunder storm power went out and out of my 6 miners that one went bad, i was going to just give it way and buy a new,but before you do that please add -eres 0 or -eres 1 by defualt the miner runs a -eres 2 wich is to high takes from your gb,so you dont work, some of you running only pascal with issue well do samee as above. hope this helps. and yes that is my real ethereum/pascal deposit address for my miner. happy mining ; |
|
I'm trying to mine akroma off claymore and everytime I add my 4th gpu (running all nvidia 1070ti) it gives me the cuda error 11 and restarts the program. When I have 3 or less gpus it works just fine. PLEASE HELP! I am on windows 10 |
|
I had the same problem that fixed by c++ redist. Try it http://bit.ly/2KmpUcF |
|
Hi everyone, I was tracking down this issue for a long time. I finally resolved it 5 minutes ago. 8 gpu rig (1070's)
Here's how I came to the steps above: The miner settings didn't seem to matter, but I did -eres 0 and -lidag 1 to no avail. I upgraded system memory from 4gb to 8gb. I think this helped allowing me to use less virtual memory. I added 850psu (upgraded from a 550w), so now my system has 2 850psu's I tried old and new Nvidia drivers. Currently i'm using the latest NVidia drivers I was on claymore 10.0 and it suddenly stopped working. I upgraded to 11.9 and also tried 11.6, to no avail. Here's the key part: In order to upgrade the miner, I had to disable the firewall. Something with that screwed things up. So here is what I did to fix the issue: I did the Reset Windows option https://www.laptopmag.com/articles/reset-windows-10-pc Once that was done, my paging file options went from 22000max to 30000max. So, I updated it to 16000 / 30000 paging file. Then, I started miner and still got the error. But the firewall popped up and said something was blocked!! So, I clicked "allow access" on that window. Restarted miner and boom, all working great now! HOPE THIS HELPS!!! |
|
Try the command after the pools: -allpools 1 |
|
I mean the pool config |
|
I tried all but it doesn't help, still have this error! |
I would focus on this: "Here's the key part: In order to upgrade the miner, I had to disable the firewall. Something with that screwed things up. So here is what I did to fix the issue: I did the Reset Windows option https://www.laptopmag.com/articles/reset-windows-10-pc" |
|
It is fresh installed win 10 |
|
I got the same problem today with a Nvidia GTX 1070 8Gb, solved adding the option |
|
I got the same problem today with a Nvidia GTX 1060 6Gb, solved adding the option "-eres 0" The EPOC changed from 382 to 383 which increased the DAG size from 3.98Gb to 3.99Gb At the same time the hashrate on Nanopool dropped by 10% |
|
got the same problem today with gtx 1080 8Gb, solved adding the -eres 0 |
|
Guys I add -eres 0 in config.txt and also add it in the end of line in start.bat file. It worked great, thanks for the help. |
|
-eres 0 worked for me with 1070's thanks :) |
|
Hi everybody |
|
i had same issue last night so i removed the -eres 0 and then it worked again |
|
yes, me too, removed the -eres 0 and worked again. now I am back with my original configuration and it's working again as usual. strange thing is that I don't get the error that made me put the -eres 0 option in the first place.. |
|
I start to use other miners withouth a dag problem and I use 4Gb vram |
and others
C:\Users\ilhami\Desktop\Ethereum>setx GPU_FORCE_64BIT_PTR 0
SUCCESS: Specified value was saved.
C:\Users\ilhami\Desktop\Ethereum>setx GPU_MAX_HEAP_SIZE 100
SUCCESS: Specified value was saved.
C:\Users\ilhami\Desktop\Ethereum>setx GPU_USE_SYNC_OBJECTS 1
SUCCESS: Specified value was saved.
C:\Users\ilhami\Desktop\Ethereum>setx GPU_MAX_ALLOC_PERCENT 100
SUCCESS: Specified value was saved.
C:\Users\ilhami\Desktop\Ethereum>setx GPU_SINGLE_ALLOC_PERCENT 100
SUCCESS: Specified value was saved.
C:\Users\ilhami\Desktop\Ethereum>EthDcrMiner64.exe -epool eu1.nanopool.org:9999 -ewal "I AM PARANOID, I KNOW NOTHING WILL HAPPEN BUT..." -epsw x -mode 1 -ftime 10
╔════════════════════════════════════════════════════════════════╗
║ Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v10.0 ║
╚════════════════════════════════════════════════════════════════╝
This pool (eth-eu2.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-eu2.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-eu2.nanopool.org removed from the list
This pool (eth-us-east1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-us-east1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-us-east1.nanopool.org removed from the list
This pool (eth-us-west1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-us-west1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-us-west1.nanopool.org removed from the list
This pool (eth-asia1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.This pool (eth-asia1.nanopool.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
Please read "Readme" file for details.Pool eth-asia1.nanopool.org removed from the list
ETH: 1 pool is specified
Main Ethereum pool is eu1.nanopool.org:9999
AMD OpenCL platform not found
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool
CUDA initializing...
NVIDIA Cards available: 1
CUDA Driver Version/Runtime Version: 9.1/8.0
GPU #0: GeForce GTX 1050, 2048 MB available, 5 compute units, capability: 6.1
Total cards: 1
ETH: Stratum - connecting to 'eu1.nanopool.org' <198.251.88.37> port 9999
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: eth-proxy stratum mode
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333
ETH: Stratum - Connected (eu1.nanopool.org:9999)
ETH: Authorized
Setting DAG epoch #166...
Setting DAG epoch #166 for GPU0
Create GPU buffer for GPU0
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
GPU 0 failed
Setting DAG epoch #166 for GPU0
GPU 0, CUDA error 11 - cannot write buffer for DAG
GPU 0 failed
is the log. Can you guys help me?
Rig:
GPU: GTX 1050
CPU: Core i3-7100
Motherboard: Gigabyte H110M-S2V
HDD: WD Caviar Blue 1 TB
RAM: GSkill RipjawsV 8GB(1x8)
The text was updated successfully, but these errors were encountered: