Bitcoin Forum
June 22, 2024, 06:20:43 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [Problem] I can't connect more than 2 card ( Code 43 )  (Read 97 times)
Morxander (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 19, 2018, 07:06:26 AM
 #1

Hey Miners,

I have a rig with 3 cards ( Vega 64 ) running on Windows 10.
I can connect the 3 cards on the motherboard directly but I'll face a heating problem so I decided to take one card out and I connected it with a USB Riser.
It's works fine for couple of minutes ( sometime hours ) then the mining software stops and If I ran it again it doesn't mine so I have to restart my machine and when I do that Windows can't read the third card and it shows a yellow triangle with Error Code 43.
I changed the USB Riser and still the same problem, I tried to switch the cards and the slots and everything and the problem is always there.
I have ASUS Z270E with 4 GB Ram and I increased the Virtual Memory but still no luck.
huntingthesnark
Member
**
Offline Offline

Activity: 357
Merit: 26


View Profile WWW
February 19, 2018, 09:25:54 AM
 #2

Hey Miners,

I have a rig with 3 cards ( Vega 64 ) running on Windows 10.
I can connect the 3 cards on the motherboard directly but I'll face a heating problem so I decided to take one card out and I connected it with a USB Riser.
It's works fine for couple of minutes ( sometime hours ) then the mining software stops and If I ran it again it doesn't mine so I have to restart my machine and when I do that Windows can't read the third card and it shows a yellow triangle with Error Code 43.
I changed the USB Riser and still the same problem, I tried to switch the cards and the slots and everything and the problem is always there.
I have ASUS Z270E with 4 GB Ram and I increased the Virtual Memory but still no luck.

Think you'll need more than 4GB ram installed - 8 or 16.

For the latest Crypto news and alts info check out https://coinsjar.info/
leonix007
Sr. Member
****
Offline Offline

Activity: 1008
Merit: 297


Grow with community


View Profile
February 19, 2018, 09:33:55 AM
 #3

this might of help. try these steps just in case would solve the problem.

https://www.drivethelife.com/windows-10/how-to-fix-amd-radeon-graphics-error-43-on-windows-10.html
treanski
Full Member
***
Offline Offline

Activity: 364
Merit: 106


ONe Social Network.


View Profile
February 19, 2018, 09:35:03 AM
 #4

Hey Miners,

I have a rig with 3 cards ( Vega 64 ) running on Windows 10.
I can connect the 3 cards on the motherboard directly but I'll face a heating problem so I decided to take one card out and I connected it with a USB Riser.
It's works fine for couple of minutes ( sometime hours ) then the mining software stops and If I ran it again it doesn't mine so I have to restart my machine and when I do that Windows can't read the third card and it shows a yellow triangle with Error Code 43.
I changed the USB Riser and still the same problem, I tried to switch the cards and the slots and everything and the problem is always there.
I have ASUS Z270E with 4 GB Ram and I increased the Virtual Memory but still no luck.

Think you'll need more than 4GB ram installed - 8 or 16.

4gb is enough even for vega, @topic dont connect your riser with sata to molex.

Morxander (OP)
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
February 19, 2018, 10:08:00 AM
 #5

Hey Miners,

I have a rig with 3 cards ( Vega 64 ) running on Windows 10.
I can connect the 3 cards on the motherboard directly but I'll face a heating problem so I decided to take one card out and I connected it with a USB Riser.
It's works fine for couple of minutes ( sometime hours ) then the mining software stops and If I ran it again it doesn't mine so I have to restart my machine and when I do that Windows can't read the third card and it shows a yellow triangle with Error Code 43.
I changed the USB Riser and still the same problem, I tried to switch the cards and the slots and everything and the problem is always there.
I have ASUS Z270E with 4 GB Ram and I increased the Virtual Memory but still no luck.

Think you'll need more than 4GB ram installed - 8 or 16.

4gb is enough even for vega, @topic dont connect your riser with sata to molex.

Yes I think 4GB is enough because I checked the memory usage, My riser takes sata OR 6 pins for power and I am using the sata cable to power it.
phuocduong
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
February 19, 2018, 10:27:40 AM
 #6

enable 4g coding, disable vga onboard ...
huntingthesnark
Member
**
Offline Offline

Activity: 357
Merit: 26


View Profile WWW
February 19, 2018, 11:15:46 AM
 #7

Hey Miners,

I have a rig with 3 cards ( Vega 64 ) running on Windows 10.
I can connect the 3 cards on the motherboard directly but I'll face a heating problem so I decided to take one card out and I connected it with a USB Riser.
It's works fine for couple of minutes ( sometime hours ) then the mining software stops and If I ran it again it doesn't mine so I have to restart my machine and when I do that Windows can't read the third card and it shows a yellow triangle with Error Code 43.
I changed the USB Riser and still the same problem, I tried to switch the cards and the slots and everything and the problem is always there.
I have ASUS Z270E with 4 GB Ram and I increased the Virtual Memory but still no luck.

Think you'll need more than 4GB ram installed - 8 or 16.

4gb is enough even for vega, @topic dont connect your riser with sata to molex.

Maybe, but I once had a horrible few weeks trying to build a stable Vega rig with 4gb.

Anyway, aside from that check power connections, especially the risers, and as treanski says avoid sata if possible. If not possible use one sata PSU output per riser max.


For the latest Crypto news and alts info check out https://coinsjar.info/
legendster
Hero Member
*****
Offline Offline

Activity: 1778
Merit: 764


www.V.systems


View Profile
February 19, 2018, 11:40:27 AM
 #8

Get 8 gigs total. Connect the cards first. Make sure wake on lan is enabled in Bios. Update to the most latest (stable) driver available. Uninstall the card from your computer hardware management tab. Make sure you uninstall the driver as well as the hardware. Then redetect your hardware and do the autoinstall.

Should fix it.


   ██████████        ████████████
     ██████████        ██████████
       ██████████        ████████
         ██████████        ██████
           ██████████        ████
             ██████████        ██
               ██████████
                 ██████████
                   ████████
                     ██████
                       ████
                        ██
|
     ▄▀▀▀▀▀▀▀▀▀█                 ▄▀▀▀▀▀▀▀▀▀█
 ▄▀                ▄▀█             ▄▀                ▄▀█
 ██████████    █             ██████████    █
 █                █                   █                █    █
 █                █     ▀▀▀▀▀▀▀█                █    █
 █                █  ▄▀             █                █  ▄▀
 ██████████▀                 ██████████▀
          █                                    █
          █                                    █
     ▄▀ █  ▀▀▀▀█                   ▄▀ █ ▀▀▀▀▀▀█
 ▄▀             ▄▀█               ▄▀               ▄▀ █
 █████████   █               ██████████    █
 █              █   █               █                █    █
 █              █   █               █                █    █
 █              █  ▄▀▀▀▀▀▀▀  █                █  ▄▀
 █████████▀                  ██████████▀

Blockchain
Database
                             ▄▄▄
                         ▄▄▀  ▀▄▄
        ▄           ▄▄▀  ▄▀▄  ▀▄▄
      █▄█   █████████████████    █
        █     █                              █ ▄▀ ▌
        █     █        ▄    █   ▄         █▀ ▄▌
       ██    █      ▀▄   █    ▄▀       █▀█
       ▌ ▌   █            █                █  █
       ▌ ▌   █                              █  █
       ██    ███████████████████
                     ▀▀▄  ▀▄▀  ▄▀▀
                         ▀▀▄  ▄▀▀
                             ▀▀▀
Dev friendly
SDK Platform
                             ▄▄▄▄
                         ▄▄█    █▄▄
                     ▄▄█            █▄▄
                 ▄▄█       ▄▄▄       █▄▄
                 █       ▄▀      ▀▄       █
               █▀     █      █      █     ▀█
               ▀▀█  █   ▄█▀█▄   █  █▀▀
               █▀▀   █  ▀███▀  █   ▀▀█
               ▀▀█     █    █    █     █▀▀
                   ▀▀█   █  █  █   █▀▀
                       ▀████████▀
                           █▄▄▄▄█
                 █        █▄▄▄▄█      █
             ▄▀ █▄                   ▄█  ▀▄
            █   █▀▄         ▀      ▄▀█    █
           █   █  █  ▌      ▀   ▐  █  █    █
           █   █▄▀▄▌      ▀   ▐▄▀▄█    █
           █       █          ▀        █       █
        █▀▀▀▀▀▀█                █▀▀▀▀▀▀█
        ▀▀▀▀▀▀▀▀                ▀▀▀▀▀▀▀▀
User-friendly
Token Creation
|
Jr.Sasha0209
Newbie
*
Offline Offline

Activity: 78
Merit: 0


View Profile WWW
March 25, 2018, 08:15:32 AM
 #9

There was such a mistake with one card that I just did not do, starting with drivers and ending with the firmware of the motherboard, but it did not help, I had to carry it back to the store and after long disputes and card checks, it turned out that it was Zavadsky marriage
Pages: [1]
  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!