Pages:
Author

Topic: ETH miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk (Read 12887 times)

full member
Activity: 203
Merit: 168
If this doesn't work for you, try the chunked ethminer I posted above.

Quote
You need:
setx 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

full member
Activity: 214
Merit: 100
Hey guys,

I was just about to set up a ETH miner, but I always get the error, that the DAG file could not be allocated.

I use QtMiner on Windows 7 64 Bit with a HD 6950 (2GB).

Anyone has an idea what's the problem?

You need:
setx 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
full member
Activity: 203
Merit: 168
I fixed it!   at least it works for me.

I was having the same problem with a couple R9 270s and even (sometimes) a 7970 3Gb card.

I created ethminer-genoil-chunked: a fork of genoil's miner (from March) that includes a patch from equinox for chunked mining.  (The patch was for official ethminer but was never accepted.)  All my GPUs are busily mining eth again.

Sorry, no binaries.  You will need to compile it yourself.  Instructions are in the README.

happy mining.

anybody cured this problem yet, running r9 270 2gb, around 3am this morn it refused to mine ETH, miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk, tried all the setx options but still no joy.....

any info gratefully appreciated
newbie
Activity: 4
Merit: 0
Try the drivers listed at https://stream512.com/downloads . If that doesn't work on its own, try reducing the display resolution and otherwise following the instructions on the homepage of https://stream512.com .

Disclaimer: obviously, I run that site. Thought it would be helpful for you though.
sr. member
Activity: 882
Merit: 251
anybody cured this problem yet, running r9 270 2gb, around 3am this morn it refused to mine ETH, miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk, tried all the setx options but still no joy.....

any info gratefully appreciated

The DAG file rises all the time. And if it hits the maximum ram of your card it stops mining.

Try to set GPU_MEMORY_ALLOCATION to 100%

yeah i tried that and it still refuses to mine eth, tried all variations of the following options as well but still no joy Sad

setx GPU_SINGLE_ALLOC_PERCENT=100
--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0

go on tell me to wake up and lose the x off setx haha its still too early Sad

I also haven't managed to get my cards running.

Someone told me to use this Catalyst version: http://support.amd.com/en-us/kb-articles/Pages/AMDCatalyst14-4WINReleaseNotes.aspx

He said it will work with it... but I don't wanna downgrade my catalyst just in case it could be possible that it will work then.

Maybe you should try this catalyst version and tell me if it solved the problem.

better option, i just got it mining eth once more by upgrading the catalyst to the latest release 17/03/16 ver 16.3.1 release Wink and dropping the "x" off setx

http://support.amd.com/en-us/download/desktop?os=Windows+7+-+64

hope this helps some other 2gb card miners Smiley
hero member
Activity: 1308
Merit: 508
anybody cured this problem yet, running r9 270 2gb, around 3am this morn it refused to mine ETH, miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk, tried all the setx options but still no joy.....

any info gratefully appreciated

The DAG file rises all the time. And if it hits the maximum ram of your card it stops mining.

Try to set GPU_MEMORY_ALLOCATION to 100%

yeah i tried that and it still refuses to mine eth, tried all variations of the following options as well but still no joy Sad

setx GPU_SINGLE_ALLOC_PERCENT=100
--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0

go on tell me to wake up and lose the x off setx haha its still too early Sad

I also haven't managed to get my cards running.

Someone told me to use this Catalyst version: http://support.amd.com/en-us/kb-articles/Pages/AMDCatalyst14-4WINReleaseNotes.aspx

He said it will work with it... but I don't wanna downgrade my catalyst just in case it could be possible that it will work then.

Maybe you should try this catalyst version and tell me if it solved the problem.
sr. member
Activity: 882
Merit: 251
anybody cured this problem yet, running r9 270 2gb, around 3am this morn it refused to mine ETH, miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk, tried all the setx options but still no joy.....

any info gratefully appreciated

The DAG file rises all the time. And if it hits the maximum ram of your card it stops mining.

Try to set GPU_MEMORY_ALLOCATION to 100%

yeah i tried that and it still refuses to mine eth, tried all variations of the following options as well but still no joy Sad

setx GPU_SINGLE_ALLOC_PERCENT=100
--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0

go on tell me to wake up and lose the x off setx haha its still too early Sad
hero member
Activity: 1308
Merit: 508
anybody cured this problem yet, running r9 270 2gb, around 3am this morn it refused to mine ETH, miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk, tried all the setx options but still no joy.....

any info gratefully appreciated

The DAG file rises all the time. And if it hits the maximum ram of your card it stops mining.

Try to set GPU_MEMORY_ALLOCATION to 100%
sr. member
Activity: 882
Merit: 251
anybody cured this problem yet, running r9 270 2gb, around 3am this morn it refused to mine ETH, miner clCreateBuffer(-61) GPU can't allocate the DAG in a single chunk, tried all the setx options but still no joy.....

any info gratefully appreciated
hero member
Activity: 1308
Merit: 508
I did so - but same problem.



Ignore the issue, its a bug but everything is working perfectly fine.

All right - thank you very much Smiley
legendary
Activity: 3808
Merit: 1723
I did so - but same problem.



Ignore the issue, its a bug but everything is working perfectly fine.
hero member
Activity: 1308
Merit: 508
I did so - but same problem.

legendary
Activity: 1176
Merit: 1015
Try this

--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0

One more question.

I have got 2 GPU's now. One 6970 and one 6950.
I get "Pool 0 not providing work fast enough" like every minute.

Is there any possibility to get the work faster or change to another pool?

I had the same problem already with one card.

Try higher/ lower difficulty port? Worth a try.
hero member
Activity: 1308
Merit: 508
Try this

--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0

One more question.

I have got 2 GPU's now. One 6970 and one 6950.
I get "Pool 0 not providing work fast enough" like every minute.

Is there any possibility to get the work faster or change to another pool?

I had the same problem already with one card.
legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
sometimes ive found i get errors if i start ethash while old dag files exist.

try deleting the dag files in %appdata%/local/ethashing
hero member
Activity: 1308
Merit: 508
Try this

--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0

Perfect, thank you.

Now it shows 620 Mh/s in the miner with no stale shares.
Pool also shows ~ 600 now Smiley
legendary
Activity: 3808
Merit: 1723
Try this

--vectors 1 --no-submit-stale --gpu-threads 1 --scan-time 2 --queue 0
hero member
Activity: 1308
Merit: 508
But all in all the pool anly shows 200-300 Mh/s... that's a bit low...
hero member
Activity: 1308
Merit: 508
You might be right. I have nearly exact 50% stale shares. So only 50% of the 1,3 Gh/s.

legendary
Activity: 3808
Merit: 1723
I have done some overclocking. I just started a miner and it does 1,3 Gh/s
And tomorrow I will have a second 6950 flashed to 6970.. so maybe something around 2,5 -3  Gh/S

Do you know a marketplace to trade DCR to BTC?

The  miner reports the incorrect hashrate should be half that. A 6950 will do 0.6Ghs. You can sell DCR at Bittrex.
Pages:
Jump to: