Topic: Does the Asus Prime B350-Plus support more than three GPUs? (Read 203 times)
Hi, did you solve this?, I'm building a rig with that mother and need to add more gpus and don't know where to start..
Hi choppermines,
i have the problem that i cant run with 3 1060 gpus. I have the same board but it will not work. Two cards are plugged in the PCIe slots and the third with a riser, but it just boot with two cards. Can you help me with that problem please?
i have the problem that i cant run with 3 1060 gpus. I have the same board but it will not work. Two cards are plugged in the PCIe slots and the third with a riser, but it just boot with two cards. Can you help me with that problem please?
Has anybody been able to get 4 GPUs to run on an Asus Prime B350-Plus? Ive tried everything. Help!
See my post below for what Ive already done to try and fix it. Also now hooked up two psu's and both work fine. The secondary 1000W pushes one GPU, the main 1600W pushes two, the fourth GPU is on but not working (connected to the 1600W main).
My mobo does not have the option to enable 4g decoding or forcing pci to gen 1. I don't have experience with Hive OS? Would that involve changing the OS to Hive or can it be done explicitly from the USB.
Still fairly new to computer programming/troubleshooting.
Hey everybody. I recently upgraded to a fourth GPU (1080 ti Hybrid) on my Asus Prime B350-Plus and Ryzen 7 1700, dedicated miner. I have not been able to get the fourth GPU to operate. When I have four gpus connected, the PCIe 2.0x16_2 shows this error: "Windows has stopped this device because it has reported problems (code 43)".
These are the things that I have done so far:
- checked all connections to gpus, risers, and pci slots
- plugged in the new gpu to all the different pci slots and different risers to ensure that it was working properly.
- All gpus, risers, and pci slots work with up to a three gpu configuration.
- updated the bios to 3401 version (current on ASUS website).
- Connected gpus to all different power rails on the psu (1600w evga T2).
- Updated driver for the new 1080ti (the update manager said they were the newest version, but I updated anyway)
Any thoughts?
See my post below for what Ive already done to try and fix it. Also now hooked up two psu's and both work fine. The secondary 1000W pushes one GPU, the main 1600W pushes two, the fourth GPU is on but not working (connected to the 1600W main).
did you enable 4G Decoding and set pci express to gen 1 ? if you did and still doesn't work use hive os on a usb drive or something see if it brings other gpus up.
My mobo does not have the option to enable 4g decoding or forcing pci to gen 1. I don't have experience with Hive OS? Would that involve changing the OS to Hive or can it be done explicitly from the USB.
Still fairly new to computer programming/troubleshooting.
Hey everybody. I recently upgraded to a fourth GPU (1080 ti Hybrid) on my Asus Prime B350-Plus and Ryzen 7 1700, dedicated miner. I have not been able to get the fourth GPU to operate. When I have four gpus connected, the PCIe 2.0x16_2 shows this error: "Windows has stopped this device because it has reported problems (code 43)".
These are the things that I have done so far:
- checked all connections to gpus, risers, and pci slots
- plugged in the new gpu to all the different pci slots and different risers to ensure that it was working properly.
- All gpus, risers, and pci slots work with up to a three gpu configuration.
- updated the bios to 3401 version (current on ASUS website).
- Connected gpus to all different power rails on the psu (1600w evga T2).
- Updated driver for the new 1080ti (the update manager said they were the newest version, but I updated anyway)
Any thoughts?
There are not enough free PCI-E lines.
The upper port uses lines from the processor.
The lower x16 uses the lines from the chipset, which means x4 mode.
And it is indicated that he divides them between x1 slots.
Specifications: PCIeX16_2 slot shares bandwidth with PCIeX1_1 and PCIeX1_2.
I was able to get the 4th GPU running when I unplugged the PCI2 port. The configuration that works is as follows:
PCIeX1_2 - Connected via X1 riser
PCI2 - Not connected
PCIeX16_2 - Connected via X1 riser
PCIeX1_1 - Connected via X1 riser
PCI1 - Not connected
PCIeX16_1 - GPU directly connected to motherboard
If I get another GPU down the road, do you think the PCI1 or PCI2 slots will work with this configuration? I will probably get a X16 riser for the main (PCIeX16_1) slot, if I do get another GPU. The PCI2 was not working, but I have not tried the PCI1 slot yet.
Thanks for all the posts trying to help!! Happy new year!
Yes it supports more then 3...
what does Device Manager show ?
Have you tired ruining it with Linux yet ? .
I've found when using 4 or more NV card resinstalling the drivers by using DDU https://www.wagnardsoft.com/content/display-driver-uninstaller-ddu-v17081-released in safe mode for a clean install of the drivers live, helps a lot and usually fixes it for me .. don't install the windows update drivers all ways uninstall then do a clan install of the ones from NV site http://www.nvidia.com/Download/index.aspx?lang=en-us.
what does Device Manager show ?
Have you tired ruining it with Linux yet ? .
I've found when using 4 or more NV card resinstalling the drivers by using DDU https://www.wagnardsoft.com/content/display-driver-uninstaller-ddu-v17081-released in safe mode for a clean install of the drivers live, helps a lot and usually fixes it for me .. don't install the windows update drivers all ways uninstall then do a clan install of the ones from NV site http://www.nvidia.com/Download/index.aspx?lang=en-us.
Code:
How to Fix a Code 43 Error
Restart your computer if you haven't done so already.
There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.
Note: Some users have also reported that powering off their computer completely (not just a reset) and then turning it back on has corrected their Code 43 issue, especially if it exists on a USB device. In the case of a laptop, turn it off and remove the battery, wait a few minutes, and then put the battery back in and start the computer.
Did you install a device or make a change in Device Manager just before the Code 43 error appeared? If so, it's possible that the change you made caused the Code 43 error.
Undo the change if you can, restart your PC, and then check again for the Code 43 error.
Depending on the changes you made, some solutions might include:
Removing or reconfiguring the newly installed device
Rolling back the driver to a version prior to your update
Using System Restore to undo recent Device Manager related changes
Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a possible solution to a Code 43 error.
Important: If a USB device is generating the Code 43 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Properly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
Update the drivers for the device. It's also very possible that installing the latest drivers for the device could correct the Code 43 error.
If updating the drivers does remove the Code 43 error, it means that the stored Windows drivers you reinstalled in Step 3 were probably damaged or were the wrong drivers.
Install the latest Windows service pack. One of Microsoft's service packs or other patches for Windows might contain a fix for whatever might be causing the Code 43 error, so if you're not fully updated, do so now.
Update BIOS. In some situations, an outdated BIOS could be causing a specific issue with a device that is making it report an issue to Windows - thus the Code 43 error.
Replace the data cable that connects the device to the computer, assuming it has one. This potential fix for a Code 43 error is most often useful if you're seeing the error on an external device like a USB or FireWire device.
Reference the hardware device's manual and follow any troubleshooting information provided.
I know this sounds like really general advice but the Code 43 error is specifically referring to the hardware as the source of the error information, so there may actually be some useful troubleshooting information in the product manual.
Purchase a powered USB hub if the Code 43 error is showing up for a USB device. Some USB devices need more power than the USB ports that are built into your computer can provide. Plugging those devices into a powered USB hub solves that issue.
Replace the hardware. A problem with the device itself might be causing the Code 43 error, in which case replacing the hardware is your next logical step. In most cases, this is the solution to a Code 43 error but I wanted you to try the easier, and free, software-based troubleshooting ideas first.
Another possibility, while not very likely, is that the device is incompatible with your version of Windows. You can always check the Windows HCL to be sure.
Note: If you're positive that a hardware problem isn't causing the Code 43 error, you could try a repair install of Windows. If that doesn't work, try a clean install of Windows. I don't recommend doing either before you replace the hardware, but you may have to give them a try if you're out of other options.
Restart your computer if you haven't done so already.
There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.
Note: Some users have also reported that powering off their computer completely (not just a reset) and then turning it back on has corrected their Code 43 issue, especially if it exists on a USB device. In the case of a laptop, turn it off and remove the battery, wait a few minutes, and then put the battery back in and start the computer.
Did you install a device or make a change in Device Manager just before the Code 43 error appeared? If so, it's possible that the change you made caused the Code 43 error.
Undo the change if you can, restart your PC, and then check again for the Code 43 error.
Depending on the changes you made, some solutions might include:
Removing or reconfiguring the newly installed device
Rolling back the driver to a version prior to your update
Using System Restore to undo recent Device Manager related changes
Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a possible solution to a Code 43 error.
Important: If a USB device is generating the Code 43 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Properly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
Update the drivers for the device. It's also very possible that installing the latest drivers for the device could correct the Code 43 error.
If updating the drivers does remove the Code 43 error, it means that the stored Windows drivers you reinstalled in Step 3 were probably damaged or were the wrong drivers.
Install the latest Windows service pack. One of Microsoft's service packs or other patches for Windows might contain a fix for whatever might be causing the Code 43 error, so if you're not fully updated, do so now.
Update BIOS. In some situations, an outdated BIOS could be causing a specific issue with a device that is making it report an issue to Windows - thus the Code 43 error.
Replace the data cable that connects the device to the computer, assuming it has one. This potential fix for a Code 43 error is most often useful if you're seeing the error on an external device like a USB or FireWire device.
Reference the hardware device's manual and follow any troubleshooting information provided.
I know this sounds like really general advice but the Code 43 error is specifically referring to the hardware as the source of the error information, so there may actually be some useful troubleshooting information in the product manual.
Purchase a powered USB hub if the Code 43 error is showing up for a USB device. Some USB devices need more power than the USB ports that are built into your computer can provide. Plugging those devices into a powered USB hub solves that issue.
Replace the hardware. A problem with the device itself might be causing the Code 43 error, in which case replacing the hardware is your next logical step. In most cases, this is the solution to a Code 43 error but I wanted you to try the easier, and free, software-based troubleshooting ideas first.
Another possibility, while not very likely, is that the device is incompatible with your version of Windows. You can always check the Windows HCL to be sure.
Note: If you're positive that a hardware problem isn't causing the Code 43 error, you could try a repair install of Windows. If that doesn't work, try a clean install of Windows. I don't recommend doing either before you replace the hardware, but you may have to give them a try if you're out of other options.
Uninstalled and reinstalled nvidea drivers. Still only 3 work. Same exact error.
Has anybody been able to get 4 GPUs to run on an Asus Prime B350-Plus? Ive tried everything. Help!
See my post below for what Ive already done to try and fix it. Also now hooked up two psu's and both work fine. The secondary 1000W pushes one GPU, the main 1600W pushes two, the fourth GPU is on but not working (connected to the 1600W main).
My mobo does not have the option to enable 4g decoding or forcing pci to gen 1. I don't have experience with Hive OS? Would that involve changing the OS to Hive or can it be done explicitly from the USB.
Still fairly new to computer programming/troubleshooting.
Hey everybody. I recently upgraded to a fourth GPU (1080 ti Hybrid) on my Asus Prime B350-Plus and Ryzen 7 1700, dedicated miner. I have not been able to get the fourth GPU to operate. When I have four gpus connected, the PCIe 2.0x16_2 shows this error: "Windows has stopped this device because it has reported problems (code 43)".
These are the things that I have done so far:
- checked all connections to gpus, risers, and pci slots
- plugged in the new gpu to all the different pci slots and different risers to ensure that it was working properly.
- All gpus, risers, and pci slots work with up to a three gpu configuration.
- updated the bios to 3401 version (current on ASUS website).
- Connected gpus to all different power rails on the psu (1600w evga T2).
- Updated driver for the new 1080ti (the update manager said they were the newest version, but I updated anyway)
Any thoughts?
See my post below for what Ive already done to try and fix it. Also now hooked up two psu's and both work fine. The secondary 1000W pushes one GPU, the main 1600W pushes two, the fourth GPU is on but not working (connected to the 1600W main).
did you enable 4G Decoding and set pci express to gen 1 ? if you did and still doesn't work use hive os on a usb drive or something see if it brings other gpus up.
My mobo does not have the option to enable 4g decoding or forcing pci to gen 1. I don't have experience with Hive OS? Would that involve changing the OS to Hive or can it be done explicitly from the USB.
Still fairly new to computer programming/troubleshooting.
Hey everybody. I recently upgraded to a fourth GPU (1080 ti Hybrid) on my Asus Prime B350-Plus and Ryzen 7 1700, dedicated miner. I have not been able to get the fourth GPU to operate. When I have four gpus connected, the PCIe 2.0x16_2 shows this error: "Windows has stopped this device because it has reported problems (code 43)".
These are the things that I have done so far:
- checked all connections to gpus, risers, and pci slots
- plugged in the new gpu to all the different pci slots and different risers to ensure that it was working properly.
- All gpus, risers, and pci slots work with up to a three gpu configuration.
- updated the bios to 3401 version (current on ASUS website).
- Connected gpus to all different power rails on the psu (1600w evga T2).
- Updated driver for the new 1080ti (the update manager said they were the newest version, but I updated anyway)
Any thoughts?
There are not enough free PCI-E lines.
The upper port uses lines from the processor.
The lower x16 uses the lines from the chipset, which means x4 mode.
And it is indicated that he divides them between x1 slots.
Specifications: PCIeX16_2 slot shares bandwidth with PCIeX1_1 and PCIeX1_2.
The device manager shows that there is a fourth GPU installed but it does not run and has the code 43 error.
I have never used Linux.
I have updated the drivers but have not done a uninstall and reinstall. I will try that next.
Thanks!
I have never used Linux.
I have updated the drivers but have not done a uninstall and reinstall. I will try that next.
Thanks!
Yes it supports more then 3...
what does Device Manager show ?
Have you tired ruining it with Linux yet ? .
I've found when using 4 or more NV card resinstalling the drivers by using DDU https://www.wagnardsoft.com/content/display-driver-uninstaller-ddu-v17081-released in safe mode for a clean install of the drivers live, helps a lot and usually fixes it for me .. don't install the windows update drivers all ways uninstall then do a clan install of the ones from NV site http://www.nvidia.com/Download/index.aspx?lang=en-us.
what does Device Manager show ?
Have you tired ruining it with Linux yet ? .
I've found when using 4 or more NV card resinstalling the drivers by using DDU https://www.wagnardsoft.com/content/display-driver-uninstaller-ddu-v17081-released in safe mode for a clean install of the drivers live, helps a lot and usually fixes it for me .. don't install the windows update drivers all ways uninstall then do a clan install of the ones from NV site http://www.nvidia.com/Download/index.aspx?lang=en-us.
Code:
How to Fix a Code 43 Error
Restart your computer if you haven't done so already.
There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.
Note: Some users have also reported that powering off their computer completely (not just a reset) and then turning it back on has corrected their Code 43 issue, especially if it exists on a USB device. In the case of a laptop, turn it off and remove the battery, wait a few minutes, and then put the battery back in and start the computer.
Did you install a device or make a change in Device Manager just before the Code 43 error appeared? If so, it's possible that the change you made caused the Code 43 error.
Undo the change if you can, restart your PC, and then check again for the Code 43 error.
Depending on the changes you made, some solutions might include:
Removing or reconfiguring the newly installed device
Rolling back the driver to a version prior to your update
Using System Restore to undo recent Device Manager related changes
Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a possible solution to a Code 43 error.
Important: If a USB device is generating the Code 43 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Properly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
Update the drivers for the device. It's also very possible that installing the latest drivers for the device could correct the Code 43 error.
If updating the drivers does remove the Code 43 error, it means that the stored Windows drivers you reinstalled in Step 3 were probably damaged or were the wrong drivers.
Install the latest Windows service pack. One of Microsoft's service packs or other patches for Windows might contain a fix for whatever might be causing the Code 43 error, so if you're not fully updated, do so now.
Update BIOS. In some situations, an outdated BIOS could be causing a specific issue with a device that is making it report an issue to Windows - thus the Code 43 error.
Replace the data cable that connects the device to the computer, assuming it has one. This potential fix for a Code 43 error is most often useful if you're seeing the error on an external device like a USB or FireWire device.
Reference the hardware device's manual and follow any troubleshooting information provided.
I know this sounds like really general advice but the Code 43 error is specifically referring to the hardware as the source of the error information, so there may actually be some useful troubleshooting information in the product manual.
Purchase a powered USB hub if the Code 43 error is showing up for a USB device. Some USB devices need more power than the USB ports that are built into your computer can provide. Plugging those devices into a powered USB hub solves that issue.
Replace the hardware. A problem with the device itself might be causing the Code 43 error, in which case replacing the hardware is your next logical step. In most cases, this is the solution to a Code 43 error but I wanted you to try the easier, and free, software-based troubleshooting ideas first.
Another possibility, while not very likely, is that the device is incompatible with your version of Windows. You can always check the Windows HCL to be sure.
Note: If you're positive that a hardware problem isn't causing the Code 43 error, you could try a repair install of Windows. If that doesn't work, try a clean install of Windows. I don't recommend doing either before you replace the hardware, but you may have to give them a try if you're out of other options.
Restart your computer if you haven't done so already.
There is always the chance that the error Code 43 you're seeing on a device was caused by some temporary problem with the hardware. If so, a restart of your computer might fix the Code 43 error.
Note: Some users have also reported that powering off their computer completely (not just a reset) and then turning it back on has corrected their Code 43 issue, especially if it exists on a USB device. In the case of a laptop, turn it off and remove the battery, wait a few minutes, and then put the battery back in and start the computer.
Did you install a device or make a change in Device Manager just before the Code 43 error appeared? If so, it's possible that the change you made caused the Code 43 error.
Undo the change if you can, restart your PC, and then check again for the Code 43 error.
Depending on the changes you made, some solutions might include:
Removing or reconfiguring the newly installed device
Rolling back the driver to a version prior to your update
Using System Restore to undo recent Device Manager related changes
Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a possible solution to a Code 43 error.
Important: If a USB device is generating the Code 43 error, uninstall every device under the Universal Serial Bus controllers hardware category in Device Manager as part of the driver reinstall. This includes any USB Mass Storage Device, USB Host Controller, and USB Root Hub.
Note: Properly reinstalling a driver, as in the instructions linked above, is not the same as simply updating a driver. A full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
Update the drivers for the device. It's also very possible that installing the latest drivers for the device could correct the Code 43 error.
If updating the drivers does remove the Code 43 error, it means that the stored Windows drivers you reinstalled in Step 3 were probably damaged or were the wrong drivers.
Install the latest Windows service pack. One of Microsoft's service packs or other patches for Windows might contain a fix for whatever might be causing the Code 43 error, so if you're not fully updated, do so now.
Update BIOS. In some situations, an outdated BIOS could be causing a specific issue with a device that is making it report an issue to Windows - thus the Code 43 error.
Replace the data cable that connects the device to the computer, assuming it has one. This potential fix for a Code 43 error is most often useful if you're seeing the error on an external device like a USB or FireWire device.
Reference the hardware device's manual and follow any troubleshooting information provided.
I know this sounds like really general advice but the Code 43 error is specifically referring to the hardware as the source of the error information, so there may actually be some useful troubleshooting information in the product manual.
Purchase a powered USB hub if the Code 43 error is showing up for a USB device. Some USB devices need more power than the USB ports that are built into your computer can provide. Plugging those devices into a powered USB hub solves that issue.
Replace the hardware. A problem with the device itself might be causing the Code 43 error, in which case replacing the hardware is your next logical step. In most cases, this is the solution to a Code 43 error but I wanted you to try the easier, and free, software-based troubleshooting ideas first.
Another possibility, while not very likely, is that the device is incompatible with your version of Windows. You can always check the Windows HCL to be sure.
Note: If you're positive that a hardware problem isn't causing the Code 43 error, you could try a repair install of Windows. If that doesn't work, try a clean install of Windows. I don't recommend doing either before you replace the hardware, but you may have to give them a try if you're out of other options.
Has anybody been able to get 4 GPUs to run on an Asus Prime B350-Plus? Ive tried everything. Help!
See my post below for what Ive already done to try and fix it. Also now hooked up two psu's and both work fine. The secondary 1000W pushes one GPU, the main 1600W pushes two, the fourth GPU is on but not working (connected to the 1600W main).
My mobo does not have the option to enable 4g decoding or forcing pci to gen 1. I don't have experience with Hive OS? Would that involve changing the OS to Hive or can it be done explicitly from the USB.
Still fairly new to computer programming/troubleshooting.
Hey everybody. I recently upgraded to a fourth GPU (1080 ti Hybrid) on my Asus Prime B350-Plus and Ryzen 7 1700, dedicated miner. I have not been able to get the fourth GPU to operate. When I have four gpus connected, the PCIe 2.0x16_2 shows this error: "Windows has stopped this device because it has reported problems (code 43)".
These are the things that I have done so far:
- checked all connections to gpus, risers, and pci slots
- plugged in the new gpu to all the different pci slots and different risers to ensure that it was working properly.
- All gpus, risers, and pci slots work with up to a three gpu configuration.
- updated the bios to 3401 version (current on ASUS website).
- Connected gpus to all different power rails on the psu (1600w evga T2).
- Updated driver for the new 1080ti (the update manager said they were the newest version, but I updated anyway)
Any thoughts?
See my post below for what Ive already done to try and fix it. Also now hooked up two psu's and both work fine. The secondary 1000W pushes one GPU, the main 1600W pushes two, the fourth GPU is on but not working (connected to the 1600W main).
did you enable 4G Decoding and set pci express to gen 1 ? if you did and still doesn't work use hive os on a usb drive or something see if it brings other gpus up.
My mobo does not have the option to enable 4g decoding or forcing pci to gen 1. I don't have experience with Hive OS? Would that involve changing the OS to Hive or can it be done explicitly from the USB.
Still fairly new to computer programming/troubleshooting.
Hey everybody. I recently upgraded to a fourth GPU (1080 ti Hybrid) on my Asus Prime B350-Plus and Ryzen 7 1700, dedicated miner. I have not been able to get the fourth GPU to operate. When I have four gpus connected, the PCIe 2.0x16_2 shows this error: "Windows has stopped this device because it has reported problems (code 43)".
These are the things that I have done so far:
- checked all connections to gpus, risers, and pci slots
- plugged in the new gpu to all the different pci slots and different risers to ensure that it was working properly.
- All gpus, risers, and pci slots work with up to a three gpu configuration.
- updated the bios to 3401 version (current on ASUS website).
- Connected gpus to all different power rails on the psu (1600w evga T2).
- Updated driver for the new 1080ti (the update manager said they were the newest version, but I updated anyway)
Any thoughts?
Jump to: