
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)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"KMD_EnableInternalLargePage"=dword:00000002