Bitcoin Forum
May 05, 2024, 07:50:31 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: New 5500 XT 8gb hashrate eth on: March 19, 2021, 06:57:15 PM
29-29.5 mh/s eth mining speed at ~80w power usage.


How did you get this? I've got 2 of these cards and are getting 27mhs,at 80w at the wall.

Thanks.
It depends on the quality of the memory. I have not more than 28.9 mh/s on xubuntu.

I'm using HiveOS.

Can I ask what settings you're using?

Sorry for the late reply.

That was with windows 10 single card, overclocking it as much as possible. It turned out that the card is not stable at these speeds to use in a miner setup.

You will get 28-28.5mh/s from this card with linux, a bit less with windows.

AFAIK bios modding is still not available for this card. But I think the card itself could do more if the tools would be available.



2  Alternate cryptocurrencies / Mining (Altcoins) / Re: New 5500 XT 8gb hashrate eth on: September 15, 2020, 06:08:47 PM
29-29.5 mh/s eth mining speed at ~80w power usage.

Significantly lower power usage then the previous generations.

I still have to see if at this speed range the card founds as many shares as expected.



3  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) on: August 04, 2020, 09:21:18 AM
When i changed the drivers the cards were not recognized cause I have flashed them, I used the atimdag-patcher but drivers can be patched, I get an error of driver file too large. Is there anything else that I can do
Thanks a lot

Simply download newer version of the patcher.
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) on: August 04, 2020, 08:06:14 AM

At DAG 353 Claymore gived up even with old driver, testing Phoenix miner.

The settings in the earlier video are working - Phoenix miner 5.1b, with adrenalin 20.4.2

Will see how good Phoenix miner works.

Regards:

azza_
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) on: July 31, 2020, 08:52:17 AM
17.30.1029 crimson beta

But I had to lower the mem speed from 2020-2080 to 2000 in all cards. If mem speed if higher the same situation shows up.

This crimson driver seems to be very sensible for modification of gpu voltage, memspeed parameters, so after each modification system restart is needed if some cards shows 0mh/s.

And don't forget to turn off automatic windows driver update with gpedit - win10 is keen to update this driver asap.

This means 29.9 mh/s for now instead of 30.9 mh/s.

Later I will take a look at other options.

Best Luck for you,

 azza_

6  Alternate cryptocurrencies / Mining (Altcoins) / Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) on: July 30, 2020, 09:55:19 AM
I would like to report an issue:

rx570 4GB cards with tuned bios, win10, latest AMD driver (adrenalin 20.7.2) - no mining after changing epoch to #352

Only first card shows 10 mh/s, the others fixed at 0 mh/s.

Normally around 30mh/s.

update: First test shows that lowering memory speed and getting back to very old crimson beta driver helps for now, at the cost of 3-5% lower performance. Memory usage around 3,895 MB

HWinfo shows that old driver is using around 27-29 MB of dynamic D3D memory while new driver is using more then 130 MB, at least for me.


7  Alternate cryptocurrencies / Mining (Altcoins) / Re: GTX 1050ti Ethereum Mining Rig on: July 20, 2017, 12:58:52 AM
Hi,

thank you for the great job - I built a similar rig. Some info:

1. I have gigabyte 4g oc 1050 ti cards with micron memory. They can reach 15.7-15.8 on ether.
2. Also have evga ssc 1050 ti cards with samsung memory. They are very stable at +1000 memory, but they do a bit less, around 15.5-15.6 mh/s
3. Gigabyte cards are hot, evga cards much cooler - evga has good quality cooler. But cards vary - some of them tend to be hotter then the other from the same brach.
4. Windows is still painful when you want something unusual like mining... (windows 10)
5. You can give high/realtime priority to miner process, doing this will increase the mh/s rate. But, windows may become irresponsive using realtime, so stay at high, or above average. The more priority given to etherminer the higher the mh/s rate is.
6. Install video cards one-by-one, wait for all the flickering each time, then check if card is recognized. Then restart and then shutdown, and put in the next card.
7. You need msi afterburner for tuning - I disabled low level io driver, polling rate to 2000 ms.
8. You might need system explorer if you want to set permanent priority, and have a better overlook of the system.
9. Disable unnecessary windows services, like Search. The main idea is not having anything crunching in the background. Crunching means lower mh/s rate.
10. Try to keep video cards as cool as possible - a cheap box ventilator will do at 15w. I dont suggest to install small pc ventilators - at the price of one good 12cm pc ventillator you can get one big box ventilator.
11. Interestingly - lowering gpu frequency below 0 increases power consumption and increasing gpu frequency can lower power consumption.
12. I think magnetic interference can be an issue with pci-e risers. Watch for separating usb, power and sata cables, check for loose connections . Bad quality risers can give a pain, makes you thinking of faulty video cards.
13. Do not use windows power saving mode, or balanced mode, use high performance power settings. Check if pci express "link state power management" is set to "off".
14. Typical windows 10 gpu overclocking failure: one or more gpu show near 0 mh/s, windows 10 unresponsive, msi afterburner eats up processor.
15. You might want to disable windows defender, or configure to whitelist your miners directory.
16. It is suggested to use 16 Gbyte virtual memory with windows 10. With 8 gpu the VM size of Claymore is 18.5 Gbyte, so you should set an even bigger vm size.
17. There is room for improvement: for example increasing intensity to 16 for nvidia cards adds a bit to your mh/s speed (claymore: -ethi 16)
18. Most of these cards does not have proper ram cooling (or any ram cooling at all), although high ram speed is key to more mh/s.
19. Its important to keep distance between cards, they heat each other up.
20. Dont forget to set minimal fan at least 50% and dinamically rising with temperature. Vram (and VRM) needs cooling even if the gpu is not working hard (and this is the case with eth).
21. "Cu_ki failed kx failed" type failure of Claymore: something is interfering with the program to communicate with gpus. Not enough cpu power due to power management, windows defender, other programs or services and can be a loose connector as well. And way too much overclock for vram. Or maybe wrong driver, try to up (or down)grade the driver.
22. Keep distance between sata power cables, otherwise they might heat each other up. Warm sata power cables can be the cause of sudden freezes of windows.
23. Get the cheapest available old pc with at least pci-e 2 ports and an old cheap gpu (nvidia nvs versions will do) and test all your risers before using them on your rig.
24. After optimizing your cards to the best mh/s speed take a look at claymore statistics and also try to optimize for max. shares/time.
25. Dont put your best card to the first slot. Maintaining video output takes away processing power, bette use motherboard graphics for video output.
26. "Got incorrect share" troubleshooting - first try to change the riser.
27. Try to find the most stable driver for your cards, saves you lot of debugging time. Best to stay with Claymore's preferred driver.


Some measurments:

8 1050 ti: with maximum overclock reaching 126 mh/s (under proper cooling conditions) with Claymore 9.7.1, but using at 123.5 mh/s because of stability issues. 455w power consumption.



Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!