Anybody using 1070? Two years ago all of the 1070s were pushing a constant 30-32 mh/s. Now, only one (EVGA) of them is pushing 29 mh/s, the rest (AERO MSI) are in the low 22-23 mh/s. I understand the 1070s are affected by the increased DAG size as well as nvidia's drivers. However, how come one of my card still pushes similar numbers to two years ago, is the EVGA using a more efficient memory or what causes this? I've tweaked mem/clock and TDP but nothing. Thanks.
OS: Win 10
Newest Nividia drivers
Latest/Beta PM.
Straps/vrtimings, etc. all applied
Thats not true. 1070s are NOT affected by DAG size so far. All mine are hashing at 30 Mh/s with no problem. It all depends on your system (power usage, OS, memory, driver...) You are wrong, every Nvidia Pascal Card, reduce the hashrate with every new DAG epoche. It's the same bug as the AMD R9 290x and R9 390 in the past. The reduction is not much, but it will happened, You see it, when you let your miner benchmark in epoch 0 and for example in epoch 300. Test it and you will see it dude;) |
|
|
|
To much OC or check the Riser. |
|
|
|
T-Rex v0.18.6 on Hive OS produces a connection error on some of my miners (but not on all of them): 20201108 03:44:03 ERROR: No connection, retry after 10 seconds
20201108 03:44:13 Using protocol: stratum3.
20201108 03:44:13 Extranonce is set to: 1684
20201108 03:44:13 Authorizing...
20201108 03:44:13 New target is set to: 0x00000009f5ffffffffff80000000000000000000000000000000000000000000
20201108 03:44:13 WARN: failed to stratum2-authorize on europe.kawpow-hub.miningpoolhub.com:20611: pool rejected connection, result {
"error" : null,
"id" : 3,
"result" : false v0.18.5 doesn't produce this error. Any ideas? Anyone knows the monitoring api port on HiveOs for T-Rex? |
|
|
|
win 10, adrenalin 20.4.2, 8rx578
Received: {"id":6,"jsonrpc":"2.0","result":true,"error":null}
2020.11.09:16:16:34.600: GPU4 GPU4: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:34.600: GPU4 GPU4: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:34.602: wdog Fatal error detected. Restarting.
2020.11.09:16:16:34.866: GPU3 GPU3: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:34.866: GPU3 GPU3: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.147: GPU7 GPU7: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.147: GPU7 GPU7: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.413: GPU5 GPU5: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.413: GPU5 GPU5: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.694: GPU1 GPU1: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.694: GPU1 GPU1: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:35.975: GPU6 GPU6: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:35.975: GPU6 GPU6: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:36.241: GPU8 GPU8: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:36.241: GPU8 GPU8: Allocating buffers failed with: clCreateBuffer (-61).
2020.11.09:16:16:36.538: GPU2 GPU2: Allocating DAG (4.01) GB; good for epoch up to #2
2020.11.09:16:16:36.538: GPU2 GPU2: Allocating buffers failed with: clCreateBuffer (-61).
What can i do ?
I have exactly the same problem, I tested it on this driver and it didn't work and the BETA driver doesn't work either. Lol, wrong commandline. I don´t know why you set so much variables in commandline, most of this you don´t need. YOU SET WRONG COMMAND: -DAGLIM 1 is wrong, because it limits the dag size to 4006mb and the dag of etc is over (4010mb) this lol  Commandline variables that you don´t need: -eres 0 -rvram 0 -dagrestart 1 And by the way, update your driver |
|
|
|
|
Which port is set for T-Rex Miner Api? A list with every miner and the standard Api ports that HiveOS set would be very useful.
|
|
|
|
Hi,
Can someone tell me exactly what does the Clean up all downloaded and uploaded mining software option on the System tools menu due?
Thank
It does what it says. It delete all downloaded and uploaded mining software on the selected rig/miner. |
|
|
|
Now i see no temps on all of my ryzen (1200, 1600, 2600x, G2400) In system tab it show me the temp, but status and the CPU tab give only 0°C, with v8.1.4 all works fine.
Thanks for the feedback. I will try to reproduce this. Are you using XmRig or any other CPU mining software? Are all CPU cores reported with 0°C? Hi patrike, i use xmrig and srbminer multi, all show 0 for all cores. And what do you mean: User interface - Organize rule actions with group labels to make it easier to find Where i can organize the rules? Or what do you mean. I find no option or something else. |
|
|
|
|
is it possible to mine eth and zil like other miners?
|
|
|
|
can anyone upload the older version? i think its the 5.0.3 this new version display a error: no cuda installation detected but the older version works fine!
Yes you read the release notes from 6.0.0? Version 6.0.0 of TT-Miner is released. - removed algos: EAGLESONG, LYRA2 - removed cuda version: cuda 10.0 and cuda 10.1 - added support for cuda 11.1 - added support for: - VeriBlock - Zelantus - Veil (ProgPoW) - added fees again. Solo mining & EPIC: 2% all others 1% - support for solomining for: - EPIC - Raven - Veil - Zelantus Install newer driver and it works |
|
|
|
Awesome Miner version 8.1.5
GPU mining
- Added the EtcHash algorithm to support the upcoming changes for Ethereum Classic
CPU mining
- Improved detection of number of cores for AMD Ryzen
Mining software
- Lolminer 1.12
- Nanominer 1.12
Corrections
- Correction to Ryzen temperature display
Now i see no temps on all of my ryzen (1200, 1600, 2600x, G2400) In system tab it show me the temp, but status and the CPU tab give only 0°C, with v8.1.4 all works fine. |
|
|
|
|
Is it possible to mine ETC and ZIL after the EtcHash fork?
|
|
|
|
Hi Patrike,
i have a difference in CPU temp only 1 rig. AM says 77°C and Coretemp and AMD Ryzen Master says it have 87°C. CPU is a Ryzen 5 2600x. On other rigs there are no problems (Ryzen 5 1600 temp is right, Ryzen 3 1200 temp is right and on all other Intel CPU´s temp is right)
There are multiple temperature sensors on the CPU, so it may not be the exact same we report as Ryzen Master reports. Awesome Miner prioritize the "CPU Core" and "CPU (Tdie)" sensors, but there are more sensors. If you want, please check with the tool OpenHardwareMonitor where you will see the name of many of the CPU temperature sensors and the reported temperature for each of them. I checked the temperature with OpenHardwareMonitor and it says only 89°C and some lower temps under 70°C and awesomeminer shows 79°C. This is only on the ryzen 5 2600x. Another rig with a ryzen 5 1600 shows 75°C in awesomeminer and 75°C in OpenHardwareMonitor. So there is something wrong. For AMD CPUs, only have a Ryzen 3000-series to test with and I will investigate on that one a bit more. Could you please also try with the older version called "Open Hardware Monitor 0.8.0 Beta", available here: https://openhardwaremonitor.org/downloads/It would be interesting to see if that one reports differently. Via Open Hardware Monitor you can also export as a report via the menu File -> Save Report. Can you please do this for the Ryzen 2600x system and send me via PM? Please also let me know the temperature you consider is correct for the time you created the report. The numbers in Awesome Miner is for one of the reported CPU temperatures sensors (so Awesome Miner isn't making up anything here) but it may not be the sensor most relevant for this specific Ryzen CPU. With the report above I might be able to find out the name of the sensors that would make more sense to display. So i tested with 0.8 beta, this version show no temperature, tested with 0.9.1 and it shows 88°C (AM 78°C), i tested with coretemp and it shows 88°C and the same in HWinfo, it also show 88°C. This is only on my Ryzen 5 2600x, Ryzen 1x00 no problem an intel cpu also ok. I will send you 2 reports. |
|
|
|
|
Today some gpu´s goes to 0 mh. But i don´t understand why. 12 Rigs with driver 19.7.4 and on 3 rigs one or 2 cards mining with 0 mh. All other rigs works perfect.
|
|
|
|
Hi Patrike,
i have a difference in CPU temp only 1 rig. AM says 77°C and Coretemp and AMD Ryzen Master says it have 87°C. CPU is a Ryzen 5 2600x. On other rigs there are no problems (Ryzen 5 1600 temp is right, Ryzen 3 1200 temp is right and on all other Intel CPU´s temp is right)
There are multiple temperature sensors on the CPU, so it may not be the exact same we report as Ryzen Master reports. Awesome Miner prioritize the "CPU Core" and "CPU (Tdie)" sensors, but there are more sensors. If you want, please check with the tool OpenHardwareMonitor where you will see the name of many of the CPU temperature sensors and the reported temperature for each of them. I checked the temperature with OpenHardwareMonitor and it says only 89°C and some lower temps under 70°C and awesomeminer shows 79°C. This is only on the ryzen 5 2600x. Another rig with a ryzen 5 1600 shows 75°C in awesomeminer and 75°C in OpenHardwareMonitor. So there is something wrong. |
|
|
|
So what is the exact week/day, when 4GB cards will not be able to mine anymore?
There is no exact day or week, much miner developers update there software to mine longer with 4gb cards, so mine as long as you can. With lolminer 1.11 you can mine on windows up to december 2020. |
|
|
|
|
Hi Patrike,
i have a difference in CPU temp only 1 rig. AM says 77°C and Coretemp and AMD Ryzen Master says it have 87°C. CPU is a Ryzen 5 2600x. On other rigs there are no problems (Ryzen 5 1600 temp is right, Ryzen 3 1200 temp is right and on all other Intel CPU´s temp is right)
|
|
|
|
Seems this may only be an issue with the Claymore miner? Edit: Updating the drivers appears to have solved the issues for AMD users with 4gb+ cards. Download here: https://www.amd.com/en/supportI use phoenix miner so might have to switch over to claymore and put them on a separate rig to try them all out (3x 4gb cards), to see if it does work after update of the amd drivers. Not sure if you can update the individual drivers for each different card you have in your rig under hiveos as it is a linux based os. Haven't fiddled around too much in linux to figure out how the command lines work to do this. Thanks OGNasty for the insight.  Mining on windows with 4GB cards are no problem. Use the right driver and internal gpu as first gpu. |
|
|
|
I'm looking for a GPU mining software that will payout to me in BTC and doesn't requires mobile apps in order to withdraw. It doesn't matter what coins it mines as long as I can cash out in BTC and preferably with a low minimum withdrawal limit. I used to use hash.fish until it disappeared off the face of the web. I tried NiceHash and BetterHash and they both require mobile apps to withdraw. Any recommendations? Thanks
Nicehash requires only your wallet address for withdrawal, once you meet the payout threshold you will get paid, ive been using nicehash since 2017 so I'm talking from experience, I don't know where or what mobile app you talking about, Nicehash is useable on web or mobilephones Ah it seems you are correct. I was having issue with withdrawing because I already had a withdraw address linked who it belonged to an old wallet.dat file. It needs an app of which I don't own a smartphone, to let me change my withdraw address. I shall contact NiceHash regarding this issue instead. Thanks for your response! You can change the address in your browser in your nicehash profile. |
|
|
|
@BoozyTalking curious, no bug on the machine you said ?
@sxemini you say in the last 2 days, does that mean you didnt have this issue before it ?
Hi doktor83, with older versions i have no issues. I have tested last week. If i mining without admin rights, no problems for 4 days. Then i start mining with admin rights and after around 8h, no more shares, but cpu is working. But i only have this problem on 1 rig, other rigs works with and without admin rights normal. |
|
|
|
Anyone else's rx570s(4gig) just drop in hashrate under windows 10? if not what driver's are you using or how are you doing it?
Thanks
No hashrate drops for both 470 4G and 570 4G... Just use recommended drivers from 1st page and you'll be fine until DAG 372ish. Mine have all dropped to between 1 and 5 mhs on the 570s. The 4gb 580s are still fine(in same rig)....Using 18.2 You must use 19.7.4 for example. |
|
|
|
|
Show Posts
