Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 235. (Read 6590565 times)

Hey there, by any chance, are you dual mining?
BTW 3GB cards can't mine ETH any more, and probably, given time, 4GB will go the same way, but at least right now, 4GB cards are ok.
Things to check, Nvidia driver, (cuda) install ok, or DDU, and clean install Nvidia drivers.

Post your batchfile content, it's helpful to get a better understanding about your rig and expectations.
Also, how much VM are you running?

You can’t.
But it looks like you can download both 1709 and 1803 from MicroSoft.

https://www.microsoft.com/en-gb/software-download/windows10ISO

If you have accidentally updated from 1709 to 1803 you can rollback (within 1 month?) by selecting Setup - Recovery - Go back to the previous version of Windows 10

OK, Ursul0, you surprised me, THANK YOU, apology heartly accepted.
Kudos also, most people are too pig headed to do it these days.

Hey so to be clear, I don't disagree with your views on cloning, simply that as a posted cloning solution to the problem tabled.
Assuming that will work in all and every case, is a generalisation, very much dependant on specific hardware, means and ability of the person doing it.
Those guys are running a single rig, and on a learning curve, and as you well know, that is a really tough combination.
Even if you have a tiny "other" rig, at least you have the vastness of differentiation available when you're trying to troubleshoot.

Anyway, all water under the bridge, they had already done an OS install.

As you asked, to clarify, why I don't clone for clients on mining rigs, (and I DO CLONE, also with Acronis, just as you do), but not for clients.
Why? Protection, mine and theirs.
Mining involves money, my clients money.

If I make a mistake, somewhere, and have cloned 50 rigs off that, and later I find out I messed up, that is a 50x mistake multiplier I'm not prepared to risk. You can mess up just as easily by something you don't do.
With single install, I'm isolating risk, constraining it to THAT rig.`
So to be clear here, this is my CHOICE in this context, but equally none of us want to clone/deploy our mistakes either.

While it might not be THE solution, it's the one I've adopted to date. I've not had to consider building more than one or two rigs, single builds, or tiny batches if you like, so clone rollout is not a big time saver for me, and certainly does nothing to build customer confidence.

Of course I have a bunch of reg files, and envrio tweaks, so the additional deploy time is minimal, and I usually multi task while doing those build stages, so I'm not idle in that time.

One thing I often see in tech support is what seems simple to you, me, is often too complex or outside the comfort zone of the people asking for help.
Usually I probe with a few questions to get a feel for their ability and experience level, and get some dialogue going, before settling on what advice to give, and walk them through it, (not so easy on a part time forum basis).
But assuming they have, blah, blah means and ability, etc etc, actually assuming anything about them at all, is my error, and usually going to cause them more issues.

Take your logical method of driver install, (extract and do it in devman), absolutely, I could not agree more, however, while that is known to you, it's not the AMD advertised method, they steer the user to setup.exe, which does usually work, time consuming as it is, but is that the "best" method?
Well, probably for the majority, yes it is according to AMD, which is why AMD release that way.
Is it the best method you have? No.

OK, so question to you, there are a lot of postings "blaming" issues on stable rigs, after updating to this recent (April) 1803 update.
For sure, some of those cases are possibly blaming 1803 unfairly, but that isn't the question.
Have you tried that update?
What issues, if any, did you encounter?

I have a feeling this is going to be a mini-plague for the coming months, and while "don't update" is one obvious answer, I'm curious to know, specifically why that breaks, (assuming it does), and how to solve that, (other than fallback etc).
If the answer is fallback, is that the only answer, or have you recovered a rig in that situation?
Cheers

No worries, wow, that is a nasty situation with win updates. But before you roll back, it would be very helpful to know, if the DDU, clean install, or alternatively a manual driver install in devman as Ursul0 pointed out, gets you anywhere.

Because one would hope that DDU/clean install-driver option is an available solution.

But indeed, you could be right, I have seen some systems in a real mess after a OS roll back, and while that isn't to say that applies in your case, it's always one of those nasty things that sow the seeds of doubt later.

Also, you might like to set all your NICs to metered connection, that at least for the most part, prevents MS from updating your rig, or if nothing else, gives you some warning when they try to.

Regedit
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]

Grant your user "folder" permissions, and change all NICs to dword 2.
e.g.
"3G"=dword:00000002
"4G"=dword:00000002
"Default"=dword:00000002
"Ethernet"=dword:00000002
"WiFi"=dword:00000002

It won't help you with your current problem, but might be useful on your rigs
Good luck.

Great! Thanks. As far as I remember, Windows will update itself on first run without asking. Let's see how it goes, it was not me in need, but I'm waiting for users to report.

All the best!

my mistake. it just never happens this way. alright. Windows reinstall is not the best idea here, nor cloning. Good advice.
 
I'm sorry I said that all your ideas in this area are total crap, actually it's just everything you said about cloning and driver issues... and also something about "client security trough fresh windows install" and... uhh...sorry again...

@svdinu Reinstall older build. Quick search finds this (Anniversary is good enough for almost all use cases): http://windowsiso.net/windows-10-iso/windows-10-anniversary-update-1607-download-build-14393-0/windows-10-anniversary-update-1607-iso-download-standard/
You can look for SHA1 hash values of the original MS ISOs and check if it's proper

I was wondering why niether of the cuda opencl boxes were checked, and there has been an error that GPU-Z gives me when I open it or switch cards. I installed W10 1709 I believe then it updated to 1803, so I reverted back and have had strange things since. So I'mma do a fresh install and see what happens, I was able to flash the mod bios already so I don't really need atiflash to work anyway so I'll try 1803 fresh.
Thank you so much!

Like I said, end of discussion!
Nothing I said was WRONG, and throwing all your toys out of your pram does nothing to further your point(less) posting.
You might like to also look up the word "apology", and be wise enough  (one day), to know when to do that.

Pay better attention to detail, it's all written down here after all, no need to paraphrase or morph what other people write.
If you don't understand it, that's fine, all you need to do is copy/paste and ask for help.

If you're  going to counter point what others post, at least give them the courtesy to take your time to read it first, understand it, and MAKE your counter points, specific and to the point. But do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"

Equally, you can look up the word redundant for yourself.

And again, some understanding or manners and protocol would do you no harm either.

Bullying a technical argument does you no credit, neither is it necessary assuming you're intentions are to be helpful.
That does not mean you assassinate other people in the process.

I suggest you let this go, you're out of order, and that is my final word on the matter.
I'm not going to be drawn into your pissing contest, this is a technical forum, sigh.
End of discussion!

Is there a post somewhere discussing what people are dual mining?  I went from Sia to Decred to Verge and now I'm just mining Keccak algo on an autoexchange.  Keccak seems to draw more power (20-30w per card) than most of the other algos I was dual mining, I'm running AMD with dcri of 7.  Curious to see what options other people are dabbling in.

I tried searching for dual mining on here, but...so many results that do not apply

Well, I'm enjoying the tough debate my comment lead to.

Question still remains: How can one "roll back" to Win 10 1709 on a fresh install, providing that 1803 release is not good for mining?

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

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 is correct, do remember that in order to be able to access GPUs this way ALL system drivers must support 64bit address space and this means Windows MUST be installed in UEFI mode.

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

its not the cpu, undernourished cpus are usually fine in miners. even single core cpus have been used with no problems (in most miners).

probably a bios limitation. vga cards need a lot of resources, and the mobo/bios can run out unless special settings are used.

see if the bios has something like "above 4g decoding". short version is it increases the range of memory the mobo can assign to the cards, which is likely the issue. that bios setting is fairly recent in consumer mobos as having 4+ video cards wasnt very common back then when those mobos came out.

11.7 gives error, DevFee: failed to mine for a long time, something is wrong, "nofee" mode is enabled until successful devfee mining.


What the problem?

Well ok Ursul0, you're entitled to your opinion and abilities, but regardless, your response is not helpful, constructive, or even civil.
Something for YOU to think about, look up "good manners" in the dictionary for a start!

Furthermore, you take this totally out of context, bringing in virtual machines! Well you SHOULD know full well, as a hardware abstraction layer solution, that in itself "solves" most of the driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.

Why you seem to think that is useful to these guys, is anyone's guess, other than to bolster your opinions, it provides no constructive, useful solution to the problem, you just add noise.

Granted you do have some good tips there, (apart from that redundant patcher), so one has to wonder why you didn't offer these suggestions sooner, although as I say, they are mostly not applicable as was already stated, these guys HAVE NO OS to clone from!


NOTE: there is no place for a pissing contest here on this forum! Lets try to keep it civil.

Oh man.. you sure have a lot of not-so-useful experience to share.
1) clones work just fine (all your ideas in this area is total crap, sorry. I have dozens of workers cloned and it works like a charm even WITH different HW, like MB and the rest. Also I once was doing production grade virtual appliances with MS OS, and the only issue with cloning is Microsoft support (none) and VERY rare conflicts in clones within Active Directory due to same SIDs issue)
2) to setup amd drivers  for 12 GPUs takes 2 minutes: 
* DDU(proper! until all gpus are microsoft adapters);
* unpack any driver since 17.10.2 (around here 8+ GPUs became supported ),
* update driver from device manager by navigating to the unpacked driver;
* set compute mode for all your devices here(0 dev sample):
* if you have modded bioses run dagpatcher to bypass the signature
*use overdriven tool profiles for clocks and volts