Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[iSuX]

TBH, I would not waste time on MB, system ram, or even PSU. (in terms if variables, there is nothing to tune, and little to gain, (assuming you have a stable rig right now)
The key point with PSU is, they are a big portion of your asset cost, so ensuring they run at optimal efficiency vs number of GPU is a quick and easy calculation, that's it, there is nothing else to tune there, no more variables to consider, (other than maintenance and mtbf)

Ok, I'm going to through my MB question. I started mining with whatever I had lying around. In my case, I have an AMD PHenom II X2 545 CPU with DDR2 ram and . I've got a PCIe x1 splitter to run out extra cards.

I've got 7 cards in total, split across two machines.

However, I would ideally run these on a single machine, so I have less CPU/RAM/HDD power overhead. But, the problem I have found is I can't run more than 5 cards on this machine, or the other one (AMD A4-4000, with DDR3 ram). The 6th card would detect but give that error-33 (32?). I swapped many cards around, tried cables, risers, rechecked mb bios settings, but I started to get the feeling that these old CPUs just don't have enough PCI lanes to run this many cards, or else there is a similar MB limit. So I ended up giving up on a single machine setup, and have the two running.

I looked at a mining motherboard, etc. but the saving in power overhead doesn't outweigh the cost of hardware for over a year. Which still makes these "free" motherboards (they were just lying around home) still appear attractive.

So, in summary, do these old boards/CPUs have a GPU limit?

(P.S. sorry to hijack the claymore thread for these kind of questions, but most people here actually seem to contribute constructively to questions!)

Good morning jeremyismer

Thanks for adding additional detail.

Yeah, that's a tough one, I don't want to speculate on your specific hardware, as I have no experience with those MBs, but...

I did exactly the same thing as you initially, in that I had Dell Optiplex 7010 kicking about, and used that as my prototype rig. As it only had 3 PCIe slots, I used a PCIe 4 port expansion card, but that rig never had more than 5 GPU running off it, BUT it was REALLY unstable, I had a lot of issues every time I added a card, or changed anything, or even powered it down.

But I learned the importance of stability and uptime, and when building my first rig from scratch, opted for the ASUS Prime 270-a, and MAN was that like a breath of fresh air, it just worked... Until I added the 5th GPU, then it would not boot, or if it did, I would have only 4, or sometimes 3 or 2 GPU detected.

Now on that board, you need to do some tweaks in the BIOS to get beyond the 4 GPU, various youtube videos are out there about that, (guess what, they vary in detail, sigh), but essentially, the only critical change you need to make is, (on the Prime 270-a), called enable above 4G decoding.

The definition of “Above 4G decoding” is to allow the user to enable or disable memory mapped I/O for a 64-bit PCIe device to 4GB or greater address space, because the primary VGA card should always be mapped below 4GB address."

OK, so after that, I used the ASUS Prime 370-A, (same situation as above, (above 4G decoding), gets you up to 13GPU, and on the ASUS B250ME, specific mining mb, you have that feature enabled by default.

Now, as it happened, a lot of back ordered GPU started flooding in, after months and months waiting, and I was able to finish the rigs I built for other people, and even then had some spares kicking about, and again found myself with a spare Dell Precision 3650, so decided if I could use that to employ 5 "spare" GPU.

This was a tough one, 2 PCIe slots, so I used the 4port card in the 16x slot, and a single PCIe in the 1x slot, and no matter what combination, cards, ports, even tried some older AMD and Nvidia cards, but it would not boot with more than 4 GPU.

I played about with that for some weeks, building up to the conclusions, it lacked the ability to cope, whether by hardware design, or BIOS limitations, (something Dell are renowned for, their goal, (understandably) is mass market, stable, reliable, nothing special or pushed too hard, means lower support costs for them, and steady revenue streams for replacements after 3 years warranty expires).
At the same time, having 5 GPU kicking about and no way to use them, I forked out for another Prime 270-A, which I chose over the 370-A, simply because I wanted to pull the i7 6700 CPU and 16MB 2400DDR RAM from the Dell precision, so in my case, that additional rig, was only really costing me the new MB, and time, as always ;-)

Interestingly, I noticed 2 other things,

1. Mining with a HDD sucks, staggering how slow that was to do everything, boot, init, you name it.
2. Mining with an i7, even an older mid range 6700, was a lot faster to init Claymore, than all my other rigs, i3 7100 or i3 8100. Probably that is obvious, but all the same it just goes to illustrate how much code is executing in Claymore during the init, so that was the real surprise I mean here.


So... I'm sorry man, I don't have any real solutions for you, I would have liked to get some definitive answers on those Dells, but time is always divided between things, and looking at the money draining away from not using those 5 GPU, that was the kick in the arse to build another rig.

BTW: One mistake I made early on, was to opt for a celeron CPU, and while that worked ok, it means you have to use one of your mining GPU to drive a monitor, and that in itself brings in a whole raft of issues, mostly when you're debugging driver problems, init issues etc. Now, that was my first from-scratch rig, and I didn't fully appreciate what the loss of intel graphics would mean, so I swapped that out for a i3 7100, and on all rigs since, having intel graphics is a check-box item for me since. It means, no matter what crap MS or AMD or drivers or PSUs through at you, at least you can get a display on it.
The i3 uses about 1W more than the celeron, (on paper), in reality, for mining, once everything is running, I don't see any difference in power consumption from the celeron.

So, in conclusion, you could be flogging a dead horse there by adding the 5th GPU, and weighing up the cost of 4 GPU doing nothing while you work on that, possibly unsolvable issue, is a situation probably already very much playing on your mind.

So... time to go shopping maybe? MB, CPU, RAM? Or by a 2nd hand bare-bones maybe.

Good luck man, lmk how you get on.

[1714174069]

1714174069

[iSuX]

We are having the same problem that Marius 85 and others seem to be having.

How may i fix this? I get a loop with this and it doesn't start mining..

Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)
ETH: Authorized
Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)

We reformatted our hard drive, reinstalled windows 10...had to go with 1803 as we did not have an older version available.  Downloaded Radeon driver 18.5.2 and Claymore 11.7.  We put the EthDcrminer64.exe into windows defender exceptions and still shuts off as soon as we start.  Here is the last log

20:26:15:884   e38   Check and remove old log files...
20:26:15:884   e38   args: -epool us2.ethermine.org:4444 -ewal xxxxxxxxxxxxxxxxx -epsw x
20:26:15:884   e38   
20:26:15:899   e38   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:26:15:899   e38   º                Claymore's Dual GPU Miner - v11.7               º
20:26:15:899   e38   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:26:15:899   e38   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:26:15:899   e38   
20:26:15:899   e38   b583
20:26:16:149   e38   ETH: 1 pool is specified
20:26:16:149   e38   Main Ethereum pool is us2.ethermine.org:4444
20:26:16:149   e38   DCR: 0 pool is specified


We even went into the console and tried to run the program...exactly the same log as this one. Just keeps shutting down as soon as it starts.

Very frustrated as the miner was running so well for the past four months.  We're newbies so we're at the limit of our knowledge base.
We are running three RX 570's with moded bios....ran patch...they are recognized and in compute mode.  One XFX RX 570 not moded on compute mode....we had stable 111mh/s on previous windows and Claymore 11.0.

Is there any hope?

Clone the SSD from another working rig. Update drivers only, if required.

I know that we are super small fish and this might work but we just have the one little 4 card rig.  I mistyped and we are running adrenaline 18.5.1.  It won't even run through the console as recommended by isux on page 1205. I have seen this same issue on several other posts but no fix that works for us.  What other things should we be looking at?  We copied the setx commands into the bat file and the log shows the only commands we have after that.  Config file is all #'ed out so no interference or double commands. Even if it is an overclock issue we should at least be seeing the stock card run something.

That sounds frustrating.
What do you have Virtual memory set to?
With 4GPU, 16GB should be fine, but if you want to absolutely exclude this possibility, set VM to 48000, (I have some 13 GPU rigs running that, and it's fine).

Also, side note, actually, I'll do a new post on this bit, hibernation!

If you didn't try it already, turn on debug and see if Claymore log adds some clues.

And if you really hit the wall, remove all the GPU but 1, boot to safe mode, run DDU, reboot, and install AMD driver with that single GPU, set to compute, reboot, and see if that works. Then add back the other GPU, build up to that etc, but get a proof of concept first.

Don't forget to switch off debug when things are running.

Good luck

Foot note: As always, if you get stuck, post your complete batch file content.
There are a lot of possible causes to this, so there is no one answer, but another common error is to command a clock the hardware can't deliver on. Claymore is waiting for some ack, which depending on what you sent to the hw, the driver, and probably the hw ability to cope with the impossible, might not send an ack, and Claymore can only wait, (and have the smarts to not wait forever, but trip a reset after 5 min).

But going back to basics, break it down, is a good method for debugging. Yes, it might be painful, but if done right and systematically, DOES deliver a good probability of finding a solution. Far more so than blindly stumbling around in the dark, hoping to get lucky, hmmm that reminds me of something else, hahaha.

[iSuX]

Hibernation.

Win7, Win10.

It's quite common for mining rigs to have "small" SSD, just enough for the OS and Claymore, so probably doable on a 64GB SSD even.

However, with swap file, page file, and setting VM to 16GB or more, (16GB is the minimum), it's easy to see some big chunks of disc space be consumed.

Worse still, if you have 16GB of RAM, with a default Win install, you're going to see some 12~16GB stolen by hibernation.

Considering one probably does not want a mining rig going to sleep or hibernating, tip of today would be to disable those, and then review your power settings, as those too can be hijacked by various apps etc,.

Open an admin command prompt

powercfg /h off


That's it, eliminates a potential cause of mining halt, and recovers a nice chunk of RAM you can then give to Claymore as VM if you need to.

Happy Mining

[jeremyismer]

Hibernation.

Win7, Win10.

It's quite common for mining rigs to have "small" SSD, just enough for the OS and Claymore, so probably doable on a 64GB SSD even.

I'm running win7 (w/o hibernation), claymore and very little else on a 40gb ssd. It all just fits, but again, one of those things that was lying around and had no other purpose.

[iSuX]

Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified

Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!

Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1


I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.

I would post a pic to make it easier but I cannot figure out how to do that :-)

Hey there,
So you have debug on, what do your logs tell you?

Try adding

-di 0

Start with GPU0 only, would be a good thing to try, as you could be overloading your PSUs.
If it's a new rig, never been running/stable, break it down, get through the init on one GPU, prove your config and basic hw/sw enviro, and take it from there.

jooi, what PSU are you using, and how many GPU on each, how many risers per cable?

Kudos on the 13gpu rig man, not so easy to get those stable.

Good luck.


footnote:
Try this.

setx GPU_FORCE_64BIT_PTR 1
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool ssl://eu1.ethermine.org:5555 -ewal wallet.rig -epsw x -di 0 -gser 1 -esm 0 -etha 0 -ethi 16 -eres 2 -erate 1 -estale 1 -asm 1 -platform 1 -y 1 -dcri 9 -wd 1 -ftime 5 -r 1440 -cclock 1200 -cvddc 900 -mclock 2100 -mvddc 850 -tstop 83 -tstart 50 -tt 60 -fanmin 40 -fanmax 100 -ttdcr 80 -ttli 80 -mode 1 -dbg 1 -altnum 3 -mport -3333 -mpsw whatever -logfile logs\

So that was a great idea taking the cards out and just doing 1, I should have tried that before posting.  Unfortunately it didn't work, same result. Here is the last log file, the others say the exact same thing :-(

20:25:58:457   1460   Check and remove old log files...
20:25:58:457   1460   args: -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
20:25:58:457   1460   
20:25:58:457   1460   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:25:58:457   1460   º                Claymore's Dual GPU Miner - v11.7               º
20:25:58:457   1460   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:25:58:457   1460   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:25:58:457   1460   
20:25:58:457   1460   b583
20:25:58:685   1460   ETH: 1 pool is specified
20:25:58:685   1460   Main Ethereum pool is eth.suprnova.cc:5005
20:25:58:685   1460   DCR: 0 pool is specified
20:26:31:509   d48   
20:27:04:325   d48   
20:27:37:141   d48   
20:28:09:957   d48   
20:28:42:541   d48   



2x 1,200 watt gold psu's, even distrubuted as with my other one.
and only 2 risers per sata leg

Thank you for you help!

OK, will it sounds like your PSU and topology is thought through, so maybe leave that for now.
Could you post the debug log, from the batch file I added above?

(Just to rule out the pool angles, as I have no experience with suprnova, and Ethermine, being pretty much the biggest there is, makes for a good choice when testing, even if you don't plan on mining with those guys).

Now that said, what SHOULD be happening at this stage is the init of OpenCL, (or CUDA if you're using Nvidia).
OpenCL is managed via the AMD driver, so assuming you don't have a problem with the pool, I think you need to investigate if OpenCL is available.

One way to do that, (with a only single GPU in the rig), is you use GPU-z, and see if the OpenCL check box is populated.

Now, I have also seen perfectly good working rigs, where that checkbox is NOT populated, and clearly that is wrong, so to be absolutely sure, you (again with only 1 GPU in the rig), could boot to safe mode, DDU, reboot, install the AMD driver, set to compute, reboot, and check GPU-z, I have never seen that fail to confirm OpenCL.

From there, try my batch file again, and post the log if you're still stuck.
Good luck

Also, VM? Set to 48000GB if need be.

Foot note, in case anyone needs convincing of the single GPU method. If you do a clean AMD driver install with 13GPU, this alone can take hours, more so, if it fails, and AMD themselves STILL have an open bug on init fail with more than 12GPU.

Often when testing theories, working through troubleshooting etc, this is time consuming, and for sure you probably work at testing, (proving) some angles that were perfectly fine to start with. Time is not wasted of course, as you can cross those off the list, elimination of them, takes you closer to the answer.
But all the same, if you have multiple GPU, that's an exponential multiplier on the possibilities of fault, and means more time to troubleshoot is a given.
Breaking it down to basics, (you only need to pull the USB cables from the MB, for the most part), is pretty quick, you don't need to physically remove the GPUs etc, means you can run DDU, and reinstall the AMD driver with the minimum time consumed, and get back to starting Claymore as quickly as possible.

AMD driver install time, is pretty acceptable with a single GPU, but 12 and 13 is really nasty, and I have seen that fail many times, so working on proof of concept with a single GPU is by far the fastest, and most likely to provide solutions imho.

BTW 18.3.4 is a stable driver for mining.
Note: there is NOTHING mentioned in any release notes from AMD, on any mining related improvements in the drivers release since 18.3.4.
That is not to say the newer drivers are bad, (some are though), but simply, 18.3.4 has been out for a while, rolls up all the mining related things you probably need for RX570/580 hardware, and has proved itself far more than any of the drivers released since then. So, if you're going to DDU etc, I'd suggest 18.3.4 is a good choice, known good, known stable, well proven choice, and when you're troubleshooting, you need to focus on elimination of doubt. Go with what you know, (is good).

[iSuX]

We are having the same problem that Marius 85 and others seem to be having.

How may i fix this? I get a loop with this and it doesn't start mining..

Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)
ETH: Authorized
Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)

We reformatted our hard drive, reinstalled windows 10...had to go with 1803 as we did not have an older version available.  Downloaded Radeon driver 18.5.2 and Claymore 11.7.  We put the EthDcrminer64.exe into windows defender exceptions and still shuts off as soon as we start.  Here is the last log

20:26:15:884   e38   Check and remove old log files...
20:26:15:884   e38   args: -epool us2.ethermine.org:4444 -ewal xxxxxxxxxxxxxxxxx -epsw x
20:26:15:884   e38   
20:26:15:899   e38   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:26:15:899   e38   º                Claymore's Dual GPU Miner - v11.7               º
20:26:15:899   e38   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:26:15:899   e38   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:26:15:899   e38   
20:26:15:899   e38   b583
20:26:16:149   e38   ETH: 1 pool is specified
20:26:16:149   e38   Main Ethereum pool is us2.ethermine.org:4444
20:26:16:149   e38   DCR: 0 pool is specified


We even went into the console and tried to run the program...exactly the same log as this one. Just keeps shutting down as soon as it starts.

Very frustrated as the miner was running so well for the past four months.  We're newbies so we're at the limit of our knowledge base.
We are running three RX 570's with moded bios....ran patch...they are recognized and in compute mode.  One XFX RX 570 not moded on compute mode....we had stable 111mh/s on previous windows and Claymore 11.0.

Is there any hope?

Clone the SSD from another working rig. Update drivers only, if required.

Interesting "solution". I'd suggest this is NOT a good idea. While svdinu might have the ability to get this to work, I'd suggest it will, in the long run, create a mass of issues, and even if you get it to work, it will take a LOT longer than a OS reinstall of Win10. (especially if you have an SSD, reinstall of Win10home, takes about 15min at most).

On cloning: Actually, unless the motherboard and peripheral devices are identical, it's quite likely the system will fail to boot, or have a bunch of driver issues, which, in the first place, IF you have the ability to solve, (and they are even solvable at all), you would simply know better than to try this solution to start with.

No criticism of svdinu here, simply that when troubleshooting, you need to ensure you are working to eliminate issues, and not introducing any new ones along the way. This solution, introduces a huge array of issues, and potential issues, and potential issues mean doubt later on when you have other problems with the rig.

Start as you intend to go on! (known good etc)

I mention this here, as I say, not to be critical of svdinu, clearly he's trying to help, but when I read that someone formatted/reinstalled their OS, that tells me, they are possibly lacking the experience to know how to identify their issue, and have opted for reinstall, which is extreme, but which is a FAR better idea under these circumstances, (given their skill level)  than trying to clone a SSD, assuming you even have one to clone from.

From a personal POV, I HAVE cloned OS discs many times, would I try it in the context of this problem? NO.

In fact, I build identical rigs for people, and I STILL don't clone SSDs, (unless I'm installing bigger ones, or replacing them etc), but for a new build, I only install fresh, this ensures stability, and no cross pollination, (security for both the client, but also security of stability).

My 5 cents.
Happy Mining

[iSuX]

Hibernation.

Win7, Win10.

It's quite common for mining rigs to have "small" SSD, just enough for the OS and Claymore, so probably doable on a 64GB SSD even.

I'm running win7 (w/o hibernation), claymore and very little else on a 40gb ssd. It all just fits, but again, one of those things that was lying around and had no other purpose.

Hahaha, MAN you're hardcore, that is quite an achievement, WOW.
Don't tell MS anyone, they'll be looking for new ways to screw us over, lol.

Side note: Do you limit the Claymore log file size? or overwrite? Or maybe log to a USB storage device?

[Ursul0]

We are having the same problem that Marius 85 and others seem to be having.

How may i fix this? I get a loop with this and it doesn't start mining..

Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)
ETH: Authorized
Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)

We reformatted our hard drive, reinstalled windows 10...had to go with 1803 as we did not have an older version available.  Downloaded Radeon driver 18.5.2 and Claymore 11.7.  We put the EthDcrminer64.exe into windows defender exceptions and still shuts off as soon as we start.  Here is the last log

20:26:15:884   e38   Check and remove old log files...
20:26:15:884   e38   args: -epool us2.ethermine.org:4444 -ewal xxxxxxxxxxxxxxxxx -epsw x
20:26:15:884   e38   
20:26:15:899   e38   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:26:15:899   e38   º                Claymore's Dual GPU Miner - v11.7               º
20:26:15:899   e38   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:26:15:899   e38   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:26:15:899   e38   
20:26:15:899   e38   b583
20:26:16:149   e38   ETH: 1 pool is specified
20:26:16:149   e38   Main Ethereum pool is us2.ethermine.org:4444
20:26:16:149   e38   DCR: 0 pool is specified


We even went into the console and tried to run the program...exactly the same log as this one. Just keeps shutting down as soon as it starts.

Very frustrated as the miner was running so well for the past four months.  We're newbies so we're at the limit of our knowledge base.
We are running three RX 570's with moded bios....ran patch...they are recognized and in compute mode.  One XFX RX 570 not moded on compute mode....we had stable 111mh/s on previous windows and Claymore 11.0.

Is there any hope?

Clone the SSD from another working rig. Update drivers only, if required.

Interesting "solution". I'd suggest this is NOT a good idea. While svdinu might have the ability to get this to work, I'd suggest it will, in the long run, create a mass of issues, and even if you get it to work, it will take a LOT longer than a OS reinstall of Win10. (especially if you have an SSD, reinstall of Win10home, takes about 15min at most).

On cloning: Actually, unless the motherboard and peripheral devices are identical, it's quite likely the system will fail to boot, or have a bunch of driver issues, which, in the first place, IF you have the ability to solve, (and they are even solvable at all), you would simply know better than to try this solution to start with.

No criticism of svdinu here, simply that when troubleshooting, you need to ensure you are working to eliminate issues, and not introducing any new ones along the way. This solution, introduces a huge array of issues, and potential issues, and potential issues mean doubt later on when you have other problems with the rig.

Start as you intend to go on! (known good etc)

I mention this here, as I say, not to be critical of svdinu, clearly he's trying to help, but when I read that someone formatted/reinstalled their OS, that tells me, they are possibly lacking the experience to know how to identify their issue, and have opted for reinstall, which is extreme, but which is a FAR better idea under these circumstances, (given their skill level)  than trying to clone a SSD, assuming you even have one to clone from.

From a personal POV, I HAVE cloned OS discs many times, would I try it in the context of this problem? NO.

In fact, I build identical rigs for people, and I STILL don't clone SSDs, (unless I'm installing bigger ones, or replacing them etc), but for a new build, I only install fresh, this ensures stability, and no cross pollination, (security for both the client, but also security of stability).

My 5 cents.
Happy Mining

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):

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"KMD_EnableInternalLargePage"=dword:00000002

* if you have modded bioses run dagpatcher to bypass the signature
*use overdriven tool profiles for clocks and volts

[iSuX]

We are having the same problem that Marius 85 and others seem to be having.

How may i fix this? I get a loop with this and it doesn't start mining..

Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)
ETH: Authorized
Reloading epools.txt
ETH: 7 pools are specified
Main Ethereum pool is eth-eu1.nanopool.org:9999
ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <79.137.82.70> port 9999 (unsecure)
ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)

We reformatted our hard drive, reinstalled windows 10...had to go with 1803 as we did not have an older version available.  Downloaded Radeon driver 18.5.2 and Claymore 11.7.  We put the EthDcrminer64.exe into windows defender exceptions and still shuts off as soon as we start.  Here is the last log

20:26:15:884   e38   Check and remove old log files...
20:26:15:884   e38   args: -epool us2.ethermine.org:4444 -ewal xxxxxxxxxxxxxxxxx -epsw x
20:26:15:884   e38   
20:26:15:899   e38   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:26:15:899   e38   º                Claymore's Dual GPU Miner - v11.7               º
20:26:15:899   e38   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:26:15:899   e38   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:26:15:899   e38   
20:26:15:899   e38   b583
20:26:16:149   e38   ETH: 1 pool is specified
20:26:16:149   e38   Main Ethereum pool is us2.ethermine.org:4444
20:26:16:149   e38   DCR: 0 pool is specified


We even went into the console and tried to run the program...exactly the same log as this one. Just keeps shutting down as soon as it starts.

Very frustrated as the miner was running so well for the past four months.  We're newbies so we're at the limit of our knowledge base.
We are running three RX 570's with moded bios....ran patch...they are recognized and in compute mode.  One XFX RX 570 not moded on compute mode....we had stable 111mh/s on previous windows and Claymore 11.0.

Is there any hope?

Clone the SSD from another working rig. Update drivers only, if required.

Interesting "solution". I'd suggest this is NOT a good idea. While svdinu might have the ability to get this to work, I'd suggest it will, in the long run, create a mass of issues, and even if you get it to work, it will take a LOT longer than a OS reinstall of Win10. (especially if you have an SSD, reinstall of Win10home, takes about 15min at most).

On cloning: Actually, unless the motherboard and peripheral devices are identical, it's quite likely the system will fail to boot, or have a bunch of driver issues, which, in the first place, IF you have the ability to solve, (and they are even solvable at all), you would simply know better than to try this solution to start with.

No criticism of svdinu here, simply that when troubleshooting, you need to ensure you are working to eliminate issues, and not introducing any new ones along the way. This solution, introduces a huge array of issues, and potential issues, and potential issues mean doubt later on when you have other problems with the rig.

Start as you intend to go on! (known good etc)

I mention this here, as I say, not to be critical of svdinu, clearly he's trying to help, but when I read that someone formatted/reinstalled their OS, that tells me, they are possibly lacking the experience to know how to identify their issue, and have opted for reinstall, which is extreme, but which is a FAR better idea under these circumstances, (given their skill level)  than trying to clone a SSD, assuming you even have one to clone from.

From a personal POV, I HAVE cloned OS discs many times, would I try it in the context of this problem? NO.

In fact, I build identical rigs for people, and I STILL don't clone SSDs, (unless I'm installing bigger ones, or replacing them etc), but for a new build, I only install fresh, this ensures stability, and no cross pollination, (security for both the client, but also security of stability).

My 5 cents.
Happy Mining

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):

Code:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"KMD_EnableInternalLargePage"=dword:00000002

* if you have modded bioses run dagpatcher to bypass the signature
*use overdriven tool profiles for clocks and volts

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.

[forbidden]

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

Code:

-epool stratum+tcp://pooladdress -ewal wallet.$rigName/mail -esm 0 -epsw x -allpools 1 -asm 1 -wd 0

What the problem?

[vapourminer]

So, in summary, do these old boards/CPUs have a GPU limit?

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.

[Ursul0]

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

[Ursul0]

So, in summary, do these old boards/CPUs have a GPU limit?

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.

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.

[iSuX]

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.

[Ursul0]

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

[svdinu]

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

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?

[Onbusy]

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

[iSuX]

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

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!

[iSuX]

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.

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?

Yeah, I can't say I'm enjoying the banality of it, in that there is no debate as such, not a single statement was rebutted on a technical level, and  emotional, personal attacks are hardly going to help you, or anyone in fact.
Anyway, moving on, I don't think you can roll back here, as you have nothing to roll back on, you've installed a newer win build.

OK, so some time has passed, you've been hard at it, how about a recap?

What is the current situation?

You're on 1803, you have a single GPU in the rig, drivers installed, debug on, can you post the log just before and after the hang?

Don't stress it man, you'll get it running.

Sorry man, I forgot to ask, where did you get your original Win10 install? Did you buy that rig perhaps?
What I mean is, could you maybe have your Win10 1607 install media kicking about somewhere?

That said, I'm not sure that 1803 is necessarily a dead duck for mining, clearly you had some issue right back at the start, that caused you to format and reinstall Win10, I'm just curious as to how your present situation compares with the original one.

What I mean is, that rig was stable, running some months as you said, then it broke, you've done a lot of work on the problem, is it still broke in the same way?

Could you have a hardware issue, is the question I have in my mind right now.

Indeed UFEI install is necessary if you plan on having multiple GPU in the rig, but it wouldn't prevent a single GPU halting claymore init, so considering your present situation, I'd set that aside for now, and focus on specific the issues as they present themselves now.

[svdinu]

driver related issues likely to be encountered when trying to boot a different chipset off the wrong clone os etc.

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?

Yeah, I can't say I'm enjoying the banality of it, in that there is no debate as such, not a single statement was rebutted on a technical level, and  emotional, personal attacks are hardly going to help you, or anyone in fact.
Anyway, moving on, I don't think you can roll back here, as you have nothing to roll back on, you've installed a newer win build.

OK, so some time has passed, you've been hard at it, how about a recap?

What is the current situation?

You're on 1803, you have a single GPU in the rig, drivers installed, debug on, can you post the log just before and after the hang?

Don't stress it man, you'll get it running.

Well, that was not me asking.

As far as I go, I have one rig/work PC with only 2 cards that got itself upgraded to 1803 and it's working just fine with AMD 18.3.4. The rest of my rigs I rolled them to Win 1709 and AMD 17.11.4 as they used to be. All my rigs run 2 epochs without any crash (5-10 days). Good enough to allow some maintenance once in a while.