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

[Flyerstarter]

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

[1714916688]

1714916688

[1714916688]

1714916688

[hagbase]

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?

[Flyerstarter]

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.

[Flyerstarter]

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.

[Bakhtra]

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.

[andydis]

HAVE YOU SET THE PAGE FILE TO >16GB?

[Flyerstarter]

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.

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)

[Bakhtra]

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.

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?

[Flyerstarter]

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.

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.

[andydis]

what OS?

[Flyerstarter]

what OS?

Windows 10 64 bit

[andydis]

PM'd you

[Flyerstarter]

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.

[Flyerstarter]

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

[Flyerstarter]

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 

[smoolae]

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.

[q43a0ef061ej]

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!  

[Flyerstarter]

hi, guys.

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

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

and reboot.

ty

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

All three GPU's running perfectly error free.

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

[q43a0ef061ej]

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.

By the way,

I examined the difference between G1840 and G3260.
They had the same number of PCIE lanes.

So, I guess that the problem of PCIE coming from the difference between these two CPUs can be ignored.

Both G1840 and G3260 belong to Haswell.

Also,
I looked into the details of HackFlags.

Unlike my expectation,
This option works to increase the limit register of "buffer size of enumerating PCI Express bridge devices"  from the initial value.

For example,
If you install an unusual number of video cards (like mining rig) with the default limit register value,
"PCIE device enumeration buffer" overflows due to too many PCIE devices,
Code12 exception seems to occur.

In addition to setting HackFlags,
disabling "some unnecessary PCIE devices" will reduce the occurrence of overflow.

Perhaps, Updating the "PCI Express root port" driver may also help you.
(ASRock H81 Pro BTC R2.0's "PCI Express root port" have more fit driver at WindowsUpdate named "intel(r) 8 series/c220 series pci express root port".)
Update: Sorry. Maybe this does not matter.

[smoolae]

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

You Sir deserve a medal!