Quote from: wolverine5pl on Today at 07:24:13 AM

Quote from: AzzAz on January 08, 2021, 05:26:10 PM

Quote from: reep74 on January 08, 2021, 04:26:12 PM

Quote from: bit-sokol on January 08, 2021, 04:23:02 PM

Quote from: reep74 on January 08, 2021, 04:16:13 PM

Quote from: dedizones on January 08, 2021, 03:40:26 PM

Quote from: bit-sokol on January 08, 2021, 03:33:45 PM

Quote from: reep74 on January 08, 2021, 03:31:21 PM

Quote from: CraigWrightGo2016 on January 08, 2021, 03:25:44 PM

Quote from: reep74 on January 08, 2021, 03:13:21 PM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG 22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG 65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
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) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

Same problem, delete all and paste what you write and same vram problem, today was working fine, i did not update nothing and stop mining

go back and read few post, I had same problem post #7311 ( https://bitcointalk.org/index.php?topic=2647654.msg56049534#msg56049534 )
Also, windows 20.4 with PM 5.4c and AMD 20.11.2 working nice

+merit if solved

try increasing virtual memory. i have 2 gpus vega 56. increased from 32 to 40gb and its fine

Quote from: Chromexnet on January 08, 2021, 10:07:00 PM

Quote from: smc_masters on January 08, 2021, 08:00:44 PM

Quote from: AzzAz on January 08, 2021, 05:26:10 PM

Quote from: reep74 on January 08, 2021, 04:26:12 PM

Quote from: bit-sokol on January 08, 2021, 04:23:02 PM

Quote from: reep74 on January 08, 2021, 04:16:13 PM

Quote from: dedizones on January 08, 2021, 03:40:26 PM

Quote from: bit-sokol on January 08, 2021, 03:33:45 PM

Quote from: reep74 on January 08, 2021, 03:31:21 PM

Quote from: CraigWrightGo2016 on January 08, 2021, 03:25:44 PM

Quote from: reep74 on January 08, 2021, 03:13:21 PM

GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH

I have that problem, virtual memory in 40.000.

Try to add -gser 2

SAME BRO, same problem

you need to find the optimal value for the -gser command for your gpus.
Example:
PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2

or

Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably.

In config.txt add:

-rvram -1

And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem

Same but i saw this: GPU4: DAG 22%
Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU3: DAG 65%
GPU2: DAG generated in 8.0 s (517.9 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
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) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0)
GPU5: Free VRAM: 7.948 GB; used: 0.052 GB

try to add this:

PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1

Same problem, delete all and paste what you write and same vram problem, today was working fine, i did not update nothing and stop mining

go back and read few post, I had same problem post #7311 ( https://bitcointalk.org/index.php?topic=2647654.msg56049534#msg56049534 )
Also, windows 20.4 with PM 5.4c and AMD 20.11.2 working nice

+merit if solved

Got the same problem today.
On 3 miners.
2 miners with Rx580's and a 3rd one with Vegas.
All of them showing the same not enough vram and gpu1 error.
I updated to the latest edition of phoenix but its still the same..
Could this be a drivers or windows update issue?

I had the same issue on my RX580 8GB (clSetKernelArg (-48)). I reinstalled AMD driver software (Adrenalin version 20.8.1) with factory reset option enabled and the issue is gone. I also turned off automatic updates from the Adrenalin settings since I suspect it had auto-updated something. So to fix the issue I suggest you reinstall your drivers to some old version that you know has worked fine before.

@PhoenixMiner Could you take a look at what is causing the clSetKernelArg (-48) issue with the auto-updated AMD driver? It seems to repro at least with RX580 8GB cards.

Was fine today running my 2 Radeon VII cards on Phoenix Miner 5.4c AMD driver 20.4.2
turned off miners to do some clean up, but didnt shut off windows
tried to restart miners and getting clSetKernelArg (-48) error

eventually found Windows was sneaky and updated the radeon drivers
rolled back driver and good to go again.

Worth a try for Windows 10 plebs
You can try and use local group policy to prevent windows from updating drivers via windows updates
If you are using windows home for some reason you will need to find a guide on installing group policy editor on windows home.
open Gpedit.msc
expand Computer configuration > Administrative templates > Windows Components > Windows update
There should be a setting that says "Do not include drivers with Windows Updates"
Enabled that.
Or just Enable "Remove access to use all Windows Update Features" all together.