Bitcoin Forum

Hi All,

Pretty new to mining but have years of "Techie" experience and this issue has me stumped. I've read through every related forum post on this issue and have been troubleshooting for days but the issue still persists.

The issue is that Windows (or any other OS) will not accept more than 2 GPU's at the same time, any more and I get the following error "This device cannot find enough free resources that it can use. (Code 12), If you want to use this device, you will need to disable one of the other devices on this system."  ???

Specs:
ASRock H81 Pro R2.0 BTC
Intel Celeron G1840 Haswell Processor. 2.8 GHz. LGA1150. 2MB Cache
Corsair 4GB DDR3 1600MHz
SanDisk SSD PLUS 120 GB
3 x Gigabyte Nvidia GeForce GTX 1050 Ti G1 Gaming 4GB GDDR5
EVGA 1000 GQ, 80+ GOLD 1000W PSU
6x 1x To 16x Extender Riser USB 3.0 Power Cable Bitcoin Card Adapter PCI-E

What I have tried so far:
Tried an updated / custom BIOS that added "enable 4g encoding" v1.2
Tried latest BIOS, selected PCI as the primary display and not the onboard, selected GEN1 and GEN2 (neither made a difference).
Complete power off, install first GPU, install drivers - power off, install second GPU, install drivers - and so on
Latest Nvidia drivers and then the second most recent (388.13, 384.76)
Had a spare GTX750TI knocking around and it wouldn't accept that as a third card either.
Tried adding additional power via the two molex ports on the M/B.
Removed CMOS battery and reset via the jumper.
Disabled onboard GPU via device manager

I've tested each GPU individually and all PCI risers and can confirm all are fine and working correctly.

I'd really appreciate any help here.

Thanks,

Flyer

There is no need for custom Bios , P1.20 is fine.
If you use powered risers do not use 4 pin Molex onboard.
You can use the iGPU or not up to you, i'm running 5 and 6 cards + igpu with this board.

Disable Render stand by in mainboard bios.
Disable sound in mainboard bios.

Is your Chipset driver installed?
Remove GPU drivers in safe mode with DDU.
All cards are connected through risers? Or do you plug in one card in PCIe 16x?

Thanks for the swift reply

Neither BIOS (1.20 or 1.30) seem to help
iGPU makes no difference
Render standby and sound are both disabled
Chipset driver up to date and installed
I've fully cleaned with DDU twice now
All three cards through risers on PCI 1,2 and 3, also tied connecting the GPU in PCI2 directly to the PCIe 16x on the board.

I've opened a support case with ASRock as something just doesn't seem right here.

Even though I have disabled the on board GPU I'm still seeing it in device manager, if i disable then the one 1050ti with "no resources" briefly goes into a normal state but then back to Code 12 following a reboot.

At device manager >> choose show hidden device aand delete all of gpu that hidden there. And then restart windows.

HAVE YOU SET THE PAGE FILE TO >16GB?

I did find a hidden adaptor and deleted it, one of the 1050ti's still go back to no resources after a rescan. I cannot seem to get rid of the Intel HD Graphics despite disabling and uninstalling - it always comes back (not that I think that's the cause of the issue though)

When the error appear? When start mining?
Have you already add swap file at least 16 (i use 50 GB swap file though) like andydis  said?

Yep, page file is at 26Gb and a max of 50Gb.
The error is seen when I right click and go properties on the third GPU in device manager that has a warning triangle against it.

what OS?

Windows 10 64 bit

PM'd you

Thanks for the offer but due to the nature of mining I'm not keen on giving remote access to my rig. Happy to provide screenshots/info.

Just had a reply from ASRock Support:

Hello,
 
1. Please try to borrow more RAM to test with.
 
2. Try increasing virtual memory in Windows to at least 16GB.
 
3. The Molex power connectors on the motherboard must be used, even with powered risers. I know you tried this already.
 
4. Please try to test with Windows 10 version 1703.
 
Any change?
 
Kind regards,
ASRock Support

Trying this now

So I've tried everything ASRock suggested but I'm still getting the error. I'll report back but it looks like I'm going to have to try another mobo  >:(

Many people have had problems with this MOBO, including me. Had to RMA my first board and now the new one works perfectly.

hi, guys.

I have same trouble. but this method can remove it in my case.

make new key "HackFlags" as (DWORD 32) type value 0x600 600 as (Hex) in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PnP\Pci\

and reboot.

ty

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

See source information.
https://support.microsoft.com/en-us/help/942959/error-message-when-you-attach-a-pci-express-expansion-chassis-to-a-com

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

update2:
It is obsolete to deal with this problem with HackFlags!

Windows Update on Jan/3/2018[KB4056892] might fix this probrem!

You no longer need HackFlags nor Disable Audio Devices!  ;D

Well I'll be dammed! You sir are a genius!  ;D ;D ;D

All three GPU's running perfectly error free.

Just for my nerd interest what is the HackFlags doing here? ???

hi, Flyerstarter.

It's hidden option to avoid InterruptReQuest(IRQ) confliction, it made by microsoft.

However, I don't know how it behaves.
..but maybe, this option might make assign IRQ in Windows instead of BIOS.

ty

update:
sorry, I misunderstood about the behavior of this option.

You Sir deserve a medal!

I am in the EXACTLY same boat as you man, I am also stumped. I have 3 GTX 1060's in my mining rig but the OS only recognizes 2 and hates the 3rd no matter which order they're in. I am also using the same ASRock motherboard and similar other hardware to you.

I am going to try that fix that q43a0ef061ej has pointed out and I will also report back ASAP.

Right guys I've just tried editing the registry however I seem to be getting the same problem, just in case I am doing something completely wrong is someone able to kindly take a quick look at the screen shot and check that the value is correct. Etc.

After creating the registry key, I've rebooted and gone back into device manager, here are the results:

http://i66.tinypic.com/k1v0qt.png

Thanks

hi, haggyy


Your editing is okay.

Also, you need to try disabling "some IRQ consuming devices".
(e.g. Disable iGPU in BIOS settings, right click and disable on HDMI audio on video card in device manager, etc)

update:
Sorry. It seems to be a problem of memory mapping, not IRQ. but, disabling "some unnecessary PCIE devices" is valid.

ty

I have the same problem but no fix yet.
Setup: asrock h81 pro btc mobo, 3 x gtx 1070, 4gb ram, cpu intel G1820

I tried hackflags, gen1, gen2 everything with a fresh w10 (1709) installation. But 1 of my 3 cards still have code 12.

Any tips left i can try? Im out of options

Maybe you change the PCIE to generation 1?

Can you provide complete system hardware configs?

hi, simpie10.

This thread might help you.
https://bitcointalk.org/index.php?topic=2307023.0;all

When the rig has less main memory,
In order to access too many PCIE devices, allocation to the IO memory map may not be enough.

You can try disabling "some unnecessary PCIE devices" (like HDMI audio on a video card) in device manager.

ty

I have the same exact set up and same exact issue . Can you please tell me what the hackflags is ? I tried searching it and found nothing

hi, Yoledo

This is a source information about "HackFlags".
https://support.microsoft.com/en-us/help/942959/error-message-when-you-attach-a-pci-express-expansion-chassis-to-a-com

Besides,
You also should care TOLUD(Top Of Lower Usable Dram) problem, when your rig has less main memories.
This problem occur due to insufficient memory address space for accessing PCIE devices.

You can try reduce TOLUD value in BIOS menus ("Auto" does not help you), If there is such item. or
You can try disabling "some unnecessary PCIE devices (like HDMI audio on video cards)" in device manager.

And also if your MOBO has Buggy PCIE 3.0 (Gen3),
This method may help you.
check it.
https://www.nicehash.com/news/128

Thanks for.the reply! I'll see if there's an option for tolud values in my bios as I can't recall there being an option for that .I tried the registry edit last night and set it to 600 and now it won't boot into windows at all, just freezes. I'm gonna install a fresh copy of windows and start over

hi, Yoledo.

oh, Editing the registry at your own risk..
..Did you enter it with DEC?
Plz care, The flag value must be on HEX, not DEC.

By the way,
if your MOBO is ASRock H81 BTC Pro R2.0,
Unfortunately, It have no TOLUD option. (TOLUD is fixed to "Auto")
but, You can try secondly method. (Disabling some unnecessary PCIE devices)

I wish you good luck.

I contacted Asrock support.

They say for some HackFlags solution works on Windows Installations (1709).
But it didnt work for me.

The solution for me was windows 10 (1703), the version before creators update.
My 4 cards (Gtx 1070s) are working with this Windows version, when i update to 1709 only 3 cards are working. So i dont update for now.

The support said its a problem which occur on Windows 10 (1709) versions. So microsoft needs to fix this in a coming update.

Hope it helps, cioa.

windows 1703 helped me get 3 out of 4 cards up now I'm just getting code 12 not enough resources
https://imgur.com/a/I90d0

Have you set your virtual memory?

Read this source at step 6. http://www.cryptobadger.com/2017/04/build-ethereum-mining-rig-windows/
I have set that before i installed nvidia drivers.

But  i also installed my 1703 fresh without internet connection. Have you tried that out? Maybe windows updates still set things up.

https://imgur.com/a/cmmus

https://i.imgur.com/Ft4vaFT.jpg

still suckin

Strange, reinstall windows again maybe? without internet connection u could try.

I'm on my like tenth install lol man this is frustrating. could it be that I went too cheap with the cpu?

I know. Its really frustrating. Try contacting support (asrock)?. U have a different card then mine, maybe another solution will be suggested?

they sent me a copy of the 1.3beta bio which enabled 4g rendering but it did squat on my code 12 issue

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

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

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?

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!

Hi, guys.

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

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

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.

hi, djtappage.


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.

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.

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.

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.   :P


What do you think?

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.

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,

hi, guys.

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

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.

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

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.

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.

You sir are my hero!

Well I did a little bit digging for this issue and I can confirm 100% that it's cause by Windows Update 1709, and this helped my issue.
I had 6x 1060 GB cards, and I had two not working.

After I applied that one started to work, and just went to Device Manager disabled HD Audio for the second graphic and it magically started to work! :)

I would like to share my experience with that problem! I had the same problem, the 3rd gpu was giving me the same error. I did pretty much everything i found online, increase the virtual memory, updated the bios, change the registry, updated the windows to 1079, switch all the hardware, and im not exactly sure what was the problem but the last thing i did is to disable the audio attached to each card and now everything is working properly. 3 more cards to go will see how will go. Thanks everybody

Followed your steps to the T with th exception of installing 1703 and all 4 gpus were detected.

I also did not install the intel graphics driver and have left the pci-e 16x slot vacant. I have a feeling i am going to have troubles when my fifth and sixth card arrives. Will probably need to disable the igpu but this would be troublesome as the cards are inside a server case. But we will cross that bridge when i get ther 😬

Thanks so much for taking the time to write it all down!

hi, geck.

Sadly, iGPU will be the obstacle.

If iGPU is enabled on my rig,
Code 12 will be indicated even if the registry is turned on and all audio devices are disabled.

hi, Guys!

It is Great News!
Windows Update on Jan/3/2018[KB4056892] might fix this probrem!

You no longer need HackFlags nor Disable Audio Devices! ;D

Bought another gpu, so rearranged the existing gpus to fit, and changed the slots. Now only 3 cards are detectable. 4th one if detected throws up a code 43 error  >:(

hackflags, uninstalling using ddu, swapping cards, resetting bios, adjust bios settings to no avail. Going to try reinstalling windows now

I hope the asus z270-a board for my 2nd rig isn't going to be such a pita

hi, geck.

The default BIOS setting will not cause problems.

After clean installation using Fall Creators Update media,
Please patch up to [KB4056892]. That is all you need today.

Finally got it working.

You are right, default bios is all that is needed.
I cleared the cmos, reinstalled windows and started plugging in my cards (without installing nvidia drivers yet) one at a time
Found one faulty riser card instantly (riser got too hot to touch, mosfet failure probably).
Replaced another riser that was causing a card to be working intermittently.

5 gpus working now; 2x1080ti, 2x1070ti and 1x1070. Going to call it a day with this rig until volta comes along

Can anyone confirm this aswel?

Hey guys, I can confirm it worked for me too. I actually used the above tips (including the registry edit) to run 5 GPU rig. Yesterday, after the update, my 5th GPU stopped working. After removing the edited registry, it works flawlessly, now even with 6 cards.

Thank you very much for the HACKFLAGS. got my rig up and running again and I fucking disabled windows update PERMANENTLY.

PIECE OF SHIT AUTO UPDATING WINDOWS 10

Try Windows Update on Jan/3/2018[KB4056892], they have fixed it in newest update.

Thanks to this thread I have successfully used 4 GPU (Gigabyte 1070) for mining on ASRock H81 Pro rev2. It took maybe 8h mostly installing OS and update (so slow). If you are crazy enough like me and want to try Linux and thinking it's going to be easier let me stop you right now. I failed miserably trying Linux but your mileage may vary.

code 12 is your best friend because it means your hardware is most likely installed correctly (all plugged correctly) and working. Code 43/45 are your enemies: double check cables and connections.

Summary solution:

1) Install Windows 10 1709. Install all latest windows update. Disable all audio device on the video card by sorting the view by connection in device manager. At this point you should already see all your video cards.
2) If you have any GPU that has error code 12 do HackFlags (400) fix. Reboot.
3) If GPU has error code 43 make sure all connectors are attached tightly. Ex: power issue (connector not properly inserted for example), I suspected heat but looking at afterburner app it's not the case.
4) If GPU has error code 45 make sure riser cable/adapter are working fine. Ex: riser issue, (code 43 or 35 are mostly hardware related)
5) If you still see error code 12 sort view by connection and disable some un-used device like a USB device (make sure it's not being used; I used a USB hub and disabled another un-used one).
5b) It doesn't hurt to run search "troubleshoot" and select "Hardware and Devices", I would not enable auto driver update feature when asked, and select device not in this list option and proceed, it might fix something. In my case it was able to find my last GPU when it was hidden (but second time this happened it didn't help).
6) Reboot and see if all GPU are detected correctly. If so start mining and see if you get VIDEO_TDR_FAILURE (BSOD).
6b) If TDR BSOD, try TdrDelay registry workaround first (reboot). MSDN: https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys (https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys). Reddit mentioned about this: https://www.reddit.com/r/nvidia/comments/79nncg/driver_38813_faqdiscussion_thread/ (https://www.reddit.com/r/nvidia/comments/79nncg/driver_38813_faqdiscussion_thread/). You may download a tool (in that link) to change the TDR registry. I would just skip to next step first.
6c) If #6b failed try mining with one algorithm only (forget dual mining). This is what made my rig stable. I was BSOD very quickly (few minutes into mining). This method worked for 4 GPU. When I added a 5th one TDR issue re-surfaced again. I am still debugging this issue. [update] I used that that tool (in previous link) to disable TDR. Let's hope it can last till tomorrow. Ideally it's better to increase delay because at least in worst case machine will reboot and you can auto start your miner [update, overnight no issue but this morning it froze without any crash; had to reset]. If you disable TDR and it fails it will freeze your machine (this is good for me right now).

If in doubt use Display Driver Uninstaller (DDU, http://www.guru3d.com/files-details/display-driver-uninstaller-download.html (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html)) in safe mode (run msconfig and select safe mode, it will ask to reboot, once in safe mode run DDU). You only need to do this if you have already installed latest driver. I had everything detected by OS and working with driver provided by Windows 10 (so until step #6 I didn't install any driver). It's possible that you don't even need to install latest display driver depending on the situation. Once I got BSOD I ran DDU and installed latest driver but the problem was elsewhere for me.

Next rig I will use better riser: https://www.amazon.com/Ubit-Express-Graphics-Extension-Ethereum/dp/B076KLJR2Y/ref=sr_1_1?s=home-garden&ie=UTF8&qid=1515290286&sr=8-1&keywords=pcie+riser+ubit (https://www.amazon.com/Ubit-Express-Graphics-Extension-Ethereum/dp/B076KLJR2Y/ref=sr_1_1?s=home-garden&ie=UTF8&qid=1515290286&sr=8-1&keywords=pcie+riser+ubit) with LED hint to help identify hardware issue.

[Update]
KERNEL_SECURITY_CHECK_FAILURE - FAIL_FAST_LIST_ENTRY_CORRUPT BSOD (nvlddmkm involved) after being stable for less than 3h.
I set up a batch script that launches the miner and put it in the startup folder and disabled password login. So after startup it will start miner automatically. Hopefully it can survive the night (update: crashed once in 12h).

[Update2]
Added a 5th GPU and TDR issue came in full force. See #6 for info. Essentially I disabled TDR with a tool (mentioned in link reddit link above), but you may try TdrDelay and other settings and have auto start on reboot to avoid down time. Only down side to this approach is that if you BSOD very often it's best to fix the issue in a more permanent way to avoid hardware damage. I am in the process of trying out different drivers (390 is out) to find the most stable one.

[update3: trying drivers]
Device Installation Settings: disable auto device update before doing DDU and installing older driver. Disable device driver update (somehow windows still updated nvidia driver with this setting disabled only) and disable windows update in group policy.
Completely disable windows update - https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10 (https://www.windowscentral.com/how-stop-updates-installing-automatically-windows-10)
Disable device update itself - https://www.itechtics.com/disable-automatic-driver-updates-windows/ (https://www.itechtics.com/disable-automatic-driver-updates-windows/)
Disable device update search - https://technet.microsoft.com/en-us/library/cc730606%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396 (https://technet.microsoft.com/en-us/library/cc730606%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396)

I am using nvidia driver 385.69 now no BSOD (it's possible other version can also work). Make sure to disable update or it will get auto updated to newer driver (it will eventually happen if you don't disable it).

Another issue I got which is puzzling is my 5th GPU stopped working (afterburner shows 0 for all sensors) after sometime even when not mining. What I ended up doing is set power limit to 80%(my other settings are temp limit 80%, core 100, memory 350). All temperatures were below 70c (67-68c). If it can run for 1 month without issues I can call it stable but for now I am happy.

Don't give up!

Confirmed - the HackFlags [600] worked for me. I initially tried HackFlags [400] but that didn't work.

Rig Specs:

• OS: Win 10 1709 with the latest update (update alone didn't work)
• Mobo: Gigabyte Z270p-D3
• GPU: 6x 1080 ti

Thanks all for the hours of troubleshooting and sharing your findings.

I did find the old version over here:  http://windowsiso.net/windows-10-iso/windows-10-creators-update-1703-download-build-15063/windows-10-creators-update-1703-iso-download-standard/ (http://windowsiso.net/windows-10-iso/windows-10-creators-update-1703-download-build-15063/windows-10-creators-update-1703-iso-download-standard/)  So if you needed, i did not tested them yet. So i dont know if those files are clean use at your own risk, just did find this source ..

After lots of troubleshoot now all is also working good.  Microsoft Windows 10 1703  did resolve all problems !!!  :-*

Only message this board give at start:     please install the psu's 4-pin power cables to the 4-pin power connector on your motherboard

While all cables are connected, and the rise cards and GPU has power directely from my 1200 watts unit. Is this something to worry about ?
Are is the board only telling you , that you have 3 cards or more  ???

hi, guys.

If you try install 1709 and patched up to [KB 4056892] and the rig successfully recognized the GPUs well without HackFlags,

I no longer recommend you to use 1703.

Hackflag didnt work for me originally with default bios. Had to set to Gen2, install latest CU for Windows, remove hackflags, and then reinstall drivers.

Just registered to come and say thanks for this thread.  It helped me get 3x1080ti (1x16channel, 2xRisers) going on my H81 Pro, even though it was not plug and play.

As I was just happy to get them going, this is not a full "debug", but some things that seemed to help, or didnt at least harm the process

• AS Rock H81 Rev2.0 with 1.20 BIOS.  I turned off everything I didnt need to be using, and maximised the compatibility/stability settings
• 4gb DDR3 RAM, Pentium G3260. Increased the pagefile to 16gb, as NiceHash was getting out of memory errors even after first two card up and running.
• Window 10 Pro. Build 1609.  I did the hackflag registry fix "just in case" but actually the second card was found when I removed the hackflag key again.
• NVIDIA drivers 388.43.  I just kept doing a clean install of just the drivers once another card on another PCie channel was found.
• Getting a single card going in any of the channels was not a problem. I used this process to make sure I had two working risers to eliminate the "bad riser" risk, and then left the first card in the mobo slot.
• I finally got a second card working on one of the risers.  Not really sure how I managed that, but lots of rebooting, bios flashing etc.
• But the the third card would not work and a third slot, until I took out the second card, got the third card working, then added the second card back in.

So in summary, if I had to start from zero I would try this to make it work with less trial and error, basically adding cards one at a time, but only adding card N to a slot that was already working with N-1 cards:

• Get one card/riser going in one slot.  Install the drivers.
• Use the same working card/riser combo in a second slot to "activate" that slot. Install the drivers
• Hopefully get two cards running on the two "active" slots.
• Move one of the cards to a third slot to "activate" it. Install the drivers
• Add the third card, using all three "active" slots. Etc...

Hope this helps someone else, and for my 4th card once the damned riser arrives...

Danny

This is true! I installed a fresh w10 1709. 1 Card had code 12. Then i update, en finally get the [KB 4056892] patch. After reboot my 4 cards are working fine! No tweaks in registry or else. Seems Microsoft patched it for us :)

Hi Friends
I need help to build my new 6 or more gpu Mining Rig on Asrock h81 R2.0 with windows 10

Hardwear I have:
Asrock h81 R2.0 Mobo needs 4tg generation cpu celeron, Pentium, i3,i5,i7
Rx 570 4 gb
Rx 470 8 GB 2 cards
Rx 470 4 gb Mining edition 3 cards
Rx 480 8 GB ( but it doesn't have bios switch nor the led light )
8 GB ram DDR3 x 2
Psu cooler master 850w and corseior 550 w
SSD 120 GB
Risers
1x to 4 x pcie expander card


I want to know
Which cpu will be better for my rig ?
Best Psu for 6 Rx 470 cards ?
Type of best power Riser molex or sata connectors ? I have sata and 6 pin connector Risers
How to setup  1x to 4x expander card? On 1x slot or on 16 x slot ? Any more I have to modify motherboard bios ?can I mount more than 6 gpu on asrock h81 r2.0 using 1x to 4x pcie expander card ?
Do I will face any problem using Pentium for 6 or more GPUs ?

Also need more advice to setup motherboard bios and any more settings related to asrock h 81 r2.0 motherboard

Use the cheapest 4th gen CPU you can find (Socket 1150 is all that matters).
Don't know about best PSU, but 1200+w 80 Plus Gold should be ok (modded server PSUs are also nice things, can be a bit loud tho).
You really cannot get "the best powered risers", always order a couple more than you really need. Please stay away from SATA risers, things can get hot. MOLEX is better and 6-pin PCIE is the best.
From BIOS change PCI Express to GEN 1 and "Restart PC after power loss".
Have seen a couple of photos people running 7 GPUs from this board, never have tried that myself.
Pentium is fine.

Hi Thanks for reply
Dose it matters celeron Pentium or i3 for 6 gpu? Socket 1150
What is the role of cpu while using 1 or 6 or more than 6 gpu
If I go for Pentium 1150 which one will be good ?

If you do not mine using cpu then any cpu would be good enough so choose the one that consumes less power.

Ok thanks

Hi.

You sir solved a lot of headaches I had with that asrock code 12 issue. Me and my customers thank you very much.  

Give me your btc adress, I'll send you 0.0025 btc as a tip.

I don't care what asrock support says, the molex power connectors aren't to be used UNLESS you are using Unpowered risers, not powered risers.
I have both the older version of the h81 and the newer r2.0 neither of which do I power the molex on the motherboards and they work as intended

it does say you can ignore the message too, and yeah it only pops up after connecting certain amount of gpus. once ya tell it to ignore the message it doesn't come back

Hello Friends

What is Hashflag how to use it ?

What is ati pixel pacher? Which is best for windows 10 with 6 gpu Rx 470 n asrock h81 R2.0 Mobo

Hi everyone, it worked for me HackFlags. My mining is running 5 gpu perfectly. Here's my setup:
Asrock H81 Pro Btc R2.0
Celeron G1840
5 Gpu Gtx 1060 3gb
4gb ddr3
Windows 7 Ultimate SP1 64bit

 I did not need to update the bios, just install the drivers with nvidia 382.53. Important, connected with the video onboard, and disabled on the audio bios onboard and disabled in the device manager all the audios of the gpu.

 ;D

I have only one of these boards - and i't been up and running for 4 months. I am running Windows 7 and 6 1070ti on it. I'm using powered, Mintcell risers and found it doesn't matter if you plug the Molex cable into the MB or not. Works fine either way. I'm not sure why you think you shouldn't use it. I actually have it plugged in right now. I don't think it matters - no harm with or without. But I am interested to hear why it should NOT be plugged in or are you saying it doesn't matter if it is or isn't?

Thanks

"Hashflag"? - That is the use of a small graphic and a Twitter hash tag together. Personally, not a fan of the use of them.
But...
"Hackflag" is describe on this thread (just page back one page) - it's used to change / modify Window's registry when you run out of Peripheral Component Interconnect (PCI) bus numbers. Just be careful when you mess around in the registry. Read up on it before changing anything.

Good luck,

so the solution, is update the latest windows?

Yes, Windows 10 , version 1709, Jan 2018 Cumulative Update.

I had nothing but problems with 1709 on the H81. Had to reinstall 1703 to overcome code 12 DMA conflicts. Maybe I'll take a system snapshot and try updating again - don't like running all this unsigned code on an unpatched OS.

After days of debug i found the solution with this motherboard.
Drop Windows 10 with this board and install Windows 7. All your GPU will be recognised in no time.

Forget about windows 10. Not to mention i have better performance with windows 7.

yeah, thanks man, already solved several days ago

A noticable hash rate difference in all your GPUs? What percentage increase did you see with w7?

Maybe the issue was with my system but with 6GPU i was running neoscrypt at around 7200 on windows 10 and 7800 on windows 7

Thanks. I'm getting about 8000 on win10 with 6x1070ti, but had to disable some CPU-intensive stuff to get there.

What is your power level ?

100% - power is cheap over here. You at 65%?

Yes... Wish i had cheap power (0.15 here) but my real limit is ventilation.
My cellar is getting too hot when i put more than 75%. I already have a massive 1000CFM fan for extraction but i'm waiting for a fan controller. It's too damn loud at max speed

I'm really, really learning to hate this board.

I have one H81 of the 5 rigs I have. all have 5 or 6 GPU's per Rig. AND this one, the H81, has given me nothing but problems. The miner crashes on this board, it freezes, and for what ever reason, this board hates me. Maybe it's Windows, maybe it's me, maybe it's the board.

I started with this rig 6 months ago, and rebuilt it so,so many times. First Win 10, but back then - Win 10 had issues, switched to Win 7. That worked for a while but recently I was having problems with ccminer freezing - so... I thought maybe it's time to go back to Win 10.

UGH... now I cant get it to boot when I add the third GPU. Every time I add the third GPU it gets stuck in Windows startup.

Any thoughts?

Finally fix it.

I followed what Asrock tech support said to do in a review on Newegg:

Dear Valued ASRock Customer,

We sincerely apologize for any inconvenience this may have caused you.
Please try following to trouble shoot the board.
Unplug the power, clear the CMOS.
Load the BIOS setting default.
Test with 1 x GPU and known good raiser card on each PCIE slot one at the time to verify all slots are working individually.
Same to raiser cards and GPU to test individually.
Populate the cards if all slots, raiser cards and GPUs are working individually.
Check the PSU is enough power for whole unit.
If you have any technical support inquiry, please contact us at http://www.ASRock.com/Support/tsd.asp
We will assist you shortly.

Thank you

ASRock Support
Tech Support Email: http://www.ASRock.com/Support/tsd.asp

After each raiser was connected, I had to allow for 3-5 minutes for Windows to get through the log on screen, but after that it worked. That was a horrible couple of days.

anyone having issues with this board on linux (simplemining). i bought a lot of these boards (only wanted 1 for testing but it wasn't my choice) and it seems like it'll work just fine (using bios 1.30b) at first but as i start adding gpus eventually the network adapter will stop responding and i get this error:
a start job is running for raise network interfaces.. and it never finds it. can't see the rigs on my local network either. i'm really not sure what could be causing this :/