Post
Topic
Board Mining (Altcoins)
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v11.7 (Windows/Linux)
by
Ursul0
on 27/05/2018, 13:32:34 UTC
driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.




RE clones:
Using Acronis TrueImage, I've got the same UEFI Win10 image running on ASROCK H110, MSI Z270, ASROCK B150,  ASROCK H81. With various AMD and NVIDIA GPUs and ZERO issues. I reiterate myself: the only known problem with cloning is absence of official Microsoft support. (and I know this because see earlier)
Also how comes dagpatcher is "outdated" or whatever is your claim

RE problem:
I'm just cautioning these guys from listening to incompetent "yet very helpful"(?) people

They are just doing something terribly wrong (like not having their drivers properly installed) as it's extremely simple:
Do this: disable windows & drivers updates, do proper DDU, add multiple GPUs (better with stock bioses), install driver (see my post above), run claymore.
for polarises you can set extremely safe 1140MHz core and 1750 mem at 900mv
You can also try other algoes / miners.


“It's not what you don't know that kills you, it's what you know for sure that ain't true.”

― Mark Twain


Yes, better to keep these,  technical discussions, rather than personalising them.
It also helps you make your point!

OK, but like I said, as indeed did the original poster, they are a small outfit, they have a single rig, and Acronis cost what?
Another fifty bucks, to do what, make a single clone, from a disc they don't have?

Again, for the last time, cloning in the context raised is not a good solution, in fact it's not even possible.
End of discussion if you please.

A bit of attention to detail would not go amiss, nowhere did I say the dagpatcher was outdated, YOU said that!
What I wrote was it was redundant, that's it.


That's exactly my point. Whomever raised question of clones was not me, but your comment apparently caught my attention NOT because it was out of place, but because it was wrong. Also again why is pixelpatcher redundant? I'm not aware of AMD starting to skip the signature check in their drivers (it was re-enabled with 16.12.1)


EDIT: @marius85 try 18.2 - 18.3 versions