I have 3 MSI RX 570s 4GB cards, with modded BIOS using 1500 straps, all were mining happily at about .0885 vcore. All was fine for a long time. All 3 cards were drawing ~120 watts each.

But recently one of the cards started drawing a lot more power, it started jumping between 150 - 170 watts, card seems stable but as result runs too hot with fans at 100%. No changes were made at all.

Any advice on what the cause of this could be?

Thanks.

[Clarification:]

What GPU mine-able coins you think look very promising at the moment?

By "promising" I mean things like: have good potential for growth, good business plan, good road map, good team, etc..

Clarification:
- I don't mean "what coins are profitable right now"
- But rather, What coins look interesting & promising in the future, have good teams, bring innovation, good dev plan and etc.

Basically what coins you think are worth mining now and holding till later.

Started having an odd issue where 3 out or 5 identical Saphire RX 470s keep getting stopped by windows:
"Windows has stopped this device because it has reported problems. (Code 43)"

All cards are Hynix cards with modified bios straps. atikmdag-patcher_1-4-6 was applied after bios flashing.

If I disable then re-enable cards in Device Manager, they appear and can mine. But after reboot Windows stops them again.

Running Windows 10 v1809 and ATI drivers v18.6.1.

Any advice / recommendations on how to resolve this would be greatly appreciated. Thanks.

What CPU mine-able coins would you consider worth mining in 2019?

Ethash aglo's favor high Memory clock, and lower GPU Core clocks for better Watt per Hash ratio.

What about CryptoNight algorithms? When optimizing for best WATT / HASH ration, is it better to have overclocked / higher GPU Core clock or or overclocked / high Memory clock?

What other optimizations would be best for CryptoNight?

Thanks.

I have a setup with 9 x RX570s & 3 x RX 560 GPUs. The problem is that 1 / 3 times some of the RX560(s) will not be detected and when booted into Windows RX 560 cannot be seen. Then just by rebooting it becomes visible. Seems completely at random. I have tried other RX 560 & RX 570 cards to rule out possibility of hardware issue - it does not seem to be a hardware problem.

I have a motherboard that tells me which PCI-E slots / GPU's are detected during POST, so I can see the 560 not detected even before Windows boots - so it's not a software problem.

What I think might be happening is that the BIOS for 560 is a bit different from 570 and it gets detected a bit slower then 570 - not sure about this one, just a guess.

Is there anything that I can try to get 560s to play nice with 570s?

[Basic information]

Having a problem with very inconsistent hash rates with this miner. I'm able to sometimes (~3 times out of 10) hit my full hash rate of ~1015 H/s.

After 3 days of trying all possible BIOS, Software & Hardware configurations the problem remains and is not effected by changes. Problem seems completely random.

Sometimes when miner is started I will get ~200H/s, then just by closing the miner and reopening it I'll get ~600 and so on.

There are many similar Issue Reports of this by other users of this on GitHub, however the team dismisses them as "Hardware configuration is out of scope of GitHub forum, bla bla bla.."

This is not hardware config related issue as ~3 times out of 10 I actually get my full hash rate. So I know that my CPU thread configuration (cpu.txt) is valid.

Any advice on how to resolve this would be much appreciated. Thanks!

Basic information
- 6 identical Servers with Dual Opteron 6274 stock settings, Fully stable
- Windows 10 Pro OS, Disabled Windows Defender and all other unnecessary junk
- Tried with 1GB, 2GB, 4GB per socket - RAM has NO EFFECT on hash rate
- Tried different pools, tried different difficulty settings - NO EFFECT
- Using latest precompiled miner version

So BTC and most alts are down 10-25% pretty much across the board from 6:30 est. this morning.

So what do you think guys, buy this dip or wait for more blood?

Having an issue with ASUS B250 Mining Expert, where windows starts to lag after a 5th card is added. For now I plan to run 12-13 AMD cards.

3 or 4 cards seems ok, but with 5th windows lag is unusable. Opening device manager, seems like its refreshing every ~30 sec as in like looking for devices or something, which is weird.

This I tried so far:
- With & without iGPU
- various slot, card & riser combinations to rule out defective hardware
- installing drivers via windows update & installing manually from AMD's site (DDU cleaned each time).
- update latest BIOS & Asus chipset drivers
- set virtual memory at 36-52GB
- Windows Home vs. Windows Pro


Hardware:
- CPU: Pentium G4560 Kaby Lake Dual-Core 3.5 GHz
- 8 GB RAM / 120gb SSD
- MSI RX 570's (unflashed, yet)
- Windows 10 Pro (latest updates)

Anyone face a similar issue?

Any pointers at this point would be appreciated. Thanks.

Trying to dial in stable voltage settings for my Saphire RX 470 4GB (Non+) Hynix memory cards.

So far Claymore crashes after 4-16 hours, getting mostly "Temperature thread hangs" or occasional "GPU hangs" error message. My OC & Voltage settings are not out of the norm, I believe I've seen other forums/articles use similar settings and report stable results.

Here are my settings:
- In BIOS Timings flashed with 1500 straps
- In BIOS TDP increased from 85W to 115W & Max Power limit from 128W to 135W
- In BIOS GPU Core voltage changed from dynamic to static 850mv
- In Claymore: -cclock 1100 -mclock 2000 -cvddc 850 -mvddc 875
- Dual mining ETH + SIA using claymores latest v10.2
- Using AMD's BETA DAG Fix Drivers Released back in August v17.30.1029
- Windows 10, 4GB RAM, Virtual Memory set to 24GB

Observations:
- Changing -cvddc in Claymore does not effect GPU-Z VDDC values
- Only when changing -mvddc in Claymore, changes can be seen in GPU-Z VDDC

Questions:
- Is it not possible to change Memory Voltage for these cards, and changing -mvddc in Claymore actually changes Core Voltage instead of Memory Voltage?

- Or is GPU-Z not showing voltage properly? I'm assuming it displays Core Voltage, not Memory Voltage..

- What Core & Memory voltage settings should I be using to get stable results?