Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: MingMining on November 03, 2018, 04:12:43 AM



Title: code 43 error
Post by: MingMining on November 03, 2018, 04:12:43 AM
So I am totally out of ideas how to fix this.

My rig has 4x rx 480 and 2x 570. Few days ago I updated the windows 10 to latest and DDU the driver and reinstalled 18.6.1. And got code 43 error on one 480 and one 570. Tried different drivers and it is always these two cards has code 43 error. I tried to set either gen1 or gen2 in BIOS (latest as well), no go. Everything works perfect in the last few months. I used patcher every time after I installed the driver.

Any idea how to fix it? The motherboard is Asrock AB350 gaming k4. TIA.


Title: Re: code 43 error
Post by: polymer_city2 on November 03, 2018, 06:32:33 AM
ati pixel clock patcher 1.4.7


Title: Re: code 43 error
Post by: MingMining on November 03, 2018, 06:46:43 AM
ati pixel clock patcher 1.4.7

I used 1.4.6. Any difference can this make?


Title: Re: code 43 error
Post by: crairezx20 on November 03, 2018, 08:50:21 AM
Let me ask if you flash your cards with modded bios?
Have you tried the blockchain driver?

According to this thread https://bitcointalk.org/index.php?topic=1954245.0

You will receive error 43 if you don't use "Pixel Clock Patcher"

You can follow the guide from the link above I'm sure will save your time fixing this issue.


Title: Re: code 43 error
Post by: abhiseshakana on November 03, 2018, 08:55:17 AM
Try DDU again (in safe mode) and re-install the 18.3.4 driver, then do patch 1.4.6 and restart your mining rig

or you can go back to the previous windows 10 if you still facing those issue.


Title: Re: code 43 error
Post by: stomachgrowls on November 03, 2018, 03:27:31 PM
Try DDU again (in safe mode) and re-install the 18.3.4 driver, then do patch 1.4.6 and restart your mining rig

or you can go back to the previous windows 10 if you still facing those issue.
This is what i dont like when trying to make some updates on Windows 10, you would messed up something leaving you no choice but to revert to previous update.
Thumbs up with suggestion ill suggest sticking out 1.4.6 than on 4.7


Title: Re: code 43 error
Post by: umine on November 03, 2018, 05:27:17 PM
So I am totally out of ideas how to fix this.

My rig has 4x rx 480 and 2x 570. Few days ago I updated the windows 10 to latest and DDU the driver and reinstalled 18.6.1. And got code 43 error on one 480 and one 570. Tried different drivers and it is always these two cards has code 43 error. I tried to set either gen1 or gen2 in BIOS (latest as well), no go. Everything works perfect in the last few months. I used patcher every time after I installed the driver.

Any idea how to fix it? The motherboard is Asrock AB350 gaming k4. TIA.

Check BIOS setting "Above 4G encoding". It should be enabled.
But it's really strange that everything previously worked well and don't work now. Do you exactly update Win 10 to the latest and that's all?


Title: Re: code 43 error
Post by: huntingthesnark on November 03, 2018, 07:04:09 PM
Win10 updates are a complete lottery - disable them via policy manager and only apply them when forced to. If it ain't broke...


Title: Re: code 43 error
Post by: MingMining on November 03, 2018, 08:43:46 PM
Thank you all for the input.

All these cards are bios modded and I always patch using 1.4.5. Tried 1.4.6 and same. 1.4.7 seemed to be a fake one.

Yes I update windows to the latest. The reason is that I did the update is that XMR-Stak is kind of slow and consumes more power for v8 so I want to use SRBMiner, which will use the 18.5.1 driver. So I thought why not just update everything to date. well guess i am wrong.

Finally I went back to the previous version of windows and reset the pc. Now everything works except I am still using xmr-stak with beta blockchain driver and very old windows 10, which can not remote in because my client pc is fully updated...


Title: Re: code 43 error
Post by: swogerino on November 03, 2018, 09:22:23 PM
Thank you all for the input.

All these cards are bios modded and I always patch using 1.4.5. Tried 1.4.6 and same. 1.4.7 seemed to be a fake one.

Yes I update windows to the latest. The reason is that I did the update is that XMR-Stak is kind of slow and consumes more power for v8 so I want to use SRBMiner, which will use the 18.5.1 driver. So I thought why not just update everything to date. well guess i am wrong.

Finally I went back to the previous version of windows and reset the pc. Now everything works except I am still using xmr-stak with beta blockchain driver and very old windows 10, which can not remote in because my client pc is fully updated...

You can install Anydesk which is a free software and does not limit you like Teamviewer does after a certain number of connections. Setup an unattended password and you remotely login to your rig at anytime, there is no problem if your client PC is updated and the remote one is not. Anydesk software does not care about this.


Title: Re: code 43 error
Post by: MingMining on November 04, 2018, 01:20:29 AM

You can install Anydesk which is a free software and does not limit you like Teamviewer does after a certain number of connections. Setup an unattended password and you remotely login to your rig at anytime, there is no problem if your client PC is updated and the remote one is not. Anydesk software does not care about this.

Wow Anydesk is great. Thanks!


Title: Re: code 43 error
Post by: crairezx20 on November 04, 2018, 04:36:52 AM
Thank you all for the input.

All these cards are bios modded and I always patch using 1.4.5. Tried 1.4.6 and same. 1.4.7 seemed to be a fake one.

Yes I update windows to the latest. The reason is that I did the update is that XMR-Stak is kind of slow and consumes more power for v8 so I want to use SRBMiner, which will use the 18.5.1 driver. So I thought why not just update everything to date. well guess i am wrong.

Finally I went back to the previous version of windows and reset the pc. Now everything works except I am still using xmr-stak with beta blockchain driver and very old windows 10, which can not remote in because my client pc is fully updated...

You can install Anydesk which is a free software and does not limit you like Teamviewer does after a certain number of connections. Setup an unattended password and you remotely login to your rig at anytime, there is no problem if your client PC is updated and the remote one is not. Anydesk software does not care about this.
I think chrome remote desktop is fine to use. This is what I am using with my rigs. The good thing about this it is free you don't need to pay for monthly subscription.

@OP the thing that comes to my mind after you update the windows 10 to the latest version it includes the latest driver for your cards which I think the reason why you are having error 43. If you could uninstall and remove all card drivers using DDU you can make a new clean install not just install but need to choose a "clean install" where all necessary settings and files can be fully erased and reinstall new drivers and settings.


Title: Re: code 43 error
Post by: Privatoria on November 04, 2018, 09:40:17 PM
You most likely have modified BIOS flashed on the video cards. Use ati pixel clock patcher 1.4.6, this is the latest version of the program. The official site is https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher. If you are offered a newer version, then it contains a trojan stealing your information.


Title: Re: code 43 error
Post by: YuSoDum on November 05, 2018, 01:11:03 AM
I use google remote desktop...i love it..Side note - I get the code 43 error on two of my amd cards, all of my cards are stock bios with NO modifications. I started getting code 43 after the last windows update. After using pixel patcher everything is fine, just odd I get the error on stock bios...Ive had the same issue before, obviously with modded bios - but never with stock. Till recently.


Title: Re: code 43 error
Post by: sxemini on November 05, 2018, 09:59:27 AM
Win10 updates are a complete lottery - disable them via policy manager and only apply them when forced to. If it ain't broke...

Win10 updates are no lottery, make the right settings (i must only change 2 thins in windows) and it will never make an update. I donīt now why all people canīt disable this and make win10 so bad. For me it is better then all other mining softwares (stable, no reboot, higher hash then linux, easier to use for the most people, and i find failure faster and better then in ethos or something like this)
My Win10 Rigs run for 3 Month without reboot or restart miner.