Topic: Windows ETH Miner all cards disabled "error 43" (Read 7281 times)

I didn't have the option to roll back. I used DDU, installed 16.9.2 driver, and then disabled windows from updating the driver. It worked like a charm and I got all my hashrate up and running again.

You're welcome, it was a long and sleepless night for me as well, however I should note that I no longer recommend skipping step 1 to 4 if you can roll back the driver - it seems it has a more dependable result if DDU is always used to uninstall the drivers and help block future updates. I crossed it out of my original post.

Thank you for the step by step directions... I had been troubleshooting all day long and part of today but to no avail. This worked perfectly.

Here's a process that worked for me, with some brainstorming, my business partner tested this out successfully through trial and error:

So if your GPUs are getting code 43 - and you don't have the option to roll back the drivers follow the steps below from 1 to 8.

If you do have the option to roll back the drivers, and the error disappears, skip to step 5 in order to block all future AMD device driver updates. This doesn't always work. From my testing, it is best to always remove the drivers using DDU, and installing the previous ones manually.

1- Reboot in safe mode and run DDU, uninstall drivers without restarting option selected.

2- Disable GPUs under device manager, then restart - alternatively, keep ethernet disconnected so it does not update GPUs - or if you're paranoid, do both and that should stop all attempts to install device drivers.

3- Install crimson 16.9.2 or your choice of driver version. This one is working well for me after other members posted about it, gave it a shot.

4- Don't restart after installing drivers, and make sure the box to automatically update drivers is unchecked.

5- Launch CMD prompt box as administrator - type gpedit and press enter

6- Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions >prevent installation of devices that match any of these device id's

7 - get hardware device id for gpu from device manager > device properties > details.  (I believe it's the same for all similar cards) add it under enabled list, save, reboot, start mining again.

---

I also ran into a problem where one of my flashed bios cards would crash on driver install since this update, so if you keep having problems, maybe start testing with process of elimination.

I have it turned of but still it installed the update. Very maddening. Anyway, this worked for my 3x 480 rig. But it does not work for my 6x 580 rig. I can use Claymore Zec miner just fine, but not the dual miner 

Solved my problem, with a 4 GPU rig. My other rigs didn't seem to have the same problem because windows update was turned off i guess...

If you have RX 570/580 GPUs this may help:  https://youtu.be/fTusQ0omj8M

Hmm good to know thanks.. could always just reinstall win10 if that ever happened i would think.



did you reinstall the drivers too?

This trick only works up to 4 cards now 

I had all six, the error happened. I disabled windows update service, and now only 4 of my 6 cards lol.

DO NOT DISABLE WINDOWS UPDATE!  Do you want your mining rigs to end up as botnets?  Because that's how you get botnets. https://arstechnica.com/security/2017/05/an-nsa-derived-ransomware-worm-is-shutting-down-computers-worldwide/

You can block driver updates, but still allow windows updates: http://www.thewindowsclub.com/stop-windows-7-from-installing-drivers-automatically

can you share your blocked DNS names and IP adresses, so i can edit localhost file :-)



My Miner is working!

-- DDU uninstall all GPU driver
-- deactivate automaticly driver update (directly from the DDU tool!)
-- reinstall the old driver


and will test a boot from a usb stick with the SimpleMining.net as a fallback if windows fucks me again!


Best regards from germany and many thanks for your help
Willi

2 of my 5 rigs still have an issue of only 5 of the 7 cards being recognized. Both are pcie slot 6 and 7. Any ideas?

Had this issue almost on all my rigs.it sucks that there is no easy way to disable update in windows 10

to prevent this I blocked microsoft and amd sites on my linksys router.  simple as that

1. Disable windows update in computer management -> services

2. Roll back driver, or if its greyed out, reinstall your good driver like 16.9.2 or w/e

/thread

Hasn't come back for any of mine so that is odd.

Fuck!

i have no option rollback the driver. The "driver rollback" button is grayed out and i have patched the driver, after the reboot i run in a reboot repair loop --> RIP WIN 10

Now i will use the last system repair point to get out of the loop, cross the fingers....

thx @Eyedol-X

your solution with driver rollback worked perfectly fine. disabled also the driver updates, since i coulndt change the registry to disable the updates at all.

rigs up and working perfectly fine. hope others managed to solve their issues too

EDIT: problem seems to come back. working on it

With win10 i had to go to computer management then services and then both stop and disable the windows update service. Then either rollback or reinstall the drivers and i have been good so far. Skipping disabling windows update and rolling drivers back only temporarily worked and then the issue came back.

Had the same issue yesterday.  The fix for it is to use DDU, reinstall the good drivers, then (and this is crucial) block any further driver updates/changes.  The easiest way to do that is via one of these options: http://www.thewindowsclub.com/stop-windows-7-from-installing-drivers-automatically  (Note:  the first option does not seem to be valid anymore with Windows 10, but the Group Policy fix worked perfectly for me)

In my case, the driver that seems to be the most consistent is 16.11.5, though I've had other rigs work just fine on different versions as well.

Yesterday and today I had the same problem on 3 rigs. I had to run DDU in safe mode and then reinstall old good drivers (in my case 16.11.5).
But, how to prevent it from happening again? And why it happens only on some rigs and on the others (same configuration and Win10 subversion) not?