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

[74hawksfan]

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

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!

[1714000629]

1714000629

[1714000629]

1714000629

[1714000629]

1714000629

[1714000629]

1714000629

[Ursul0]

do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"

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

Code:

Edition: Windows 10, product language = English

Windows 10 English 64-bit download

File name = Win10_1607_English_x64

SHA1 hash value: 99fd8082a609997ae97a514dca22becf20420891

[svdinu]

do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"

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

Code:

Edition: Windows 10, product language = English

Windows 10 English 64-bit download

File name = Win10_1607_English_x64

SHA1 hash value: 99fd8082a609997ae97a514dca22becf20420891

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!

[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).

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!

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.

[iSuX]

do NOT blanket, with wide reaching statements like "all your ideas in this area is total crap"

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

Code:

Edition: Windows 10, product language = English

Windows 10 English 64-bit download

File name = Win10_1607_English_x64

SHA1 hash value: 99fd8082a609997ae97a514dca22becf20420891

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

[Jonet]

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?

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

[iSuX]

Hello guys, i have a problem, the cards are 1050ti 4gb, updated to latest drivers and latest claymore, tried changing virtual memory, but there is still problem. What to do? Thanks in advance!

CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:234   ab8   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:240   1f48   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:258   1f18   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:295   1b30   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:24:991   a58   Set global fail flag, failed GPU2
19:36:24:999   a58   GPU 2 failed
19:36:24:998   1fec   Setting DAG epoch #189 for GPU2
19:36:25:010   1fec   GPU 2, CUDA error 11 - cannot write buffer for DAG

19:36:25:241   ab8   Set global fail flag, failed GPU0
19:36:25:247   ab8   GPU 0 failed
19:36:25:254   af0   Setting DAG epoch #189 for GPU0
19:36:25:251   1f48   Set global fail flag, failed GPU4
19:36:25:266   1f48   GPU 4 failed
19:36:25:277   af0   GPU 0, CUDA error 11 - cannot write buffer for DAG

19:36:25:272   1f18   Set global fail flag, failed GPU5
19:36:25:289   1f2c   Setting DAG epoch #189 for GPU4
19:36:25:305   1f2c   GPU 4, CUDA error 11 - cannot write buffer for DAG

19:36:25:311   1e08   Setting DAG epoch #189 for GPU5
19:36:25:305   1b30   Set global fail flag, failed GPU3
19:36:25:326   1b30   GPU 3 failed
19:36:25:337   1e08   GPU 5, CUDA error 11 - cannot write buffer for DAG

19:36:25:343   1f18   GPU 5 failed
19:36:25:350   1ff0   Setting DAG epoch #189 for GPU3
19:36:25:360   1ff0   GPU 3, CUDA error 11 - cannot write buffer for DAG

19:36:25:394   1ff4   buf: {"id":0,"jsonrpc":"2.0","result":["0x8cc05aa8be75170e0cf74ab6ac892516828e014b33e2ece87efcf493ff753f1d","0x7bb6f14a940828054edc1aa9ec9f31e274e036a730709926e1f2900225e2f745","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x56c530"]}

19:36:25:403   1ff4   ETH: 05/27/18-19:36:25 - New job from eu1.ethermine.org:4444
19:36:25:407   1ff4   target: 0x0000000112e0be82 (diff: 4000MH), epoch 189(2.48GB)
19:36:25:414   1ff4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:36:25:423   1ff4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
19:36:28:018   1fec   Set global fail flag, failed GPU2
19:36:28:023   1fec   GPU 2 failed
19:36:28:289   af0   Set global fail flag, failed GPU0
19:36:28:294   af0   GPU 0 failed
19:36:28:312   1f2c   Set global fail flag, failed GPU4
19:36:28:322   1f2c   GPU 4 failed
19:36:28:344   1e08   Set global fail flag, failed GPU5
19:36:28:351   1e08   GPU 5 failed
19:36:28:367   1ff0   Set global fail flag, failed GPU3
19:36:28:376   1ff0   GPU 3 failed

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?

[Ursul0]

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!

to get rid of the windows updates: 1) disconnect Internet (not really a must, but will be even better) 2) run gpedit.msc, find Windows Updates under Administrative templates and set (at least...as there's much more stuff to get rid of) "Configure Automatic Updates" to "disabled" and "Do not include drivers with windows update" to "enable"  3) run "gpupdate -force" from CMD and reboot

[Maniac9331]

Hello,

This is an iOS app for monitoring cryptocurrency miners. Claymores and Antminer are supported.

Features:

- Fast loading.
- Smooth GUI with asynchronous computation.
- Users are allowed to edit rig information.
- Users can re-arrange the order of rigs.
- Remote rebooting is supported.
- Users can view the full console of Claymores with one touch.
- Easier viewing long lists of rigs with Compact view mode.
- Highlight problems of too low speed and/or too high temperature.
- Both iPhone and iPad are supported, iOS 9.0 or higher is required.

Screenshots:

https://imgur.com/a/1CAfNCy

Available on Apple Store:

https://itunes.apple.com/us/app/youngbuffalo/id1386685965?mt=8

Thanks for reading my post.

good app but is this only working when the phone is connected to the same network as the miners?

[lesjokolat]

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

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!

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.

If this is actual bat then I see something missing

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


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

if you have a much longer script line like examples shown make sure its all 1 line and not hard return broken into multiple lines.

also not sure if it helps but I have my setx
setx GPU_FORCE_64BIT_PTR 0

not
setx GPU_FORCE_64BIT_PTR 1

as you are using 13 gpus the pagefile settings may need a lot more than 16 gig, can you bump it up to 32 or 48.

also check gpus are sitting well in risers I had one angled weird that caused me tons of grief.
gltu

as an aside i used to use suprnnova but switched to ethertrench.com no fees smaller pool but increased my eth ratio by 20%.

[Ursul0]

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.`

IMO your logic is flawed: Obviously the more actions you take the more chances you've got to fuck up.
Do it ONCE proper, test, automate deployment, test again.

Also I use this http://www.winsetupfromusb.com/downloads/ to create multiboot USB with acronis, all needed Win versions, Ubuntu, BootCD, and the actual image. ... and I cloned this USB drive too:) and because I'm lazy and it actually saves tons of time and gets the result I used the same fine tuned win10 miner image for my vaio laptop (and it's way better than the bloated shit it came with)

Note on updates: why would anyone want to update or in fact introduce ANY changes to OS under miner, if it hashes at the rates its GPUs are capable of?  

[danielcrypto98]

Hello guys, i have a problem, the cards are 1050ti 4gb, updated to latest drivers and latest claymore, tried changing virtual memory, but there is still problem. What to do? Thanks in advance!

CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:234   ab8   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:240   1f48   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:258   1f18   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:295   1b30   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:24:991   a58   Set global fail flag, failed GPU2
19:36:24:999   a58   GPU 2 failed
19:36:24:998   1fec   Setting DAG epoch #189 for GPU2
19:36:25:010   1fec   GPU 2, CUDA error 11 - cannot write buffer for DAG

19:36:25:241   ab8   Set global fail flag, failed GPU0
19:36:25:247   ab8   GPU 0 failed
19:36:25:254   af0   Setting DAG epoch #189 for GPU0
19:36:25:251   1f48   Set global fail flag, failed GPU4
19:36:25:266   1f48   GPU 4 failed
19:36:25:277   af0   GPU 0, CUDA error 11 - cannot write buffer for DAG

19:36:25:272   1f18   Set global fail flag, failed GPU5
19:36:25:289   1f2c   Setting DAG epoch #189 for GPU4
19:36:25:305   1f2c   GPU 4, CUDA error 11 - cannot write buffer for DAG

19:36:25:311   1e08   Setting DAG epoch #189 for GPU5
19:36:25:305   1b30   Set global fail flag, failed GPU3
19:36:25:326   1b30   GPU 3 failed
19:36:25:337   1e08   GPU 5, CUDA error 11 - cannot write buffer for DAG

19:36:25:343   1f18   GPU 5 failed
19:36:25:350   1ff0   Setting DAG epoch #189 for GPU3
19:36:25:360   1ff0   GPU 3, CUDA error 11 - cannot write buffer for DAG

19:36:25:394   1ff4   buf: {"id":0,"jsonrpc":"2.0","result":["0x8cc05aa8be75170e0cf74ab6ac892516828e014b33e2ece87efcf493ff753f1d","0x7bb6f14a940828054edc1aa9ec9f31e274e036a730709926e1f2900225e2f745","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x56c530"]}

19:36:25:403   1ff4   ETH: 05/27/18-19:36:25 - New job from eu1.ethermine.org:4444
19:36:25:407   1ff4   target: 0x0000000112e0be82 (diff: 4000MH), epoch 189(2.48GB)
19:36:25:414   1ff4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
19:36:25:423   1ff4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
19:36:28:018   1fec   Set global fail flag, failed GPU2
19:36:28:023   1fec   GPU 2 failed
19:36:28:289   af0   Set global fail flag, failed GPU0
19:36:28:294   af0   GPU 0 failed
19:36:28:312   1f2c   Set global fail flag, failed GPU4
19:36:28:322   1f2c   GPU 4 failed
19:36:28:344   1e08   Set global fail flag, failed GPU5
19:36:28:351   1e08   GPU 5 failed
19:36:28:367   1ff0   Set global fail flag, failed GPU3
19:36:28:376   1ff0   GPU 3 failed

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?

I am running 16000 MB VM, i am not dual mining, the cards are 4gb, i have another rig same exact configuration and it is working well. I did a clean installation on drivers and still no progress...
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal xxx.Mechanic -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg 0 -ethi 16

Today I had the same problem with 6 GPU Nvidia 1060 6GB, my solution it was increase the VM to 25 GB

[Jonet]

Claymore is crashing at startup ('EthDcrMiner64.exe has stopped working) unless I have a working monitor attached to the motherboard HDMI port.
I have set up several rigs with the Radeon Blockchain driver and always just used the onboard GPU during setup. I decided to try Adrenaline and OverdriveNTool for a new build but can't figure out how to get around this problem. If the rig reboots and the monitor is asleep, this problem will occur and there is no way to fix it remotely. I have tied all BIOS settings for the onboard GPU.

You sure onboard GPU is turned off in the BIOS. If not, just put an HDMI dummy dongle on it. The computer will think there is a monitor on the port.

HDMI dummy did work, but when I ran in to this issue on a second rig I found out that it can be solved by downloading and installing the most recent driver for the onboard intel GPU.
It looks like the driver that Windows 10 will install is confusing Claymore in some way.

On a rig updated to 1709 from a previous build this problem did not occur.
On an identical rig with 1709 installed from scratch I ran into this issue.

Several people has reported that claymore crashes on new buildt rigs, and if you are setting up the last bit remote or with monitor attached to one of the GPU cards, this could be the problem you are facing.

[Bigdrago]

Where is reboot.bat ? It isnt in the claymore directory.
I want the miner to restart pc when hasha goes below xx

[Raja_MBZ]

Where is reboot.bat ? It isnt in the claymore directory.
I want the miner to restart pc when hasha goes below xx

May I ask how often your miner's hashrate goes below your required criteria? IMO, rebooting the whole system isn't something you should use to tackle that issue. It'd be much better for long-term stability of your system if you focus on restarting the miner window instead of whole system. I use a particular code which I can share (similar code was shared in this altcoin mining section as well like a year back) if you're facing the decline of hashrate like after every few hours.

[Call_Me_Bambi]

Where is reboot.bat ? It isnt in the claymore directory.
I want the miner to restart pc when hasha goes below xx

The 'reboot.bat' file is not created by, nor does it come installed with, Claymore. You have to create your own 'reboot.bat' file and place it in the Claymore directory. I'd take up Raja_MBZ offer and give it a try.

[leonix007]

Hello guys, i have a problem, the cards are 1050ti 4gb, updated to latest drivers and latest claymore, tried changing virtual memory, but there is still problem. What to do? Thanks in advance!

CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:234   ab8   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:240   1f48   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:258   1f18   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

19:36:22:295   1b30   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

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?

I am running 16000 MB VM, i am not dual mining, the cards are 4gb, i have another rig same exact configuration and it is working well. I did a clean installation on drivers and still no progress...
EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal xxx.Mechanic -epsw x -esm 0 -mode 1 -wd 1 -r 1 -dbg 0 -ethi 16

try adding -eres 0 in your bat file config

[AzzAz]

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?

Settings/Updates&sequrity/view recent updates/recovery options/back to your previous version... ?

[QltMiner]

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

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.

I thought of "quoting" all of you who have posted your suggestions but that would just get ridiculous.  Thank you all for your willingness to help.  I am so thankful for all of the posts and comments.  This forum is so helpful. 
iSuX somehow I had missed the debug...I'm mining because I love learning and constantly figuring things out so we're going to try that next.  (Although 74hawksfans' log after they ran the -dbg 1 command still looks like mine.)  I reread the ReadMe file and there is the -oldkernel command and we haven't tried that either.  We're pretty sure the hibernation isn't an issue as we have a 250G SSD and our VM is set to 36 with only 4 cards. Our batch file is very basic, nothing past -epsw x as we're just trying to get it back to life for now.  I saw posts by lesjokolat and Jonet we're going to try, making sure of spaces and hard returns.


After the reinstall of Windows 10 version 1803 we ran DDU twice then reinstalled the latest Adreniline 18.5.1 with one gpu plugged in.  That gpu does not have a bios mod. We didn't try to run with just that one gpu so we'll do that with the -dbg command and update you all when we see how that goes. 
74hawksfan...have you found out how to get back to 1709?  I think that would fix all our issues.  Urs10 thank you for the link to the Win 10 Anniversary 1607 ISO. If debug doesn't get as any further we may go all the way back to that and try it and the AMD 18.3.4 as others say that driver is stable. 

All it'll take is time.  We're old retired folks...yes guys baby boomers can be into crypto!  So we have nothing but time.
Thanks again to all of you.

[74hawksfan]

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

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!

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.

Same result after multiple DDU removes and fresh GPU driver installs.  Spent today doing fresh install of 1803, which as soon as I installed 7 or more GPU's the thing would just crawl to a snails pace...lagging so heavy I couldn't handle it.
Then did a fresh install of 1709, super quick, no BSOD during install, no freezes, smooth.  Got driver installed and all the W10 tweaks done, tried to install Hwinfo64 after all the oc/uv was complete...Hwinfo64 stops working almost immediately after starting it up, gets stuck and freezes on "checking system configuration - analyzing pcie bus"
Searched and couldn't find a solution, uncheck this, check that...etc.  Nothing worked.
Then noticed your guys comments, and I'm still getting the same error on GPU-Z, and still no Opencl populated.  So there I am :-)