Pages:
Author

Topic: Bios doesn't detect all GPUs... (Read 340 times)

hero member
Activity: 1274
Merit: 556
January 22, 2019, 09:56:06 AM
#24
Right. So I swapped out that mobo for a Gigabyte GA-H110-D3A and added a PSU.
Plugged in the first Vega (using riser).
Installed Windows but the display was low-rez and the display adapter soon showed an error 43. Big facepalm moment. Went to sleep wondering how many bad risers could there even be in one batch.

Next day I swapped the riser, rebooted, ran devconsole to re-initialise the card... Bam, works. Installed 18.6.1 drivers.
Plugged the next 5 cards one by one (enabling 4G encodes after the 4th)... and all is good again.

So yeah. The Vegas do not draw less power than before on the Onda board, but at least they seem to work, and I have more overhead in case I need it.
jr. member
Activity: 131
Merit: 3
January 18, 2019, 10:30:01 AM
#23
Oh sorry that sucks, too late for that mobo I guess the only other fix I could think of was to try PCIE expander boards.
hero member
Activity: 1274
Merit: 556
January 18, 2019, 10:07:40 AM
#22
Nah.
It won't even work with three GPUs plugged in the x16 slots. Also it keeps disconnecting the keyboard plugged in USB. Earlier I had to clear CMOS three times in a row for it to even boot.

I've just ordered a Gigabyte GA-H110-D3A for £45 - will arrive tomorrow. I'll then just transfer over the Celery and the ram and re-plug all cards in it.
jr. member
Activity: 131
Merit: 3
January 18, 2019, 09:37:55 AM
#21
Oh yeah after DDU, disconnect your internet before installing your Adrenalin drivers and reboot, then you can reconnect your internet, that prevents windows from installing generic driver
And last resort you try can the HackFlags 600 registry mod.
jr. member
Activity: 131
Merit: 3
January 18, 2019, 09:26:50 AM
#20
I faced this many times with setting up rigs. You could try installing one card at a time and check bios/windows each time, the moment you have a fail you should reset cmos and start from scratch.
The order in which you install the cards can matter greatly. Going in order from PCIE slot 1,2,3,4,5,6 often doesn't work. Try installing in different orders like for example 1,3,5,2,4,6
 
hero member
Activity: 1274
Merit: 556
January 18, 2019, 09:16:44 AM
#19
Right, so after all this effort (changed risers, cleaned slots, added a PSU and cabled everything perfectly) it still does exactly the same.

I will say with a 77.77778% certainty that the board is fucked.
hero member
Activity: 1274
Merit: 556
January 17, 2019, 10:03:00 AM
#18
If you want I can send you a mobo with a cpu.

Run three cards on each mobo
Thanks Phil, but don't think that'll be necessary. Plus I'm in the UK so shipping would just cost as much as the mobos themselves! Cheesy

I'll take it all apart again, swap out all risers (I have quite a few brand new ones to use), spray the PCIe slots clean, add a second PSU to reduce the load on the first and re-wire cleanly.

DDU the whole thing (again) first.
Oh btw Windows now stubbornly reinstalls the display drivers not long after reboot. DDU can't seem to prevent it anymore like it used to.

The error 43 is definitely connected to the flakiness of the setup. Sometimes none of the cards show it, sometimes 4 out of 6, or 2 out of 5, depending on how many are detected. It's like a lottery. Which really makes me think it's really hardware/power related.

Power is an issue with Vegas. Also, sure you know this, but the new drivers don't respect registry mods like they used to, so once installed you'll need to turn off crossfire in AMD - that little gem cost me a day or so.
Yes... but I'm installing 18.6.1 since it's the driver that seems to work best for most miners out there still nowadays. Anyway, gotta jump into my mining den and start unplugging stuff now... Will update.
member
Activity: 357
Merit: 26
January 17, 2019, 06:40:42 AM
#17
If you want I can send you a mobo with a cpu.

Run three cards on each mobo
Thanks Phil, but don't think that'll be necessary. Plus I'm in the UK so shipping would just cost as much as the mobos themselves! Cheesy

I'll take it all apart again, swap out all risers (I have quite a few brand new ones to use), spray the PCIe slots clean, add a second PSU to reduce the load on the first and re-wire cleanly.

DDU the whole thing (again) first.
Oh btw Windows now stubbornly reinstalls the display drivers not long after reboot. DDU can't seem to prevent it anymore like it used to.

The error 43 is definitely connected to the flakiness of the setup. Sometimes none of the cards show it, sometimes 4 out of 6, or 2 out of 5, depending on how many are detected. It's like a lottery. Which really makes me think it's really hardware/power related.

Power is an issue with Vegas. Also, sure you know this, but the new drivers don't respect registry mods like they used to, so once installed you'll need to turn off crossfire in AMD - that little gem cost me a day or so.
hero member
Activity: 1274
Merit: 556
January 17, 2019, 04:32:20 AM
#16
If you want I can send you a mobo with a cpu.

Run three cards on each mobo
Thanks Phil, but don't think that'll be necessary. Plus I'm in the UK so shipping would just cost as much as the mobos themselves! Cheesy

I'll take it all apart again, swap out all risers (I have quite a few brand new ones to use), spray the PCIe slots clean, add a second PSU to reduce the load on the first and re-wire cleanly.

DDU the whole thing (again) first.
Oh btw Windows now stubbornly reinstalls the display drivers not long after reboot. DDU can't seem to prevent it anymore like it used to.

The error 43 is definitely connected to the flakiness of the setup. Sometimes none of the cards show it, sometimes 4 out of 6, or 2 out of 5, depending on how many are detected. It's like a lottery. Which really makes me think it's really hardware/power related.
legendary
Activity: 3318
Merit: 1247
Bitcoin Casino Est. 2013
January 17, 2019, 02:15:11 AM
#15
Use latest version of the risers, check Amazon and Ebay for those, also use the latest drivers that were just published 2 days ago by AMD. The error code 43 is one of several error codes in Device Manager and of course for you is for the Gpu-s. Uninstall all drivers, plug in newest version of risers, install latest drivers and you should be fine.
hero member
Activity: 578
Merit: 508
January 17, 2019, 12:10:27 AM
#14
The usual suspects:

Run DDU

Reset the MB by removing the battery.

In tweaking the bios, be sure to turn off as much stuff as possible: serial ports, excess usb ports, audio etc

If you can, set the pcie speed to gen 1.

Bad riser.

Riser power has gone bad (rare).

Install one card at a time. Sometimes for whatever reason it can take 10+ minutes for the device driver to setup a card.

legendary
Activity: 4326
Merit: 8899
'The right to privacy matters'
January 16, 2019, 10:33:59 PM
#13
If you want I can send you a mobo with a cpu.

Run three cards on each mobo
member
Activity: 236
Merit: 16
January 16, 2019, 07:50:20 PM
#12
If there's no option in your BIOS for it, not something you'll have to worry about most likely. I would also try to see if the cards show up in Linux (lspci) when they don't show up in the BIOS - the driver stack might reinitialize the cards if they did fail to POST. You can also rescan the PCIe bus or toggle which slots are enabled and see if they'll be detected.
hero member
Activity: 1274
Merit: 556
January 16, 2019, 07:39:50 PM
#11
If it isn't power delivery, make sure 64-bit PCIe BAR is enabled and mapping above 4GB aperture is allowed.
How do I do the 64bit BAR thing? I've got "above 4g" enabled.
full member
Activity: 294
Merit: 129
January 16, 2019, 06:20:15 PM
#10
I swap them for six Vegas

Found the problem! Dump those crap ass cards and go back to what you had and all your problems will go away.
member
Activity: 236
Merit: 16
January 16, 2019, 05:56:18 PM
#9
If it isn't power delivery, make sure 64-bit PCIe BAR is enabled and mapping above 4GB aperture is allowed.
hero member
Activity: 2534
Merit: 623
January 16, 2019, 05:36:30 PM
#8
Keep us updated and good luck.
hero member
Activity: 1274
Merit: 556
January 16, 2019, 05:30:44 PM
#7
I think it might also be a power delivery issue.
I will stop this shit tonight, I'm only finding more issues as I go so I'll unplug everything tomorrow, add a second PSU, rewire the GPUs and the risers properly and pressure-clean the mobo slots.

Hopefully that'll do it.
hero member
Activity: 2170
Merit: 612
Online Security & Investment Corporation
January 16, 2019, 05:12:44 PM
#6

Use ati patch then the Code 43 will be fixed.
and i m sure there is dust on your risers socket and pcie
hero member
Activity: 1274
Merit: 556
January 16, 2019, 05:08:58 PM
#5
Are all of them even showing up in device manager?
Only if they are picked up by the bios.

Actually I'm trying with only 3 cards plugged in now. Bios picks them all up but Windows throws up a code 43 after driver install for one of them... I'm pulling my hair out...
Pages:
Jump to: