Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 276. (Read 784965 times)

I also have the same problem in the pool Crazypool.org, I put the -coin auto, but I still have the problem.

manual pool switch not working too. already crash after switch

Eth: New job #b22f175f from daggerhashimoto.eu.nicehash.com:3353; diff: 3436MH

Eth: Select pool (press key from 1 to 6)
* 1. daggerhashimoto.eu.nicehash.com:3353
  2. daggerhashimoto.usa.nicehash.com:3353
  3. ssl://eu1.ethermine.org:5555
  4. ssl://eu1.whalesburg.com:7777
  5. eth-eu1.nanopool.org:9999
  6. eth-eu2.nanopool.org:9999

Eth speed: 206.796 MH/s, shares: 0/0/0, time: 0:00
GPUs: 1: 29.765 MH/s (0) 2: 29.762 MH/s (0) 3: 28.223 MH/s (0) 4: 29.760 MH/s (0) 5: 29.759 MH/s (0) 6: 29.775 MH/s (0) 7: 29.753 MH/s (0)
Eth: Switching to pool: ssl://eu1.ethermine.org:5555

C:\PhoenixMiner>pause

Not fixed. Now, after switching from ETC to ETH, all shares become invalid.

We have just released PhoenixMiner 5.0d that should fix the problem that some are experiencing when switching from ETC to ETH mining. You can find the download link and the checksums in the first post of this thread.

The new features in this release are:

• Fixed problem with crashing or slowing down when switching from ETC to ETH mining

After hearing all the issues with 5.0c I figured I work with 4.9c. But I am having the same errors as the 4.8c I was using for a while:

Can someone please help me??

All starts great:

https://i.imgur.com/Q9Qt5zW.jpg
https://i.imgur.com/Q9Qt5zW.jpg
https://i.imgur.com/Q9Qt5zW.jpg

Then two minutes later 3 out of 4 GPUs get disabled:

CudaProgram.cu:271 unknown error

https://i.imgur.com/FR0xWiW.jpg
https://i.imgur.com/FR0xWiW.jpg
https://i.imgur.com/FR0xWiW.jpg

Man could you have used a crappier download site than MEGA? It failed four times and takes 25 minutes to download 5MB file. So dumb.

Having the same issue with restarts using version 5.0c.  All my 34 rigs are restarting after DEVFee disconnects. Never had these kind of issues with 4.9c
I'm using simplemining ( linux ) with amd18.20 drivers


DevFee: GPU6: DevFee share found!
DevFee: Share actual difficulty: 5672 MH
DevFee: Share accepted in 43 ms
DevFee: Disconnected and stopped
GPU5: Starting up... (0)
GPU3: Starting up... (0)
GPU2: Starting up... (0)
GPU4: Starting up... (0)
GPU6: Starting up... (0)
GPU1: Starting up... (0)
GPU5: Allocating DAG for epoch #340 (3.66) GB
GPU5: Generating DAG for epoch #340
GPU3: Allocating DAG for epoch #340 (3.66) GB
GPU3: Generating DAG for epoch #340
GPU2: Allocating DAG for epoch #340 (3.66) GB
GPU2: Generating DAG for epoch #340
GPU4: Allocating DAG for epoch #340 (3.66) GB
GPU4: Generating DAG for epoch #340
=======and here it crashes =========


and here it is the last part from the DEBUG Dmesg data :


 1159.100648] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[ 1159.100649] Node 0 hugepages_total=128 hugepages_free=128 hugepages_surp=0 hugepages_size=2048kB
[ 1159.100649] 97718 total pagecache pages
[ 1159.100650] 0 pages in swap cache
[ 1159.100650] Swap cache stats: add 0, delete 0, find 0/0
[ 1159.100651] Free swap = 0kB
[ 1159.100651] Total swap = 0kB
[ 1159.100651] 967180 pages RAM
[ 1159.100652] 0 pages HighMem/MovableOnly
[ 1159.100652] 37451 pages reserved
[ 1159.100652] 0 pages cma reserved
[ 1159.100652] 0 pages hwpoisoned
[ 1159.127897] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.127932] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.127984] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128012] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128040] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.
[ 1159.128068] amdgpu_mn_invalidate_range_start_gfx+0x0/0x140 [amdgpu] callback failed with -11 in non-blockable context.

Many thanks for your answer

Smells like bug in 5.0X. Maybe PhoenixMiner should restart when switching the pools or coin and -dagrestart 1 is specified.

After upgrading to version 5.0c I also ran into a problem. I have cards with 4 GB of VRAM, the worker has 4 GB of RAM and runs on Linux, and I mine Ethash on NiceHash. During the switching from ETC to ETH the miner process is killed by OOM killer. On version 4.9c this doesn't happen.

add -coin ETH

I have change to PPS+ ETH, but I cannot connect, where I'm making the mistake…

 -pool eu.crazypool.org:3333 -wal ./ -pass x -proto 4 -tstop 75 -ttli 73 -tstart 55


It was working perfect before on the PPS+ ETC:

 -pool eu.crazypool.org:7000 -wal ./ -pass x -proto 4  -tstop 75 -tstart 55



Many thanks in advance...

manual pool switch same trouble. miner crash. dagrestart options add in bat file. add logs

2020.06.06:08:48:40.048: main
2020.06.06:08:48:40.048: main Eth: Select pool (press key from 1 to 6)
2020.06.06:08:48:40.048: main * 1. daggerhashimoto.eu.nicehash.com:3353
2020.06.06:08:48:40.048: main   2. daggerhashimoto.usa.nicehash.com:3353
2020.06.06:08:48:40.048: main   3. ssl://eu1.ethermine.org:5555
2020.06.06:08:48:40.048: main   4. ssl://eu1.whalesburg.com:7777
2020.06.06:08:48:40.048: main   5. eth-eu1.nanopool.org:9999
2020.06.06:08:48:40.048: main   6. eth-eu2.nanopool.org:9999
2020.06.06:08:48:40.048: main
2020.06.06:08:48:41.254: main Eth: Switching to pool: ssl://eu1.ethermine.org:5555

and crash without log record

use nicehash
no devfee change. return to main pool. dont know what coin before crash

Does it crash on epoch change switch or on Devfee mining switch? If it is on epoch change use -dagrestart 1. DO you mine ETC or ETH? What is your pool?

plz help. have stable trouble on different version/

miner crash then switch to main pool
different drivers different windows version 1703 1709 1607 drivers 18.3.4 18.6.1 18.12.1.1
different amd card 470 480 570 580 4\8 gb different vendor. stable work on claymore without restart and crash....

check log. all ok but crash on switch
run as admin

The problem is not the version... there are the new Nvidia Drivers. The best drivers Nvidia drivera are 442.59 ... de 445.87 are also really good they allow more overclock but hangs the computer.

Phoenix Miner 5.0c Windows/msvc - Release build
CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 1080 Ti (pcie 1), CUDA cap. 6.1, 11 GB VRAM, 28 CUs
NVML error in CudaProgram.cu:83 : Unknown Error (999)
Unable to initialize NVML


I'm getting 33 MH/s ... what i have wrong?

What hash rate were you getting with your 1080ti? Im currently getting around 44mhs. With claymore i would get up to 48mhs using the OhGodAnETHlargementPill script. Not sure what hashrate to expect with Phoenix? Phooenix seems to run a bit more stable.

Thanks

I have crashes with 5.0b and GTX1080Ti (11GB VRAM), driver 446.14.

CUDA error in CudaProgram.cu:456 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.

Display driver nvlddmkm stopped responding and has successfully recovered.

This was not happening with older versions.
Could you please advise.