Guys,
I have one miner that i cannot figure out. Mind you i have 30+ but yes i cannot figure this one out, and its driving me nuts.
The issue is that after the Windows 10 April update the miner will start but pauses....it does not close. I have tried everything i know and nothing. So i went ahead and installed a clean version of 1709 build with all of its updates.
I have reinstalled 11.7(which was working with no issues prior) and still nothing. I have tried adrenaline 18.2 and even downgraded to the blockchain drivers and still nothing. The motherboard is up to date, windows sees all the cards...no issues there. I have patched the drivers...etc...etc...
These are AMD RX560's that have been modded...and again these were working fine before the darn update got me.....I have also excluded the claymore folder in defender, set a pause for 30 seconds etc...
Im hoping someone out there has run into this prior....i am now having this same issue with another rig running rx470's
Any help would be appreciated
Thanks
Updates, sigh.
Well, OK...
You have 30+ miners? WOW, so this should be well within your means to solve.
First: Work out if you have a hardware problem. (Take one/some of those problem GPU to a good rig and test)
Given you have 30+, I assume you long ago recognised the absolute necessity for a dedicated development/testing rig, so use that one, which of course you would NEVER update, if you expect it to act as your benchmark. ;-)
Check my post on power supply cables, I mention this, as it's easy to waste time thinking only about the stuff you most recently changed, and back track from there, but if the rig was off for a while, during updates, and subsequent issues, it's not impossible you have other problems, hardware related set of some time bombs etc.
I'd suggest not wasting time, and MAN that wastes time, on anyone using the Aug 2017 blockchain drivers, certainly not for purposes of troubleshooting, they are beta after all, and specifically tagged as not stable/released.
But to be clear, make sure you eliminate the hardware before expending time on the software.
(You could also pull all GPU from that rig, drop in a known good GPU, riser, cable etc), and see what that reveals.
All the more easy when you have as much hardware as you have.
If you're 100% certain the hw is ok, set log to debug, see what is going on before/after the hang event
Hope you get some sleep too.
Good luck man.