Bitcoin Forum
May 04, 2024, 04:27:49 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 »  All
  Print  
Author Topic: Windows ETH Miner all cards disabled "error 43"  (Read 7236 times)
willi9974 (OP)
Legendary
*
Offline Offline

Activity: 3430
Merit: 2658


Escrow Service


View Profile
May 17, 2017, 06:01:37 AM
 #1

Hello Miner,

my windows 10 ETH Miner with 6 RX 470 cards are running the last 3 weeks whitout any problems.
yesterday the mining stoppt and all cards have the "error 43" reboot and driver reinstall dos not solfe my problem.

Someone has an idea how I can solve that?

Or a other question, is a Mining OS boot from a USB Miner available, i hate windows updates by windows 10

Regards
Willi




.
.BLACKJACK ♠ FUN.
█████████
██████████████
████████████
█████████████████
████████████████▄▄
░█████████████▀░▀▀
██████████████████
░██████████████
████████████████
░██████████████
████████████
███████████████░██
██████████
CRYPTO CASINO &
SPORTS BETTING
▄▄███████▄▄
▄███████████████▄
███████████████████
█████████████████████
███████████████████████
█████████████████████████
█████████████████████████
█████████████████████████
███████████████████████
█████████████████████
███████████████████
▀███████████████▀
█████████
.
1714796869
Hero Member
*
Offline Offline

Posts: 1714796869

View Profile Personal Message (Offline)

Ignore
1714796869
Reply with quote  #2

1714796869
Report to moderator
1714796869
Hero Member
*
Offline Offline

Posts: 1714796869

View Profile Personal Message (Offline)

Ignore
1714796869
Reply with quote  #2

1714796869
Report to moderator
1714796869
Hero Member
*
Offline Offline

Posts: 1714796869

View Profile Personal Message (Offline)

Ignore
1714796869
Reply with quote  #2

1714796869
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
construktor
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
May 17, 2017, 06:45:52 AM
 #2

Same thing happened to me and someone else I know. Win10 update broke something really badly.

If you're lucky, you will have option to roll back to previous driver in device manage, I was able to fix 2 rigs this way. But some others it did not fix all cards, and even after reinstalling windows, or reseting windows, both scenarios have not solved the issue.

Walrusbonzo
Hero Member
*****
Offline Offline

Activity: 682
Merit: 500


View Profile
May 17, 2017, 07:00:36 AM
 #3

You need to use AMD Pixel Clock Patcher tool

Download from here - https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher

Run it and reboot.

It modifies the drivers to allow running of non-signed custom BIOS which sounds like the problem you are having.
tgejesse
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
May 17, 2017, 07:10:03 AM
 #4

Same thing happened to me and someone else I know. Win10 update broke something really badly.

If you're lucky, you will have option to roll back to previous driver in device manage, I was able to fix 2 rigs this way. But some others it did not fix all cards, and even after reinstalling windows, or reseting windows, both scenarios have not solved the issue.


Same shit happened to me today, messed up my rig. Its 3am and I'm extremely happy this is not just me. Fuck windows and their updates.
construktor
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
May 17, 2017, 07:29:23 AM
 #5

@Walrusbonzo - I just spent all night trying to troubleshoot, this patch seemed to have done the trick on the first rig - thank you!

Only reason I chose win10 was for good hashrate, dual mining for amd specifically.. hate the updates as much as the next guy.
klaaas
Hero Member
*****
Offline Offline

Activity: 1568
Merit: 544



View Profile
May 17, 2017, 07:36:56 AM
 #6

Or a other question, is a Mining OS boot from a USB Miner available, i hate windows updates by windows 10

Google will point you to the linux distros.
Pick your flavor.  Wink

Shopping online and sats back as a discount! (satsback) + LightningNetwork
Heardalis
Sr. Member
****
Offline Offline

Activity: 453
Merit: 264


View Profile
May 17, 2017, 07:44:56 AM
 #7

Hello Miner,

my windows 10 ETH Miner with 6 RX 470 cards are running the last 3 weeks whitout any problems.
yesterday the mining stoppt and all cards have the "error 43" reboot and driver reinstall dos not solfe my problem.

Someone has an idea how I can solve that?

Or a other question, is a Mining OS boot from a USB Miner available, i hate windows updates by windows 10

Regards
Willi





hmmm its autoupdate from amd driver:)

so just use ddu to cleanthe driver and load the old one or use the patcher for the new one


construktor
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
May 17, 2017, 09:30:58 AM
 #8

I spoke too soon,

I tried cleaning with DDU, installing older version, but the error code does not go away for all the cards. After running the patcher, it is often causing the rigs to have start up errors.

I have to start in safemode, uninstall display drivers again, and reinstall, but I get faced with code 43, even when using an older amd installer.
un4given
Full Member
***
Offline Offline

Activity: 192
Merit: 100


View Profile
May 17, 2017, 10:02:54 AM
 #9

bad to see i am not the only one stuck with this error. so using ATI PIXEL PATCHER will help? did any1 test it. don't want to reinstall the complete system...

i think i should deactivate automatic driver updates on all machines...wanted to do it for a long time already
construktor
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
May 17, 2017, 10:16:01 AM
 #10

Pixel patcher worked for my rig only running 2 GPUs, I tried on two of my 6x GPU rigs, and windows would be unable to restart afterwards, repair fails, I would have to boot in safe mode, uninstall display drivers, and back to square one.

I stayed up all night, only managed to get half my hashrate up. Need some sleep, I think I might say goodbye to windows.

I even tried switching my dual bios to the unmodded ones and same code 43 stuck around
un4given
Full Member
***
Offline Offline

Activity: 192
Merit: 100


View Profile
May 17, 2017, 10:18:16 AM
 #11

Pixel patcher worked for my rig only running 2 GPUs, I tried on two of my 6x GPU rigs, and windows would be unable to restart afterwards, repair fails, I would have to boot in safe mode, uninstall display drivers, and back to square one.

I stayed up all night, only managed to get half my hashrate up. Need some sleep, I think I might say goodbye to windows.

I even tried switching my dual bios to the unmodded ones and same code 43 stuck around

i think i will do a fresh win 10 install anyway and install 16.9.2 driver and disable all kinds of updates possible...slowly thinking about installing simplemining OS for the rx series...
construktor
Newbie
*
Offline Offline

Activity: 35
Merit: 0


View Profile
May 17, 2017, 10:37:35 AM
 #12

Quote

i think i will do a fresh win 10 install anyway and install 16.9.2 driver and disable all kinds of updates possible...slowly thinking about installing simplemining OS for the rx series...

Fresh install didn't do it for me either, tried on two rigs..
un4given
Full Member
***
Offline Offline

Activity: 192
Merit: 100


View Profile
May 17, 2017, 11:47:08 AM
 #13

Quote

i think i will do a fresh win 10 install anyway and install 16.9.2 driver and disable all kinds of updates possible...slowly thinking about installing simplemining OS for the rx series...

Fresh install didn't do it for me either, tried on two rigs..

but how comes the reinstall didn't help? it is a software issue not a hardware one...or did the update lock smth. in BIOS of the board (which i doubt)
Eyedol-X
Hero Member
*****
Offline Offline

Activity: 952
Merit: 508



View Profile
May 17, 2017, 11:52:02 AM
 #14

Go into device manager, find video card, any of them, right click and select properties.

On the Driver Tab: If you have the option to "Roll Back" the driver this means Windows update installed a new one. Roll back the driver to restore functionality.

Has happened on a few of my rigs with updates from yesterday.

On a side note: Supposedly doing this prevents windows 10 from reinstalling the newer driver, until a "newer" one comes out.

2nd note: you'll need to re-run pixel patch after doing this.
FFI2013
Hero Member
*****
Offline Offline

Activity: 906
Merit: 507


View Profile
May 17, 2017, 12:27:29 PM
 #15

the problem is win 10 installs updates while your installing also I've removed the drivers and as soon as you reboot it starts installing the updated driver you have to google how to stop win 10 update by going through the registry and download the drivers you need than disconnect from the internet disable the updates through registry install your drivers and connect back the internet I think its bullshit that win 10 just updates drivers without your consent   
Truthchanter
Sr. Member
****
Offline Offline

Activity: 689
Merit: 253


View Profile
May 17, 2017, 12:57:29 PM
Last edit: May 17, 2017, 01:14:18 PM by Truthchanter
 #16

Someone should try reinstalling win10 with internet/ethernet unplugged and then going into computer management -> services -> and disabling win10 updates.. then plug in internet get good drivers like 16.9.2 and see if the error is there or not.

I'm having this issue too and working towards a solution

EDIT:

I think i fixed it on one of my rigs by simply reinstalling the driver (16.9.1)

EDIT2: nvm it worked for a minute then stopped. let me try disabling windows update and then reinstalling the drivers (idk if I can access services through chrome remote desktop correctly though, i first had a display bug)
un4given
Full Member
***
Offline Offline

Activity: 192
Merit: 100


View Profile
May 17, 2017, 01:04:54 PM
 #17

Someone should try reinstalling win10 with internet/ethernet unplugged and then going into computer management -> services -> and disabling win10 updates.. then plug in internet get good drivers like 16.9.2 and see if the error is there or not.

I'm having this issue too and working towards a solution
i will try multiple solutions on 2 of my rigs and post the results. heading home in 30 mins so will do an update in 2-3 hours
Eyedol-X
Hero Member
*****
Offline Offline

Activity: 952
Merit: 508



View Profile
May 17, 2017, 01:23:18 PM
 #18

If it works then stops, you should have the rollback driver option, once this is done, Windows will stop trying to auto-update it

I have multiple rigs now with this issue and all were fixed in under 5 mins each by doing what I outlined above.
minerman121
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
May 17, 2017, 01:25:23 PM
 #19

check to make sure you have set at least 32000 virtual memory. This error sounds familiar to something I experienced where some cards ran , the others disabled. It could be a ram stick that died but regardless of that, check to make sure you have sufficient virtual memory.
miropp
Full Member
***
Offline Offline

Activity: 810
Merit: 101



View Profile
May 17, 2017, 01:41:04 PM
 #20

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?

Pages: [1] 2 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!