 Show Posts
|
|
Pages: [1]
|
I have a RX 5700 XT MIS Mech 8gb Windows 10.
It runs fine for 1-12 hours then cuts back to 47mh/s. I have tried adjusting the clock/mem down with a starting hashrate from 57mh/s down to 52mh/s(almost stock). 1230-1340 clock and 1750-1896 mem, all do this reset to 47mh/s...
Any idea why this card would randomly cut back to 47mh/s or a way to diagnose it? A restart of the software does not work I have to reboot the computer. I have 2 RX 570 8gb running with they card at 31mh/s and they are not affected.
Thanks
Put another fan on it cooling it....sounds like thermal throttling. Probably more the thermal pads? Just guessing I dont own that card but saw on YT a lot of videos with the pads on the 3080? Anyways hope you get it to work |
|
|
|
|
HI,
i tried searching for an answer but did not found so sorry if it was already addressed.
I am running straps but i want to use Afterburn again to OC my Nvidia cards but afterburn is grey out or disabled any ideas?
Using 5.5c
thanks
|
|
|
|
A little at a lost here. I have two identical rigs with each 6 - 1060/6gb/p106, Same windows updates same NVIDIA driver both startup phoenixminer in adminmode 1 is working with the straps option the other crashes as soon the straps are applied. Hope someone can point something out as i am at a loss :S 021.02.05:15:36:57.545: main Phoenix Miner 5.5c Windows/msvc - Release build
2021.02.05:15:36:57.545: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal xxx.xxx -proto 3 -nvidia -minRigSpeed 130 -log 1 -logsmaxsize 100 -rmode 2
2021.02.05:15:36:57.701: main CUDA version: 10.0, CUDA runtime: 8.0
2021.02.05:15:36:57.706: main Available GPUs for mining:
2021.02.05:15:36:57.706: main GPU1: P106-100 (pcie 1), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2021.02.05:15:36:57.706: main GPU2: P106-100 (pcie 3), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2021.02.05:15:36:57.706: main GPU3: P106-100 (pcie 4), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2021.02.05:15:36:57.706: main GPU4: P106-100 (pcie 5), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2021.02.05:15:36:57.706: main GPU5: P106-100 (pcie 6), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2021.02.05:15:36:57.706: main GPU6: P106-100 (pcie 7), CUDA cap. 6.1, 5.9 GB VRAM, 10 CUs
2021.02.05:15:36:57.713: main NVML library initialized
2021.02.05:15:36:57.799: main Nvidia driver version: 432.00
2021.02.05:15:36:57.802: main NVAPI error in NvapiWrapper.c:320 : -6
2021.02.05:15:36:58.103: main Eth: the pool list contains 2 pools (2 from command-line)
2021.02.05:15:36:58.103: main Eth: primary pool: ssl://eu1.ethermine.org:5555
2021.02.05:15:36:58.103: main Starting GPU mining
...
2021.02.05:15:36:48.133: GPU3 GPU3: Using v3 Ethash CUDA kernels (P106-100)
2021.02.05:15:36:48.138: GPU5 GPU5: Using v3 Ethash CUDA kernels (P106-100)
2021.02.05:15:36:48.138: GPU2 GPU2: Using v3 Ethash CUDA kernels (P106-100)
2021.02.05:15:36:48.138: GPU4 GPU4: Using v3 Ethash CUDA kernels (P106-100)
2021.02.05:15:36:48.139: GPU6 GPU6: Using v3 Ethash CUDA kernels (P106-100)
etc..
|
|
|
|
|
tried the 3.0 beta have 6x 1060 GB pulling 30watts total more without hash increase. switched back to 2.9e for now
|
|
|
|
Got a weird error today after windows update. See below out of mem error. Mining Win10 with 6x 1060 6GB and 16GB PageFile. Resolve it finally by increasing the page file to 24GB. Hope this helps others. 2018.05.27:10:37:56.494: main Phoenix Miner 2.9e Windows/msvc - Release
2018.05.27:10:37:56.494: main Cmd line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal XXX -proto 3
2018.05.27:10:37:59.271: main Available GPUs for mining:
2018.05.27:10:37:59.272: main GPU1: GeForce GTX 1060 6GB (pcie 1), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU2: GeForce GTX 1060 6GB (pcie 2), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU3: GeForce GTX 1060 6GB (pcie 4), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU4: GeForce GTX 1060 6GB (pcie 6), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU5: GeForce GTX 1060 6GB (pcie 8), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.272: main GPU6: GeForce GTX 1060 6GB (pcie 9), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
2018.05.27:10:37:59.283: main NVML library initialized
2018.05.27:10:37:59.506: main Listening for CDM remote manager at port 3333 in read-only mode
2018.05.27:10:37:59.508: main Eth: the pool list contains 4 pools
2018.05.27:10:37:59.508: main Eth: primary pool: eu1.ethermine.org:4444
2018.05.27:10:37:59.508: main Starting GPU mining
2018.05.27:10:37:59.509: wdog Starting watchdog thread
2018.05.27:10:37:59.509: main Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: QtMiner)
2018.05.27:10:37:59.544: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (94.23.36.128)
2018.05.27:10:37:59.544: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["XXX"]}
2018.05.27:10:37:59.573: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2018.05.27:10:37:59.573: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.05.27:10:37:59.591: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":2018.05.27:10:37:59.591: eths Eth: New job #7d15954f from eu1.ethermine.org:4444; diff: 4000MH
2018.05.27:10:37:59.592: GPU1 GPU1: Starting up... (0)
2018.05.27:10:37:59.592: GPU1 Eth: Generating light cache for epoch #189
2018.05.27:10:37:59.594: GPU2 GPU2: Starting up... (0)
2018.05.27:10:37:59.595: GPU3 GPU3: Starting up... (0)
2018.05.27:10:37:59.598: GPU4 GPU4: Starting up... (0)
2018.05.27:10:37:59.601: GPU5 GPU5: Starting up... (0)
2018.05.27:10:37:59.602: GPU6 GPU6: Starting up... (0)
2018.05.27:10:37:59.711: main GPU1: 38C 0%, GPU2: 35C 0%, GPU3: 37C 0%, GPU4: 46C 0%, GPU5: 42C 0%, GPU6: 42C 0%
2018.05.27:10:38:00.985: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":
2018.05.27:10:38:00.985: eths Eth: New job #992bc07d from eu1.ethermine.org:4444; diff: 4000MH
2018.05.27:10:38:02.597: GPU6 GPU6: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.625: GPU5 GPU5: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.625: GPU1 GPU1: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.662: GPU2 GPU2: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.666: GPU4 GPU4: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.681: GPU6 GPU6: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.715: GPU1 GPU1: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.756: GPU5 GPU5: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.780: GPU4 GPU4: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.805: GPU2 GPU2: Allocating light cache buffer (39.9) MB; good for epoch up to #191
2018.05.27:10:38:02.895: GPU6 GPU6: Generating DAG for epoch #189
2018.05.27:10:38:02.906: GPU3 GPU3: Allocating DAG (2.49) GB; good for epoch up to #191
2018.05.27:10:38:02.941: GPU1 GPU1: Generating DAG for epoch #189
2018.05.27:10:38:02.969: GPU5 GPU5: Generating DAG for epoch #189
2018.05.27:10:38:02.992: GPU4 GPU4: Generating DAG for epoch #189
2018.05.27:10:38:03.020: GPU2 GPU2: Generating DAG for epoch #189
[color=red]2018.05.27:10:38:03.099: GPU3 CUDA error in CudaProgram.cu:377 : out of memory (2)
2018.05.27:10:38:03.103: GPU3 GPU3: CUDA memory: 6.00 GB total, 4.97 GB free
2018.05.27:10:38:03.103: GPU3 GPU3 initMiner error: out of memory
2018.05.27:10:38:03.597: wdog Thread(s) not responding. Restarting.[/color]
2018.05.27:10:38:04.557: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2018.05.27:10:38:04.557: main 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)
2018.05.27:10:38:04.592: GPU6 GPU6: DAG 13%
2018.05.27:10:38:04.650: GPU5 GPU5: DAG 13%
2018.05.27:10:38:04.686: GPU4 GPU4: DAG 13%
2018.05.27:10:38:04.703: GPU2 GPU2: DAG 13%
2018.05.27:10:38:04.744: GPU1 GPU1: DAG 13%
|
|
|
|
|
when can we expect an exchange listing and get added to the main stream coin calculators?
|
|
|
|
|
Please add -coin support for ETHO.
thanks
|
|
|
|
For now i have never problem with PhoenixMiner. Now i have a problem with this: I using PM 2.9e2018.05.13:10:26:26.668: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.13:10:26:26.668: GPU2 GPU2 search error: unspecified launch failure
2018.05.13:10:26:26.678: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.13:10:26:26.678: GPU5 GPU5 search error: unspecified launch failure
2018.05.13:10:26:26.694: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.13:10:26:26.694: GPU3 GPU3 search error: unspecified launch failure
2018.05.13:10:26:26.709: wdog Thread(s) not responding. Restarting.
2018.05.13:10:26:26.725: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.13:10:26:26.725: GPU6 GPU6 search error: unspecified launch failure
2018.05.13:10:26:26.725: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.05.13:10:26:26.725: GPU1 GPU1 search error: unspecified launch failure
2018.05.13:10:26:26.756: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
My settings are same all time. I have gtx 1070 (8gb) gpus. How to solve this problem any idea? try lowering the GPU2 overclock settings a bit, looks like that is the card that is causing the issue |
|
|
|
 Getting good results from 2.9e. thank you dev team |
|
|
|
What is the best version for nVidia driver to run PhoenixMiner 2.8c or 2.9d?
I open multiple instances to run claymore on RX580 and Phoenix on GTX1070/1060 on the same rig, right?
Use two instances of Phoenix (or maybe you can specify which kernel for which GPU?) 1 for your AMD and another for your NVIDIA? |
|
|
|
Hi, just downloaded 2.9b and copied over my startup.bat but for some reason i am getting ID "0" in the mining pool overview instead of the worker name specified in the command. http://beta-pirl.pool.sexy/#/account/0x7D7764c9D0EC722e246E1b717A7e11Aad08ACe9fmy start.bat file 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 PhoenixMiner.exe -pool beta-pirl.pool.sexy:10052 -wal 0x7D7764c9D0EC722e246E1b717A7e11Aad08ACe9f -worker miner1 -coin pirl -nvidia -minRigSpeed 120 -log 0 -cdm 1 -cdmport 3333 -rmode 2 -mi 14 pause Thank you for reporting this, the problem is fixed and an updated beta (2.8d) has now replaced 2.8b. You can find it at the same location (see this post: https://bitcointalk.org/index.php?topic=2647654.msg34449237#msg34449237). Could performance on Baffin (RX 460/560) be improved?
I have a system with a Baffin card and got around 11 Mh/s while Claymore's gives 14 Mh/s.
Try to change the -gt parameter (the default is 15), or try using the command line option -clkernel 2 (only works with the latest beta version few posts above). thanks man -worker name is resolved for me! now thats what i call support !!! |
|
|
|
Hi, just downloaded 2.9b and copied over my startup.bat but for some reason i am getting ID "0" in the mining pool overview instead of the worker name specified in the command. http://beta-pirl.pool.sexy/#/account/0x7D7764c9D0EC722e246E1b717A7e11Aad08ACe9fmy start.bat file 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 PhoenixMiner.exe -pool beta-pirl.pool.sexy:10052 -wal 0x7D7764c9D0EC722e246E1b717A7e11Aad08ACe9f -worker miner1 -coin pirl -nvidia -minRigSpeed 120 -log 0 -cdm 1 -cdmport 3333 -rmode 2 -mi 14 pause |
|
|
|
i think my one nvidia based rig is having a similar issue. it's running 2.8c.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
this is what's happening.  normally something like this would just trigger the watchdog, but it crashes in windows and just hangs. so it cant restart itself. lower the OC on GPU 7, i had the same issue working stable now |
|
|
|
not sure if already mentioned but there is an typo when starting your miner  |
|
|
|
When this happens, what do you guys do?  |
|
|
|
|
HI, is there an option to have my rig reboot i the speed drops below a set point?
I see that you can restart the miner but i want to restart the rig.
thanks, Robin
|
|
|
|
|
