Quote from: QltMiner on May 28, 2018, 05:06:21 AM

Quote from: iSuX on May 27, 2018, 07:23:26 AM

Quote from: QltMiner on May 27, 2018, 02:38:29 AM

Quote from: svdinu on May 27, 2018, 02:18:54 AM

Quote from: QltMiner on May 27, 2018, 01:49:34 AM

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

Quote from: marius85 on May 26, 2018, 10:34:54 PM

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? Huh

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.

Sorry I just now seen this, stuck in a crawlspace for part of the day...
So here's what I've done:
Installed fresh 1709 then ran updates as Mining.help says to do, which included 1803. Slows to a crawl with mouse sticking every few seconds for several seconds...unusable.
Installed fresh 1803...same result.
Installed 1709 ran updates and then rolled back, some things worked but CM miner not one of them. Also, found that I would get error with GPU-Z, so I hit him up and he sent me a different version that no longer errors on opening or when switching cards, but still OpenCL not populated, which I think is the reason CM miner won't go to that next step.
Installed 1709 ran updates and killed Windows Update as soon as I got all the updates but before 1803 was completely installed...same issue, no CM miner and no OpenCL.
Also have tried 3 different version of AMD drivers...no bueno either.
Tonight, I will go all the way back to 1709 with NO UPDATES, and see if it works. If not, I will try 1607 with NO UPDATES and see if that works. So bothersome :-)