Topic: Phoenix miner clCreatebuffer (-61) (Read 94 times)

I talked about that here

https://bitcointalksearch.org/topic/m.56080332

Have you heard about OpenCL problems when a file larger than 4 GB is loaded into the video card memory?
Update the drivers from the AMD website and enable the compute mode.
If I'm not mistaken, the OpenCL issue was resolved in July 2020, and you can use any drivers newer than that date.

And why clkernel 0? i think this command is not needed or why you want to start with generic kernels? If the miner make problem without this command, then you have maybe another problem. CClock is also low. Can you start with more voltage or without oc? Does it work?

By the way - teamredminer or lolminer is the better option for miner -> give more poolside hashrate.

ive found the problem and the solution was:
''-clKernel 0''
i removed that from the startup and let them run untill the 'dag' was generated.
i closed phoenix miner and added ''-clKernel 0'' again and now it started up good.

(if i dont add ''-clKernel 0' i get the 'clsetkernelarg -48' error.)

Hello im using Phoenix 5.5c & 5.6d and getting the error clCreatebuffer (-61)

ive got 3 cards

rx 590 MSI oc 8gb
rx 580 asrock oc 8gb
rx 570 asus strix oc 8gb

Ive changed the bios with PolarisBiosEditor 1.7.5, 1click patch

Next ive installed the drivers Win10-64Bit-Radeon-Software-Adrenalin-2019-Edition-19.8.2-Aug26
and the driver patch atikmdag-patcher 1.4.9

Phoenix miner startup settings are:
 -clKernel 0 -mode 1 -fanmin 30 -fanmax 96 -cclock 1000 -mclock 2000 -cvddc 850 -mvddc 850 -acm -coin eth

then it shows:

No CUDA driver found
OpenCL driver version: 19.8.2/9.1-2
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
GPU3: Radeon RX 590 Series (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: ssl://eu1.ethermine.org:5555
Starting GPU mining
GPU1: AMD driver 19.8.2
GPU2: AMD driver 19.8.2
GPU3: AMD driver 19.8.2
GPU1: set GPU clocks to 1000 MHz (Vddc 850 mV)
GPU1: set VMEM clocks to 2000 MHz (Vddc 850 mV)
GPU2: set GPU clocks to 1000 MHz (Vddc 850 mV)
GPU2: set VMEM clocks to 2000 MHz (Vddc 850 mV)
GPU3: set GPU clocks to 1000 MHz (Vddc 850 mV)
GPU3: set VMEM clocks to 2000 MHz (Vddc 850 mV)
Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy)
GPU1: 28C 0% 4W, GPU2: 27C 19% 7W, GPU3: 28C 30% 21W
GPUs power: 32.6 W
Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (172.65.207.106)
Eth: New job #16f94a88 from ssl://eu1.ethermine.org:5555; diff: 4295MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #429
GPU2: Starting up... (0)
GPU3: Starting up... (0)
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #d811547b from ssl://eu1.ethermine.org:5555; diff: 4295MH
Eth: New job #7342f660 from ssl://eu1.ethermine.org:5555; diff: 4295MH
Eth: New job #288739f9 from ssl://eu1.ethermine.org:5555; diff: 4295MH
Light cache generated in 4.3 s (16.1 MB/s)
Eth: New job #9ae03d6b from ssl://eu1.ethermine.org:5555; diff: 4295MH
GPU1: Using generic OpenCL kernels
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Allocating DAG for epoch #429 (4.35) GB
GPU1: Allocating buffers failed with: clCreateBuffer (-61).
Fatal error detected. Restarting.
Eth: New job #110135b2 from ssl://eu1.ethermine.org:5555; diff: 4295MH
GPU2: Using generic OpenCL kernels
GPU2: Free VRAM: 7.948 GB; used: 0.052 GB
GPU2: Allocating DAG for epoch #429 (4.35) GB
GPU2: Allocating buffers failed with: clCreateBuffer (-61).
Eth: New job #417f2863 from ssl://eu1.ethermine.org:5555; diff: 4295MH
GPU3: Using generic OpenCL kernels
Eth: New job #84edd62c from ssl://eu1.ethermine.org:5555; diff: 4295MH
GPU3: Free VRAM: 7.948 GB; used: 0.052 GB
GPU3: Allocating DAG for epoch #429 (4.35) GB
GPU3: Allocating buffers failed with: clCreateBuffer (-61).

And then the program shut itself down.Does anyone have a solution for this problem?