So i started mining 9 months ago. 8 card rig, all of em 1060 6 GB cards. Things ran relatively smooth. I took the steps necessary and advised to block any and all windows updates. Well, at some point Windows overpowered.......windows lol. It went from 1709 to the latest 1803 build. This foooked everything up.
Happened like 2 days ago. Anyway, after 4 hours of messing with -eres 1 or -litag 0,1,2,3 etc etc and trying new and old claymore versions; not to mention hours of googling, i finally just did a restore build. You can rapidly and VERY simply roll back windows builds. Zero issues.
Everything is up n humming at my normal 193.7 Mh/s!!!!
This is just an FYI for anyone who gets an update on accident. I did have my updates completely shut off. I have no clue how it updated but when i saw my miner offline the other night i went downstairs to check on it and saw it in action, doing an update.
Happy mining!
0 ·
Comments
I spoke with Asus and they told me their entire product line is affected by the Windows update and they are trying to play catch up to update all their drivers. Nice BS from Microsoft with this! I also had updates disabled including the update service but it still came through. 1803 did make my I9 Windows Workstation with a 1080ti more stable though. Computer is more stable now than it was a few months ago.
Windows updates were shut off when I first setup the rig.
My rigs have been shut off for over a week now due to a lack of mining profitability because of high electric cost.
The other day, I noticed that the rig with 6 sapphire nitro cards was on and only one of the sapphire cards lit up. It should not have been on. I shut it off.
Today, I decided to check on it and turned it on. At first, all of the saphire cards lit up and then 5 of them went out with only the one with the monitor plug into it staying on. It uses a dvi to vga adaptor and the monitor appeared to inactive. I then connected a dvi monitor to it and got a windows screen. A browser window appeared saying that an update for April or some such had been done. Then, trying to start ethminer it failed.