 Show Posts
|
|
Pages: [1]
|
Why doesnt this work anymore?
phoniex miner cant set memory clock delta -137
I get the above error when trying to do this: -mclock +1000,+1000,+1250,+950,+1000,+1000,+1000,+950
did you run phoenixminer as administrator? |
|
|
|
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. Use hwinfo to monitor temps particularly the memory junction temps. From what i heard, Mechs are terrible at at cooling memory. Should be below 100c. |
|
|
|
Is there any way to delay the application of overclock on the core during dag creation. I know its possible on the memory with -mcdag but Im having issues on the coreclock during dag creation process. I know increasing memory will increase the hashrate but in my case, increasing the coreclock increases the hashrate as well. Weirdly it only happens on my gtx 1070.
Have you tried using -lidag 3 or 2 or 1. 0 is default but it slows down dag creation and may solve your issue. i have tried -lidag already. Same issue |
|
|
|
|
Is there any way to delay the application of overclock on the core during dag creation. I know its possible on the memory with -mcdag but Im having issues on the coreclock during dag creation process. I know increasing memory will increase the hashrate but in my case, increasing the coreclock increases the hashrate as well. Weirdly it only happens on my gtx 1070.
|
|
|
|
I cannot get Pheonix to work more than 4-6 houirs without crashing. Errors 216, 219, 462, 999 All sorts of errors.
I have the latest 461.09 Nvidia drivers. Do I need to downgrade my drivers?
I was mining in my computer with a Gigabyte Geforce RTX 3060Ti 5.5c since february 9th and it was ok. Later, I swaped to a MSI Geforce RTX 3070 on February 12th and it was ok, but a couple of days after that I started to see problems. Since then, I've seen it starts to mine for a couple of minutes (or a couple of hours, I actually can't get the time pattern here), then shows some artifacts on the screen (  ) and crashes, rebooting the PC. I was always working with Nvidida drivers 461.40. Right now I'm downgrading to 457.51 version for testing that. Anyone have an idea what could be happening here? Looking into the log files, I see that sometimes it stops randomly (the file ends there) without giving any error. But sometimes the files show some kind of errors like these: 2021.02.12:18:55:39.192: GPU1 CUDA error in CudaProgram.cu:465 : unknown error (999)
2021.02.12:18:55:39.196: GPU1 GPU1 search error: unknown error
2021.02.12:18:55:39.198: wdog Fatal error detected. Restarting.
2021.02.12:18:55:41.188: main Eth speed: 0.000 MH/s, shares: 63/0/0, time: 1:22
2021.02.12:18:55:42.057: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xb10f847382424686ae3e90635f73a18f98cd9c03647a002baea49dd900e2345e","0xecea8576ebef188c15f64731e7a9f84c1cb41d85516730fa7b0bab88c4feb506","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb4bb50"]}
2021.02.12:18:55:42.057: eths Eth: New job #b10f8473 from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.12:18:55:42.505: hwmc GPU1: unable to get temperature - Unknown Error (999)
2021.02.12:18:55:42.633: main GPU1: 60%
2021.02.12:18:55:43.945: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2fdb5f38896382e201c369209b6ff9b8b9d4cc06ece2f3ddeaebed496b40b75c","0xecea8576ebef188c15f64731e7a9f84c1cb41d85516730fa7b0bab88c4feb506","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb4bb51"]}
2021.02.12:18:55:43.945: eths Eth: New job #2fdb5f38 from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.12:18:55:44.252: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x41609475f936b4a4e238f52b00e780bc7cbfa5358854e3326f861b2d21d8b3ca","0xecea8576ebef188c15f64731e7a9f84c1cb41d85516730fa7b0bab88c4feb506","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb4bb51"]}
2021.02.12:18:55:44.252: eths Eth: New job #41609475 from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:13:09:01.748: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
2021.02.21:13:09:01.749: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x750cea9c12d42b76b61c980a1545bd6e693bc7a12490a4fbc1083869283a8cf9","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb5994f"]}
2021.02.21:13:09:02.096: GPU1 CUDA error in CudaProgram.cu:465 : unknown error (999)
2021.02.21:13:09:02.096: gps1 CUDA error in CudaProgram.cu:267 : unknown error (999)
2021.02.21:13:09:02.097: GPU1 GPU1 search error: unknown error
2021.02.21:13:09:02.098: wdog Fatal error detected. Restarting.
2021.02.21:13:09:02.423: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2b6ce5fb860f98940c532b9207a559d08f20d0efcccb9f00fc47f181aa72faad","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb59950"]}
2021.02.21:13:09:02.423: eths Eth: New job #2b6ce5fb from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:13:09:02.615: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x5bc91187170c303dc2947e1d5bbf2fa2e1ab911a1eba6aa6a2544141b6e74663","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb59950"]}
2021.02.21:13:09:02.616: eths Eth: New job #5bc91187 from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:13:09:03.901: main Eth speed: 0.000 MH/s, shares: 22/0/0, time: 0:31
2021.02.21:13:09:06.560: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xd385ea208d4bdb8d78b958c948bc6dbb1fe88301a2d1f00d96c2d24db58dc111","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb59950"]}
2021.02.21:13:09:06.560: eths Eth: New job #d385ea20 from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:13:11:39.238: main *** 0:02 *** 2/21 13:11 **************************************
2021.02.21:13:11:39.238: main Eth: Mining ETH on ssl://us1.ethermine.org:5555 for 0:02
2021.02.21:13:11:39.238: main Eth: Accepted shares 3 (0 stales), rejected shares 0 (0 stales)
2021.02.21:13:11:39.238: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2021.02.21:13:11:39.238: main Eth: Maximum difficulty of found share: 19.0 GH (!)
2021.02.21:13:11:39.238: main Eth: Average speed (5 min): 51.916 MH/s
2021.02.21:13:11:39.238: main Eth: Effective speed: 88.89 MH/s; at pool: 88.89 MH/s
2021.02.21:13:11:39.238: main
2021.02.21:13:11:40.643: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x6f7620ad2471b23fd6b810b1bf83867bdf536129eadb7e361ffcdc4cdfdaddb3","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb5995e"]}
2021.02.21:13:11:40.643: eths Eth: New job #6f7620ad from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:13:11:41.831: gps1 CUDA error in CudaProgram.cu:267 : unknown error (999)
2021.02.21:13:11:41.831: GPU1 CUDA error in CudaProgram.cu:465 : unknown error (999)
2021.02.21:13:11:41.831: GPU1 GPU1 search error: unknown error
2021.02.21:13:11:41.831: wdog Fatal error detected. Restarting.
2021.02.21:13:11:42.392: main Eth speed: 0.000 MH/s, shares: 3/0/0, time: 0:02
2021.02.21:13:11:44.014: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2021.02.21:13:16:11.849: main Eth speed: 51.915 MH/s, shares: 0/0/0, time: 0:00
2021.02.21:13:16:14.511: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x9830b31ad6f538da3773ddb39e70c534aaa5e889b109a9e3aadeb0c7cd9da923","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb59977"]}
2021.02.21:13:16:14.511: eths Eth: New job #9830b31a from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:13:16:15.957: gps1 CUDA error in CudaProgram.cu:267 : unknown error (999)
2021.02.21:13:16:15.957: GPU1 CUDA error in CudaProgram.cu:465 : unknown error (999)
2021.02.21:13:16:15.957: GPU1 GPU1 search error: unknown error
2021.02.21:13:16:15.957: wdog Fatal error detected. Restarting.
2021.02.21:13:16:16.921: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2021.02.21:23:22:28.835: eths Eth: New job #36a2e139 from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:23:22:28.863: gps1 CUDA error in CudaProgram.cu:267 : unknown error (999)
2021.02.21:23:22:28.863: GPU1 CUDA error in CudaProgram.cu:465 : unknown error (999)
2021.02.21:23:22:28.863: GPU1 GPU1 search error: unknown error
2021.02.21:23:22:28.863: wdog Fatal error detected. Restarting.
2021.02.21:23:22:29.459: main Eth speed: 0.000 MH/s, shares: 5/0/0, time: 0:03
2021.02.21:23:22:31.819: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2021.02.21:23:22:31.820: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x39865a0","0x67726f38238f0422bcbefb08bd64b5dc32b6cb63381cb91d01ce8188ad102c54"]}
2021.02.21:23:22:32.000: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x36a2e139aee6782c36d135ed5bbc1cb936b23919f3ae3bcd69e89dc5bb9e48ca","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb5a474"]}
2021.02.21:23:22:32.776: hwmc GPU1: unable to get temperature - Unknown Error (999)
2021.02.21:23:22:32.844: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xf211f60e309aeb7087c64a517c4f4468360457d49c9390e855969b1ddb4966bd","0x6b7fe9651d4c13b078206f499a8bf24cfe4fb734f8627aa5eadf268f6b2c57ed","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xb5a474"]}
2021.02.21:23:22:32.844: eths Eth: New job #f211f60e from ssl://us1.ethermine.org:5555; diff: 4000MH
2021.02.21:23:22:32.900: main GPU1: 38%
2021.02.21:23:22:34.562: main Eth speed: 0.000 MH/s, shares: 5/0/0, time: 0:04
try changing your riser if you are using one |
|
|
|
I tried using -powlim option but it sets power limit on miner exit to 100%. Is there any way to prevent it from doing this, or even better to specify which limit I want ?
use -leaveoc in your bat file |
|
|
|
Again there was another DAG change and 3 out of 10 miners wen't offline.
Is this a known problem ?
Ubuntu 18.04.4 with AMD 20.20 drivers.
use -lidag to slow down the dag creation process and prevent crashes. I agree this is a good setting to try. I've used -lidag 3 and it does seem to help with the crashes during dag changes and also helped with crashing at startup I was having on an 11 gpu rig. But I still get crashes on some rigs during the dag change even with the lidag setting. if you dont want dag creation every 2 epoch change. use -eres to create a dag good for a number of epochs ahead. I use -eres 10 so dag will be processed after 10 epoch change. I haven't tried the -eres setting before (thought that was for 4GB issues but I'm wrong). I'll give it a try. Thank you.  eres has nothing to do with 4gb cards. We are currently on epoch 396 and my next dag creation process is on epoch 406 which is scheduled on april 14 of this year, almost 2 months   . This is according to dag calendar from minerstat |
|
|
|
Again there was another DAG change and 3 out of 10 miners wen't offline.
Is this a known problem ?
Ubuntu 18.04.4 with AMD 20.20 drivers.
use -lidag to slow down the dag creation process and prevent crashes. I agree this is a good setting to try. I've used -lidag 3 and it does seem to help with the crashes during dag changes and also helped with crashing at startup I was having on an 11 gpu rig. But I still get crashes on some rigs during the dag change even with the lidag setting. if you dont want dag creation every 2 epoch change. use -eres to create a dag good for a number of epochs ahead. I use -eres 10 so dag will be processed after 10 epoch change. |
|
|
|
Again there was another DAG change and 3 out of 10 miners wen't offline.
Is this a known problem ?
Ubuntu 18.04.4 with AMD 20.20 drivers.
use -lidag to slow down the dag creation process and prevent crashes. |
|
|
|
|
Does every epoch change requires -gt autotune?
|
|
|
|
|
My OC ssettings are as follows: 2x radeon 7 and 2x rx5700
-lidag 3 -cclock 1710,1710,1450,1450 -cvddc 915,915,885,885 -mclock 1000,1000,1800,1800 -fanmax 85 -fanmin 40
OC is stable on windows but unstable on hiveos. Anybody have the same issue?
|
|
|
|
Is hashrate really fluctuating with Phoenix Miner?  My radeon 7 and rx5700 hashrates are very inconsistent. GT on autotune, driver 20.12.1. I tried Team Red Miner and it was consistent. Yes, it happens because of overclocking. Don't overclock your memory too much... Memory is not overclocked that much. I noticed the fluctuation started when we switched to epoch 384 |
|
|
|
Is hashrate really fluctuating with Phoenix Miner? My radeon 7 and rx5700 hashrates are very inconsistent. GT on autotune, driver 20.12.1. I tried Team Red Miner and it was consistent. |
|
|
|
Hi,
I have nvidia ASUS p106-100 6gb mining series card and WIN 7 x64 operating system.
Phoenix miner version 4.9c and main Nvidia driver version: 382.53 working - BUT the hashrate is drop significantly last two months. Now is ~16.8 MH/s. (with -mclock +790) I think it must be more!
Every miner after 4.xx don`t work. (even 5.5b)The cmd window closes almost immediately!
I can change everything but operating system.
What i can do to increase hashrate, command line options , drivers... ? Hi! Ive had many issues with p106 and 382.53 on win10. Changing drivers made it worse. So ive installed hive. 23.5 mhs on eth I laso have p106 6gb with 460.89 on windows 10 and 5.5b but no issues. |
|
|
|
|
Radeon 7 hashrate decreased and fluctuating since epoch 384. From 89mhs down to 82mhs. It was fine before epoch 384. My 5700 on the same rig is not affected. Tried other versions of the miner but still the same problem. Anybody have the same issue. Im on driver 20.8.1. GT on autotune
|
|
|
|
|
