-eres 0 doesnt work anymore.
Confirm. Same for me. Stopped working after few days. Tried to change second line in the file - no results. Will be looking furhter for the solution to this problem.
Topic: CUDA error 11-cannot write buffer for DAG - page 4. (Read 3706 times)
Confirm. Same for me. Stopped working after few days. Tried to change second line in the file - no results. Will be looking furhter for the solution to this problem.
-eres 0 doesnt work anymore.
its time to migrate to linux or other coin.
-eres 0 doesnt work anymore.
Thanks all - this tread helped us and we are backup and running on ETH for a month anyway 
Epoch 177
DAG 2.38 GB
6x 1060's 3GB
Windows 10 ver.1709
Swapfile 21GB
NVIDIA drivers 371
Claymore 11.5
-eres 0 added to the end of the command line
Claymore was updated Swapfile increased - did not work until -eres 0 was added
No further testing with other settings as it worked off the bat with the above, so left as is.
-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.
To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation.
This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.
Epoch 177
DAG 2.38 GB
6x 1060's 3GB
Windows 10 ver.1709
Swapfile 21GB
NVIDIA drivers 371
Claymore 11.5
-eres 0 added to the end of the command line
Claymore was updated Swapfile increased - did not work until -eres 0 was added
No further testing with other settings as it worked off the bat with the above, so left as is.
-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.
To avoid it, miner reserves a bit larger GPU buffer at startup, so it can process several epochs without buffer reallocation.
This setting defines how many epochs miner must foresee when it reserves GPU buffer, i.e. how many epochs will be processed without buffer reallocation. Default value is 2.
I used to have the same problem as you all, I have a few MSI Gtx 1060 3gb versions and the -eres 0 added option solved the issue for me from a few minutes ago. I was desperate and was searching google and come to this thread, I thought mining Ethereum with 3gb cards was over at Dag 177 but that is not the case, just edit your start.bat file in Claymore miner and also if you are using nicehash in 3rd party miners in Claymore do the same.
Hello everyone!
I had the same problem with my 1060 3gb, but "-eres 0" is not halpful for me...
I've tried another miner "ethminer" and all is working now))
https://github.com/ethereum-mining/ethminer/releases
P.S.
кому удобно читать на русском - вот описание и настройка майнера:
https://blogmajnera.blogspot.com/2017/11/nastrojka-majner-ethminer-0-12-0.html
I had the same problem with my 1060 3gb, but "-eres 0" is not halpful for me...
I've tried another miner "ethminer" and all is working now))
https://github.com/ethereum-mining/ethminer/releases
P.S.
кому удобно читать на русском - вот описание и настройка майнера:
https://blogmajnera.blogspot.com/2017/11/nastrojka-majner-ethminer-0-12-0.html
Wow.. add -eres 0 is helpfull. Thank everyone!
Hi guys!
I got 4x1060 3GB and 1x1060 6GB, started having "Cuda error 11......" this tuesday, was looking for solution all this time. First thing that helped me, temporary though, was this:
1. Set swap file to 0mb / diasble it
2. Defrag the system drive, so it has continuous chunk of free space big enough for placing your swap file in one piece.
3. Set the swap file size to 14750mb
4. Profit!!
It worked for me, but it didnt work for long, on the next day the problem came back... So i started digging again.
And here's what i found (the problem i had - was with the NHML 1.8.10, so the method will be described for this miner, if you use claymore itself - it is even easier):
1. Open \internals\MinerOptionPackage_ClaymoreDual.json in your NHML folder using any text editor (i.e. notepad)
2. Find "Type": "ClaymoreDual_eres", set "0" instead of "2" to the "Default": "2" parameter
3. Save changes
4. Restart NHML
5. Profit!!
P.S. Just found that there are 2 lines in "\internals\MinerOptionPackage_ClaymoreDual.json" with "Type": "ClaymoreDual_eres" parameter, i onle changed lower one, and everything works fine for.
I got 4x1060 3GB and 1x1060 6GB, started having "Cuda error 11......" this tuesday, was looking for solution all this time. First thing that helped me, temporary though, was this:
1. Set swap file to 0mb / diasble it
2. Defrag the system drive, so it has continuous chunk of free space big enough for placing your swap file in one piece.
3. Set the swap file size to 14750mb
4. Profit!!
It worked for me, but it didnt work for long, on the next day the problem came back... So i started digging again.
And here's what i found (the problem i had - was with the NHML 1.8.10, so the method will be described for this miner, if you use claymore itself - it is even easier):
1. Open \internals\MinerOptionPackage_ClaymoreDual.json in your NHML folder using any text editor (i.e. notepad)
2. Find "Type": "ClaymoreDual_eres", set "0" instead of "2" to the "Default": "2" parameter
3. Save changes
4. Restart NHML
5. Profit!!
P.S. Just found that there are 2 lines in "\internals\MinerOptionPackage_ClaymoreDual.json" with "Type": "ClaymoreDual_eres" parameter, i onle changed lower one, and everything works fine for.
-eres 0 fixed this problem for me while mining ETC. I have not tried it yet with ETH. I will prob. be moving to ETH soon as I have been toggling back and forth. No idea why it is not working for some. I have 12x 3gb Gigabyte OC cards (the cheapest 2 fan versions) on this rig
worked for me after my evga 1060 3go got me this error after 1 years of good work.Dont know what -eres 0 does but its work!
I hope it will work until june 2019
Prepare to install something else or mine another coin.
-eres 0 fixed this problem for me while mining ETC. I have not tried it yet with ETH. I will prob. be moving to ETH soon as I have been toggling back and forth. No idea why it is not working for some. I have 12x 3gb Gigabyte OC cards (the cheapest 2 fan versions) on this rig
worked for me after my evga 1060 3go got me this error after 1 years of good work.Dont know what -eres 0 does but its work!
I hope it will work until june 2019
take the command -eres 0 in the claymores bat file and you will be happy for sometimes more
helped on MSI 1060 3GBthanks
For me the problem (DAG Error) only exist with Claymore binaries.
Change ETH binaries and there is no error at all using a 3GB 1060.
No dual mining though but im fine with that.
Hey. Tell me how to change binaries ETH or where i can read about it, please? ThanksChange ETH binaries and there is no error at all using a 3GB 1060.
No dual mining though but im fine with that.
I just used "-eres 0" and it worked! I'm using Awesome miner so had to add it in the command line override but all good 
- thanks for your help!
- thanks for your help! take the command -eres 0 in the claymores bat file and you will be happy for sometimes more
this worked for me tankyou! Same boat here, seems like nothing works!
3Gb cards nomore eth miners!
3Gb cards nomore eth miners!
Add -eres 0 in claymore, works for all on these topic
Same boat here, seems like nothing works!
3Gb cards nomore eth miners!
3Gb cards nomore eth miners!
Dear friends. We are moving forward. As the Russian proverb says. "By buying iron without departing from the cashier's office." Forward friends to financial independence.
Quoting myself here as well for visibility because it seems like some people are starting to get hit by the memory limit:
The problem is only for Windows 10 1709. Switch to Windows Server 2016 or any Linux distro and you'll be fine.
ETH is still unaffected by this, though - only ETC, because it is few epochs ahead. But ETH should hit the 3GB Windows limit within a month or so. If you still got a problem - try using the iGPU as primary or get another card with more memory as the main one.
ETH is still unaffected by this, though - only ETC, because it is few epochs ahead. But ETH should hit the 3GB Windows limit within a month or so. If you still got a problem - try using the iGPU as primary or get another card with more memory as the main one.
For me the problem (DAG Error) only exist with Claymore binaries.
Change ETH binaries and there is no error at all using a 3GB 1060.
No dual mining though but im fine with that.
Hey. Tell me how to change binaries ETH or where i can read about it, please? Thanks Change ETH binaries and there is no error at all using a 3GB 1060.
No dual mining though but im fine with that.
For me the problem (DAG Error) only exist with Claymore binaries.
Change ETH binaries and there is no error at all using a 3GB 1060.
No dual mining though but im fine with that.
Change ETH binaries and there is no error at all using a 3GB 1060.
No dual mining though but im fine with that.
Jump to: