ASRock H81 Pro will not accept more than 2 GPU's (Code 12)

[Yoledo]

Following this thread since i got the same problem after updating Windows. For while I could only get 4/6 gpus working (code12) on the others but trying all possible fixes got me to 5/6. Now done wasting time finding a solution, 6/6 cards worked before win update....

Hopefully someone solves this, I maxed out my technical potential on this one...

How'd u get 5 working?

[1715178183]

1715178183

[1715178183]

1715178183

[1715178183]

1715178183

[1715178183]

1715178183

[1715178183]

1715178183

[Miner3000]

Following this thread since i got the same problem after updating Windows. For while I could only get 4/6 gpus working (code12) on the others but trying all possible fixes got me to 5/6. Now done wasting time finding a solution, 6/6 cards worked before win update....

Hopefully someone solves this, I maxed out my technical potential on this one...

How'd u get 5 working?

Well first of all as I said I had just 4/6 and couldnt do anything. So I cleaned drivers and started by plugging them in one by one, thinking there was a problem with me installing windows with all cards hooked up. Then I got stuck on the third card. 2 working, 1 with code 12. So I did all the fixes, regedit hackflags, updating bios to ver1.30 enabling 4G-decoding option, turned off onbard audio etc. Changed swapfile to 16gb-32gb.

When nothing of that worked I figured after reading this thread and it seems to be an problem with windows 10 ver. 1079, okay I'll plug in all six and just mine with however many cards I can. But then 5 cards run problemfree, and code 12 error on just 1. So thats what I did, cant explain it any better, sorry. Mining at the moment with 5 and only hope of getting 6 working is this thread it seems...

[Yoledo]

Following this thread since i got the same problem after updating Windows. For while I could only get 4/6 gpus working (code12) on the others but trying all possible fixes got me to 5/6. Now done wasting time finding a solution, 6/6 cards worked before win update....

Hopefully someone solves this, I maxed out my technical potential on this one...

How'd u get 5 working?

Well first of all as I said I had just 4/6 and couldnt do anything. So I cleaned drivers and started by plugging them in one by one, thinking there was a problem with me installing windows with all cards hooked up. Then I got stuck on the third card. 2 working, 1 with code 12. So I did all the fixes, regedit hackflags, updating bios to ver1.30 enabling 4G-decoding option, turned off onbard audio etc. Changed swapfile to 16gb-32gb.

When nothing of that worked I figured after reading this thread and it seems to be an problem with windows 10 ver. 1079, okay I'll plug in all six and just mine with however many cards I can. But then 5 cards run problemfree, and code 12 error on just 1. So thats what I did, cant explain it any better, sorry. Mining at the moment with 5 and only hope of getting 6 working is this thread it seems...

It seems to be a common problem with a myriad of different solutions

[rizabbasi]

Hi OP,

I have same board, H81 Pro BTC R2.0. Whats the status of your issue? Can your board detect all six cards?

I believe this is much popular board; possibly issue with your mobo.

Would be great if you update.

Regards,

Rizwan

[Michael20]

Very annoying, don't thought that the asrock board make such trouble. Is it most a windows problem, so linux is the solution?

Is the H110 Pro BTC+ also such problematic?

[Miner3000]

Guys!! I got all six working. What did it was actually the fix in https://forums.geforce.com/default/topic/470858/code-12/ that someone suggested to you Yoledo, I suggest you try it again if you havent done what i shortly describe:

More exactly going to the 'memory' tab,  and inactivating hd audio controllers under pci root port #1 or in your specific case the pci-e port that aint working.

No restart no nothing required, exclamation mark just went away.

Good luck!

[q43a0ef061ej]

Hi, guys.

Yes. Specific operations in the device manager are as follows.

Guys!! I got all six working. What did it was actually the fix in https://forums.geforce.com/default/topic/470858/code-12/ that someone suggested to you Yoledo, I suggest you try it again if you havent done what i shortly describe:

More exactly going to the 'memory' tab,  and inactivating hd audio controllers under pci root port #1 or in your specific case the pci-e port that aint working.

No restart no nothing required, exclamation mark just went away.

Good luck!

[djtappage]

Hi Guys, having same issues over here with this

only purchased all hardware last week and still havn't got to the bottom of this issue. Tried multiple fixes so any suggestions i would gratefully appreciate it in advance

My Hardware setup is as follows:
asrok h81 Pro BTC r2.0
Intel g3220
4gb ddr3
windows 10 1709 build
Latest bios Flashed via internet
4 pins are connected both sides on board
3x Nvidia gtx 1050ti's - firmware 388.43 (drivers)
3x gpu risers (https://www.amazon.co.uk/Ptsaying-Powered-Riser-Adapter-Extension/dp/B073F1QHZ5/ref=sr_1_1?ie=UTF8&qid=1512829644&sr=8-1&keywords=gpu+risers)

My issue is code 12 in device manager. I have managed to get 2 cards working at the same time but never 3. They are registering there connected however the third card will always show code 12.
https://ibb.co/kDp2Zb

heres what ive tried so far,
tried older drivers for graphics card
ive tried removing cards individually to determine if the riser's are faulty - which there not and nor are the cards
tries the suggested methods of modifying the bios i.e setting to gen 1 gen 2, None of which seem to make any difference also disabled hd audio
Tried increasing page file.
Tried adjusting registry with HackFlags method.
tried installing ubuntu however i couldnt get this to recognize 1 card let alone 2 or three. (im not a fan of ubuntu) so i gave up with this but i want it to work on windows anyway.
tried following the https://forums.geforce.com/default/topic/470858/code-12/   - however my 3rd card doesn't show on the lists
tried DDU to remove drivers and starting again (45 restarts and counting)


Ive done a few more things but im starting to run out of ideas

one question i do have - does physical RAM effect the amount of resources that can be allocated for a gpu? - bascially is 4gb ddr3 enough to run 3 gpu's? or should this not matter

Im sure its the later but i feel like im missing something really obvious here

George

[ordi87]

I didn't go through all posts BUT I had same issue. I started with wind10, tried all options listed on internet - nothing helped. The best result was that I could run 2 GPU (gtx 1080) on my windows but still with error code 12 on third one. When I added 4th, then the windows was freezing at the login page. I think it is Windows issue and one of the recent patches.

Solution:
Install Ubuntu 16.04 - it took me one hour to configure the system for mining. I know there is no MSI afterburner software but it is quite easy to use nvidia-smi commands instead.

[q43a0ef061ej]

hi, djtappage.

one question i do have - does physical RAM effect the amount of resources that can be allocated for a gpu? - bascially is 4gb ddr3 enough to run 3 gpu's? or should this not matter

Yes.
If TOLUD setting to "Auto" (like ASRock H81 BTC Pro R2.0)
"The amount of resources that can be allocated for GPUs" will Adjusted by physical RAM amount automatically.

So, If the rig have less physical RAM.
We must makeshift with fewer resources.
(like disabling some HDMI audio on video devices.)

A simple way to reduce the problem is to add physical RAM.
But, I have seen the case of driving 3GPUs with 4GB RAM. It seems possible.

The Haggyy's rig with 3GPUs and 4GB physical RAM finally started running.
https://bitcointalk.org/index.php?topic=2307023.0;all

Aside from this.
"HackFlags" increases limit of "the number that Windows can enumerate PCIE devices".
"devices not enumerated" also indicate CODE 12.
Perhaps, I think that initial limit value has changed to less value in FallCreatorsUpdate. Or Update have bugs.

be careful.
The problems of TOLUD and LimitRegister are independent each other.

[Spitshinetommy]

Hi guys, I'm looking for help with this MOBO rev1.0  using GTX970's. I have 3 connected via risers all power is connected to risers and mobo.

The HKEY I need to add, please could you walk me through this to make sure I have it correct. I pretty sure it is though it hasn't worked.

I have followed the advice so far with little success.

Is there a list of Bios settings?

Thanks in advance of any help.

[gregfromo]

I had the same problems yesterday-today with a rig where I wanted to add 2 card to the existing 2 cards.
long story short:
killed the win 10 v1709 and fresh install v1703, deactivated updates, antivirus. now it's like it should be.
imho don't waste time finding workarounds, just use 1703 and deactivate updates.

[Scippylisp]

Hey all,

Thank you for making this thread. It has helped me troubleshoot the same problem. I have 6 GTX 1070s, but only 4 work. Yes, it definitely seems to be the latest Windows update. I updated on Wednesday and have had the problem since that time. I did NOT have a problem before the update.


I should state going in that I'm no tech wizard, but built the rig myself. So apologies if I get the language wrong.

Many of the workarounds here have not worked for me (even though I feel I've cleaned up my system a bit).

Here is one thing I am noticing though, maybe others have the same setup.


BEFORE the update, I am pretty certain that the PCI slots on the mobo were the same as the device properties. In other words, the card plugged into slot 1 would read "PCI Bus 1" in the properties.

NOW, this appears to be screwed up. It appears as if 1 and 2 are swapped, 3 and 4 are swapped, & 5 and 6 are swapped. So the Windows updated created a conflict where it now thinks PCI slot 6 (for example) is actually PCI slot 5 and so on.


In trying to troubleshoot this, I noticed when I went into the device manager and sorted by "resources by connection", I noticed that the larger slot (PCIE 2) was not being resourced by one of the PCI root drivers. As such, I believe this is why both cards plugged into slot 1 and 2 work.

However, I believe that slots 3/4 and slots 5/6 are only able to take one card each because they have been swapped by the Windows update. Both slots are trying to draw off the same PCI root driver/resource. This explains to me why Windows recognizes that the card is plugged into the slot but can't use it.

So based on that, perhaps any workaround would have to involve manually assigning a PCI port to the driver that is not currently using a resource.

Either that or wait for the new Windows update or roll back to 1703.  


What do you think?

[q43a0ef061ej]

Hi, Scippylisp.

About the screw of PCI bus number.
There may be no problem if the numbers are not overlapped each other.
These are automatically numbered, it may be a consecutive number or not be so.

Physical Slot2(PCIEx16) of this MOBO is different from other PCIEx1.
It seems that it is directly connected to the CPU.

You can find it under "Intel (R) Xeon (R) processor E3-1200 v3 / 4th Gen Core processor PCI Express x16 Controller".
Not "Intel (R) 8 Series / C220 Series PCI Express Root Port".

However,
It seems that "the behavior of PCIE assignment to memory" was surely changed in version 1709.
Combining version 1709 with "this MOBO with less memory" seems to make the problem serious.

By the way,
6GPUs on my rig running with windows10 1709 now.

OS: Windows10pro 64bit 1709 (Clean install from USB media. Then edit HackFlags turn on)
MB: ASrock H81 BTC Pro R2.0 (BIOS v1.20, Setting is "load default".)
CPU: Intel Celeron G1840
RAM: DDR3 8GBx2 (16GB)
GPUs
 PCIE1: GTX1060 6GB
 PCIE2: GTX1080
 PCIE3: GTX1070
 PCIE4: GTX1070
 PCIE5: GTX1070
 PCIE6: GTX1070

(All GPUs connected via riser card. and Disabling HD audio devices in device manager.)

When turn off HackFlags and enable audio devices,  Three GPUs indicate code12.

[Hashers_co_uk]

Hi do you (Or someone else) have a screenshot of the HackFlags setting in Regedit?

I couldn't set it to 0x600 but it looked more like 0x0000600 (Can't remember, my pc didn't start up after that). 
And I am quite unsure if I did it correct.  (seems not, otherwise my rig would start up),   

Thanks,

[q43a0ef061ej]

hi, guys.

I couldn't set it to 0x600 but it looked more like 0x0000600 (Can't remember, my pc didn't start up after that).  

Sorry. That's right. I made a mistake in expression.
Since this is a "32bit value", the "numbers of zeros" after "0x" has significance.

Correct screenshot is here.
https://bitcointalk.org/index.php?topic=2307023.msg24696485#msg24696485

If you are doing exactly the same edits and your rig does not run yet.
I want to know the cause. Please tell me about your rig composition.

ty

[elchocador]

Guys!! I got all six working. What did it was actually the fix in https://forums.geforce.com/default/topic/470858/code-12/ that someone suggested to you Yoledo, I suggest you try it again if you havent done what i shortly describe:

More exactly going to the 'memory' tab,  and inactivating hd audio controllers under pci root port #1 or in your specific case the pci-e port that aint working.

No restart no nothing required, exclamation mark just went away.

Good luck!

All the other options didn't work for me.  2 cards were fine the 3rd had a code 12.  The above work around worked perfectly.  I just deleted some HD audio under the pcie list and it worked.

[q43a0ef061ej]

hi Guys,

Today,
I tried to clean installation again on this MOBO. (BIOS 1.20, Using default settings)
The successful procedure is below.

1. Using "Media Creation Tool", prepare the latest USB installation media. (Version 1709)

2. Install the OS without connecting to the network.

3. Please still be offline after installation. Make sure that all of your GPUs are visible in Device Manager. (The NVIDIA driver has not been installed yet.)

4. Disable all HD audio devices. (Optionally, set HackFlags and reboot.)

5. Connect to the network. Install the driver automatically in device manager, or install Nvidia genuine. (Keep all HD audio devices disabled even after driver installation.)

6. If HackFlags does not set and Code12 still indicated, try HackFlags and reboot.

But I do not know if this is effective with AMD's GPU.
Can anyone verify it.

ty

[WickedPigeon]

Thanks for all the great help on this thread! I'm back up. I was doing fine for a couple weeks until I did a Windows update. Then everything went down and I couldn't get but 1 or 2 GPUs to show up. Drove me crazy. Tried all the suggestions on this board. Nothing worked. Until...

Here is what I have:
ASRock H81 Pro R2.0 BTC
Intel Celeron G1840 Haswell Processor. 2.8 GHz. LGA1150. 2MB Cache
Gskill (2X4) 8GB DDR3 1600MHz
Kingston A400 SSD 120 GB
5 x MSI Nvidia GeForce GTX 1070 Ti G1 Gaming 8GB GDDR5
EVGA 1000W G3,  
6x 1x To 16x Extender Riser USB 3.0

No changes to the bios except "on board" video.

Ended up formatting SSD. Unplugged the Internet cable. Installed Windows 10 Home, V1607 (because that's what I have in the original, flash media).  Disabled Windows Updates - Via Control Panel > Administrative Tools, you can access Services. In the Services window, scroll down to Windows Update and turn off the process. Then I uninstalled the Windows Update Assistant. With one riser in the x16 Pci slot (I believe that is slot 1), updated Nvidia graphic driver. Rebooted. Shut down, added next card and rebooted. Once I had all the cards in (I'm only using 5 cards), I re-installed Nvidia driver with "Clean instillation" checked. And it's finally working.

I believe this is a new Windows update problem.

[q43a0ef061ej]

hi WickedPigeon.

Perhaps, FallCreatorsUpdate(1709) triggered a malfunction of GPU driver installation.
If you are going to install 1709 cleanly, please try disabling HD audio before installing the GPU driver.