nanopool / Claymore-Dual-Miner

Claymore's Dual Ethereum+Decred_Siacoin_Lbry AMD+NVIDIA GPU Miner
1.12k stars 276 forks source link

CUDA error 11 - cannot write buffer for DAG #207

Open Ablazed1 opened 6 years ago

Ablazed1 commented 6 years ago

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)

nikusworld commented 6 years ago

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.

ZhongOu commented 6 years ago

How you make 35 gb file and where to do that?

SicKMinD37 commented 6 years ago

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

theebuddylee commented 6 years ago

I ran into the issue on an all 1070 8GB rig. Had to update to 11.7 and increase virtual to 20GB. Very strange

pioniere commented 6 years ago

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.

victovmb commented 6 years ago

-lidag 1 on my gtx 1070 resolved. thank you

fastminer789 commented 6 years ago

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. 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.

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 setx GPU_MAX_HEAP_SIZE 100 setx GPU_USE_SYNC_OBJECTS 1 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_SINGLE_ALLOC_PERCENT 100 -eres 0 EthDcrMiner64.exe -epool eth-us-east1.nanopool.org:9999 -ewal 0xdcaddaf45a2cf1bae51e4c5daa9584c88235633b worker/email -eres 0 -epsw x -dcoin pasc -dpool pasc-us-east1.nanopool.org:15555 -dwal 573196-86.0 workername/email -dpsw x -ftime 10

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

;

prman561 commented 6 years ago

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

hosseinraaad commented 6 years ago

I had the same problem that fixed by c++ redist. Try it http://bit.ly/2KmpUcF

jdcryptoanon commented 6 years ago

Hi everyone,

I was tracking down this issue for a long time. I finally resolved it 5 minutes ago.

8 gpu rig (1070's) Windows 10 2 850w PSU's 8gb ram

  1. Reset windows https://www.laptopmag.com/articles/reset-windows-10-pc
  2. Set paging file to min16000- max30000
  3. Install latest NVidia drivers 988.2 as of August 2018.
  4. Install Claymore 11.9
  5. Enable (Allow access) through windows defender if the firewall message pops up the first time you run the miner (see below for what happened to me and caused something to be blocked by the firewall)
  6. Here are my claymore settings: EthDcrMiner64.exe -epool ssl://us2.ethermine.org:5555 -ewal [minder address] -mode 1 -lidag 1

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!!! ETH: 0xd029a5Fa47d499e56Df257a2e73617E2Ae84290B

aaronllowe commented 6 years ago

Try the command after the pools: -allpools 1

aaronllowe commented 6 years ago

I mean the pool config

Blisk commented 4 years ago

I tried all but it doesn't help, still have this error! Waiting for a solution!

jdcryptoanon commented 4 years ago

I tried all but it doesn't help, still have this error! Waiting for a solution!

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"

Blisk commented 4 years ago

It is fresh installed win 10

ferraroroberto commented 3 years ago

I got the same problem today with a Nvidia GTX 1070 8Gb, solved adding the option -eres 0

tdohertyau commented 3 years ago

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%

AliceMargatriod commented 3 years ago

got the same problem today with gtx 1080 8Gb, solved adding the -eres 0

arn3d commented 3 years ago

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.

stefi01 commented 3 years ago

-eres 0 worked for me with 1070's thanks :)

ShadowOfTheDamn commented 3 years ago

Hi everybody adding the -eres 0 first cleared the error for me but now I get: CUDA error 77 - cannot write buffer for DAG I have 4x1060 6Gb any help is appreciated.

stefi01 commented 3 years ago

i had same issue last night so i removed the -eres 0 and then it worked again

ferraroroberto commented 3 years ago

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..

Blisk commented 3 years ago

I start to use other miners withouth a dag problem and I use 4Gb vram